The Field Training File,
and What It Shows

Field training begins where the academy ends. A newly hired officer who has completed basic training is assigned to a field training officer (FTO), rides with that trainer, and performs the job under direct daily observation. The program runs in phases, each with written objectives, and the recruit’s share of the work increases as the phases advance until the trainer is riding largely as an observer.

Nearly every shift is graded. At the end of the tour the trainer writes an evaluation of that day’s performance across a fixed set of categories, using rating definitions the program publishes in writing. A recruit who does not meet a standard is placed on documented remediation. Where remediation does not close the gap, the phase or the program can be extended. At the end, a named person signs a decision to release the recruit to solo patrol, or not to.

That structure is why the file matters so much later. Field training is the one stretch of a career in which a trainer watches an officer work every day and writes down what was seen, before any incident, complaint or lawsuit gave anyone a reason to shade the description.

Program design varies. Phase counts, category lists, rating scales and remediation rules are set by the agency, so the first document to read is the program’s own written manual rather than a national template.

In litigation the file is read for one distinction above all others. A deficiency that was identified, remediated and then demonstrably corrected is evidence of a program doing its job. The same deficiency, documented and then signed past without any record that it was corrected, is a different fact entirely, and the file usually shows which one happened.

• What the daily reports identified, how often, and in which performance categories
• Whether a written remediation plan followed each identified deficiency
• Whether the plan was completed, and which document says so
• Whether ratings improved before release, or the file simply stops mentioning the problem
• Who released the recruit to solo patrol, and against what stated criteria

A thin or absent file is a finding in itself, measured the way any training absence is measured, against the program’s own written requirement, which is the method the linked brief on training records sets out. What is specific to field training is that the manual usually states which shifts had to produce a report, so the count of what is missing comes from the agency’s own rule.

The file also answers a question about the program rather than about the recruit. Read across trainees, a field training program that never extends anyone, never documents a deficiency and rates every recruit the same way on every category is describing its own rigor, and that description is organizational evidence. Compared with the agency’s own manual, it shows whether the program the agency wrote is the program the agency ran.

The wider training file, from academy transcripts through in-service histories, and the method for reading absence in it, are the subject of the brief on what training records reveal. This page stays with the field training layer, because it is the layer that speaks in a trainer’s own words about observed performance.

Ask for the manual edition that governed during that officer’s training rather than the one in force at production, and for every phase of the file, and ask for the manual edition that governed during that officer’s training rather than the one in force at production. Programs get revised, and the rating definitions move with them, so the wrong edition will misdescribe every score in the file.

• The complete field training file for each involved officer, every phase, without date narrowing
• The program manual and the standardized evaluation guidelines in force during that officer’s training
• The trainer roster showing which field training officer rode which phase
• Every remediation plan, and every document bearing on whether it was completed
• Extension memoranda and the release-to-solo sign-off
• The training coordinator’s file on extension and release decisions
• The selection, training and performance file for each field training officer involved
• Any probationary review or evaluation that followed release to solo patrol

Two of those items are worth naming separately when the demand is drafted. The trainer roster shows which field training officer rode which phase, and a recruit usually rotates through several, so the ratings are only as comparable as the trainers behind them. The training coordinator’s file is where extension and release decisions get argued before anyone signs them, and it often holds the reasoning the signed memorandum leaves out.

In the report each answer lands on a page. What the trainer saw comes from a dated observation report, what the program concluded from a phase evaluation, what was done about a deficiency from a remediation plan, and who accepted the result from the release sign-off. That structure is what lets a failure-to-train, supervision or negligent-retention question rest on produced documents.

Those documents do not answer the legal question. Whether the facts they establish amount to notice, deliberate indifference or municipal liability is a matter for the pleadings and the briefing, and legal conclusions remain counsel’s.