A candidate-message draft may be finished while the hiring decision it refers to is still under review. If the file is simply labeled “ready,” someone else may reasonably misunderstand what has been completed. The wording is ready to review; the underlying decision may not be approved, and nothing may have been sent.
The fictional example below follows a communication record with those states kept separate. It concerns preparation and handoff, not deciding who should progress in a hiring process. A clear record tells the authorized team what the draft represents and what still needs to happen before anyone uses it.
Identify the decision status before editing the message
Start by checking the decision status with the responsible source. Do not infer an outcome from a draft filename, a calendar change or the absence of a response. If the status is unconfirmed, mark the message as a draft awaiting that confirmation.
In the fictional example, a team member has prepared wording for a possible process update, but the responsible reviewer has not completed the underlying review. The preparation record should retain that distinction. A completed writing task is not evidence of an approved employment decision.
Keep the article's example free of applicant identifiers. In an actual workflow, use the organization's approved records and access arrangements for any necessary references. The person reviewing the message needs a reliable connection to the authorized status without copying personal details into every planning note or general task board.
Use only the approved wording and facts
Once the appropriate status is confirmed, compare the draft with the wording and facts approved for that communication. Do not invent a reason for a decision because a message feels incomplete without one. A plausible explanation can still be inaccurate.
Look for statements about future opportunities, feedback or contact. “We will be in touch about another opening” is a commitment, not just a courteous closing. Include it only if the responsible team has authorized that promise and has a process for honoring it.
The same applies to timing. A draft should not promise detailed feedback by Friday when no one has agreed to provide it. If a required detail remains unresolved, flag it for review. Copy preparation can continue around a visible hold without turning an unsupported sentence into an approved fact.
Separate draft, approved and sent states
Use status labels that identify separate events. A draft exists when someone has prepared wording. Approval means the responsible person has authorized the specific version for the intended use. Sent means an authorized action actually occurred through the agreed channel.
In the fictional record, keep those events in separate fields or entries, with the appropriate evidence for each. An approval date should not automatically populate a sent date. A scheduled action should also remain distinguishable from a completed one.
If the team uses a handoff checklist, make the final status explicit. “Copy approved; delivery pending” is clearer than “complete” when another person still owns delivery. The record does not need a complex system to make this distinction, but everyone using it needs to understand what each label does and does not establish.
Record changes without overwriting their meaning
When the draft changes, retain the reason and the version the reviewer approved. A correction to a date may be straightforward, while a new explanation for a decision can change the substance of the message. Both need to remain traceable to the appropriate source.
Do not quietly replace the approved wording and keep the old approval marker. Route the revised version through the required process. The record should allow someone to identify which text was authorized at the time of any later action.
If the underlying status changes while a message is waiting, stop treating the earlier draft as current. Record the change and ask the responsible person what follows. Do not guess whether the old message should still be used or create a second communication to repair an event that has not been verified.
Confirm the next action with the authorized owner
At handoff, identify the actual remaining action and its owner. The writer might be waiting for a factual correction, a decision confirmation or approval of the latest version. Keep that request specific enough for the responsible person to resolve.
After the response, update only the status supported by the evidence. If the message remains a draft, say so. If delivery later occurs through the authorized process, connect its receipt to the version used without treating the preparation record itself as proof of delivery.
The examples here are original fictional documentation guidance, not statements of exact product contents. They do not rank applicants, prescribe outcomes or promise a particular response. Their purpose is to help a team preserve the difference between writing a message, approving its use and completing the next authorized action.
Review the Rejection Pipeline Toolkit and its listed format and scope.