An ATS demo test script for hiring teams

A sales demonstration shows the route someone has rehearsed. Your ATS trial should also cover the mistakes and interruptions your team encounters during a normal week.

Send the vendor a short scenario beforehand, then ask for time to complete it yourself. Use fictional information so the evaluation does not expose candidate data.

Prepare a vacancy and several awkward cases

Use a realistic job description with a location, working arrangement, and clear requirements. Create fictional applications that include a text-based PDF, a duplicate email address, an incomplete profile, and a person applying for two jobs.

Make one candidate withdraw during the exercise. This tests whether the software distinguishes an application outcome from the person's wider relationship with your company.

Do not make the test depend on hidden features. Ask the vendor which capabilities are included in the quoted plan and which require another module.

Give each user a task

User	Task	What to observe
Recruiter	Publish the test job and review an application	Required setup and manual corrections
Hiring manager	Find the shortlist and leave evidence	Navigation without coaching
Interviewer	Review the assigned candidate	Access to unrelated or sensitive records
Administrator	Export the test records	Completeness and usable file structure

Keep screen recordings only if everyone involved agrees and the trial terms allow them. Written observations are usually enough to compare options.

Test what happens after a mistake

Move a fictional candidate to the wrong stage. Check whether you can correct the stage, whether a message has already been sent, and whether the history explains what happened. A reversible status change does not necessarily reverse an external email.

Try an invalid upload and a lost connection while completing the application. Look for clear errors, preserved form entries, and an unambiguous submission confirmation.

Ask how administrators handle an unavailable integration or a failed import. A useful answer identifies an owner and a recovery procedure.

Record evidence immediately

For every task, write one of four outcomes: completed independently, completed with help, unavailable in the plan, or unresolved. Keep your requirement wording identical across vendors.

Finish by exporting your synthetic records and asking how the trial account is closed. Discuss the unresolved items before the quote expires. If a requirement affects your actual hiring process, get the answer in writing rather than relying on a future roadmap item.

Further reading

• The Easiest ATS to Use and Implement in 2026: What Actually Matters - Workable
• Best ATS for Small Business: Selection Guide | JazzHR

Related guides

• Choose an ATS for your team
• Check hiring-team permissions