From requirement to assignment
How a client's demand becomes a submission and then a placement, and what each stage move means.
The staffing desk runs one chain, over and over:
client demand → consultant match → submission → decision → assignment
Each link is a record, and each record keeps its own history. Nothing in the chain replaces the link before it.
1. Capture the requirement
A requirement (labelled Requisition in Full mode) records what one client asked for: the role, how many openings, the skills, the dates, the location or work mode, and how urgent it is.
Openings matter more than they look. A requirement for three people is one record with three seats, not three records — which is why the lists show openings / filled rather than a simple open-or-closed status.
2. Put a consultant forward
A submission presents one consultant against one requirement. Create it from the requirement, from the submissions list, or from the pipeline.
A submission is a relationship, not a copy of the consultant. It holds the match, the current status, who owns it, and the decision history. When a client passes on someone, the submission stays — that record is how you avoid re-submitting the same person next quarter and how you learn what a client actually says yes to.
Submissions do not carry bill or pay rates. The consultant's current rates stay on the Consultant, and the placement's agreed rates belong on the Assignment.
3. Move it through the stages
Submissions progress through the stages your organization has configured — the Staffing pack ships no fixed lifecycle, so your stage names are your firm's. You can move a record from its detail page, from the list, or from the pipeline — all three use the same stage rules, so working from the pipeline never skips a step that the detail page would have enforced.
If a stage move is refused, the record is telling you a condition has not been met yet. Read the reason rather than routing around it.
4. Convert to an assignment
When the client accepts, convert the submission. Conversion opens a dialog that creates the assignment — the live engagement, with its dates, owner and rates — and links it back to the client, the consultant, the requirement and the submission that produced it.
Always convert rather than creating an assignment from scratch. Conversion is what fills a seat on the requirement and what preserves the trail; a hand-made assignment has no submission behind it and leaves the requirement looking unfilled.
If conversion is unavailable, the dialog says why — commonly the requirement has no seat left, or the submission is not yet at a stage that permits it.
5. Run and close the assignment
An assignment has its own dates and status: it can be extended, completed, or end early.
The assignment record leads with its stage, so what state the engagement is in is the first thing you read, and you move it from there rather than hunting for a separate button. Beside it sit the dates and the bill rate.
Its Lineage card, on the overview, is the chain that produced it — the client, the consultant, the requirement and the submission — each a link back to that record. Lineage is fixed at conversion and does not change afterwards.
If an assignment has been terminated, the record says so at the top, whether or not anyone recorded a reason.
Rates live on the Assignment and use the Assignment's normal read and manage permissions. Its commercial panel shows the bill and pay rates, the rate period and the resulting margin.
Where this shows up day to day
The Staffing home at /staffing ranks whatever is waiting on a person across all three record types, so you rarely need to walk the chain manually. The pipeline at /staffing/pipeline is the same work seen as lanes, for when you want to read the desk rather than clear it.