role-intake

Role Intake

Purpose

Normalise the signed engagement request and SOW role extract into the ps.engagement-staffing-bench-match.v1 contract: engagement identity, client, known parent/subsidiary/affiliate names, practice, role requirements, start dates, allocations, location, language, industry context, rate band and citations.

When to use

At the start of every Engagement Staffing & Bench Match run.

When NOT to Use

• Summarising payment terms, liability caps or termination clauses of an SOW — that is contract review, not staffing.
• Normalising the bench roster — use bench-query instead.
• Scoring, ranking or naming candidates — use fit-score instead.
• Clearing conflicts or independence — use constraint-check instead.
• Drafting the partner recommendation or slate note — use slate-draft instead.

Inputs

• Staffing request email or mobilisation note.
• SOW role extract with open roles, start dates, expected duration and required skills.
• Rate-card or commercial guardrail excerpt if supplied.

Steps

1. Extract engagement{} with source, confidence and citation. Include every source-backed parent, subsidiary or affiliate in engagement.affiliates[]; never infer corporate relationships. Use the engagement ID exactly as it appears in the source; if the firm's internal code is not supplied, carry the SOW ID and add an escalation. When only the SOW ID is supplied, even if the request repeats it, carry it and add the internal-code escalation. Set practice only from an explicit practice statement in the SOW or request body; never take it from a sender's signature, title or team name. If it is not stated, leave it empty and escalate; never infer it.
2. Extract each role into roles[]: required and preferred skills, required certifications, seniority, start date, allocation, location, remote_ok, required_languages, duration, industry_context (the client industry as the SOW or request words it — fit_score.py reads it for rubric #1.6 and reads "&" as "and", ignores "and", "of", "the", simple plurals and generic words such as "provider", "services" or "sector", and needs the remaining words to equal a bench industry_experience entry, so "healthcare provider" matches "healthcare" and "oil & gas" matches "oil and gas" but "retail banking" does not match "retail"; it escalates partial matches once per role and a role whose industry matches no candidate) and rate band. Normalize seniority to lowercase canonical values: associate, consultant, senior consultant, manager, senior manager, director or partner. required_languages is the SOW's stated working language plus any language the role itself names (for example "Spanish-speaking").
3. Set each role's confidence by how far the staffing request restates the SOW row (allocation, start, duration, location, every required and preferred skill and certification): 0.96 all, 0.95 some, 0.94 none or role not named. engagement.confidence is 0.96 when the request names the SOW client, else 0.94. Preserve uncertainty. If a role requirement is ambiguous or unstated (for example no language stated), carry it as an escalation rather than guessing. If a source-backed requirement has no contract field (for example on-site days per week), preserve its source wording and citation in a role-specific escalation; never drop it or invent a field.
4. Record any partner preference for a named person as an escalation note only — never as a selection. Name the person only; do not invent or look up a candidate ID.
5. Hand off the contract payload to bench-query.