What a Methods Note Owes the Reader

Most methods notes get written in a hurry, tacked onto the end of a piece as an afterthought once the reporting is already done. That's a shame, because a good one does real work: it tells the reader exactly what the reporting can support and where it stops, which is often more useful than another paragraph of claims.

The habit is easy to describe and slightly harder to practice consistently: say plainly what you examined, who you spoke with, and where you were unable to get further confirmation. That last part is the one most often left out, usually because it feels like an admission of weakness rather than a normal part of honest reporting.

Readers notice the omission

A story that never says what it couldn't confirm reads, to an attentive reader, as either flawless or incomplete about its own limits. Neither impression serves the piece well. Naming the boundary — "records from before 2015 were not available," "the subject declined to comment on this specific claim" — gives the reader the tools to weigh the reporting fairly, rather than assuming either total certainty or hidden gaps.

Keeping the note short and specific

A methods note doesn't need to run long to do its job. Three or four sentences covering sources consulted, records reviewed, and any notable limitation usually cover it. What matters is specificity over length: naming the actual gap rather than a vague disclaimer that could apply to any story.

We help reporters draft this note early, sometimes before the final version of the piece is locked, because it often reveals a question worth chasing down before publication rather than after. A template helps with structure, but the content still has to come from what the reporting actually found — and didn't.