Staffing requests

Demand intake

A Project Manager files a ResourceRequests row when the pm-projects workspace reveals a staffing gap: Project, RoleNeeded, StartDate, EndDate, AllocationPct, Priority, Justification, LocationPreference, MaxBillRate, plus one or more RequestSkills line items (Skill, MinProficiency, Importance: MustHave / NiceToHave). On submit (Status: Draft → Submitted), the resource-request-approval-routing workflow routes to the matching Practice’s Resource Manager and stamps Status: Submitted → PendingApproval.

Match and suggest

On request creation, the skill-match-suggester workflow runs the configured matching service to score every active Resource against the RequestSkills (skill match, proficiency delta, capacity in window from WeeklyCapacity, BillRate fit, Practice match, location preference) and writes the top 10 candidates as RequestSuggestions rows (one per candidate, each with MatchScore, SkillMatchPct, ProficiencyDelta, CapacityFitPct, BillRateFitPct, and Rank). The Resource Manager reviews the suggestions on the request detail view, picks the right Resource, sets MatchedResource, and approves (Status: PendingApproval → 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 RejectionReason; the Project Manager can revise and resubmit.

Assignment generation

On approval the assignment-on-approval workflow fires: a code node creates an Assignments row (Resource, Project, Role, RateCard resolved from Practice + StartDate, BillRate resolved from RateCardRows and frozen on the Assignment, CostRate snapshotted from Resources.CostRate, AllocationPct carried from the request) plus N AssignmentPeriods rows (one per week from StartDate to EndDate at the requested AllocationPct). 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.

Resolve two requests for the same specialist

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.