Skip to content

Free practical resource · no email required

Construction job record template.

Keep each site note, photo and document labelled by job and work area—plus who recorded it and what needs to happen next.

Download editable CSV
UngatedNo sign-up or email form
EditableCSV for Excel or Sheets
PracticalBlank and completed examples

Enough structure to find the record later.

The useful unit is not “a folder of photos”. It is one small record tied to a job, a specific work area and a clear event. The template keeps that context beside the files.

  1. 01 / Where

    Job and work area

    Use the same project, block, floor, room, asset or section names that the site and office already recognise.

  2. 02 / When

    Date and time

    Record when the work, delivery, inspection or issue was actually seen—not when someone later filed it.

  3. 03 / What

    Type and short note

    Choose one useful category and add a short factual note that will still make sense months later.

  4. 04 / Evidence

    Photo or document names

    List the attached filenames so the record and the original files can be matched without guesswork.

  5. 05 / Ownership

    Recorded by

    Keep the name or role of the person who created the record, using a format agreed by the team.

  6. 06 / Next action

    Owner, due date and status

    If the record needs a response, make the next action visible instead of burying it inside the note.

Use this on paper or adapt it to your spreadsheet.

Print this page for a simple paper version, or download the CSV and change the labels to match one real workflow.

Delaney Works · free template

Construction job record

Record reference
________________

Job
Work area or section
Date
Time
Record type
Progress Inspection Delivery or document Snag or issue Other
Short factual note
Photo or document name What it shows Stored location
Recorded by
Status
Filed Needs action Closed
Follow-up action
Follow-up owner
Due date
Download the blank CSV

The CSV contains only the field headings and a blank row. Open it in your usual spreadsheet tool and adapt it before use.

What one useful record can look like.

Keep the note short, keep the labels consistent, and keep any follow-up separate from the observation itself.

Riverside Apartments — Block C

Fictional information · example only

Date and time
23 July 2026 · 14:10
Work area
Roof level 04 — west section
Record type
Progress photos and site note
Short note
Membrane completed to gridline C7. Upstands ready for inspection.
Attachments
progress-photo-01.jpg
upstand-detail.jpg
Recorded by
Site supervisor
Follow-up
Review upstands before the area is covered.
Owner and due
Project engineer · 24 July 2026
Status
Needs action

Start with one record type on one current job.

A small shared convention is easier to test than a complete new reporting system.

  1. Pick the record that causes chasing.

    Choose one repeated item: progress photos, delivery records, inspection photos, snags or service evidence.

  2. Agree the labels first.

    Write down the exact job, work-area, record-type and status names people should use. Fewer clear options usually work better than free-form naming.

  3. Decide where the record lives.

    Use one agreed job folder, spreadsheet or existing system. The template should point to the files, not create another disconnected copy.

  4. Test it for one week.

    Ask the office whether the records arrived complete and whether anyone could find a specific note or photo without asking the person who created it.

  5. Automate only the proven friction.

    If the format is useful but copying, naming or routing still takes time, that is the part worth improving with software.

This is an operational starter, not a compliance system.

Adapt the fields with the people responsible for your contracts, quality, safety and record-keeping requirements. This general template is not legal advice, a statutory site diary, a safety record or a substitute for an approved company process.

Show me the workflow you use today.

Bring one repeated process and a real recent example. I’ll help you decide whether the problem needs a clearer template, better use of existing software, or a small custom workflow. See exactly what the small first build includes.

Or email emmet@delaneyworks.ie.