Track compliance per project

Pro plan Project Manager or org Admin

The org-wide compliance dashboard tells you who filed their hours. The project-scoped view answers the project lead’s sharper question: of the hours my team logged this week, how much actually landed on my project?

Open the project compliance view

Open the project and select the Compliance tab (it sits in the Finance group of tabs).
Use the week navigator to move between weeks.

The view shows summary cards for Compliance rate, Hours expected, Hours logged total, and Hours on this project, plus a per-member table. Each row carries the member’s status badge, their hours on this project, their total hours for the week, and an allocation bar showing what share of their week went to this project.

Access mirrors the budget view: project Owners and Managers see it, as do org admins with the timesheet enforcement permission. Regular project members do not.

The total-hours rule

By default, compliance here uses the same expectation as the org-wide view: a member who hit their weekly total counts as Compliant on this project even if only a small slice of their week was logged here. The allocation bar is what surfaces that nuance; a green badge with a 15% allocation tells you “they did their week, just mostly elsewhere.”

This is deliberate. Without it, every member working across two projects would show as non-compliant on both.

Scale expectations with allocation

If you want the project view to judge members against this project specifically, set an allocation on the project’s Members tab. Give a member an allocation percentage (0 to 100) and two things change for them, in this view only:

Their expected hours scale by the allocation. Someone expected 40 hours a week at 50% allocation is expected to log 20 hours here.
Compliance compares their hours on this project, not their weekly total.

Members without an allocation keep the total-hours behavior, so you can adopt allocations gradually, one member at a time.

Best practices

Use total-hours by default; only set allocation for projects with clear hourly commitments. “I want 50% of Alex this sprint” is allocation. “Alex works here when needed” is not. Setting allocation indiscriminately turns the project view into noise.
Adopt allocations one member at a time. The mixed mode (some members allocated, some not) is intentional. A project manager migrating from “loose” to “structured” capacity can do so gradually without breaking the view.
Read the allocation bar alongside the status badge. A green Compliant + 15% allocation tells a different story than green Compliant + 95% allocation. The bar is the nuance.
Coordinate allocation with the Capacity Planner. Allocation here doesn’t update the Capacity Planner’s available-hours number. If you also use Capacity Planner, align them manually so the two pictures match.
Surface non-compliant project work to project leads, not org admins. Project compliance is most actionable for the project’s leads. Org admins should focus on org-wide compliance; project leads on this view.

Troubleshooting / common pitfalls

The Compliance tab is missing on a project. Three causes: (a) compliance isn’t enabled at the org level; (b) the project’s billable flag affects visibility on some Finance views — verify; (c) the user isn’t a project Owner/Manager or org admin with timesheet enforcement permission.
Numbers don’t match the org-wide compliance dashboard. That’s expected when allocation is set — this view uses project-specific math. Without allocation, both views should agree on total hours.
Member’s status changed mid-week. Allocation or expected-hours edits affect the live calculation. Refresh the view to see the latest.
My team has 6 projects but no allocation per project. Then they all share the total-hours rule. Setting allocation on one project doesn’t take from another; each project’s compliance is independent.
Allocation shows 0% but I set a value. Save was lost (you navigated away without saving). Re-enter the value on the Members tab.

How this combines with other features

Per-project compliance + Org-wide compliance. Org-wide is the rollup; per-project is the slice. Set up the org-wide first, then dive into projects where the rollup says there’s a gap. See Monitor timesheet compliance.
Per-project + Allocation field. The Members tab is where allocation is set; this view is where it shows. The two surfaces work together.
Per-project + EVM. A team’s utilization on a project (this view) and the project’s labor cost (EVM Finance tab) tell different stories. The two together answer “Are people overworked here?” plus “What does that cost?”. See Read the EVM dashboard.
Per-project + Goals. Linking projects to goals lets you see compliance against goal-relevant work. See Track goals and OKRs.

Coming from another tool

Tool	Mapping
Microsoft Project Online	Resource Center per-project utilization ≈ this view
ServiceNow PPM	Direct concept
Smartsheet Resource Management	Direct
Float	Direct concept; Float is allocation-first by design
Custom dashboards	Onplana surfaces this view first-class

FAQs

Why does a member show Compliant here but Partial on the org dashboard? They cannot, under the default rule: both compare the same weekly total. A mismatch can appear only when the member has an allocation set here, because this view then compares project hours instead.

Does cost at risk appear in the project view? No. The currency figure lives on the org-wide dashboard, described in Monitor timesheet compliance. The project view focuses on hours and allocation.

Who can set a member’s allocation? Whoever can manage the project’s members, on the project’s Members tab. Empty means no allocation, which keeps the default behavior.

Can a member have allocation on multiple projects that sum to over 100%? Yes — Onplana doesn’t enforce a “must sum to 100” rule. Multi- project allocation is the org’s responsibility to coordinate.

Does setting allocation here affect EVM cost calculations? No. Allocation here only affects this view’s compliance math. Cost calculations use logged hours × rate cards, regardless of allocation.

Is there a portfolio rollup of per-project compliance? The org-wide compliance dashboard is the portfolio rollup. Use Reports to slice by project, owner, or department for finer groupings.

Monitor timesheet compliance — the org-wide rollup
Plan team capacity — total-hours capacity view
Set expected hours overrides — refining expectations

Was this helpful?