Before a timed test or interview, check job duties, timing, access, disability questions and the process for accommodation requests.
Key takeaways
- Match each test item to a core job duty.
- Write down why the test needs a clock.
- Check the room, device and format before invitations go out.
- Review disability questions before asking them.
- Name a person to handle accommodation requests.
Title I of the ADA "makes it unlawful for an employer to discriminate against a qualified applicant or employee with a disability," and the EEOC's guidance on job applicants and the ADA applies that rule to hiring. A timed test is part of hiring.
Most unfair screens are not designed to be unfair. They come from habits: a test copied from an old version, a clock nobody questioned, a room that gets hot in the afternoon, or a casual question about someone's health asked before the offer. The five checks below are meant to run once for each test or question set, before the first applicant sits down. Each one connects to a point in the EEOC guidance and ends with a step you can take.
You do not need a legal background to run these checks. You need the job's duty list, the test itself, a walk through the room, and a clear path for requests. Small firms often feel this most, because the recruiter may also be the test writer, the room booker, and the person who answers the applicant's email. That is a lot to hold at once, which is why a short written checklist beats memory. Most of the work happens before the first invitation goes out, when changes are cheapest and easiest to explain.
Does the test measure what the job actually needs?
Only if you can name the job duties it measures, because the ADA's standard is built around those duties. The EEOC guidance says an applicant with a disability must be able to perform the "essential functions" of the job, which it describes as the fundamental duties of the position, with or without a reasonable accommodation. That gives you a working test for each item on your test.
Start by writing a short list of the core duties for the role. Do it with the person who will manage the hire, not alone at your desk, because managers often know which tasks matter most day to day. Then go through the test section by section and ask one question about each item: which duty does this measure? If the answer is "none," or "it seemed like a good question," remove it or replace it.
Skills tests drift over time. A question written for a senior role gets reused for a junior one. A coding exercise picks up a niche library because someone liked it. A writing sample grows a word limit that nobody remembers choosing. Each drift adds a requirement the job may not have. An unneeded requirement is hard to defend if an applicant challenges it, and it can screen out someone who could do the work with a reasonable accommodation.
Pay attention to the difference between a skill and a method. If the job requires clear written reports, a writing task measures that skill. If the job does not require writing quickly under pressure, a timed essay measures something else, and it may be the method, not the skill, that filters people out. The next check deals with that problem directly.
Watch for duties you have assumed rather than written down. A job posting may say "strong communicator," but the test might mainly measure how fast someone types. Compare the test with the posting, too. Applicants read the posting to decide whether to apply, and a test that asks for skills the posting never mentioned is a surprise they cannot prepare for.
Two reviewers catch more gaps than one. Ask someone who did not write the test to score a sample set of answers and explain what they took from each part. If they cannot tell you what a section tested, the applicant will not know either.
Consider how the test scores answers as well as what it asks. A rubric that rewards a particular phrasing, a particular tool, or a particular background can measure familiarity rather than ability. Write the scoring criteria next to each duty, and check that the criteria would reward a correct answer given in a different but valid way. Use an interview scorecard to organize those criteria.
Keep the duty list with the test file. If an applicant asks why a part of the test exists, you can point to the duty it measures, and you can change the test later without guessing what it was for.
Is the time limit really part of the job?
Not always, and if you cannot explain the clock in a sentence, it is fair to question it. The EEOC gives a plain example: "A 30-minute timed written test may pose a problem for a person whose learning disability requires additional time." ( EEOC guidance) The example does not set a rule for your test. It shows how a clock can become a barrier when it measures something other than what the job needs.
A time limit is a choice, and you should be able to say what it protects. Ask three questions. Does the job require quick work under a deadline in real conditions? Is speed itself one of the essential duties, or is it standing in for accuracy, judgment, or confidence? If you removed the clock, could you still measure the skill you care about?
A dispatcher who must sort incoming calls in real time may have a reason for a clock; check which duty it measures. A bookkeeper who reconciles accounts may not, unless speed appears in the written duties. If the clock is needed, write that down in the job posting and in the test instructions, and explain the reason in one plain sentence. Applicants who know why a test is timed can decide whether to apply and how to prepare, and they can ask for an accommodation before the day rather than during the test.
If the clock is a stand-in, you have options: an untimed version, a longer window, or a work sample the applicant completes within a set period. Choose the option that still measures the skill. Switching formats before anyone asks is easier than explaining a rejection afterward.
An untimed version has trade-offs of its own. It can make it harder to compare applicants on a single number, and it may invite more time than you planned for. If you choose it, set a clear end date for the work window, state it in the invitation, and score every applicant against the same rubric.
Be honest about what a timed score tells you. It shows how an applicant performed under that clock, on that day, in that room and that noise. It says little about how the person will do in a normal workday, which usually lets people pause, check notes, and come back to a problem. Use that gap as a reason to test in a format closer to the work when you can.
When an applicant asks for more time, do not read the request as an attempt to gain an advantage. The EEOC's timed-test example concerns a possible barrier for someone with a learning disability who needs additional time. The question to ask is whether the extra time lets the applicant show the same skill the job needs. If it does, the request deserves serious consideration, with the same review as any other accommodation request, which the last check covers.
Document the decision. Write one line in the test file: the duty the clock supports, or the reason you removed it. A short note turns a judgment call into something you can explain, and it helps the next person who edits the test.
Illustrative example: reviewing a writing test
The team matches each question to the duty of writing clear reports, then finds no written duty requiring speed. It chooses an untimed work window, states the end date in the invitation and keeps the same scoring criteria. The test file records why the clock was removed.
Are the room, the device and the format workable for everyone?
Check the conditions around the test as carefully as the questions, because the conditions can be the barrier. The EEOC describes an applicant named Tara who has multiple sclerosis, and it says that condition makes the applicant "unable to tolerate prolonged exposure to temperatures in the 90's." ( EEOC guidance) The example is about a hot room, not about a question on the test. That is the point. A test can be fair on paper and still be unworkable in the room where it is taken.
Visit the room yourself at the time of day the test will run. Note the temperature, the light, the noise from the hallway or the office, and where people sit. Check whether applicants can stand, move around, or take a short break, and whether a break stops the clock. If the test runs on a computer, check screen size, text size, and whether the page works with the zoom and reader tools an applicant may already use. Ask your test vendor or your IT team what the platform allows, and write the answers down.
Plan for alternatives before you need them. The easiest option is a second room with better conditions, a different desk or chair, or the same test on a different device. Decide in advance who can approve these changes, so no one has to improvise in front of an applicant. Leave some slack in the schedule too, so an applicant who needs a break or a slower start does not throw off the whole day.
Tell applicants what to expect. The invitation should say how long the test runs, whether a clock is visible, whether they can take breaks, what the test is for, and who to contact before the day. Clear information lets an applicant ask for what they need early, when you have time to arrange it, and it reduces surprises for everyone else too.
Think about format. A test that works only in one browser, only with a mouse, or only with a particular keyboard layout excludes people for reasons that have nothing to do with the job. If the job does not require that setup, change it. If it does, say so in the posting and be ready to explain why.
Interview rooms need the same review. If an interview takes place in a building without a step-free entrance, or in a room where an applicant cannot hear clearly, the interview has the same problem as a test. Walk the route an applicant will take from the lobby to the room, and check the signage and the seating before the day.
When is it safe to ask about a disability?
Before a job offer, you generally cannot ask about a disability, and the exceptions the guidance describes in its Question 15 are the ones to check before you ask anything that touches on health. The EEOC states the general rule this way: "Except as explained in Question 15 below, an employer cannot ask questions about an applicant's disability either because it is visible or because the applicant has voluntarily disclosed a hidden disability." ( EEOC guidance) In practice, check those exceptions before commenting on a visible condition or asking follow-up questions about a disclosed disability.
After an offer, the rules loosen, with one condition. The EEOC says: "An employer can ask all of the questions listed in Question 9, and others that are likely to reveal the existence of a disability, after it extends you a job offer as long as it asks the same questions of other applicants offered the same type of job." ( EEOC guidance) The key word is "same." Write the list once, use it for each hire in the same type of job, and keep the answers separate from the hiring decision. A single question asked of only one person can look targeted, even when you meant nothing by it.
Asking about accommodation is its own topic. The EEOC points readers to a separate discussion of employers asking about an applicant's need for reasonable accommodation for the job, in its Question 16. ( EEOC guidance) Read that section before you write the line in your invitation that says "tell us if you need anything for the test." Your wording should fit what the guidance describes, and the line should lead to the process in the last check, not to a question about the applicant's health.
Train everyone who talks to applicants, including reception staff and the people who run the test room. A casual remark from someone outside the hiring team can create the same problem as a formal question.
Do not guess at what someone needs based on how they look or sound. Guesses are where stereotypes slip into decisions. Let the applicant tell you what they need, and let the job's duties decide what matters.
Keep your questions tied to the job. Asking about an applicant's medication, medical history, or time off for treatment is a health question, even when it sounds casual, and it does not help you judge a skill. If you find yourself wanting that information, stop and ask whether the job's duties need it. Usually they do not.
What do you do when an applicant asks for an accommodation?
Send the request to one named person, give it a real look, and do not turn it down on the spot. The ADA bars discrimination against a qualified applicant with a disability, so a quick refusal without consideration is the kind of decision that can later look like discrimination. ( EEOC guidance)
The same guidance sets the outer limit: an employer "does not have to provide a reasonable accommodation that will cause 'undue hardship,' which is significant difficulty or expense." ( EEOC guidance) Read that definition closely. Whether a given change meets that definition depends on the circumstances, so judge each request against it rather than assuming it does or does not.
Start by naming one person who takes accommodation requests, and put that person's contact in every test invitation. Ask the applicant what they need and what would make the test workable for them, since they often know. Then check the request against the duty list from the first check. If the request changes the method but not the skill, it is often easy to agree to. If it seems to change the skill itself, bring in the hiring manager and talk through alternatives that still measure the same duty. Use the accommodation request process to organize the review.
If the requested option is too costly or hard, do not stop there. Look for another option that still gives the applicant a fair chance, and explain your reasoning in writing. A written explanation helps the applicant understand where they stand, and it shows the firm considered the request.
Tell the applicant what happens next. Say who will reply and roughly when, in plain words. If the team needs longer to decide, say so, and say what you are checking. Silence after a request is often read as a no, even when it is not.
If you decline a request, say so in plain language. Give the reason in terms of the duty and the options you considered, and offer to talk it through again. Do not send a bare refusal. An applicant who understands the decision is more likely to trust the process, even when they disagree with it.
Keep a short record for each request: what was asked, the options you considered, the choice you made, and the date. Keep it with the test file.
Run the five checks once for each test, and again whenever the job's duties change. The process works best when the same person runs it every time. Ask an employment lawyer in your state to review the final process, because state and local rules can add to the federal ones, and this post is no substitute for that review.
Today, open the next test you plan to use and write the job duty beside each item before sending invitations.
What should you bring to the review?
Bring the job's duty list, the test, the scoring criteria and the invitation. Work through them together so changes to the test also appear in its instructions.