Contractor action lists

Give contractors an action list, not an entire inspection archive.

Filter the project to the work that remains, preserve the evidence and required action, and send a document designed for execution.

PDF + XLSX + CSV
Reports, editable workbooks, and registers
No account required
Local, offline-first capture
Evidence-led
Photos, integrity records, action, and closeout
Example SiteReportKit report output relevant to contractor action lists

This is a real report preview. Download the complete PDF to assess structure, legibility, and handoff quality.

The operational problem

A clear action list reduces retyping and keeps references consistent with the complete project report and later closeout evidence.

Large reports can hide the next action. A contractor action list narrows the handoff to open items while retaining the identifiers and evidence needed to find, price, complete, and verify each task.

Who this is for: Main contractors, subcontractors, trade supervisors, fit-out teams, contract administrators, and client representatives coordinating outstanding works.

What a reliable field record needs

Every item should be understandable without relying on the inspector’s memory. Keep the description factual, make the location findable, show enough photographic context, and write the required action as an outcome that can be checked. Responsibility and due dates make the register actionable; status and closeout evidence make it traceable.

StageUseful output
CaptureArea, trade, owner, priority, status, date, notes, and photographs stay attached to one item.
HandoffGenerate a full report, a focused action list, or a CSV register from the project record.
Follow-upRetain the original condition, add resolution notes and after evidence, and issue a closeout record.

A three-stage workflow

01

Prepare

Capture all findings once in the project register.

02

Capture and review

Filter by status, trade, assignee, area, or the scope needed for the handoff.

03

Issue and close

Export the focused PDF or CSV and use the same item references during follow-up.

Field and report checklist

Adapt the checklist to your role, contract, jurisdiction, records policy, and the technical scope of the visit. SiteReportKit organises information; it does not confer inspection authority or make professional judgments for the user.

  • Stable item references
  • Area and location
  • Evidence and annotation
  • Required corrective action
  • Responsible trade or assignee
  • Due date and current status

Report quality checks before issue

  1. Confirm the title, author, date, site, client, scope, and intended recipient.
  2. Check that item references are unique and locations use one consistent hierarchy.
  3. Remove duplicates and split conditions that require different owners or closeout decisions.
  4. Verify captions, annotations, names, dates, status, and required actions against the field record.
  5. Open the exported PDF, XLSX, or CSV, inspect image legibility, page breaks, filters, and counts, then store the issued version under the project’s records process.
SiteReportKit sample report cover

Inspect the output

Download a real SiteReportKit sample.

Review the cover, summary, issue structure, evidence pages, responsibilities, and closeout presentation before deciding whether the workflow fits your reports.

Frequently asked questions

Questions about contractor action lists

Can the action list contain only open items?

Yes. The project can be filtered before export to focus on outstanding work.

Why not send the full client report?

The full report may include context, accepted items, and presentation material that does not help a trade complete its immediate scope.

Can I also provide CSV?

Yes. CSV is useful when the recipient needs to sort or coordinate the register in another tool.

Does the action list replace the project record?

No. It is a scoped handoff generated from the broader project record.

Continue exploring

Related SiteReportKit guides and workflows