Checks built in
What Resource Planning System enforces at each step.
- Do not guess among ambiguous assignment matches.
- Show null ratios when available hours are zero.
- Forecast value is separate from recognized revenue.
Reconcile approved source time before publishing utilization and bench signals.
Daily, time-sync-from-pm-time reads approved Timesheet rows from the pm-time app and matches each to the corresponding assignment periods by Resource + Project + Week, writing actual hours and computing variance hours = actual hours − allocation hours. Closed weeks flip assignment period status: In progress → Closed. This is the only path by which actuals enter the Resource Management app — staffers do not log time here.
Weekly on Monday, utilization-rollup aggregates the prior week’s closed or frozen assignment periods and effective time actuals into one Utilization row per Resource (available hours, allocated hours, actual hours, billable hours, non billable hours, utilization pct, billable utilization pct). Right after, bench-detection scans the latest Utilization plus forward-booking coverage and writes a Bench row for every Resource whose forward-4-week average utilization pct falls below the bench threshold (default 60%). Practice Leads get a digest; the bench-clearing motion (cross-Practice loan, investment work or training time) starts from the Bench Report.
Daily, assignment-end-cleanup flips every Assignments row with end date < today AND Status: Active to Status: Completed (or Substituted for an approved effective replacement), freezes the trailing assignment periods to Status: Frozen, and recomputes the Resource’s forward weekly capacity to release the freed allocated hours. The Resource is now visible to skill-match-suggester for the next request.
What Resource Planning System enforces at each step.
Start free, then use Proto to change fields, steps and approvals before your team goes live.