This original procedure example checks administrative readiness. A missing record is not a candidate score, a hiring decision or proof that an interview never occurred.
One original application packet
Fictional review snapshot: October 13, 2026. No candidate has been assessed, contacted or hired through this example.
| Record | Supplied identity or state | Missing input |
|---|---|---|
| Candidate | C02 | Actual identity and contact details not used |
| Application | A03, linking C02 to J01 | Confirm against maintained hiring record |
| Job | J01 | Actual requisition/scope authorization to confirm |
| Criteria | CR01 reference | Revision and actual criteria to confirm |
| Interview record | IR01 required by this proposed packet gate | Record missing |
| Evaluation/decision | No reference supplied | Actual evidence and decision not supplied |
| Offer | O01, Draft | Authority, review and terms unconfirmed |
Preserve A03/J01 on every dependency, including IR01 and O01. Do not attach another application's evaluation merely because its candidate name looks similar or its file is readily available.
The requirement for IR01 is an original illustrative gate. The actual organization must supply its required records and authorized process; this example does not prescribe universal interview stages or selection criteria.
Workable's hiring-guide template asks organizations to customize requisition and approval arrangements and separates offer review, sending and acceptance. This packet adopts those process distinctions, not the source's corporate titles, assessment rules, reference-call advice or employment terms.
Define the controlled procedure before using it
Prepare a native Word/PDF control block with procedure ID, title, scope, version, owner, approval evidence, effective date and related criteria/policy references. Leave actual roles, permissions and approval dates to confirm until supplied. A document title cannot grant authority.
Keep permissioned hiring records in the maintained workflow. The public or colleague-review example uses fictional IDs rather than actual interview notes, contacts or compensation information.
Make each handoff name its required evidence
The functions below describe responsibilities to assign; they are not actual role appointments.
| Handoff function | Record needed | Evidence check | Current example result |
|---|---|---|---|
| Confirm job/process scope | J01 and actual criteria/authority references | Correct job, applicable CR01 revision, authorized reviewer identified | To confirm |
| Assemble application packet | A03/J01, IR01 and evaluation reference | All records belong to this application and required evidence is present | IR01 missing; evaluation not supplied |
| Prepare offer review | O01 plus required decision/review references | Draft tied to the same application; actual terms and authority supplied | O01 remains Draft |
| Record authorized approval | Actual approval record | Who approved, under what authority, which version and when | Blank |
| Record sending | Actual send record | Which approved version was sent through the authorized process | Blank |
| Record acceptance/start | Actual response and separate start record | Acceptance and commencement supported independently | Blank |
Assign the real owner and recipient for each function in the controlled procedure. Do not fill the matrix with invented executives or assume a particular job title can sign.
Walk A03 through the proposed sequence
- Confirm scope and authority: Check J01, the required evidence gate, CR01 revision and actual reviewer authorization. Resolve missing process inputs before describing the procedure as approved.
- Bind the packet: Match candidate C02, application A03 and job J01 across all relevant records. Flag an association mismatch instead of transferring an evaluation from another application.
- Request missing evidence: Identify IR01, evaluation and decision references required under the confirmed process. Log the gap and responsible next step; do not invent what an interview or evaluation would say.
- Prepare a draft for review: Retain O01 as Draft while its packet and authority are unresolved. An existing offer file is not an approval record.
- Record actual approval separately: After the required review occurs, record its evidence and exact offer version. Do not populate this field from a walkthrough selection.
- Record actual sending separately: Use the maintained authorized process and retain the observed send record. Approval alone does not mean a candidate received the offer.
- Record response and start separately: Preserve actual acceptance evidence and, later, actual commencement evidence without assuming one from the other.
These are proposed steps, not completed actions. No message, signature, candidate assessment or background check is performed by the preparation packet.
Hold the packet without rejecting the person
Under this illustrative rule, missing IR01 prevents the administrative handoff from being treated as ready. It does not reject C02, assign a merit score or establish that the interview was unsuccessful.
A useful original internal request draft is “For A03/J01, provide the required IR01 reference and confirm the applicable CR01 revision, evaluation/decision references and authorized reviewer. O01 remains Draft while these inputs are unresolved.” It is wording to review, not a sent message.
Keep an exception log with application/job IDs, missing input, responsible owner to confirm, requested next step, actual response and resolution evidence. Leave the latter fields blank until supplied. Preserve the first finding when a corrected packet arrives.
Keep offer states distinct
Use a proposed evidence ledger that distinguishes Draft, Approval pending, Approved not sent, Sent not accepted and Accepted not started. Define each state against the actual organizational process and evidence.
O01 is currently Draft. None of the later states has occurred in this example. Actual criteria, terms, timing, contacts, signatures, start date and retention policy remain to confirm. The ledger provides no automatic selection, acceptance or legal-compliance conclusion.
Copy an application-bound SOP brief
Create one complete, self-contained US-English HTML companion for “Recruiting SOP • A03 handoff review”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for IR01 requirement; O01 draft; Offer-state evidence; Check association; Inspect an A99 mismatch; Select text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Draft a recruiting SOP in US English in the required native Word/PDF format.
Procedure scope/version and actual owner/approval/effective-date inputs: [enter]
Candidate/application/job/offer IDs and confirmed associations: [paste]
Actual criteria revision, required records and decision references: [paste]
Authorized reviewer, role-to-record handoffs and permissions: [paste or TO CONFIRM]
Actual approval/send/acceptance/start evidence: [paste or NOT PERFORMED]
Required business terms, timing and retention policy: [paste or TO CONFIRM]
Bind every handoff to the correct application and job. Do not borrow another
application's evaluation. Keep missing evidence distinct from candidate merit. Under the supplied packet gate, unresolved records/authority prevent a ready
handoff claim, not an automatic rejection. Keep offer draft, review, approval,
sending, acceptance and start as separate evidence states. Preserve exceptions
and later resolution; leave actual actions/decisions blank until supplied. Do not invent criteria, reviewers, pay, terms, signatures, assessments or hires.
Return the controlled draft, handoff matrix, walkthrough, missing-input request,
exception log and offer-state ledger. If requested, specify a sanitized HTML
procedure-review copy. No approval, candidate contact, record storage/sync,
automatic selection or saved-edit controls.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Recruiting SOP Template: Keep the Offer Draft Until Its Handoff Evidence Is Complete
An offer draft exists, but the packet lacks its required interview record and nobody has identified who can approve it. “Ready to send” would skip both evidence and authority. Bind the records to the application and job before handing the draft onward.
This original procedure example checks administrative readiness. A missing record is not a candidate score, a hiring decision or proof that an interview never occurred.
## One original application packet
**Fictional review snapshot: October 13, 2026. No candidate has been assessed, contacted or hired through this example.**
| Record | Supplied identity or state | Missing input |
| --- | --- | --- |
| Candidate | C02 | Actual identity and contact details not used |
| Application | A03, linking C02 to J01 | Confirm against maintained hiring record |
| Job | J01 | Actual requisition/scope authorization to confirm |
| Criteria | CR01 reference | Revision and actual criteria to confirm |
| Interview record | IR01 required by this proposed packet gate | Record missing |
| Evaluation/decision | No reference supplied | Actual evidence and decision not supplied |
| Offer | O01, Draft | Authority, review and terms unconfirmed |
Preserve **A03/J01** on every dependency, including IR01 and O01. Do not attach another application's evaluation merely because its candidate name looks similar or its file is readily available.
The requirement for IR01 is an original illustrative gate. The actual organization must supply its required records and authorized process; this example does not prescribe universal interview stages or selection criteria.
[Workable's hiring-guide template](https://resources.workable.com/hiring-guide-template) asks organizations to customize requisition and approval arrangements and separates offer review, sending and acceptance. This packet adopts those process distinctions, not the source's corporate titles, assessment rules, reference-call advice or employment terms.
## Define the controlled procedure before using it
Prepare a native Word/PDF control block with procedure ID, title, scope, version, owner, approval evidence, effective date and related criteria/policy references. Leave actual roles, permissions and approval dates **to confirm** until supplied. A document title cannot grant authority.
Keep permissioned hiring records in the maintained workflow. The public or colleague-review example uses fictional IDs rather than actual interview notes, contacts or compensation information.
## Make each handoff name its required evidence
The functions below describe responsibilities to assign; they are not actual role appointments.
| Handoff function | Record needed | Evidence check | Current example result |
| --- | --- | --- | --- |
| Confirm job/process scope | J01 and actual criteria/authority references | Correct job, applicable CR01 revision, authorized reviewer identified | To confirm |
| Assemble application packet | A03/J01, IR01 and evaluation reference | All records belong to this application and required evidence is present | IR01 missing; evaluation not supplied |
| Prepare offer review | O01 plus required decision/review references | Draft tied to the same application; actual terms and authority supplied | O01 remains Draft |
| Record authorized approval | Actual approval record | Who approved, under what authority, which version and when | Blank |
| Record sending | Actual send record | Which approved version was sent through the authorized process | Blank |
| Record acceptance/start | Actual response and separate start record | Acceptance and commencement supported independently | Blank |
Assign the real owner and recipient for each function in the controlled procedure. Do not fill the matrix with invented executives or assume a particular job title can sign.
## Walk A03 through the proposed sequence
1. **Confirm scope and authority:** Check J01, the required evidence gate, CR01 revision and actual reviewer authorization. Resolve missing process inputs before describing the procedure as approved.
2. **Bind the packet:** Match candidate C02, application A03 and job J01 across all relevant records. Flag an association mismatch instead of transferring an evaluation from another application.
3. **Request missing evidence:** Identify IR01, evaluation and decision references required under the confirmed process. Log the gap and responsible next step; do not invent what an interview or evaluation would say.
4. **Prepare a draft for review:** Retain O01 as Draft while its packet and authority are unresolved. An existing offer file is not an approval record.
5. **Record actual approval separately:** After the required review occurs, record its evidence and exact offer version. Do not populate this field from a walkthrough selection.
6. **Record actual sending separately:** Use the maintained authorized process and retain the observed send record. Approval alone does not mean a candidate received the offer.
7. **Record response and start separately:** Preserve actual acceptance evidence and, later, actual commencement evidence without assuming one from the other.
These are proposed steps, not completed actions. No message, signature, candidate assessment or background check is performed by the preparation packet.
## Hold the packet without rejecting the person
Under this illustrative rule, missing IR01 prevents the administrative handoff from being treated as ready. It does not reject C02, assign a merit score or establish that the interview was unsuccessful.
A useful original internal request draft is **“For A03/J01, provide the required IR01 reference and confirm the applicable CR01 revision, evaluation/decision references and authorized reviewer. O01 remains Draft while these inputs are unresolved.”** It is wording to review, not a sent message.
Keep an exception log with application/job IDs, missing input, responsible owner to confirm, requested next step, actual response and resolution evidence. Leave the latter fields blank until supplied. Preserve the first finding when a corrected packet arrives.
## Keep offer states distinct
Use a proposed evidence ledger that distinguishes **Draft**, **Approval pending**, **Approved not sent**, **Sent not accepted** and **Accepted not started**. Define each state against the actual organizational process and evidence.
O01 is currently **Draft**. None of the later states has occurred in this example. Actual criteria, terms, timing, contacts, signatures, start date and retention policy remain to confirm. The ledger provides no automatic selection, acceptance or legal-compliance conclusion.
## Copy an application-bound SOP brief
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Walk A03/J01's missing IR01 and unconfirmed authority with the procedure owner before advancing O01. Keep the controlled procedure and permissioned hiring records authoritative, and require the separate evidence for each actual offer transition before changing its recorded state.