Checks built in
What Resource Planning System enforces at each step.
- Lock affected resource-weeks during confirmation.
- Changed dates or scope invalidate approval.
- Track target membership acknowledgment separately.
- Resource Planning System
- Process
- Request to project assignment
Request to project assignment
Review current fit and capacity before creating one approved assignment.
Step by step
-
Capture demand Project Manager
A Project Manager files a resource requests row when the pm-projects workspace reveals a staffing gap: Project, role needed, start date, end date, allocation pct, Priority, Justification, location preference, max bill rate, plus one or more request skills line items (Skill, min proficiency, Importance: Must have / nice to have). On submit (Status: Draft → Submitted), the resource-request-approval-routing workflow routes to the matching Practice’s Resource Manager and stamps Status: Submitted → pending approval.
- Submit scoped project requirements
- Updates Resource requests, Request skills
-
Approve match Resource Manager
On request creation, the skill-match-suggester workflow runs the configured matching service to score every active Resource against the request skills (skill match, proficiency delta, capacity in window from weekly capacity, bill rate fit, Practice match, location preference) and writes the top 10 candidates as request suggestions rows (one per candidate, each with match score, skill match pct, proficiency delta, capacity fit pct, bill rate fit pct, and Rank). The Resource Manager reviews the suggestions on the request detail view, picks the right Resource, sets matched resource, and approves (Status: Pending approval → Approved) only after an atomic capacity recheck. Missing inputs block approval. Overcommit is rejected unless the practice explicitly permits it and an independent Resource Manager records the current conflict and reason. On reject, sets Status: Rejected with rejection reason; the Project Manager can revise and resubmit.
- Record an independent current-capacity decision
- Updates Resource requests, Request suggestions, Weekly capacity
ApprovalA person approves before the work moves on. -
Staff project Resource Manager
On approval the assignment-on-approval workflow fires: a code node creates an Assignments row (Resource, Project, Role, rate card resolved from Practice + start date, bill rate resolved from rate card rows and frozen on the Assignment, cost rate snapshotted from resource cost rate, allocation pct carried from the request) plus N assignment periods rows (one per week from start date to end date at the requested allocation pct). The workflow then writes the Resource into the matched pm-projects project as a project member via the connected record service so the team appears in the project workspace. The Resource and Project Manager are emailed.
- Reserve capacity and reconcile project membership
- Updates Assignments, Assignment periods
Who does what
Roles and permissions- Project Manager
- Project owner — files resource requests for own projects, sees Assignments staffed against own projects, requests Substitutions, and consumes the staffed team into the pm-projects workspace. No write on Resources or Skills catalog.
- Resource Manager
- Owns the demand-supply marketplace for one or more Practices. Sole authority to approve resource requests for own Practice, match a Resource, create the Assignment, intake Substitutions, and clear Bench rows.
- Resource
- The staffed person. Self-service on own Skills profile and read-only on own Assignments. Cannot see other Resources’ rates, costs, or assignments.
Set up Resource Planning System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.