From a gap on a project to somebody working on it
- A project reports a gap — A staffing request names the role, the skills and the dates. Until somebody is allocated it sits in the capacity view as an unmet need, not as a note in a spreadsheet. (needs the staffing module, which this vertical does not enable by default)
- The gap becomes an opening — The opening remembers the request it came from, so the pipeline is answerable to the project that asked. Candidates carry their consent date and a retention deadline from the moment they are created. (needs the recruiting module, which this vertical does not enable by default)
- Interviews, kept separate — Each interviewer files their own evaluation. A split panel is shown as a split panel rather than averaged into a number that hides the disagreement. (needs the recruiting module, which this vertical does not enable by default)
- The hire becomes a person on the payroll — Marking a candidate hired writes the consultant record. The database refuses the state otherwise: an application cannot claim a hire that produced nobody. (needs the contractor-portal module, which this vertical does not enable by default)
- And an onboarding that already exists — The same action instantiates a checklist from a template, one row per item, with due dates counted from the start date rather than from today.
- Then the hours start arriving — The new consultant files time against the project that raised the request. The loop closes where it opened. (needs the timesheet module, which this vertical does not enable by default)