Field Work Report

Use the sections that fit the mission. Delete the rest. Replace every [placeholder] before you send.

Publisher: Liquid Consulting. Free to adapt with attribution to Liquid Consulting.

Use the sections that fit the mission. Delete the rest. Replace every [placeholder] before you send. Keep page breaks tidy and refresh the contents list last.

Companion blank: field-work-report-daily-log.csv for the daily log rows.

Cover

Client / city
[Client name, city]
Date of service
[YYYY-MM-DD to YYYY-MM-DD]
Liquid service work order
[Work order number]
Equipment type and serial number
[Type and serial]
Type of service
[One sentence purpose]
Liquid field engineer
[Name]
Customer contacts
[Name, role, email, phone]
Distribution list
[Name 1], [Name 2], [Your reports inbox]

Summary

Write so anyone interested can see the whole mission in about one page. Skip deep technical detail here (that belongs in the body).

The summary must answer:

  1. Why were we there, and what was the task?
  2. Did we solve the task?
  3. What were the most important activities and findings?
  4. What remains open?
  5. What was agreed in the final meeting with the project lead and the customer?
  6. What do we recommend next to improve the operation?

For commissioning, state the phase in plain words, for example: installation supervision, I/O check, water test, production test, sterile test, commercial production, or performance validation. Note crucial remaining items for that phase. Include key dates such as media available, first successful water trial or CIP, first product in, first commercial production.

Remaining items or to-do

List only what still matters for the current phase. Do not pad with work that belongs to a later phase.

  • [ ] [Item]
  • [ ] [Item]

Parts or support needed

For parts: what, why, and item number if known. For support: who or which function, and what you are waiting on.

[Part or support]
[Reason] — [Name or function]

Improvement recommendations

What would help the customer’s operation, performance, equipment, or competence next? Which Liquid services could support that on a later visit?

  • [Recommendation]

Agreements and meetings

Initial start-up meeting

Date
[YYYY-MM-DD]
Participants
[Names]
Agreements
[Plant availability, hours, people, media, access, success criteria]

Final wrap-up meeting

Date
[YYYY-MM-DD]
Participants
[Names]
Agreements
[Mission complete or not, remaining items, next visit]

Other meetings (optional)

Meeting [YYYY-MM-DD]

  • Participants: [Names]
  • Agreements: [Notes]
  • Next meeting: [YYYY-MM-DD]

Installation

Use during installation, or when installation issues appear during commissioning. Cover work outside the process-module boundary. Electrical covered by the electrical manual belongs under Electrical.

Mechanical

[Results, issues, steps, notes]

Electrical (installation)

[Results, issues, steps, notes]

Supply and utilities

[Installation notes, remaining items, major delays, interruptions, or deviations]

Water tests

Delete this section if you have nothing useful to say. Many water trials do not need a narrative.

Water test #n

[Results, issues, steps, notes]

Sterility test

[What was planned]

Sterility test #n

[Results, issues, steps, notes]

CIP

Note chemical supplier and detergent types when relevant (for example membrane work). For most modules, focus on deviations and local adaptations.

CIP #n

[Results including concentrations, issues, steps, notes]

Production

Note trials and commercial runs. Put detailed process parameters in the parameter list. Here record volumes, product type, start and stop times, alarms, and deviations. If a run was smooth, say so clearly.

Production #n

[Results, issues, alarms, start/stop, volume, total time]

Performance validation

[Results against the project’s specified criteria]

Electrical

Corrections that belong in the electrical manual for the module or line.

Electrical manual correction #n

[Change needed, with screenshots or markups when useful]

Automation

Faults and on-site program changes. Give each change its own short heading, screenshots after the change, and why the solution was chosen.

  • [ ] Temporary settings and trace tags removed from PLC and HMI programs before leave.
  • [ ] Verified backups taken, stored on the Liquid team site, and sent to the project lead.

[Short description of change or issue]

[Issue, steps, notes, why this solution]

Daily log

Fill this every day on site. Copy points 1 to 4 into the daily email to the project manager, with [Your reports inbox] on CC. Do not email point 5 (internal only).

Email subject pattern: [Project name/code] [Order description] FWR Wxx (replace Wxx with the work-week number).

Put start-up meeting notes into the first day’s log. Put wrap-up notes into the last day’s log. Those feed the weekly summary.

Use field-work-report-daily-log.csv or the blocks below.

[YYYY-MM-DD] [Weekday] - [HH:MM] to [HH:MM]

  1. Today’s notes

1. Important customer issues (meetings or informal)

2. Highlights worth mentioning

3. Completed items (short)

4. Planned but not achieved, and why

  1. Delays the project lead must know about
  2. Support or parts needed

1. Help needed from the project lead

2. Parts to order or parts waiting

  1. Plan for tomorrow
  2. General notes (internal only - do not email)

Reminders, PID or program notes, links to local files, investigation detail for your own later write-up.

Attachments

Prefer integrating photos into the body (two-cell tables work well). Use this section only when a picture does not fit cleanly. Refer to each attachment from the text.

Attachment 1

[Description, steps, notes, images]

Attachment 2

[Description, steps, notes, images]

Before you send

  • [ ] Placeholders and unused headers removed
  • [ ] Summary answers the six required questions
  • [ ] Page breaks checked (no empty pages)
  • [ ] Contents / outline updated
  • [ ] Spell check done
  • [ ] PDF plus editable file ready for stakeholders
  • [ ] Daily log for the last day complete
  • [ ] Backups and documents uploaded to the Liquid team site

Suggestions to improve this template: [Your reports inbox]

More Free Field Resources

Browse the resources hub for related templates and training guides.

Talk To An
Automation Engineer

Tell us what you run and how it is reached today. You will speak with an automation engineer, not a sales rep. We respond within one business day.

If you are not ready to talk Work through the self-check list. It costs nothing and it will tell you whether you have a problem.
Advisory AA26-231A, August 19, 2026