Keeping Interview Notes Honest: Recording Decisions Without Inflating Them
Most recruitment problems do not start with a bad hire. They start with a record that no longer matches what actually happened. A shortlist gets rebuilt from memory, a note says a candidate was 'confirmed' when only a conversation took place, and six weeks later nobody can explain why one applicant was chosen over another. For small employers and independent workers who handle their own hiring, the discipline of keeping accurate notes matters as much as the job post itself. This article looks at how to record recruitment decisions in a way that stays useful and truthful, and what to check before you trust a note.
Separate what was said from what was decided
A useful recruitment note distinguishes between observations, interpretations and decisions. An observation is a fact you can point to: the applicant described two previous projects of similar scope, or their availability was given as three afternoons a week. An interpretation is your reading of that fact: this person seems experienced with client handoffs. A decision is an action: we will invite them to a second conversation. When these three are blended into a single line such as 'strong candidate, moving ahead', the reasoning disappears. Someone reviewing the file later cannot tell which part was evidence and which part was impression.
Try writing each stage of a hiring process with three short labels. Keep the observation column blunt and specific. Keep the interpretation column short and tentative. Record the decision with a date and the name of the person who made it. This structure takes a few extra minutes per candidate but prevents the common failure in which an impression is later remembered as a verified fact.
Describe the role before judging the applicant
Many hiring notes are really notes about the applicant's distance from an imagined ideal rather than about the actual work. Before reviewing any applications, write down the specific tasks the role covers, the information the work depends on, and the conditions under which it will be done. A brief that says the worker will prepare a weekly summary from a shared spreadsheet is easier to assess against than one that says the worker should be organised and dependable.
Once the scope is written, check each candidate against it rather than against a general sense of quality. If a note says a candidate lacks something, ask whether that thing was actually part of the task. This habit also protects you from quietly changing the requirements halfway through a shortlist, which is one of the most frequent sources of unfair decisions.
Question the compensation and timing language
Recruitment briefs often contain indicative figures for pay or schedule, and those figures can be read in ways the author did not intend. An indicative amount is an estimate of what the employer is considering, not a commitment that a placement will happen or that work will be paid at that level. When you record a conversation about pay, write down exactly what was stated, who stated it, and whether it was described as final. Do not let an estimate migrate into your notes as an agreed term.
Ask the same questions of any listing you rely on. Is the vacancy confirmed and funded, or is it a proposed brief still being tested? Are the hours fixed or expected to vary? Who decides on the final terms? These are general questions to put to any hiring counterpart, and an honest answer to each one should appear in your records before you move a candidate to the next stage.
A short checklist for each candidate file
Before closing a candidate file, check the following in plain terms. Does the file name the role and the date it was reviewed? Does it separate observations from interpretations? Is every decision attributed to a person and dated? Does it state any compensation or schedule discussed, marked as discussed rather than agreed? Does it note what remains unknown, such as references not yet checked or availability not yet confirmed? And finally, would a colleague unfamiliar with the process be able to tell from the file alone why the decision was made?
If the answer to any of these is no, add the missing detail before the file goes into storage. A file that is accurate about its gaps is far more useful than one that appears complete but cannot be trusted. Honest records do not guarantee a good hire, but they make every later decision easier to examine, explain and correct.