Staffing requests

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.

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.

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.

Two project managers may choose the same suggested specialist before either request is confirmed. Suggestions describe the capacity observed when matching ran. Approval rechecks the current resource-week commitments and reserves capacity in one transaction, so the second decision cannot rely on an outdated ranking.

A mandatory skill is an eligibility condition. Preference factors such as location or a desirable secondary skill help compare eligible people; they do not compensate for a missing mandatory qualification. Show the component scores and the observation time so the resource manager can explain the selection.

The project manager can revise a rejected request without changing its earlier review history. A changed date span, rate ceiling or allocation invalidates the prior decision. If the project is closed in the delivery source, the local request cannot create a new membership merely because its cached project name still exists.

• Pending Resource Requests. Open the current records for this module within your assigned role and permitted scope.