Work-Time Governance

Flowcharts

Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.

flowchart TD
  Cat[Catalog default off] --> App[Application Config]
  App --> Proj{Project override?}
  Proj -->|No| Role
  Proj -->|Yes| Role[Role gate AND]
  Role --> Dep[Dependencies AND]
  Dep --> Eff[Effective enabled]
            

flowchart TD
  Day[Work day] --> Leave{Approved leave?}
  Leave -->|Yes| Out[Leave evidence]
  Leave -->|No| Swipe{Swipe ingest on?}
  Swipe -->|Hit| Out2[Swipe evidence]
  Swipe -->|Miss| Wfh{Timesheet WFH on?}
  Wfh -->|Hours| Out3[WFH from timesheet]
  Wfh -->|No| Reg{Regularization?}
  Reg -->|Yes| Out4[Override]
  Reg -->|No| Empty[No composed source]
            

Overview

Work-Time Governance is not a second timesheet product. It is a switchboard: about twenty catalog features grouped into approval, timesheet, planning, attendance, integration, and admin families. Turning a feature on does not invent a new source table. Hours still live on timesheet activity, projects still live on Purchase Order → Project → Task → Task Activity, and attendance marks still live on the attendance matrix.

The Feature Flags panel shows each feature’s inherited value, optional project override, role gate, and whether a missing dependency is blocking it. Effective state is Enabled, Blocked (selected on but role or dependency failed), or Off.

How to configure

Catalog families

Catalog keys are stable ids. Defaults in code are off; organisation seeds may turn selected features on for a tenant.

Deadline preview, late reason, reminders, and lock

• Deadline preview — when timesheet.reminders or timesheet.late-workflow is on (and approval.chain is effective), the timesheet page calls GET …/timesheets/deadline-preview for the selected week. The UI follows that preview; it does not guess Friday 18:00 locally. If both features are off, preview is DISABLED and not late.
• Late reason — when timesheet.late-workflow is on and the preview reports reasonRequired, Submit shows a late-reason field (Other needs detail). Exactly seven elapsed days follows the moderately late band (TIMESHEET-LATE-LTE7); later follows TIMESHEET-LATE-GT7. Changing week or team clears leftover submit governance so an on-time week does not keep a prior late reason.
• Validation — timesheet.validation can WARN (submit allowed with hints) or BLOCK.
• Reminders — catalog timesheet.reminders supplies cut-off day and offsets (default Friday 18:00 UTC, 3 / 1 / 0). Emails still need the master flag timesheetAdditional.timesheetSubmissionReminderEnabled and the reminder job. Master off blocks emails even if the catalog reminder is on.
• Period lock — with timesheet.period-lock on, lockAfterDays greater than 0 (tenant seed often 7), and job TIMESHEET_PERIOD_LOCK, approved weeks lock. Reopen can require a reason. The older month lock disableLastMonthAfterXDays still applies separately.
• Approval units — weekly units can feed the chain engine. If no TIMESHEET chain policy is published, approvalChainFallbackLegacy=true keeps the existing manager approval path.

Approval chain and inbox

When approval.chain is effective and a domain policy is published, instances appear with step metadata. My Approvals remains the action inbox; it does not store a second copy of the timesheet. Escalation and bulk actions require the chain feature plus their own flags (bulk is role-gated).

Delegation still uses the existing approval-authority and delegation services. Governance does not replace leave or attendance approval.

Project import and timesheet export

Enable integration.project-import and integration.timesheet-export separately. Both are role-gated. Import creates or updates projects from a mapped payload; export emits timesheet rows for a scoped period. Least-privilege scopes apply. There is no bundled vendor project-tracking adapter, delivery receipt, or dead-letter queue until those are configured as connectors.

Estimates and FTE

Grade, skill, and resource dimensions resolve from Application Config lists. Resource-level estimates stay optional unless planning.fte is effective. Variance reporting reads Task Activity hours — it is not a separate hours store.

Current limits

Permissions