The Field PM Form Library: 90+ Ready-to-Use Field Forms

What is actually in the library

The form library is organized around the paperwork field crews fill out every day, not generic templates. It breaks down into a few major groups: safety forms (JSAs, pre-task plans, incident reports, safety inspection checklists), QA/QC forms (inspection and test plans, nonconformance reports, hold-point sign-offs, material inspection records), and toolbox talks (52 pre-written topics covering fall protection, electrical safety, excavation, PPE, and more, ready to assign and log attendance against).

Beyond the pre-built set, the library includes 32 industrial QA/QC forms drawn from real customer paperwork — civil, electrical, piping, and mechanical inspection checklists that match how those trades actually document work, not a generic "quality checklist" that has to be reworked for every discipline.

Why a pre-built library beats building your own

• •Consistency across crews and foremen: everyone fills out the same JSA fields the same way, instead of five different versions floating around from five different foremen's phones.
• •Faster crew onboarding: a new foreman does not need a week of training on "our forms" — the standard set is already there and already familiar to anyone who has worked in the trade.
• •Built by trade, not generic: a weld inspection form built for piping crews asks about weld number, WPS, and NDE result — not a generic "quality checked yes/no" box that satisfies no one.
• •One place, not five: the JSA, the toolbox talk log, and the QA/QC checklist all live in the same app as the daily report and photos, instead of a separate paper form, a separate safety app, and a separate spreadsheet.

How forms attach to the daily record

A form in the library is not a static PDF — it is a structured record that attaches to a project, a date, and (where relevant) a daily report. A JSA filled out for a trenching task links to that day's daily report and crew list, so the safety record and the labor record sit next to each other in the same job file, not in two unconnected systems.

For QA/QC forms this matters even more: an inspection checklist tied to a hold point can require a signature before work proceeds, and that signed record becomes part of the <a href="/features/qaqc-workflows">QA/QC workflow</a> with e-signature approvals — the same sequenced hold-point process used for civil, electrical, and piping scopes. A rejected inspection does not just disappear into a filing cabinet; it stays open until closed out, the same way a rejected weld stays open until re-tested.

Build your own, when you need to

No library covers every possible form a contractor has ever used, so Field PM also supports custom forms — building your own inspection checklist, safety form, or client-specific document with the same structured fields (text, checkbox, signature, photo attachment) as the pre-built library. That means a custom form gets the same treatment as a library form: it attaches to the job, shows up in the <a href="/features/form-library">form library</a> alongside everything else, and its data is queryable rather than locked inside a PDF.

In practice most contractors use maybe 15-20 of the 90+ forms regularly — the ones that match their trade and their client requirements — plus one or two custom forms for a specific client's paperwork. The value of having 90+ available is that when a new project type or a new client requirement shows up, the form is very likely already built rather than something the office has to create from scratch under deadline.

Where this fits with QA/QC and safety

The form library is the raw material for two bigger systems: <a href="/features/qaqc">QA/QC</a> tracking, where inspection forms feed nonconformance reports and closeout documentation, and <a href="/features/safety">safety</a> tracking, where JSAs and incident reports feed TRIR/DART calculations and the safety record for the project. A form filled out in isolation is just paperwork; a form filled out inside Field PM becomes data that rolls up into the reports a safety director or a QA manager actually needs at the end of the month.

None of this replaces judgment in the field — a JSA is only as good as the hazard analysis someone actually does before the task, and a toolbox talk is only as good as whether the crew actually listens. What the library does is remove the friction of finding, printing, and filing the right form, so the time goes into doing the task safely rather than hunting for the right piece of paper.