Documenting A Mission

Documentation is a large part of the value customers place on a commissioning or service supplier. This guide is the minimum document set Liquid expects on every end-customer site mission.

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

Documentation is a large part of the value customers place on a commissioning or service supplier. It is often the lasting record for later troubleshooting. The aim is high quality without turning engineers into bureaucrats.

This guide is the minimum document set Liquid expects on every end-customer site mission that is commissioning, troubleshooting, or technical service. Always confirm with the project lead (and the ordering party) whether extra customer forms are required before you start. Ask early so you are not surprised on day one.

Saving finished files to the Liquid team site matters as much as writing them. When a colleague gets a question months later, being able to pull the right report or backup in minutes is what “professional” looks like.

Why documentation is part of the job

  • The field work report is how you talk to the project lead week by week.
  • Daily notes become the weekly summary; the weekly summary becomes the lasting mission record.
  • Memories fade; disputes do not. The report is what remains.
  • Customers who run continuous improvement expect delays and open items to be visible, not hidden.

Core document set

This guide (Documenting a mission)
Reference before and during the mission — Keep as reference
Start-up and wrap-up meeting notes
First day and last day on site — Copy into the daily log and the field work report
Time reporting (company instructions)
Every day on site — Per company time rules (usually weekly)
Field work report (FWR)
Open every morning; update during the day — Daily email excerpts; full weekly pack at end of week / end of visit
Correction / punch list (if the project uses one)
Every day when faults or delays appear — Usually with the weekly pack
Mission workflow chart (internal)
Prep through handoff — Reference

Blank FWR: see Field work report template and field-work-report-daily-log.csv in this folder.

Start-up meeting (first day)

Hold it before deep work starts. Prefer agreeing the meeting before you arrive. Introduce yourselves, exchange contacts, and leave with shared expectations.

Cover at least:

  • [ ] Who is the project lead?
  • [ ] What was ordered?
  • [ ] Who is involved on site?
  • [ ] What is the time schedule?
  • [ ] When do we have access to the equipment?
  • [ ] What is the expected result?
  • [ ] What extra material or tools are needed now?
  • [ ] Any extra customer requests, written down

Put the minutes into the first daily log and into the FWR. If something is urgent or disputed, escalate to the project lead or Liquid management the same day.

Start-up minutes (copy block)

Date
Participants
Project lead
Customer contact (name, email, phone)
Ordered scope
On-site people
Schedule
Equipment access
Expected result
Extra tools / material
Extra customer requests

During the mission

Daily discipline

  1. Open the FWR first thing on site.
  2. Enter yesterday’s leave time and today’s arrival time.
  3. Update continuously: agreements, automation changes (with screenshots), electrical-manual corrections, customer issues.
  4. Before you leave site, finish points 1 to 4 of the daily log and put the daily email in the outbox.
  5. Point 5 of the daily log stays internal. Do not email it to the customer.
  6. Back at lodging (or as soon as you have a link), send the mail and upload files to the team site.

What the daily email must include

Copy only:

  1. Today’s notes (issues, highlights, completed, not achieved)
  2. Delays the project lead must know
  3. Support or parts needed
  4. Plan for tomorrow

Subject pattern: [Project name/code] [Order description] FWR Wxx

CC: [Your reports inbox] plus anyone else who needs the daily update.

Weekly pack (usually last day of the week on site)

  • [ ] Summary completed (written during the week, finished today)
  • [ ] Spell check
  • [ ] Page breaks checked
  • [ ] Contents / outline updated
  • [ ] Converted to PDF
  • [ ] PDF + editable file + supporting docs emailed to stakeholders
  • [ ] Same pack uploaded to the team site

Field work report quality bar

The FWR summary must answer:

  1. Why were we there?
  2. Did we solve the task?
  3. Main activities and findings?
  4. Remaining issues?
  5. What was agreed in the final meeting?
  6. Recommendations for the future?

Use only the body sections that fit the mission. Delete unused headers. Prefer photos in the body over a dumping ground of attachments.

Automation changes: one heading per change, screenshot after the change, temporary tags removed, backup verified before you leave.

Wrap-up meeting (last day)

Do this before you leave site. Confirm whether the mission is complete, capture remaining items and owners, and write down customer feedback.

Cover at least:

  • [ ] Short summary of what was done
  • [ ] Agreement: mission finalized or not
  • [ ] Remaining items
  • [ ] How and when remaining items will be solved
  • [ ] Customer feedback and extra requests

Put the minutes into the last daily log and into the FWR summary.

Wrap-up minutes (copy block)

Date
Participants
Summary of work done
Mission finalized? (yes / no)
Remaining items
Plan and timing for remaining items
Customer feedback

Correction and delay tracking (when the project uses it)

If the project requires a correction or punch list:

  • Track real delay caused by the fault, not only the length of the interruption. Example: media lost for ten minutes that forces a two-and-a-half-hour recovery is reported as two and a half hours.
  • Waiting for product, people, or decisions that shift a planned trial counts as delay even if you used the time on other useful work.
  • On troubleshooting, time spent finding and proving the fix belongs on the list.
  • No delay is too small to record if the customer runs a continuous-improvement culture.

Keep customer names, plant codes, and commercial figures out of any public or shared training copy of these lists.

Handoff checklist

  • [ ] Start-up minutes in first daily log and FWR
  • [ ] Daily emails sent every working day (points 1 to 4 only)
  • [ ] Weekly FWR pack complete and uploaded
  • [ ] Time reported per company instructions
  • [ ] Correction / punch list current (if used)
  • [ ] Automation and documentation backups on the team site
  • [ ] Wrap-up minutes in last daily log and FWR
  • [ ] Open items have owners and dates

Questions or improvements: contact.us@liquidconsulting.com

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