Bayou & Co. runs their client intake checklist every time a new client signs. Mei Lin, their compliance lead, needs to know whether the team is actually doing it — not just that the process exists, but that it's being run at the expected cadence. Adherence reporting gives her that number at a glance.
Before you start
- The process must have status Active. Archived and draft processes do not appear in adherence reports.
- Setting adherence targets requires admin-level access (
process.adherence.managepermission). - Adherence is calculated from completed runs only. Abandoned and in-progress runs do not count toward the completion total.
Step 1: Configure the adherence target
Open the process in Process → Library and click the Adherence tab on the process detail page.
If no target has been set, the tab shows "No adherence target configured" with a Set expected runs per period link.
Click the gear icon (or the link) to open the configuration form. Set two values:
- Expected runs per period — an integer. How many completed runs should happen in each period. Bayou & Co. sets this to
1for their intake checklist (one run per client, but they track by month, so they enter23for their typical monthly volume). - Period — choose Weekly, Monthly, or Quarterly.
Click Save. The adherence card updates to show the current period's completion rate.
Step 2: Read the adherence card
The Adherence tab on the process detail page shows:
- Adherence percentage for the current period (completed runs ÷ expected runs × 100, rounded to the nearest whole percent).
- Run counts — "3 of 4 runs · Monthly" summarizes actual vs. expected at a glance.
- Progress bar — color-coded: green (90%+), yellow (60–89%), red (below 60%).
- Sparkline — a small bar chart showing adherence across the previous periods. Bars use the same color thresholds.
If no expected target is set, the percent and progress bar are not shown — only the raw completed run count for the period.
Step 3: Review the workspace-wide adherence report
Process → Reports → Adherence shows every active process with an adherence target in a single sortable table.
| Column | Description |
|---|---|
| Process | Process name, links to the detail page. |
| Period | Weekly, Monthly, or Quarterly. |
| Expected | Expected runs per period. |
| Completed | Completed runs in the current period. |
| Adherence | Percentage, color-coded (green / yellow / red). |
Click any column header to sort. Processes without an adherence target set are excluded from this table. Northwoods Outfitters sorts by Adherence ascending to surface their least-followed procedures first.
Understanding the period boundaries
Periods use UTC boundaries:
- Weekly — Monday 00:00 UTC through the following Monday 00:00 UTC.
- Monthly — first day of the calendar month through the first day of the next month.
- Quarterly — Q1 (Jan–Mar), Q2 (Apr–Jun), Q3 (Jul–Sep), Q4 (Oct–Dec), using UTC month boundaries.
The current period's count resets automatically when the period rolls over. Historical periods are shown in the sparkline (last 8 periods for monthly, last 12 for weekly, last 4 for quarterly).
Adherence thresholds
| Range | Indicator |
|---|---|
| 90% and above | Green |
| 60%–89% | Yellow |
| Below 60% | Red |
These thresholds are fixed and apply consistently across the Adherence tab, the sparkline, and the workspace-wide report.
Clearing an adherence target
To remove the target for a process, open the configuration form (gear icon on the Adherence tab), clear the Expected runs per period field and set Period to None, then click Save. The process will no longer appear in the workspace-wide adherence report.
Tips
- Adherence is a trailing metric — it reflects what happened in the current period so far, not a projection. A low score mid-period may recover by period end.
- Setting the expected count to match your actual capacity is more useful than aspirational targets. Bayou & Co. found that inflated targets caused the team to tune out the red indicators.
- The schedule and adherence features complement each other: use scheduling to automate runs, and adherence to confirm they're completing successfully.
What comes next
If runs are completing but steps are being skipped or overridden, review the run detail pages via Process → Runs. Admin-override completions are noted in the audit log under Settings → Audit log.