On Monday a candidate receives a case assignment for a consultant role. Nobody says when it is due, so she sends it back on Thursday evening. The file lands in the inbox of a hiring manager who is travelling. A week later the recruiter asks how it went and hears “looked fine, I think”. By then the candidate has accepted another offer, and the only trace of the test is an attachment in someone’s mailbox. This article explains why every assessment or test stage in an Applicant Tracking System needs a deadline and a recorded result: what both mean, where they live on the stage, who records the result and how that result feeds the next step in the process.
The stage looks different per segment. Recruitment agencies often send a skills test or case before presenting a candidate to a client. Staffing teams use short practical checks, language tests or safety tests at volume. Secondment firms assess technical knowledge before someone is placed at a client site. Executive search consultants work with management assessments and psychometric reports from external providers. In-house recruitment teams depend on hiring managers who have to review a work sample or case.
Why assessment stages stall without a deadline
- The candidate does not know when the test is due, so it is postponed in favour of other applications and interviews
- A finished test has no review date, so it waits until the assessor happens to have time
- Reminders depend on the memory of one recruiter instead of a date on the record
- Candidates who never start the test stay in the stage for weeks, which makes the pipeline look fuller than it is
- Good candidates drop out because they hear nothing after putting hours into a case
An assessment asks the candidate for real effort. A process that then goes quiet costs you exactly the people who took the effort seriously.
What “a deadline and a recorded result” means
The stage needs two dates and one result:
- A submission deadline for the candidate — a clear date by which the test, case or assessment has to be completed, sent along with the invitation and agreed with the candidate if the timing is tight
- A review deadline for the assessor — a date by which the completed test has been assessed, for example two working days after submission, so the next step does not wait on one person’s calendar
- A recorded result — a fixed outcome such as passed, doubt or not passed, or a score on the criteria agreed in advance, with a short piece of evidence, the name of the assessor and the date, and where relevant the report or file attached to the candidate record
The result belongs in a structured field, not only in an email or a comment. A structured result can be filtered, counted and compared between candidates; a sentence in a mailbox cannot.
Where it lives: on the assessment stage itself
Set up the assessment or test as its own stage in the pipeline of the Applicant Tracking System, with the deadlines and the result as fields of that stage. When a candidate enters the stage, the submission deadline is set and becomes the next action date on the record. When the test comes in, the review deadline takes over. A candidate can only leave the stage once a result has been recorded, or once the candidate has withdrawn with a recorded reason.
Because the dates are on the stage, the system can warn you when a deadline passes. The same logic as alerts for candidates stuck in a stage applies here, only with a sharper limit: a test that is two days overdue deserves a reminder, not a weekly review. It works the same way as the first review deadline for new applications: the clock starts automatically, not when someone remembers.
Who records the result
Name one assessor per test when it is sent, not afterwards. That can be the recruiter, a hiring manager, a specialist at the client or an external test provider. The rule is simple: whoever assesses the test is responsible for the result in the record, before the review deadline.
- If an external provider delivers a report, the recruiter records the outcome and attaches the report on the day it arrives
- If a hiring manager reviews the work, a reply deadline for hiring-manager feedback keeps the review from slipping
- If several people assess the same case, each scores on their own against the same criteria, just like a shared interview scorecard, before the results are combined
Agree the criteria and the pass level before the first test goes out. A test that is judged on criteria invented after reading the answers is not an assessment; it is an opinion.
How the result feeds the next stage, the interview and rejection reasons
A recorded result makes the next decision traceable. It can be held against the written entry criteria of the next pipeline stage: did the candidate meet the agreed level, yes or no, and on which evidence. If the next step is an interview, the interviewers can prepare with the test result in front of them and refer to it in the written interview outcome, for example by asking about the weakest part of the case.
If the candidate does not pass, the recorded result is the basis for a standardised rejection reason and for clear feedback to the candidate. Because test results are personal data, they follow the same retention date as the rest of the candidate record.
Common mistakes to avoid
- “Send it back when you can” — without a submission deadline, the test competes with everything else in the candidate’s week and usually loses
- A deadline for the candidate, none for the assessor — the candidate delivers on time and then waits ten days for an answer
- The result only in email — nobody else on the team can see it, and it disappears when a colleague leaves
- Only a pass or fail without evidence — a verdict nobody can explain cannot be used in a client presentation or in feedback to the candidate
- Different tests and pass levels for the same role — candidates for one vacancy can no longer be compared
- Candidates who never start stay in the stage — close them out with a recorded reason after the deadline and a reminder, so the pipeline shows reality
Measure it with your own data
Count from your own records: what share of candidates in an assessment stage has a submission deadline, what share of tests is completed on time, how many working days pass between submission and a recorded result, what share of results includes evidence, and how many candidates withdraw during the assessment stage. Report the number of candidates behind each figure. Do not rely on general claims about faster hiring; your own counts show where the assessment stage really waits.
A practical start
- Create one assessment or test stage per pipeline that uses tests, instead of hiding tests inside an interview stage
- Set a standard submission deadline and a standard review deadline, and let them be adjusted per candidate with a note
- Name the assessor when the test is sent
- Agree the criteria and the pass level with the hiring manager or client before the first test goes out
- Make the recorded result with evidence a requirement for leaving the stage
- Review once a month how many tests were late, how long reviews took and how many candidates dropped out
A test only counts once the result is written down
Candidates put real time into an assessment. A clear deadline shows them you take that time seriously, and a recorded result makes sure their effort actually informs the decision. Explore the product or book a demo — we show how pipeline stages, deadlines and candidate records are set up in BoldATS for your segment.