Daily Field Report Template (US)

Updated on October 1, 2026

A daily field report is the operational record of what happened away from the office. It is used on construction sites, installation jobs, field service routes, maintenance visits and other work where the facts change by the hour: weather, crew, subcontractors, equipment, deliveries, delays, safety issues, customer decisions and work completed. A useful report does not read like a diary. It creates a neutral record that a project manager, client, insurer, safety officer or scheduler can understand weeks later.

The Jotform source shows a real field-services daily report but provides no direct PDF. This US master rebuilds it as a fuller jobsite log with the fields the screenshot was missing: scope completed, crew hours, equipment responsibility, weather-delay facts, material deliveries, observations, safety notes, photos or attachments, unresolved issues and reviewer sign-off. It is not an invoice, a quote, a change order or an OSHA injury report; it links to those workflows when needed.

1 of 15 blanks filled

Tap any highlighted blank in the document below and type straight into it.Free — no sign-up, no watermark

Other details

Report title

Daily Field Report

Report date:
Project or program:
Location:
Prepared by:

1. Weather and Site Conditions

2. Crew and Subcontractors

3. Work Performed

4. Deliveries, Materials and Equipment

Deliveries and materials:

Equipment on site, rental responsibility and condition:

5. Delays, Blockers and Safety Routing

Delays, access issues, customer decisions or blockers:

Safety observations, near misses, incidents or required routing:

6. Summary and Follow-Up

Open corrective actions, coaching items, missing information, approvals, or escalation steps:

7. Review

Reviewed by . The reviewer should confirm that this report is complete for ordinary operational use and route any incident, injury, payroll, privacy, licensing, or contractual issue into the required controlled process.

Prepared by

Date signed:

Reviewer

Date signed:

Record facts while they are fresh

Field reports become valuable when they are completed the same day, before memory turns into negotiation. The template starts with date, site, weather, prepared by, customer or project reference, crew and subcontractors. Those fields make later disputes easier to sort because they show who was present, what conditions existed and what work the team says it performed.

The document separates observations from conclusions. A supervisor can record that access was blocked until 10:30 a.m., a lift was rented by a subcontractor, three pallets arrived damaged, or rain stopped exterior work after lunch. Whether those facts justify an extension of time, extra charge or claim belongs in the project contract process, not in loose report language.

Keep work progress distinct from billing

Jotform often lets quote, estimate, invoice and report intent blur together. This template keeps the daily report in its lane. It records work performed, labour hours, materials delivered and equipment used, but does not demand payment or certify final acceptance. If the report supports a later invoice, work order or change order, the reference number can be added without turning the report into that document.

That firewall matters for SEO and for project control. A daily report should be searchable by date, site and crew, then reconciled against work orders, photos, delivery notes and the contract schedule. It should not be the only evidence of a priced variation or the only customer authorization for extra work.

Safety observations need a routing path

A daily report can note safety observations, near misses or incidents, but it should not pretend to replace the employer recordkeeping process. OSHA recordkeeping rules use specific forms and criteria for recordable injuries and illnesses. The report therefore includes a safety flag and an escalation line, rather than burying the issue in general comments.

For ordinary observations, the template asks for hazard, location, responsible person and follow-up date. For an injury, illness or serious incident, the report prompts the user to open the controlled safety process. That avoids the Jotform problem of treating a serious compliance workflow as a generic text box.

Delays should capture cause, duration and effect

A useful delay entry says more than "delayed." It records the cause, start and end time, affected crew or task, mitigation taken, and whether notice was sent under the contract. The template includes these fields so the daily report can support a future schedule discussion without overclaiming that a delay claim has already been approved.

Weather is handled the same way. The report records conditions, temperature and practical effect on the work. A project team can then compare the daily log to weather data and schedule terms later. The document does not declare entitlement by itself.

A reviewer sign-off protects the record

Daily reports are often prepared by foremen, technicians or subcontractors. A reviewer sign-off gives the company a chance to catch missing attachments, unclear customer instructions, unsafe conditions or statements that conflict with the contract. The template includes a reviewer line and an issue-routing section.

The sign-off is not a warranty that every fact is perfect. It is a control that shows the business reviewed the report and sent sensitive matters into the correct workflow. That is much better than Jotform-style reports that end at a comments box and a generic signature.

Clause and field guide

Project and date: Identifies the job, site, report date, customer reference and person preparing the report.
Weather and site conditions: Records conditions that affected productivity, access, drying time, exterior work or safety.
Crew and subcontractors: Lists people, companies, hours and roles without turning the report into payroll.
Work performed: Describes tasks completed and work areas in neutral operational language.
Deliveries and equipment: Tracks materials, tools, rented equipment, responsible party and condition on arrival.
Delays and blockers: Captures cause, duration, affected task, mitigation and whether formal notice may be needed.
Safety and incidents: Flags hazards and incidents for the controlled safety process instead of hiding them in notes.
Review and sign-off: Shows the report was checked and assigns follow-up ownership.

US compliance checklist

Use this as an operational daily log. It is not a substitute for OSHA injury and illness forms, payroll records, change orders, invoices or required notices under a project contract.

Route recordable injuries to OSHA recordkeeping
Covered employers must use OSHA Forms 300, 300A and 301 or equivalent forms for recordable work-related injuries and illnesses.
OSHA recordkeeping forms and recording criteria
Do not treat safety notes as the whole incident report
If an event meets OSHA criteria, complete the controlled incident workflow rather than relying on daily report comments.
OSHA 29 CFR 1904.29 recordkeeping forms
Keep payroll and immigration data out of the report
Crew hours can support project records, but sensitive personnel data belongs in HR/payroll systems with proper access controls.
Separate delay facts from claims
Record cause and effect, then use the contract notice/change-order process for entitlement or cost claims.
Preserve attachments consistently
Photos, delivery tickets, inspection notes and customer directions should be stored with the project record, not only on a phone.

How to use this template

Fill the site facts first. Enter date, project, location, weather, prepared-by details and customer or contract reference.
Log crews, work and materials. Record who was on site, what they did, what arrived, what equipment was used and what was incomplete.
Flag exceptions. Use the delay, safety and issue fields for anything that needs formal follow-up.
Attach evidence. Add photo, delivery ticket, inspection, customer direction or equipment records where they support the facts.
Review before filing. Have a supervisor check the report and route any change-order, safety or customer notice issue.

Frequently asked questions

Is a daily field report the same as a work order?

No. A work order authorizes or assigns work. A daily field report records what happened during the work and should cross-reference the work order when one exists.

Can this report approve extra charges?

Not by itself. It can document facts that support a later change order, but pricing and approval should follow the contract change process.

Should incidents be written here?

Briefly flag them here, then open the required safety or incident-report process. The daily log should not be the only record of a reportable event.

Who should sign the report?

Usually the foreman, supervisor, technician lead or project manager prepares it, and a manager or client representative reviews it if the contract requires review.

How long should field reports be kept?

Retention depends on the contract, state law, insurance, tax and safety rules. Keep them consistently with the project file and any litigation hold.

Can subcontractors use it?

Yes, but they should make clear who prepared the report and whether the general contractor, owner or customer has reviewed it.

Related templates

Disclaimer

This template and guide are general information only, not legal, tax, employment, privacy, licensing, financial, safety, or childcare advice. No attorney has reviewed your facts, and nothing here is certified as compliant or approved by a regulator. Federal, state, local, industry, and contract rules differ and change. Check the current rules that apply to you and take professional advice before you sign, send, publish, or rely on this document.