Recruiter resources

Candidate assessment invitation email: templates and recruiter checklist

Editable invitation, reminder and interruption-response templates, plus a practical check of deadlines, candidate access and assessment instructions.

By AssessEngine · Published · Updated

An open assessment invitation envelope beside a clock and instruction sheet on a mint-green desk
Conceptual editorial illustration, not an AssessEngine interface or an actual candidate invitation.

What should an assessment invitation email include?

The invitation is the candidate’s working instruction for the next hiring stage. It should answer what they have been invited to do, how to access it, when it must be finished and where to get help. Use the same core instructions for candidates completing the same assessment, with any agreed individual arrangements communicated privately.

CIPD’s selection guidance recommends telling candidates what to expect, including the assessment type, time involved and technology used. SHL’s candidate help also directs candidates to the access link and instructions in their invitation. The templates below are original recruiter resources; they are not copied vendor emails or messages automatically generated by AssessEngine.

Confirm each field against your live assessment setup
Invitation fieldWhat the recruiter should confirm
Employer and roleThe recognisable hiring organisation, job title and reason for the assessment.
Assessment scopeThe sections or task formats and expected time, without exposing confidential test questions.
AccessThe approved link, any required login details and the expected sender or support domain.
TimingThe opening window, duration, completion deadline and an explicit time zone.
Device and materialsThe supported setup and exactly which calculators, notes or other aids are allowed.
Monitoring and helpEnabled monitoring, relevant candidate information, support hours and a contact for access needs.

An assessment invitation email template you can adapt

Replace every bracketed field before sending. Remove instructions that do not apply, and add a support contact that is actually monitored during the assessment window. The download at the end includes this invitation, a reminder and an interruption-response template in editable plain text.

Subject: [Company] assessment invitation — [Role] — complete by [Date, time and time zone]

Hello [Candidate first name],

Thank you for your interest in the [Role] position at [Company]. The next stage is an online assessment covering [Sections or task types]. We will review the results alongside the other information gathered during our hiring process.

Please access your assessment using [Verified assessment link]. [Add only the login or registration steps required by this setup.] The assessment is available from [Opening date, time and time zone]. Allow [Expected assessment duration] plus time for the required setup, and complete it by [Completion date, time and time zone]. [Explain any section timers, breaks or latest-start rule you have confirmed.]

Use [Confirmed device and browser requirements]. You may use [Permitted materials]. [Explain enabled monitoring and provide the relevant candidate information or privacy link.] Read the on-screen instructions before starting.

If you need an adjustment or help accessing the assessment, contact [Monitored contact] before [Relevant date]. If a technical issue occurs, follow [Confirmed interruption instructions] and contact [Support route and hours]. Do not share your access credentials.

After completion, [Explain the confirmed next step and communication route, without promising an unagreed response time].

Thank you, [Recruitment team / Company]

How do you explain the deadline, test window and duration?

These are different instructions. The test window says when access is available. The duration says how much working time the configured assessment allows. The completion deadline says when the attempt must be finished. Ask the platform team how the closing time affects an attempt already in progress; do not assume the candidate can finish after access closes.

Fictional planning example: an assessment allows 40 minutes of working time and must be completed by 5:00 pm IST on 2 November 2026. A candidate starting at 4:50 pm has only 10 minutes before that deadline. An invitation that says only “take the test before 5 pm” leaves an important ambiguity. State that the attempt must be completed by the deadline and allow an appropriate setup buffer.

For candidates in different locations, write the date, time and named time zone rather than “tomorrow evening” or a time without a zone. Review the invitation and platform configuration together so the message does not promise a different access window.

What should you tell candidates about devices and proctoring?

Describe the controls enabled for this assessment and any permissions candidates need to grant. Do not paste every feature a platform offers into the invitation. If the assessment records webcam snapshots or tab changes, explain the relevant instructions and how the candidate can ask questions before starting.

AssessEngine’s public features page describes browser access, invitation or public-link options, and configurable opening and closing times. Its proctoring page describes activity records for recruiter review. Confirm the device, browser and monitoring combination for your own setup; a general mobile-access claim does not establish that every configured assessment works on every device.

Give candidates a private contact for access or adjustment requests. Ask for information needed to arrange participation; do not ask them to send sensitive personal documents to a public form or shared mailing list. Explain permitted materials and how to report an interruption instead of relying on “do not cheat” as the only instruction.

What should an assessment reminder email say?

Check the candidate’s current status before sending a reminder. A person who has completed the assessment should not receive a message saying they have not started. A reminder is a communication example here, not a claim that AssessEngine automatically schedules reminders.

Subject: Reminder — [Company] [Role] assessment closes [Date, time and time zone]

Hello [Candidate first name], our records currently show that your [Role] assessment is [Verified status]. If you intend to continue, please complete the assessment by [Deadline and time zone], allowing [Duration] plus the required setup time. Your access link is [Verified link].

If you have already completed it, or need help accessing it, contact [Monitored support contact]. We will check the attempt status before advising on any further action. Thank you, [Recruitment team / Company].

Keep the original deadline and instructions unless a change has been authorised. If the deadline changes, make the platform setting and message agree, and explain which candidates the change applies to.

How should recruiters respond to an assessment interruption?

Do not promise a reset, extra time or a free retry before checking the attempt record and the agreed process. Confirm who can review the issue and what evidence is available. Keep technical support separate from the interpretation of assessment or proctoring results.

Original response template: “Thank you for reporting the interruption. Please share the approximate time and the on-screen error text through [Private support route], without sending passwords or test questions. Our team will review the attempt status and confirm the next step. Please follow the stated support instructions before starting another attempt.”

Adapt that response to your actual support process. If a retry or extension is approved, record the decision and send the candidate the verified new instructions. Do not describe an approved exception as an automatic entitlement for every attempt.

A recruiter checklist before sending assessment invitations

Run one approved pilot through the same invitation and access route candidates will use. This is a delivery check, not proof of test validity or a guarantee that no candidate will encounter a problem.

  • Open the link from the draft invitation and confirm the employer, role and intended assessment.
  • Check any login or registration steps, and remove all unfilled template placeholders.
  • Compare the stated sections, duration, opening time and completion deadline with the actual configuration.
  • Verify the supported device, browser, permissions and permitted materials for this setup.
  • Confirm that monitoring information, access-needs contact and interruption instructions are understandable.
  • Complete an approved pilot attempt and have a recruiter inspect the resulting report.
  • Assign an owner to monitor support, verify status before reminders and communicate any approved changes.

How can you review the invitation process after a hiring round?

Keep a simple operational log: the invited cohort, invitations sent, access problems reported, verified starts, verified completions and unresolved support issues. Separate technical delivery issues from withdrawals or decisions not to participate. Do not label an unanswered invitation a platform failure without investigating it.

When calculating completion, state the denominator: completed attempts divided by starts answers a different question from completed attempts divided by invitations. Reconcile duplicate invitations, approved retries and changes to the cohort before comparing rounds. The editable resource includes a review log; this article does not claim those metrics are automatically available as a single AssessEngine report.

Use the next review to fix specific ambiguities in your message or setup. If candidates repeatedly ask whether the deadline means start or finish, change that instruction before the next round rather than adding a longer generic FAQ.

What should you check in an AssessEngine invitation walkthrough?

Bring the role, candidate volume, assessment sections, planned dates and any proctoring requirements. Ask the team to demonstrate the candidate access route and how a recruiter will inspect attempt status and results for that configuration.

Use the editable templates to prepare your own candidate communication. Confirm the sender, support responsibilities, timing behaviour and exception process before launch. AssessEngine’s publicly described access and reporting features do not imply an email editor, automatic reminder schedule or guaranteed email delivery.

Common questions

What should the subject line of an assessment invitation email include?

Identify the employer and role, describe it as an assessment invitation, and include the completion deadline where useful. Use recognisable wording and confirm that the email body and configured deadline agree.

Should the invitation include the actual assessment questions?

Describe the sections or task types and any approved preparation material. Do not include confidential live test questions or answer keys in an invitation.

Is the assessment deadline the same as the time limit?

No. The time limit is the configured working duration; the deadline is the required completion time. Explain the access window, time zone and how closing time affects an attempt already in progress.

Can the same invitation template be used for experienced and graduate hiring?

The structure can be reused, but change the role, task formats, sections, duration and practical requirements. The instructions must describe the actual assessment that each group will take.

Can we automatically resend invitations to everyone who has not completed?

Check the supported communication workflow and verify candidate status first. Separate people who have not started from interrupted attempts, approved extensions and completed candidates. This guide does not establish automatic reminder functionality in AssessEngine.

Does a technical interruption mean the candidate should receive another attempt?

Review the attempt record and the agreed support and retry process before deciding. Confirm an authorised next step; do not promise a reset or retry solely from the email template.

Sources and further reading

Explore AssessEngine

Have a correction or a question? Contact the AssessEngine team and include this article's title.