What should you ask a docketing clerk in an interview? Questions and what good answers sound like
A question bank for law firms interviewing docketing clerk candidates — deadline computation, systems fluency, judgment and confidentiality, a practical exercise, and the questions to keep off your list.
The questions to ask when hiring a docketing clerk are the ones that make a candidate show the work: where a deadline's clock starts, how the days get counted, what happens when the rule and the software disagree, and who gets told.
Below is that question bank for law firms — what each question reveals, what strong answers sound like, a practical exercise, and the questions to keep off your list.
Before the interview
Write the questions from the job description, not from a generic list.
If you have not settled the role itself — which deadlines the seat owns, the level you are hiring, who reviews the work — start with our guide to how to hire a docketing clerk, then sharpen the questions once the docketing clerk job description says what the hire will actually do.
The interview's job is to test the claims that posting makes.
Docketing skill is nearly invisible on a resume.
Every candidate can claim deadline responsibility, and the ones who only entered dates somebody else computed can claim it loudest.
So the interview has one purpose: make the computation visible.
The questions below ask for the work, not the title.
Decide two things before the first candidate sits down: the practical exercise you will use, and the scoring sheet you will fill in right after each interview.
Keep both the same for every candidate, and score while the specifics are fresh — comparisons made from memory weeks later are comparisons made from charm.
Two legal rails belong under the exercise.
If you require applicants to take a test, the EEOC's position is that it must be necessary and related to the job, and must not exclude people of a particular protected group or people with disabilities.
And an employer must provide an accommodation a disabled applicant needs to apply for the job — a sign language interpreter, for example — unless it causes significant difficulty or expense.
Build the exercise so both are easy to honor: a written packet a candidate can complete with more time, or have read aloud, still tests the skill.
Design the exercise around a mock, disguised file rather than live matters.
The FLSA defines "employ" to include "to suffer or permit to work" (29 U.S.C.
203(g)), so a candidate doing real, usable work for the firm — entering deadlines onto a live calendar you then rely on, for example — may be an employee owed wages; a short exercise on a mock file is the safer design.
Tell every candidate up front that they should not share client-identifying detail in the room: the calendar they kept at their last firm maps that firm's matters, and your interview needs the kind of entry, not the parties.
How a candidate handles the instruction is itself a data point.
Then check your draft list against the risky-questions section below, and have employment counsel confirm the final version — the rules vary by state and they move.
Which skills questions reveal real docketing clerk experience?
Walk me through one deadline you computed from start to finish — the document that started the clock, the rule that set the window, and the date that landed on the calendar.
What to listen for: Strong answers name the trigger document, where the clock starts, how they counted the days forward, and what they did when the period landed on a weekend or holiday — and they show the work clearly enough that someone else could check it.
Probe one step deeper before you score the answer.
The weak answer is a date with no chain behind it: “the system produced it.”
Which docketing systems have you used daily, and what did you personally enter in a typical day?
What to listen for: Strong candidates name the systems unprompted, describe the entry work they owned — new matters, events, closings — as distinct from what the team did, and separate daily use from passing exposure.
A candidate who cannot say what they typed into the system is telling you what their role actually was.
Tell me about a deadline that moved after the case moved — an amended order, an extension, a rescheduled hearing. What did you do?
What to listen for: Strong answers catch the change, update the entry, recompute anything downstream that depended on it, and tell the attorneys the date moved before the attorneys discover it themselves.
Weak answers assume someone else updated the calendar, or change the date without checking what else hung off it.
Whose rules set the deadlines you calculated at your last firm, and how did you keep up when a rule changed?
What to listen for: Depth here separates a specialist from a data-entry clerk — either can be the right hire, but you should know which one you are interviewing.
Strong answers can name the kinds of rule sets their dates came from and describe how changes reached them — a rule-change notice, a supervisor's memo, a system update.
Weak answers describe software screens with no rules anywhere behind them.
How were your computed deadlines checked at your last firm — by whom, and how often?
What to listen for: Strong candidates describe the review structure without prompting — who re-checked their dates, on what schedule — and can explain why it exists.
A candidate who describes the structure understands that the job is producing dates someone else can trust; one who bristles at the question is telling you how they will treat your review structure.
Which behavioral questions test judgment, confidentiality and deadlines?
Tell me about a time you caught a date problem — yours or someone else's — before it became a missed deadline. What did you do?
What to listen for: Strong answers show the reflex the seat exists for: noticed early, escalated fast on a known path, and a process change afterwards so the same catch does not depend on luck.
Weak answers have no example, or the fix was working harder.
A candidate with no story has either not done the work or never watched for the failure mode.
The calendar you would keep here maps the firm's matters, clients and strategy dates. How did you handle sensitive information at your last firm — who saw your reports, and what did you do when someone outside the case team asked for detail?
What to listen for: Strong answers describe the practice, not a philosophy: reports went to the case team, requests from outside it were routed to a supervisor, and nothing identifying traveled in an elevator conversation.
The dangerous answer is the entertaining one — a candidate who walks you through a former employer's matters by name is showing you how they will treat yours.
Walk me through a week when several deadlines collided. What moved, and who did you tell?
What to listen for: Strong answers triage by consequence, escalate early, and treat a collision as a staffing question for the attorneys rather than a secret to keep.
Weak answers amount to “I worked harder,” with no system and nobody told.
Ask what changed in their process afterwards — the fix is the real answer.
Tell me about a time someone pressed you past the role — an attorney wanted a judgment call made, or a client asked you what they should do about a date. What did you say?
What to listen for: This is the boundary the seat sits next to: computing and reporting the date is the desk; advising the client what to do about it is not.
Strong answers stayed on their side of the line and routed the request to the attorney — without drama, and without guessing.
Weak answers are proud of the guess.
Tell me about a deadline that was missed on your watch — one you computed, or one you caught too late. What happened next?
What to listen for: Strong answers own it fast, say who was told and when, and name what changed so it cannot repeat.
Weak answers blame the software, the attorney or the volume — or insist it has never happened.
A candidate who can describe a well-handled miss is safer than one with no misses at all.
What practical exercise or test should a docketing clerk complete?
Hand them a mock packet — a disguised notice, the rule excerpt that sets the response window, and a blank calendar entry — and ask for the due date with the work shown.
What to listen for: Watch the work, not just the answer: where they say the clock starts, how they count the days forward, what they do when the period lands on a weekend or holiday, and whether the entry shows its reasoning clearly enough for a reviewer to check it quickly.
A candidate who annotates the calculation has just demonstrated the habit your calendar is buying; a candidate who only announces a date has shown you a black box.
Build a wrinkle into the packet — the window lands on a weekend or holiday, or the rule excerpt and the system's proposed date disagree — and ask what they do.
What to listen for: This is the test that matters, because real calendar work produces wrinkles like these.
Strong candidates stop on the ambiguity, hold the entry and escalate on a defined path — they do not silently pick a date.
Ask who they would tell at their last firm; the answer should be a person, not “whoever noticed.”
Ask for the two things the seat actually produces, written to the scenario: the calendar report and the reminder that goes to the attorney.
What to listen for: Strong samples are short, unambiguous and dated: what is due, the trigger behind it, what happens if it slips, and who owns the next step.
Weak samples are vague or padded.
The report is how your firm's week gets planned, so score the writing — with the same prompt for every candidate.
Hand them a mock month — a stack of matters at different stages with dates attached — and ask how they would run the calendar for it.
What to listen for: Strong candidates triage by date and consequence, spot the entries that depend on other entries, and say what they would escalate and to whom.
Weak candidates narrate the list.
Keep the packet small enough to finish inside the interview, and identical for every candidate, so the comparisons mean something.
Say how long the exercise should take and invite questions before they start — then notice what they ask.
What to listen for: Strong candidates ask about the rules that govern the mock matters, the review structure, and what happens to the exercise afterwards — the questions of someone who has run a real calendar.
No questions at all is its own signal: the work they have done may have arrived pre-computed.
What do strong vs weak answers sound like?
Computation: “I counted from the service date the notice showed, the period landed on a Saturday so I flagged the adjustment for the reviewer, and I initialed the entry” — strong. “The system shows me what's coming due” — weak.
What to listen for: The strong version contains a chain you can verify — a starting point, a count, an adjustment someone else could re-run — and the candidate can go a level deeper on any link of it when you probe.
The weak version describes a screen.
Every follow-up you ask tests which version you are hearing.
Confidentiality: “I can describe the kind of entry without the matter” — strong. A tour of a former employer's docket, case names attached — weak.
What to listen for: The strong answer protects the employer and describes the practice, not the story.
The weak answer is entertaining — and disqualifying: a candidate who walks you through a former employer's calendar will walk someone else through yours.
Score charm lower than discretion.
Ambiguity: “The rule excerpt and the system disagreed, so I held the entry and asked the supervisor before anything went on the calendar” — strong. “I'd just go with whatever the system says” — weak.
What to listen for: The strong answer shows a defined path: stop, hold the entry, ask, document.
The weak answer outsources the judgment to the tool.
Press on the strong answer — where they went, how fast it got resolved — and you will learn whether the path existed or the story is borrowed.
Deadlines: “Two response dates collided, so I flagged it to the attorneys at the start of the week and we re-sequenced” — strong. “I have never missed a deadline” — weak.
What to listen for: The strong answer shows a system — early warning, escalation, a calendar that moved on purpose.
The weak answer offers perfection; press gently and the follow-up tells you which one it is.
Ownership: “The date was wrong because I read the notice wrong; I told the attorney the same day and we fixed the entry before it mattered” — strong. “That's why firms buy the software” — weak.
What to listen for: The strong answer owns the miss, names who was told, and shows the repair.
The weak answer hands the responsibility to a tool you will own.
A candidate who can describe a well-handled mistake is safer than one with no mistakes at all.
Which questions are illegal or risky to ask?
Interviews are part of the hiring process the anti-discrimination laws reach: protections enforced by the EEOC extend to job applicants and former employees, not just current staff.
Title VII, the ADA and GINA cover private employers with 15 or more employees who worked at least 20 calendar weeks in the current or prior year, and the ADEA's age protections cover private employers with 20 or more employees who worked at least 20 calendar weeks in the current or prior year.
State and local laws can reach smaller employers — that coverage was outside our research, so confirm what applies to your firm.
Read this section with the EEOC's own framing: federal law does not clearly forbid every pre-employment question touching race, sex, national origin, religion or age, but such questions can be used as evidence of intent to discriminate unless justified by a business purpose — treat them as risky, not as technicalities.
A docketing hire sits close to two of these lines — the calendar holds client identities, and scheduling questions drift easily toward family questions — which is exactly why the loop needs a clean list.
Have employment counsel confirm the final version before your first interview.
- Salary history — “What did you make at your last firm?” California bars all employers from seeking an applicant's salary history, including benefits, orally or in writing, and from relying on it in hiring or pay decisions; New York bars relying on it and requesting it as a condition of being interviewed, considered, hired or promoted, and permits confirming it only when an offer with compensation is on the table and the candidate responds by citing prior pay to support a higher number; Illinois makes it unlawful to screen applicants by salary history or request it as a condition of an interview or offer; Massachusetts bars seeking it from the candidate or a current or former employer; Connecticut bars asking about it unless the candidate volunteers it first; Virginia and Nevada bar seeking salary history as well. Those are the jurisdictions our research verified, not the full map — other states and cities have rules we did not read, so check yours. Ask “What are you looking for in pay for this role?” instead — California's statute expressly permits asking about salary expectations — and keep the question anchored to the range in your posting.
- Protected-trait probes — “Where are you really from?”, comments on an accent, graduation years as an age proxy, religion, family plans, who watches their children. The EEOC's position is that pre-employment questions should be limited to what is essential to decide whether a person is qualified, and that questions about race, sex, national origin, age and religion are irrelevant to that decision; the EEOC also maintains separate guidance pages on pre-employment inquiries about race, height and weight, financial information, unemployed status, religious affiliation, citizenship, and marital status or number of children. The docketing trap is the scheduling question: coverage expectations are a real job fact, so ask about the schedule the seat carries — never about the household that has to be home for it.
- Medical questions before an offer — health conditions, past injuries, treatment. The FTC and EEOC's joint background-check guidance says employers should not ask medical questions before a conditional job offer; before an offer, keep questions on how the candidate would handle the job's actual demands — deadline volume, competing dates, the reporting cycle — rather than on any condition.
- Criminal history, asked casually. The same FTC and EEOC guidance says it is generally not illegal for an employer to ask about an applicant's background or require a background check, apart from restrictions around certain medical and genetic information — but it warns that a criminal-record exclusion that significantly disadvantages a protected group and does not predict job performance can be unlawful disparate impact. Where and when you may ask is also regulated: California bars employers with five or more employees from asking about conviction history until after a conditional offer, and an employer there that plans to deny the job over conviction history must make an individualized assessment, notify the applicant in writing, and give at least five business days to respond; New York City makes it unlawful for most employers to ask about or consider applicants' criminal history before a conditional offer; Illinois bars covered employers from asking until the applicant has been found qualified and notified that they are selected for an interview — or, where there is no interview, until after a conditional offer. Those are the jurisdictions our research verified — state and city rules vary, so confirm yours before asking. And whatever screen you ultimately run, anchor it in what predicts the work: the warning above is about exclusions that do not.
- Tests and exercises without a job anchor. If you require a test, the EEOC's position is that it must be necessary and related to the job, and must not exclude people of a protected group or people with disabilities — and an applicant who needs an accommodation to apply for the job, such as a sign language interpreter, must be provided it unless it causes significant difficulty or expense. An exercise built from the work — a mock notice, a rule excerpt, a calendar entry — is what “necessary and related to the job” describes; a screen unrelated to the work is not.
- Anything you could not connect to a duty in the job description — if a question survives that test awkwardly, replace it with the job question you actually meant; the work itself gives you more than enough to ask about.
After the interview
Score every interview on the same sheet while the details are fresh: the computation walkthrough, the behavioral answers, the exercise, and anything the candidate volunteered that you did not ask about.
Compare candidates against the rubric and the job description rather than against each other's polish, and write down the specifics you intend to verify — the employers, the systems, the dates, and the name of the supervisor who watched their calendar.
That last call is the strongest check this seat gets: a former supervisor who can describe how the candidate's computed deadlines were reviewed is worth more than any interview answer.
Keep what you wrote down.
The FTC and EEOC's joint guidance says private employers must keep personnel and hiring records, including applications from people who were not hired, for at least one year from the date the record was made or the personnel action taken, whichever is later.
The questions a docketing clerk candidate asks you — and what they signal.
Leave real room at the end, because the questions are data too:
- “What docketing system does the firm run, and how long has the current setup been in place?” — they have worked a real desk and want to know what they are walking into. Have an honest answer, including about conversions — a system migration is exactly the project a new hire can inherit.
- “Who reviews my computed deadlines, and how quickly will I get feedback?” — a candidate who has worked inside a review structure asks about it early. Your answer is your supervision structure speaking out loud, so know it before the loop starts.
- “What happens here when a rule and the system disagree?” — process awareness, and the strongest question on this list. If your firm has no defined escalation path, say so honestly and fix it before the seat is filled.
- “Which courts and practice areas will my deadlines come from?” — rule awareness; they are asking whether the desk covers one jurisdiction or many, which changes the work. Answer with the practice mix you actually have.
- “What is the pay range for this role?” — a reasonable question and, in places, one with a legal answer behind it: California requires employers to give an applicant the position's pay scale on reasonable request, and Nevada requires the wage or salary range for an applicant who has completed an interview. Have the number ready and keep it consistent with the posting — how to hire a docketing clerk covers what benchmark data can and cannot say for this title.
- “How does the desk handle the heavy stretches — is there backup, or does the calendar live with one person?” — they have lived a deadline-driven seat before and are testing whether you tell the truth about it. Answer plainly; a one-person calendar with no backup is a question you should be asking yourself too.
- No questions at all — explore it rather than reading it as disinterest; asking what they are still weighing tells you more than moving on.
This page is employer information, not legal advice. Interview rules come from federal and state laws that change and vary by jurisdiction — confirm your question list, exercise, background-check process and pay-disclosure duties with employment counsel and the EEOC or your state fair-employment agency before the first interview.
More hiring resources
Ready to interview docketing clerk candidates?
Post your opening where attorneys and legal staff look for law firm work.