Reporting and leaveswithout manual nudging.

A member submits a report or files an absence, a leader reviews it, and automation sends reminders about requests that are stuck.

What this module coversand how reports differ from leave.

A report is about work done and points; leave is about an agreed absence. Both are visible in the profile and in the member table.
A report with a decisionA leader accepts or rejects the report and can award points. The decision lands in the log and in the author’s notifications.
Leave with datesA request with a reason and start and end dates. Active leave shows in the profile, so the person isn’t considered missing.
Reminders on their ownA rule reminds you when a report waits for a decision or leave is about to end — the member, the leadership or a channel.

When reportsstop getting lost in DMs.

A report sent as a message lives until the first chat cleanup. In the panel it has a decision, an author and a deadline.
  1. Reports pile up undecided

    An automation reminds that a report is still unreviewed — the member, the leadership or a channel.

  2. Someone is away but warned

    A filed inactivity is visible in the profile and in the roster table, so nobody goes looking for a person who is not missing.

  3. Contribution needs measuring

    An accepted report earns points, and the decision and its author stay in the log — the monthly total is not assembled by hand.

Common questionsabout reporting.

How is a report different from inactivity?

A report is about work done: it is reviewed and can earn points. Inactivity is an agreed absence with a start and end date.

Who sees the decision on a report?

The author gets a notification in the bell, and the decision stays in the action log.

How do I chase stalled requests?

With a rule in Automations: the check runs every 10 minutes and fires once per record, so there are no duplicates.

Can inactivity be ended early?

Yes, early completion is done in the Inactivity section — the same place where requests arrive for review.