When an application is shortlisted, assign a named person to request the required documents. A status change alone is not a handoff. Start a request log before sending anything, and keep not requested, requested, received and ready for review separate.
A drafted message is not a sent request. A received file is not proof of readiness or a decision to accept the applicant.
Define the trigger and minimum document
For hypothetical training-program application TR-024, written answers support shortlisting, but final review requires one PDF containing a short work sample and a note explaining the applicant’s contribution. These are illustrative requirements, not a universal document standard.
Mina coordinates requests; Joel conducts final reviews. Shortlist approval triggers Mina’s request for that sample, not a full portfolio or unrelated certificates.
Explain this later document requirement during initial intake so applicants know what to prepare.
Verify the private return route before collection
This example assumes an existing private applicant area, not a feature every WordPress form provides. Before collection, have the site administrator test with fictional accounts and files that:
- The intended applicant can submit to the correct application, with that association recorded.
- Signed-out visitors and another applicant cannot access its private records or files.
- Authorized reviewers can retrieve files; unauthorized staff cannot.
- Published format and size limits match what the route accepts.
An application reference helps match records; it is not authentication. If checks fail, keep requests pending while the administrator fixes the route. Agree on an approved alternative for anyone unable to use it; do not default to email attachments.
Assign file-access and disposal responsibility under your team’s retention policy; this guide does not prescribe a retention period.
Send a specific request with a response deadline
Replace this hypothetical message’s document requirements, deadline, file limit and route instructions with your verified arrangements.
Subject: Work sample requested for application TR-024
“Your training-program application has been shortlisted. Before final review, please provide one PDF containing a short work sample and a note explaining your contribution. Exclude confidential client information and other people’s personal details.
“Sign in to the private applicant area on our program website and open the work-sample request for TR-024. Upload one PDF no larger than 5 MB by 19 March 2027 at 17:00 UTC.
“If you cannot use this route or need more time, reply without attaching the sample so we can agree the next step. Shortlisting and document receipt do not confirm admission.”
A recorded send event establishes sending, not inbox receipt. Record available delivery evidence separately; outgoing-mail acceptance alone does not confirm inbox delivery.
Check each returned document before handoff
A located file is received, not automatically ready for review. For each return, Mina must check that:
- The return route’s record connects the file to TR-024 and its signed-in applicant; a filename or typed reference alone is insufficient.
- It opens through the approved viewing process and contains the sample and contribution note.
- Any replacement is identified so Joel knows which version is current.
These are matching and completeness checks, not suitability assessment or security certification. Keep an incomplete return received—correction needed, and record the correction request and its deadline.
Notify Joel only after the checks pass. Mina owns follow-up until he acknowledges the handoff.
Keep a request record through reviewer acknowledgment
Use a restricted manual log connected to the application. Keep files and links that themselves grant file access out of broadly shared sheets.
Every event below is illustrative, not an observed result. All dates are in March 2027 and times are UTC. File locations are recorded in the application’s restricted document record.
- 8 March — Not requested: Shortlist approved; message drafted. Mina owns sending by 9 March. A draft does not advance the state.
- 9 March — Requested: Mina sends the message above at 10:00 and logs the message version and send time. Delivery evidence: mail provider accepted it; inbox receipt unverified. Mina owns checking for a return by 19 March, 17:00.
- 16 March — Received, correction needed: Sample v1 located and matched to TR-024, but the contribution note is missing. Mina requests a replacement and agrees an extended correction deadline of 22 March, 12:00; she owns follow-up then.
- 22 March, 10:00 — Received: Replacement v2 located in the restricted record. Mina owns matching and completeness checks by 16:00 today.
- 22 March, 15:00 — Ready for review: Checks pass; v2 is marked current. Mina notifies Joel and owns obtaining acknowledgment by 23 March, 12:00.
- 23 March, 09:00 — Ready for review; acknowledged: Joel acknowledges. Current next-action owner: Joel. Next action: assess the sample by 25 March, 17:00.
Assign overdue work to the right person
Use the record to assign work, rather than treating every overdue item as applicant nonresponse.
- Unsent: Mina sends the request or coordinates a return-route fix, then sets a usable response deadline.
- Sent, no file located: Mina checks delivery evidence and unmatched submissions before reminding the applicant. Unverified delivery is not evidence of nonresponse.
- Received, unchecked: Mina completes or assigns the checks; do not chase the applicant.
- Correction requested: Mina follows that request’s agreed deadline, recording any extension.
- Ready, unacknowledged: Mina follows up with Joel internally.
Use neutral reminder wording:
“We have not yet matched a work sample to TR-024. If you already submitted it, please tell us approximately when, without attaching another copy. Reply if you need help with the return route or more time.”
Record the next follow-up date. Escalate unresolved cases under the team’s stated admissions policy, not an invented automatic rejection rule.
Rehearse before requesting real documents
Before contacting real applicants, complete one rehearsal:



