Monitor timesheet compliance

Timesheet compliance answers one question every week: who has logged the hours they were expected to log? Once enforcement is enabled, a compliance dashboard tracks each person’s status and puts a price tag on the gap, and a background worker sends the reminders so you do not have to.

Turn on compliance enforcement

1. Open Organization Settings, go to the Configuration tab, then the Timesheets section.

2. Find the Compliance enforcement panel and check the Prerequisites bar. Enforcement requires at least one active rate card, because the cost-at-risk figure is priced from rate cards. If none exist, the save is rejected with a prompt to set one up first.

3. Choose where expected hours come from: Per-user capacity (each person’s weekly availability from the Capacity Planner) or Fixed (one number for everyone).

4. Set the Compliance threshold, the percentage of expected hours someone must log to count as compliant. The default is 95%.

5. Set the Submission deadline: a day of week, an hour, and a timezone (the default is Friday at 5:00 pm). Everyone sees the same wall-clock deadline.

6. Pick your Reminders, then flip the panel’s toggle on and select Save changes.

Reminders and digests

Two automated reminders are available, both on by default:

• Per-user nudge: sent the hour before the deadline to everyone who is not yet compliant, with their logged-versus-expected count.
• Admin digest: a weekly summary sent Monday at 9 am (org local time) to Owners and Admins, listing non-compliant members and the total cost at risk.

Roles listed under Exempt from compliance (Guests by default) are left out of both the stats and the nudges.

Read the compliance dashboard

The dashboard lives on the Timesheet page, under the Approvals tab, in the Compliance section. It is visible to whoever can approve timesheets. For each week you get:

• Summary cards: Compliance rate, Hours expected, Hours logged, and Cost at risk.
• A per-person table with a status badge per row: Compliant (at or above the threshold), Partial (logged something, but below it), Missing (logged nothing), or Exempt.
• Filter chips per status, a week navigator, and an All hours / Billable only view toggle.
• A per-row link to view that person’s compliance event history in the audit log.

Cost at risk multiplies each person’s missing hours by their rate-card rate, so the gap reads in currency, not just hours. If a person has no applicable rate card, the figure is flagged as using a fallback rate.

Tip

If expected hours should differ by team, role, or person, layer expected hours overrides on top of the baseline instead of switching everyone to Fixed.

FAQs

Who can change these settings? By default Owners and Admins. The permission is configurable in the permissions matrix, so an org can widen or tighten it.

Does enabling compliance block anyone from working? Not at this level. Pro-tier enforcement is visibility and reminders only. Blocking modes are an Enterprise feature, covered in Enforce timesheets with a hard lock.

Why does the dashboard show someone as Compliant with zero expected hours? An expected value of zero means no requirement for that week, so the person cannot be out of compliance.