Checks built in
What Resource Planning System enforces at each step.
- Missing leave inputs block new confirmation.
- Keep original actuals on their accepted assignment.
- A requester cannot approve their own substitution.
Resolve capacity changes while retaining the history of the original commitment.
The capacity-recompute workflow runs nightly: for every active Resource it rebuilds the next-26-weeks weekly capacity grid by reading approved PTO imports (sourced from the hrms-leave-attendance app) and US holidays for the Resource’s home state, deducting PTO hours and holiday hours from base hours to produce available hours. The grid is what every staffing decision reads against — there is no other source of truth for “is this person free?”
Whenever an Assignments or assignment periods row is created or updated, the over-allocation-alert workflow sums all active assignment period allocation hours per Resource per Week and compares to weekly capacity available hours. If the sum exceeds capacity in any week of the span, the workflow flips assignment over allocated: true and emails both the Resource Manager and the offending Project Manager with the breach detail. The Resource Manager resolves by reducing allocation pct, ending an Assignment early, or running a Substitution.
When a Resource needs to come off a project mid-flight (resignation, medical leave, reassignment, performance swap, client request), the Project Manager (or Resource Manager) proposes a Substitutions row with outgoing resource, incoming resource, effective date, and Reason. On independent approval (Status: Proposed → Approved), the workflow rechecks incoming capacity and the current assignment revision, then atomically truncates the original Assignment’s end date to effective date − 1, keeps it Active until the boundary becomes effective, and creates a new Assignments row + assignment periods for the incoming resource starting effective date.
What Resource Planning System enforces at each step.
Start free, then use Proto to change fields, steps and approvals before your team goes live.