Fire Department Training Records: What Should You Actually Be Documenting?

Training Happened. Can You Prove It?

Fire departments spend countless hours training every year. Crews stretch hose, throw ladders, conduct searches, practice vehicle extrication, review EMS skills, complete annual requirements, and work through department-specific procedures. But once the drill is over and the equipment is back in service, what actually gets documented? In some departments, the answer may be a detailed training record. In others, it may be a sign-in sheet, a quick entry into a records management system, or nothing more than a note that training occurred. The problem is that conducting training and being able to demonstrate what training was actually completed are two different things. A strong training record should tell the story of what was taught, who participated, when it occurred, and what the department intended its members to learn or demonstrate. When those records are incomplete or inconsistent, departments can create unnecessary gaps in accountability, continuity, and their ability to demonstrate the training their personnel have received.

What Do the Regulations and Standards Actually Say?

Before deciding what a fire department should include in its training records, it is important to separate good administrative practice from an actual regulatory requirement.

OSHA’s Fire Brigades standard, 29 CFR 1910.156, requires covered employers to provide training and education that is commensurate with the duties and functions members are expected to perform. The standard also requires training to occur frequently enough for members to perform those duties safely and satisfactorily. At a minimum, fire brigade members must receive training annually, while members expected to perform interior structural firefighting must receive training or an education session at least quarterly.

NFPA guidance adds another important layer to the conversation. NFPA 1401, Recommended Practice for Fire Service Training Reports and Records, specifically addresses fire service training reports and records. NFPA currently lists the 2026 edition of NFPA 1401 alongside NFPA 1400, Standard on Fire Service Training, as part of its current fire service training publications.

The distinction between these sources matters. OSHA requirements may carry regulatory force when they apply to a particular employer. NFPA 1401, however, is identified as a recommended practice. Its recommendations should not automatically be presented as legal requirements. NFPA documents may also be adopted, referenced, or incorporated by an authority having jurisdiction, law, regulation, contract, or departmental policy, which can change their significance for an individual organization.

Other current NFPA documents also address firefighter training more broadly. NFPA 1400, Standard on Fire Service Training, and NFPA 1550, Standard for Emergency Responder Health and Safety, are part of the larger framework departments may need to consider when evaluating their training programs. Which requirements or standards apply will depend on the department, jurisdiction, adopted codes and standards, and other governing requirements.

Just as importantly, neither citing OSHA nor referencing an NFPA document should become a substitute for understanding what actually applies to a specific department. Federal OSHA’s 29 CFR 1910.156 has defined applicability and exclusions, and public-sector fire departments may operate under an OSHA-approved State Plan or other state requirements. Departments should identify the laws, regulations, adopted standards, policies, and local requirements applicable to their organization before treating any particular training or recordkeeping practice as universal.

The goal of a strong training record system is not simply to satisfy a citation. It is to create an accurate, consistent, and defensible record of what training occurred, who participated, and what the department expected its personnel to learn or demonstrate.

A Sign-In Sheet Only Tells Part of the Story

A sign-in sheet can establish that a firefighter was present for a training session, but attendance alone does not necessarily explain what occurred during that training. Months or years later, a list of names beside a date may provide very little information about what was taught, what skills were practiced, or what level of performance was expected.

A stronger training record provides context. At a minimum, departments should consider documenting the date and duration of the training, the subject or topic covered, the instructor or person responsible for the training, participating personnel, and a description of the material or practical skills addressed. When applicable, the record may also identify lesson plans, departmental policies, manufacturer information, standards, or other materials used to develop or deliver the training.

Hands-on training may require even more detail. There is a meaningful difference between attending a lecture on ground ladders and demonstrating the ability to select, carry, raise, position, and work from a ladder during a practical evolution. The training record should be detailed enough that someone reviewing it later can reasonably understand what personnel actually did.

Departments should also consider how competency or performance is documented when the training is intended to evaluate a specific skill. Depending on the purpose of the training, that could include a skills checklist, practical evaluation, written assessment, instructor verification, or another documented method established by the department.

Not every training session needs pages of documentation. The amount of detail should be appropriate to the training being conducted. A short company drill and a formal competency evaluation may require very different records. What matters is consistency and enough information to accurately describe the training that occurred.

A useful question for any training officer or department administrator is simple: If someone reviewed this record three years from now, would they understand what our firefighters were actually trained to do?

What Should a Fire Department Training Record Include?

There is no single training record format that will fit every fire department or every type of training. A department using a full records management system may document training differently than a small volunteer organization using standardized forms or spreadsheets. Regardless of the system being used, the record should contain enough information to accurately reconstruct what occurred.

A well-developed training record may include:

• Date, start time, and duration of the training
• Training topic or course title
• Training objectives
• Instructor or individual responsible for the training
• Names of participating personnel
• Type of training, such as classroom, hands-on, online, drill, or evaluation
• Skills or tasks performed
• Equipment, apparatus, or specialized systems used when relevant
• Applicable departmental SOPs, SOGs, lesson plans, manufacturer information, or other reference material
• Method used to evaluate competency when an evaluation was conducted
• Completion, remediation, or follow-up information when applicable
• Instructor verification or other method of authenticating the record

The purpose is not to create unnecessary paperwork after every company drill. The information being documented should be proportional to the training and its purpose. A thirty-minute review of a departmental procedure does not necessarily require the same level of documentation as an annual SCBA competency evaluation, live-fire evolution, driver/operator evaluation, or certification course.

Departments should also be cautious about relying too heavily on a generic “training hours” field. Recording that a firefighter completed two hours of training provides a useful measure of time, but it says very little about what occurred during those two hours. Training hours become significantly more useful when they are connected to a documented subject, objective, activity, and participant record.

Consistency is equally important. If each company officer documents training differently, the department may eventually have hundreds or thousands of records that cannot easily be compared, searched, audited, or used to demonstrate an individual firefighter’s training history. Establishing a standardized process helps turn individual training entries into an organized department-wide recordkeeping system.

Attendance Is Not Competency

One of the most important distinctions a department can make in its training records is the difference between attendance, participation, and demonstrated competency.

A firefighter being present at a training session does not automatically mean that firefighter participated in every evolution. Participation does not automatically mean the firefighter successfully demonstrated the skill being taught. Yet when all three are documented simply as “complete,” the training record can create a picture that may not accurately reflect what occurred.

This becomes particularly important with hands-on skills.

If a department conducts SCBA training and a firefighter watches the evolution but never performs the skill, should the record show the same completion as the firefighter who actually performed it? If crews conduct a search drill and one member never enters the training area, has that member demonstrated proficiency in the skills being evaluated? If a driver/operator attends pump training but never operates the pump, what exactly has been completed?

These distinctions are not about punishing firefighters or creating paperwork for the sake of paperwork. They are about maintaining an accurate training record.

When a training objective requires personnel to demonstrate a skill, departments should have a method for documenting whether that demonstration actually occurred. Depending on the training, that could involve an instructor sign-off, skills checklist, practical evaluation, completion criteria, or another method established by the department. If a firefighter does not complete the required evolution, the record should accurately reflect that rather than automatically showing the same completion status as everyone else in attendance.

This also protects the integrity of the training program. A department may appear on paper to have a fully trained workforce while individual members have never actually performed some of the skills listed in their training histories. Over time, those discrepancies can become difficult to identify, particularly when personnel change assignments, officers promote, instructors leave, or records are reviewed years after the training occurred.

Training documentation should reflect reality.

If someone attended, document attendance. If someone participated, document participation. If someone demonstrated competency, document competency. Those terms should not become interchangeable simply because checking the same box is easier.

A completed training record should mean what the department says it means.

Documenting Incomplete Training and Remediation

If departments are going to distinguish between attendance and competency, they also need a process for what happens when a firefighter does not complete a required evolution or cannot demonstrate the expected skill.

An incomplete training record should not automatically be viewed as a failure or disciplinary issue. There are plenty of legitimate reasons why someone may not complete an evolution. A firefighter may be assigned to a call during training, equipment may become unavailable, the evolution may be stopped for safety concerns, or additional instruction may simply be needed before the member can successfully demonstrate the skill.

The record should accurately reflect what happened.

When additional training is necessary, departments should consider documenting what portion of the training remains incomplete, what additional instruction or remediation is needed, who is responsible for providing it, and when the firefighter ultimately completes the requirement. This creates a clear path from the original training session to final completion instead of allowing an incomplete item to disappear into the training system.

Remediation is especially important when a firefighter has difficulty demonstrating a critical operational skill. The purpose should be to identify the deficiency, provide additional instruction and repetitions, and give the firefighter another opportunity to demonstrate the expected level of performance. Simply marking the original training complete does not correct the problem. On the other hand, documenting a deficiency without providing a reasonable path toward improvement does little to strengthen the firefighter or the organization.

Follow-up matters just as much as the initial documentation. If the department records that a member requires additional training but never documents whether that training occurred, the record remains incomplete. A well-designed system should allow training officers and company officers to identify outstanding training, assign follow-up, and close the record once the established requirements have actually been met.

The goal is not to build a file of mistakes. The goal is to ensure that when the department says a firefighter has completed a required skill, there is a reliable record showing how that conclusion was reached.

Good documentation should identify gaps, but a good training program should also help firefighters close them.

Consistency Across the Department Matters

Even a well-designed training record system can lose its value if every company, shift, or officer uses it differently.

One officer may document a drill with the topic, objectives, personnel, skills performed, and supporting references. Another may enter “hose training - 2 hours.” Both records may technically show that training occurred, but they do not provide the department with the same quality of information.

Over time, those inconsistencies add up.

A department should establish clear expectations for how training is documented regardless of who conducts it. That does not mean every drill needs to follow an identical lesson plan or that company officers should lose the flexibility to train based on the needs of their crews. It means the administrative process used to capture that training should be consistent enough that records can be understood across the organization.

Standardized terminology can help as well. If one officer records “search,” another records “primary search,” and another records “interior operations,” the department may have difficulty determining how much search training its personnel have actually completed. Establishing common training categories, naming conventions, and documentation expectations makes those records easier to review and track over time.

The same principle applies to completion criteria. If one instructor considers attendance sufficient for completion while another requires each firefighter to perform the skill, the department does not have a consistent definition of what “complete” means. Training expectations should be established before the evolution begins, particularly when competency or proficiency is being evaluated.

Technology can make this process easier, but a records management system (RMS) cannot fix an undefined process. Drop-down menus, electronic signatures, automated reports, and training dashboards are only as useful as the information being entered into them. Departments should establish the process first and then configure their forms, spreadsheets, or software to support it.

Ultimately, standardization allows a department to answer basic questions with confidence: What have we trained on? Who completed it? Who still needs it? What skills were actually performed? And can we produce the records to support those answers?

If the answers depend on which officer entered the training, the problem is not just recordkeeping. It is the system behind it.

Retention and Accessibility Matter Too

Creating a good training record is only part of the process. Departments also need to determine how those records will be stored, how long they will be retained, and how they can be retrieved when needed.

There is not one universal retention period that can safely be applied to every fire department training record. Retention requirements may depend on the jurisdiction, type of training, applicable law or regulation, state or local records retention requirements, collective bargaining agreements, departmental policy, or other governing requirements. Certain specialized training records may also be subject to requirements that differ from routine department training documentation.

For that reason, departments should avoid choosing a retention period simply because another department uses it. A records retention schedule should be developed after identifying the requirements that actually apply to the organization and the types of records being maintained.

Accessibility is equally important. A department may have years of training documentation, but those records provide limited administrative value if locating an individual firefighter’s training history requires searching through filing cabinets, disconnected spreadsheets, emails, paper sign-in sheets, and multiple software systems.

A well-organized system should allow authorized personnel to retrieve records efficiently. Departments should be able to identify what training an individual firefighter has completed, review training conducted during a particular period, determine whether required training remains outstanding, and locate supporting documentation when necessary.

Departments should also consider continuity. Training records may need to remain understandable long after the instructor, company officer, training officer, or chief who originally created them has left the organization. File names, categories, abbreviations, storage locations, and documentation practices should make sense to the next person responsible for maintaining the system.

The question is not simply whether the department keeps training records. The better question is whether the department can reliably find, understand, and use those records when they are needed.

The System Does Not Have to Be Expensive

Good training documentation does not necessarily require an expensive records management system.

Departments have different staffing levels, call volumes, budgets, and administrative resources. A large career department may benefit from a dedicated records management system with automated training assignments, electronic approvals, certification tracking, and reporting capabilities. A smaller combination or volunteer department may accomplish many of the same basic recordkeeping objectives through standardized forms, organized digital files, or a carefully managed spreadsheet.

The platform matters less than the process behind it.

Whatever system a department uses should make it reasonably easy to enter training consistently, identify participating personnel, document what occurred, track completion when necessary, and retrieve the information later. If the process is overly complicated, officers may avoid using it or enter the minimum amount of information necessary to close the record. If it is too simplistic, the department may fail to capture information it actually needs.

Departments should also consider who is responsible for maintaining the system. A process that works only because one training officer understands an elaborate spreadsheet or filing structure can become a problem when that individual changes positions or leaves the organization. Documentation systems should be organized so another authorized member can reasonably understand and continue the process.

The same principle applies when purchasing software. Technology should support an established administrative process, not become the process itself. Before investing in a new platform, departments should understand what information they need to capture, who will enter it, how completion will be verified, how records will be reviewed, and what reports the organization actually needs.

A simple system that is consistently used and properly maintained can be more valuable than an expensive system filled with incomplete or inconsistent information.

The best training record system is not necessarily the one with the most features. It is the one the department can use consistently, maintain over time, and trust when the records are needed.

Audit Your Training Records Before Someone Else Does

Departments should not wait until training records are requested to find out whether their documentation system works.

Periodically reviewing a sample of existing training records can reveal problems that are difficult to see during day-to-day operations. Pull several records from different shifts, stations, companies, instructors, and types of training. Then review them as if you had no prior knowledge of what occurred.

Can you determine what was taught? Can you identify who participated? Can you tell whether personnel simply attended or actually performed the skill? If competency was evaluated, is there documentation showing how it was determined? Can supporting lesson plans, policies, evaluations, or other referenced materials be located? If someone did not complete the training, can you determine whether follow-up occurred?

The answers can quickly show whether the department has a functioning training record system or simply a collection of training entries.

Departments should also review individual training histories. Select a firefighter and attempt to reconstruct that member’s training over a defined period. Look for missing records, inconsistent terminology, duplicate entries, unexplained completion statuses, or training that appears complete without enough information to determine what was actually performed.

This type of internal review does not need to become an elaborate inspection process. The purpose is to identify weaknesses while the department still has the opportunity to correct them. If officers consistently misunderstand a documentation field, clarify the expectation. If training categories are inconsistent, standardize them. If incomplete training is disappearing without follow-up, establish a process to track it. If records cannot be located, address the storage and retention system.

Most importantly, departments should use what they find to improve the process rather than simply correcting individual records.

A strong administrative system should not depend on someone remembering what happened. It should be capable of showing what happened.

Finding the gaps internally gives the department an opportunity to fix them before those records are needed for a reason outside of its control.

Build a Training Record You Can Stand Behind

Fire service training is too important for the documentation behind it to become an afterthought.

A department can have motivated instructors, aggressive company-level training, and firefighters putting in hours of meaningful work, but the administrative record still needs to accurately reflect what occurred. Attendance should mean attendance. Participation should mean participation. Competency should mean the firefighter actually demonstrated the skill to the standard established by the department.

That does not require turning every company drill into an administrative burden. It requires establishing a process that is clear, consistent, and realistic for the organization using it.

Departments should know what information needs to be documented, who is responsible for documenting it, what constitutes completion, how incomplete training is addressed, where records are maintained, and how those records can be retrieved later. Those expectations should not change depending on the shift, station, company officer, or instructor entering the information.

This is an area where Fire Service Administrative Solutions can help.

FSAS works with fire departments to evaluate and improve the administrative systems behind their operations. For training documentation, that can include reviewing existing recordkeeping practices, developing or revising training documentation policies, standardizing training forms and completion criteria, establishing workflows for incomplete training and remediation, organizing training categories and documentation expectations, and helping departments build a more consistent process around the tools they already use.

FSAS does not provide a records management system. Instead, the focus is on helping departments build the administrative structure that makes their existing system more effective, whether records are maintained through an RMS, standardized digital forms, spreadsheets, or another department-approved method.

Technology can store the record. It cannot determine whether the record is accurate.

That responsibility still belongs to the department.

When a firefighter’s training record says a skill was completed, the department should be able to stand behind what that designation means. When someone asks what training occurred, the answer should not depend on memory, assumptions, or who happened to enter the record.

Train with purpose. Document what actually happened. Build a system you can defend.

Fire Service Administrative Solutions helps departments turn inconsistent administrative practices into clear, standardized systems built around the realities of the fire service.