FieldAppCheck
Take the quick check

Template

Job Time Overrun Note Template (Cause Tagging)

Time overrunCause taggingNotes

Document why a job ran long and tag the cause (parts, access, scope change, customer delay, weather) so you stop guessing and fix the same problems that keep repeating. Use one note per overrun; tag one or more causes; add one line on what you did to prevent it next time. After two weeks you'll see which causes show up most—fix those first before buying more software.

For teams where jobs keep running over but nobody tracks why, or the same issues repeat and never get addressed.

Next: Use this note on every overrun for two weeks; then sit down and review which causes appear most and tackle the top two with a concrete rule or checklist.

Copy/paste template

Job Time Overrun Note Template (Cause Tagging)

  • - Job Time Overrun Note
  • -
  • - Job: [Job number/name]
  • - Planned time: [X hours]
  • - Actual time: [Y hours]
  • - Overrun: [Z hours]
  • -
  • - Cause (tag one or more):
  • - - [ ] Parts not ready
  • - - [ ] Access issues
  • - - [ ] Unexpected issue found
  • - - [ ] Customer delay
  • - - [ ] Scope change
  • - - [ ] Weather/traffic
  • - - [ ] Other: [specify]
  • -
  • - Notes:
  • - [Brief description of what caused the overrun]
  • -
  • - Action taken:
  • - [What was done to resolve or prevent in future]

How to customize

Replace placeholders:

  • [Name] → Customer or tech name
  • [time] → Arrival time (e.g., "2:00 PM" or "in 30 minutes")
  • [link] → Job link or tracking URL

Avoid these mistakes:

  • Don't use overly aggressive language (e.g., "URGENT: Payment due now!")
  • Don't use confusing abbreviations or jargon
  • Don't make promises you can't keep (e.g., "We'll be there in 10 minutes" if it's not realistic)

How to use it

  1. Fill this note as soon as the job is done when actual time beat planned time—same day so the cause is fresh.
  2. Tick every cause that applied (often it's more than one: e.g. parts delay plus scope change).
  3. Write one or two sentences in Notes: what actually happened, not a novel.
  4. In Action taken, write what you did or will do (e.g. 'Order parts 24h before next similar job' or 'Customer will leave key with neighbor next time').
  5. Once a month, skim all overrun notes and count causes; fix the top two with a clear rule or checklist before adding tools.

Common tweaks

  • Add cause tags that match your reality (e.g. 'Waiting for approval', 'Wrong part on truck').
  • Add a yes/no: 'Customer notified of delay?' so you don't forget to text when you're late.
  • Add 'Follow-up needed?' and a name so someone owns the fix.
  • If you use FSM job notes, keep the same cause list there so you can report on it later.
Back to Scheduling Mess hub

Related guides

Guides that help with this pain:

Scheduling Chaos? A Simple System for 1-5 TechsDrive Time Reduction: Intake Fields That Matter

Take the FSM quick check

See if Field Service Management tools are right for your team.

Take the FSM quick check