Candidate-Friendly Assessment Invitations and Reminders: A Practical Employer Guide
A candidate applies for a role, receives an assessment link and wonders whether the message is genuine. The email gives no company name, the deadline is expressed in an unfamiliar time zone and the sender does not explain what will happen if the link fails. The candidate postpones the test, then misses the deadline.
A candidate applies for a role, receives an assessment link and wonders whether the message is genuine. The email gives no company name, the deadline is expressed in an unfamiliar time zone and the sender does not explain what will happen if the link fails. The candidate postpones the test, then misses the deadline.
That outcome may say more about the invitation than about the candidate's skills. Employers can lose useful applicants when assessment messages are confusing, late, inaccessible or mistaken for spam.
A good assessment invitation tells the candidate what the assessment is, why it matters, what to do next and where to get help. A good reminder provides useful notice without pressure or excessive messaging. This guide covers the full invitation-to-completion journey, with templates, timing examples, operational controls and metrics that help employers improve candidate experience.
An invitation is part of the assessment process
The assessment begins before the first question appears. Candidates must receive the invitation, recognise it as legitimate, understand the requirements and access the test under reasonable conditions.
A clear invitation can reduce preventable non-completion. It cannot make an unsuitable test valid, and it cannot guarantee that every candidate will participate. Some people may decline or withdraw for legitimate reasons. The employer's aim is to offer a consistent, understandable opportunity, not to force completion.
The communication process should match the actual assessment configuration. A beautifully written message becomes misleading if it promises a 45-minute test that takes two hours, a pause feature that does not exist or a deadline that the platform applies differently.
The seven questions every invitation should answer
Before sending a message, check whether a candidate can answer these questions without contacting support:
- Who is inviting me? Name the employer or authorised assessment administrator and the vacancy or programme.
- Why am I receiving this? Explain the assessment's role in the selection or development process.
- What will I do? Describe the skills or task formats in clear, non-technical language.
- How long will it take? State the expected duration and any fixed timer accurately.
- When is it due? Give a clear deadline with date, time and time zone.
- What do I need? Explain supported devices, connection, permitted tools and any preparation information.
- What if I need help? Provide an accessible support and accommodation route, plus next-step information.
A message that answers these questions can be concise. It does not need several pages of recruitment policy pasted into the email. Link to accessible details when necessary, but keep the essentials in the message itself.
Use a subject line that candidates can recognise
Generic subject lines such as “Important Action Required” can look suspicious. A clear subject might be:
Assessment invitation — Customer Operations Analyst — Example Company
A reminder might say:
Reminder: Your Customer Operations Analyst assessment closes Thursday
Use the real employer name and vacancy. Avoid false urgency, exaggerated claims or language that resembles phishing. If an external platform sends the message, explain that relationship in the original application communications so the sender does not appear unexpectedly.
Do not imply that a candidate has already been hired or guaranteed an interview merely because they were invited to an assessment. State the actual selection stage.
A practical invitation template
The following is a model to adapt, not a ready-to-send system message. Replace every placeholder and verify the platform behaviour before use.
Subject: Assessment invitation — [Role] — [Employer] Thank you for your interest in the [Role] position at [Employer]. We would like to invite you to complete an online assessment as part of our selection process. The assessment covers [brief description of relevant skills]. It contains [number] questions and is expected to take [duration]. Please complete it by [day, date, time and time zone] using your personal invitation link: [secure link]. Before you begin, review the instructions and permitted materials here: [preparation link]. If you need an accessible arrangement or experience a technical problem, contact [verified support channel]. Completing the assessment does not guarantee an offer. We will update you about the next stage through [communication channel] by [realistic timeline, if known]. Thank you, [Recruitment team and employer].
The employer should not include a password, sensitive identity documents or other confidential candidate information in the email. The link should use an appropriate secure access mechanism and avoid exposing results to someone who forwards the message.
Make deadlines unambiguous across countries
International recruitment creates a common problem: “Complete by Friday at 5 pm” may mean different things to people in different time zones.
A safer format is: “Deadline: Friday, 23 October 2026, 17:00 West Africa Time (UTC+1).” That date and time are illustrative. The platform must enforce the same instant, and any candidate-local display should be tested carefully, including daylight-saving changes in other regions.
If the test window is described as “open for five days”, specify whether the five days begin when the email is sent, delivered, opened or accepted. These are not equivalent events. A candidate should not lose time because an invitation sat in a mail queue.
For a timed assessment, distinguish the completion deadline from the test duration. If a candidate starts a 45-minute test ten minutes before the window closes, what happens? The invitation must reflect the actual system rule, whether the session is blocked, allowed to finish or ended at the deadline.
Design the reminder sequence around candidate usefulness
There is no universal ideal number of reminders. Too few may leave candidates unaware of an approaching deadline; too many can feel like pressure or spam.
For a fictional five-day assessment window, a proportionate sequence might be:
| Stage | Message purpose | Example timing |
|---|---|---|
| Initial invitation | Explain assessment, deadline and support | When candidate becomes eligible |
| First reminder | Offer a helpful nudge and preparation link | Around the middle of the window |
| Final reminder | State exact closing time and support route | About 24 hours before closing |
| Closure notice, if needed | Confirm window closed and explain next steps | After deadline |
These are editorial examples, not requirements. For a short two-hour window, this cadence would be inappropriate. For a month-long programme, one mid-window reminder may be too early to be useful. Adapt to the recruitment timeline, local communication expectations and candidate preferences.
Stop ordinary reminders once the candidate has completed the assessment or withdrawn. A reminder that arrives after completion damages confidence and can generate unnecessary support tickets. Allow for status-update delays and use a final status check immediately before sending.
A respectful reminder template
Subject: Reminder — [Role] assessment closes [date] This is a reminder that your online assessment for [Role] at [Employer] is available until [day, date, time and time zone]. If you have already completed the assessment, thank you; no further action is required. If not, you can use your secure invitation link from the original email or [verified access method]. The assessment is expected to take [duration]. For technical assistance or accessible arrangements, contact [support channel] before the deadline where possible. We understand that candidates may choose not to continue with an application. Regards, [Recruitment team].
If the system cannot reliably determine completion status, avoid falsely saying “Our records show you have not started.” A neutral reminder is safer than an incorrect personalised assertion.
SMS, email and messaging apps: choose the channel carefully
Email is useful for detailed instructions and links. SMS may be effective for a brief reminder, but it can be expensive, easily forwarded and unsuitable for lengthy information. Messaging apps may be familiar to some candidates but raise consent, privacy and recordkeeping considerations.
Use channels consistent with the application process, the candidate's reasonable expectations and applicable communication and data-protection rules. Do not automatically add applicants to unrelated marketing lists. Recruitment communications should not be repurposed for promotional messages without an appropriate lawful basis.
Where a candidate has requested an accessible communication format, provide it. A message should not rely solely on an image containing text. If SMS is used, include the employer's identity and a safe way to access the official invitation rather than sending ambiguous shortened links.
Avoid creating a phishing-like experience
Candidates are right to be cautious about unexpected links. Employers can make legitimate messages easier to verify:
- Use a consistent, recognisable sender identity and employer name.
- Explain in the job application process that an assessment invitation may come from an authorised provider.
- Use a secure domain and avoid unnecessary redirect chains.
- Do not ask candidates to reply with passwords, payment-card details or sensitive documents.
- Provide a way to verify the invitation through the employer's established recruitment contact.
- Test the invitation on common email clients and mobile screens.
No invitation can be guaranteed to reach the inbox. Delivery depends on the recipient's provider, spam filtering, domain configuration and other factors. Monitor bounces and failures rather than treating “sent” as proof of receipt.
Accessibility is part of communication quality
An assessment invitation should be understandable with assistive technology and should provide an accessible route to request support. Use descriptive link text, clear headings where the format permits, readable contrast and short paragraphs. Avoid sending crucial instructions only as text embedded in an image.
A candidate with a disability should not have to disclose a diagnosis to an untrained hiring manager to ask about an adjustment. Direct requests to an appropriate confidential process. If an accommodation changes timing or the assessment window, ensure that reminder messages reflect the approved arrangement and do not expose it to other recipients.
Also consider language clarity. Plain language benefits many candidates, including people applying in a second language, without reducing the assessment's intended challenge. The invitation is not the place to test complex reading comprehension unless that is explicitly part of the assessment itself.
Technical failures require a clear support path
Every invitation should explain what to do if a link fails, the candidate loses connectivity or a session ends unexpectedly. The support team should know which information is needed to investigate, such as an assessment reference and approximate incident time, without asking candidates to send passwords or unnecessary personal data.
Do not promise an automatic retake unless the policy and system support it. A reported incident should be reviewed under consistent rules. The candidate should receive acknowledgement and an explanation of what happens next.
If a platform outage affects many people, pause reminders that falsely imply the candidate is at fault. Send a correction with the revised arrangements and document the change. Where a deadline is extended, communicate the new date, time and time zone explicitly.
How to measure invitation effectiveness responsibly
The most useful metrics describe the journey from invitation to completion without confusing operational problems with candidate ability.
A fictional employer sends 400 invitations. Of those, 260 candidates start and 240 complete the assessment.
- Start rate: 260 ÷ 400 × 100 = 65%.
- Completion rate among starters: 240 ÷ 260 × 100 ≈ 92.3%.
- Overall completion rate: 240 ÷ 400 × 100 = 60%.
These three figures answer different questions. A high completion rate among starters does not mean invitations are reaching everyone effectively. A low start rate may reflect delivery failures, candidate withdrawal, timing, role interest or other causes.
Now imagine a later campaign sends 400 invitations and records 290 starts and 270 completions. The start rate is 72.5%, completion among starters is approximately 93.1%, and overall completion is 67.5%. The overall rate is 7.5 percentage points higher than in the earlier campaign.
That comparison alone does not prove the revised reminders caused the increase. Different roles, candidates, recruitment periods or platform conditions may explain some of the change. Use the metrics to ask better questions and investigate, not to claim guaranteed improvement.
What metrics should not be overinterpreted?
An email-open rate may be unreliable because some mail clients block or prefetch tracking pixels. A link click does not establish that a candidate began the assessment. A bounced message is not the same as a candidate declining. A candidate who does not complete may have chosen to withdraw for a legitimate reason.
Where lawful and appropriate, review patterns in delivery failures and support requests across devices, languages and regions. Small groups can produce unstable percentages; protect privacy and avoid drawing sweeping fairness conclusions from a handful of records.
The employer should collect only the data needed for recruitment operations and evaluation, keep them for a defined period and restrict access. Do not build unnecessary behavioural profiles from email tracking simply because the technology permits it.
Build a simple invitation quality-control process
Before launch, have one person check the content and another test the actual link flow. The second person should behave like a candidate using a common device rather than relying solely on an administrator preview.
Check that the employer name, role, number of questions, duration, deadline and time zone are accurate. Confirm that the login route works, the help contact is staffed or monitored, the preparation link opens, and the privacy notice is accessible. Test whether a completed candidate is removed from the reminder queue.
Run a dry test for an expired invitation, an already-completed assessment, an accommodation-adjusted deadline and an interrupted session. These edge cases often reveal more than a perfect-path test.
For bulk invitations, verify the recipient mapping before sending. A candidate should not receive another person's assessment link or personal details. Use appropriate access controls and logs to investigate mistakes without exposing the whole candidate list.
A five-stage operational workflow
Stage 1 — Prepare. Confirm the approved assessment, candidate eligibility, window, communication rules and support arrangements. Separate assessment invitations from marketing communications.
Stage 2 — Send. Deliver the initial invitation through an authorised channel. Record the message version, intended recipient and delivery outcome where available.
Stage 3 — Support. Respond to access problems, accommodation requests and questions. Escalate technical incidents using a documented process.
Stage 4 — Remind selectively. Check current status before each reminder. Exclude completed, withdrawn and otherwise ineligible candidates. Use accurate deadlines and respect approved adjustments.
Stage 5 — Close and review. Confirm completion records, communicate next steps, review delivery and support metrics, and improve the next campaign. Do not infer candidate ability from non-completion without considering the circumstances.
This workflow can be implemented with simple tools or a larger assessment platform. The principle is the same: candidates should receive timely, accurate information and a fair opportunity to respond.
Common mistakes to avoid
Sending the link without context. The candidate may not recognise the invitation or understand its purpose.
Using an ambiguous deadline. “Tomorrow evening” is not a reliable instruction for international candidates.
Overloading candidates with reminders. Repeated urgent messages can undermine trust and may violate communication preferences or applicable rules.
Promising unsupported features. A message should never say that the timer pauses automatically unless this has been verified.
Mixing recruitment and advertising. An assessment invitation should not become a vehicle for unrelated promotions.
Treating non-completion as a failed test. Someone who never accessed the assessment has not demonstrated low skill on its questions.
Ignoring status synchronisation. Candidates who already completed should not keep receiving “you have not started” messages.
Publishing private data in bulk emails. Recipient lists, tokens and results require careful handling.
Frequently asked questions
How many reminders should an employer send?
There is no universal number. Choose a proportionate cadence based on the length of the window, candidate expectations and communication rules. For a five-day window, one mid-window and one final reminder may be reasonable, but the system should stop after completion or withdrawal.
Should reminders contain the candidate's assessment score?
Normally no. A pre-completion reminder concerns access and deadlines, not results. Outcome communications should follow a separate, secure process.
Can we send reminders by WhatsApp or SMS?
Potentially, where appropriate and lawful, with attention to candidate expectations, privacy, delivery and recordkeeping. Use recognisable sender details and avoid ambiguous or suspicious links.
What if the candidate says the invitation never arrived?
Check delivery records and the address or contact information used. Offer a fair remedy under the documented policy where a delivery failure is established. Do not treat “sent” as proof that the candidate received or read the message.
Should we include sample questions in the invitation?
A link to a separate, non-secure preparation guide is usually clearer. Do not include protected live items or answer keys. Make official preparation resources available consistently.
What if candidates are in different time zones?
State an unambiguous deadline with a named time zone and verify how the platform converts it. Avoid relying only on a local-time display without testing daylight-saving and locale handling.
Can an employer automatically reject candidates who do not start?
An employer may have a documented process for incomplete applications, subject to applicable law and fair administration. It should first consider delivery failures, approved accommodations and reported incidents. Non-start is not a test score.
Should the invitation promise a particular result date?
Only if the employer can reasonably meet it. Otherwise explain the expected next step and communication channel without inventing certainty.
Related guides and reference standards
Employers may also consult Candidate Preparation Guides Without Compromising Assessment Integrity, Accessible Online Assessments and Explaining Assessment Outcomes and Candidate Appeals. These internal routes are proposed and must be checked against CMS slugs before import.
The International Test Commission Guidelines on Test Use and the ITC/ATP Guidelines for Technology-Based Assessment, updated July 2025 offer broader professional context for appropriate digital assessment administration, fairness, accessibility and privacy. They do not prescribe a single reminder cadence for every recruitment process.
Conclusion
An assessment invitation should remove uncertainty about the process, not create it. Clear deadlines, trustworthy links, accessible support and respectful reminders help candidates decide when and how to participate. Employers should judge their communication system by whether it provides a consistent opportunity and reliable information—not by how many messages it can send. A candidate-friendly process begins with an invitation that is accurate, understandable and easy to act on.
