The Polygraph Pre-Test Statement: Getting a Clean Written Account First

A note on the polygraph itself

Let's be straight about what a polygraph is and isn't, because it shapes everything else. A polygraph measures physiological responses — breathing, heart rate, skin conductance — while a person answers questions. It does not detect lies; it detects arousal, which may accompany deception but also accompanies fear, anger and stress in perfectly honest people. Polygraph accuracy is contested, results are inadmissible in many courts, and its use is restricted or regulated in various jurisdictions and employment contexts. Treat any polygraph output as one input among many, never as a verdict. The value discussed here is mostly in the process around it — and especially the written account taken first.

Why the written account comes first

A polygraph examination isn't a machine reading a person cold. It's built around a pre-test phase where the subject's account is established and the questions are formulated. If that account is vague, half-formed or shifting, the examination is built on sand. A clean written statement, taken before any of that, gives you three things:

A fixed baseline. The subject's account, in their own words, frozen before the examination. Whatever happens later, you have what they said at the start — and you can compare it to what they say during and after.

Sharper questions. Polygraph questions have to be specific, unambiguous and grounded in the actual facts of the case. You can only write good questions if you have a detailed account to draw them from. A rich pre-test statement is the raw material for a focused examination.

Leads independent of the instrument. Even setting the polygraph aside entirely, a careful written account often surfaces contradictions, gaps and points worth probing on its own — the same leads any good statement would. In many cases the statement is more useful than the reading.

How to take the pre-test account

Take it the way you'd take any good investigative statement, because that's what it is:

Free recall first. Ask for the whole account in the subject's own words, uninterrupted, before you ask anything specific. Don't lead, don't fill silences, don't feed them the facts. You want their version, produced by their memory. (A companion guide on investigative interviewing covers this in depth.)

In their own writing where possible. A statement the subject wrote themselves, unprompted, is more valuable for later analysis than your paraphrase of what they said. Their word choices, their order, their omissions — all of that is signal, and it's lost if you write it up for them.

Complete and specific. Push gently for detail on time, place, sequence and people — the concrete anchors. Not by leading, but by asking open follow-ups: "what happened next?", "tell me about that part."

Recorded contemporaneously. Capture when it was taken and preserve it unaltered. This is the baseline; it only works if it's genuinely fixed.

What to look for in the account

Once you have a clean written statement, examine it the way you would any statement — for the parts worth probing, not for signs of "lying." Look at where the account is detailed and where it goes thin. Look for skipped time, vague transitions, points the subject volunteers unprompted, and places where the language shifts. Each of these is a marker — a place worth a question — and each has an innocent explanation you should hold in mind. (The guide on SCAN statement analysis covers reading these markers and the leads-not-verdicts rule that governs them.)

The point of this examination isn't to decide guilt from the text. It's to identify the specific issues worth focusing the examination and the follow-up on — to turn a long account into a short list of pointed questions.

The leads-not-verdicts rule applies doubly here

Everything in this space is high-stakes for the person being examined, so the discipline matters more, not less. Neither the written statement's markers nor the polygraph's readings are proof of anything. Both produce leads: places to ask better questions, points to test against other evidence. A finding that rests on "the statement showed deceptive markers and the subject failed the polygraph" is not a finding — it's two contested indicators stacked on each other. The defensible position is always to anchor conclusions in facts you can point to, using the statement and the examination as tools that told you where to look, not what to conclude.

Keep it fair and lawful

Because polygraph use touches consent, employment law and admissibility, know the rules where you operate before you go near it. The subject's participation should be genuinely voluntary and informed. The written account should be taken without coercion. And the whole process should be documented so that, if it's ever scrutinised, you can show it was conducted properly. An examination obtained improperly is worse than none.

Doing the statement analysis part well

The pre-test statement is only as useful as your ability to read it — to find the markers worth probing without over-reading them into an accusation. Conectir's SCAN tool marks up a written statement, lists the linguistic features it finds, attaches an innocent alternative to every one, and turns them into suggested follow-up questions — exactly the raw material for a focused pre-test process. It never returns a verdict of deception; it produces the leads and the question list and leaves the judgement to you. If you work with written statements ahead of examinations, see how the SCAN tool handles a statement.