When Does an Expired Offer Approval Need Reauthorization?

Research question. When a recruiting offer is not issued before its approval window ends, what evidence should a coordinator preserve before any later communication or document is sent? The study examines expiry, changed inputs, reauthorization, and candidate messaging. It does not decide compensation, selection, fairness, employment terms, or whether an offer is binding. Create 105 fictional journeys across new roles, replacement hires, referrals, remote arrangements, changed start dates, revised levels, currency changes, signing bonuses, contingent approvals, and withdrawn requisitions. Include same-day issue, weekend expiry, candidate delay, approver role change, corrected name, budget revision, and a document generated from stale data. All identities, amounts, companies, and messages are synthetic.

Model approval as scoped evidence rather than a green flag. Required fields are requisition version, candidate token, role and level, compensation components, currency, work arrangement, location class, start-date constraint, contingencies, approver identity and authority source, approval instant, effective interval, expiration trigger, and source hash. Unknown scope is not broad approval. An email saying looks good remains ambiguous unless the owner-defined process identifies the reviewed version and allowed action. Connect approved inputs to template version, populated draft, owner review, released document, delivery event, and replacement. Hashes identify observed bytes but do not prove authorization or meaning, and a correct filename cannot rescue a stale draft.

Run expiry in stages. First approval is valid, then its release window closes, then the candidate requests a different start date, and finally a manager says send it anyway. Reviewers identify observed facts, whether scope covers the change, and which owner route applies. They cannot extend the window, treat silence as renewal, or decide the changed date is immaterial. The reauthorization packet shows prior approved terms, exact changes, elapsed time, current requisition and budget state, communications already made, and requested action. The accountable owner records a new decision, scope, time, and expiry; administrators cannot invent a shortcut because most fields match.

Candidate communications are tested before and after expiry. Approved messages distinguish process update, owner review pending, revised timing, released offer, and withdrawn process. They avoid promising terms, blaming an approver, exposing budget discussions, or suggesting that a stale draft remains open. A correction route addresses a mistakenly sent message. Seed a race: the document service queues a valid draft, approval expires, a date change arrives, and the queued email sends later. The workflow detects the late release, preserves what the candidate received, stops reminders under an approved rule, alerts the response owner, and links any replacement. It never deletes the event to improve the record.

Compare a requisition status plus email trail with a versioned approval-to-release graph. Give teams identical information and time. Measure stale-offer sends, unauthorized field changes, false approval claims, candidate-message errors, duplicate active documents, owner-decision time, and complete lineage. Severe errors remain visible outside averages. Boundary cases include a recruiter authorized elsewhere, a manager whose authority ended that morning, an approval forwarded without attachments, and compensation described differently in two systems. Coordinators retrieve records and assemble conflicts; they do not choose which authority counts, interpret economic equivalence, or disregard an organizational change.

Privacy controls restrict candidate identifiers, draft terms, approval discussions, and withdrawn artifacts. Role-specific views reveal only what is needed; external links expire; exports are logged; broad chat and local copies are inspected; and superseded drafts receive an owner-defined treatment. Calibration uses two reviewers on unseen cases. Each cites the approval version, artifact, event, and rule. Disagreement may expose an unclear trigger, missing authority source, or inaccessible evidence. The owner clarifies the rule, versions change, and a fresh sample is tested. Cannot determine is accepted when evidence does not establish scope rather than forcing agreement with a hidden answer.

Report approval-scope coverage, expired-release attempts, changed-field detection, reauthorization completeness, duplicate active artifacts, message accuracy, access exceptions, owner response time, and reviewer agreement. Separate observation, procedure classification, owner decision, and research inference. Recovery restores a stale requisition snapshot and replays an old generation event after reauthorization. The team retains the newer decision, quarantines the replay, identifies downstream copies, and checks the candidate portal, email queue, document store, recruiting record, and export. Closure states which paths acknowledged correction and which remain unknown; a clean primary screen is not enough.

Approval-window analysis uses the site’s configured timezone, the approver’s recorded timezone where relevant, and UTC instants. A date-only approval that lacks a cutoff convention is classified as ambiguous and routed to its process owner. The exercise includes a daylight-saving change in an overseas approver’s location while the Philippines remains on a constant offset. Reviewers do not choose the favorable interpretation. They identify which instant each system used, whether a queue delayed release, and what the candidate had already been told. The resulting chronology makes technical timing visible without letting a coordinator decide whether an approval remained legally or organizationally effective.

The changed-field matrix distinguishes identity presentation, role substance, monetary terms, work location, start constraint, contingency, and formatting. Owners predefine which changes require which review path; staff do not infer materiality from size or familiarity. One test changes a currency label without changing the number, another changes a number after conversion, and a third corrects a typographical name while a background process references the old token. Reviewers preserve the differences, route them, and ensure the released artifact matches the newly authorized combination. This catches cases where two individually approved sources were never approved together.

Candidate-experience analysis measures silence, contradictory messages, expired links, duplicate documents, correction clarity, and time to an accountable update. It does not treat acceptance speed as the only outcome. A candidate may act on a stale deadline or disclose personal information through an obsolete portal even when the internal team fixes its master record quickly. The exercise checks every outward path and records what the candidate could reasonably observe at each moment. Communications state facts and next steps without implying blame or inventing a continuing offer, while the owner decides any remedy or substantive response.

A procurement decision brief lists the exact approval rules, authority source, artifact paths, candidate channels, and observation window tested. It reports boundary breaches individually, identifies excluded offer types, and explains the strongest alternate cause of each failure. The recommendation can support a limited administrative pilot only for the tested scope. It cannot justify delegating compensation or selection authority. Review triggers include a template change, new compensation component, different hiring geography, altered approver directory, or document-platform migration. Naming those triggers prevents a point-in-time success from becoming a permanent claim about a changing recruiting system.

Handoff testing gives a substitute coordinator only the versioned case record, not undocumented team memory. The person must identify the current approval, its expiry, the active artifact, communications already sent, the next owner, and the safe reversible step. Missing context remains an exception rather than an invitation to ask the candidate to confirm confidential terms. This trial measures whether the record is portable across shifts and service transitions, whether old drafts are mistakenly revived, and whether temporary permissions are revoked after coverage ends. A reliable process should preserve decision boundaries even when the original recruiter is unavailable.

Limitations. This synthetic study cannot determine fair compensation, candidate rights, contract formation, discrimination, budget authority, tax treatment, or legal validity. It cannot establish that a real approver understood a term. It can assess whether support preserves versions and waits for accountable decisions. Procurement should request a sanitized expiry case, changed-field packet, authority view, late-send recovery, candidate correction sample, and immutable export. Sources checked October 5, 2026: NPC, “Republic Act No. 10173,” https://lawphil.net/statutes/repacts/ra2012/ra_10173_2012.html; NIST, “Identity Proofing Overview,” https://pages.nist.gov/800-63-4/sp800-63a/proofing/; NIST, “CSF 2.0,” https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20. These frame controls, not offer decisions.