Field reporting

Construction inspection log checklist: requests, results and corrective work

An inspection log should identify the work area, inspection type, requested date, attendance, result, source and corrective or reinspection action. Keep requested, attended, passed and accepted distinct. A text saying “inspection done” does not prove the work passed or authorize concealment.

Record what is known, not what is assumed

Completion of a request, attendance and acceptance are different events. Check the project’s inspection and hold-point requirements before treating “complete” as permission for the next activity.

StateMeaning
RequestedRequest exists; attendance and result unconfirmed
ScheduledDate arranged; visit has not necessarily occurred
AttendedAttendance known; result still needs evidence
Result receivedReport identifies outcome and conditions
Corrective workAction, owner and evidence recorded
Reinspection or closureRequired follow-up and actual result recorded

Minimum useful inspection fields

  • Date, location and exact work inspected.
  • Inspection type and drawing, specification or test reference.
  • Request reference and planned contact or attendance.
  • Actual attendance and inspector identity where appropriate.
  • Result source, conditions and attachments.
  • Corrective action owner and agreed follow-up date.
  • Reinspection reference and closure evidence.

Inspection does not automatically release responsibility

On federal contracts incorporating FAR 52.246-12, the contractor must maintain an adequate inspection system and complete inspection records. Government inspection does not relieve contractor quality-control responsibility, imply acceptance or let an inspector change contract terms without required authority.

That clause is not a universal private-project rule. Check the quality plan, permits, specifications and contractual authority before treating a visit or verbal comment as permission to proceed.

Give each open item an owner

The GC often coordinates inspection results with access and the next trade. Link unresolved results to the affected activity and confirm whether work must remain exposed. A subcontractor needs preparation requirements, evidence to provide and a named reviewer for corrective work.

Record an issue factually: observation, source, requested remedy and response. An unresolved inspection alone does not establish liability or justify a backcharge. Commercial responsibility requires a separate review.

A message should trigger clarification

This is illustrative. Magra can help organize reported facts and ask for missing information in project context. It does not inspect physical work, certify compliance or replace an authorized quality reviewer.

ILLUSTRATIVE EXAMPLE
Foreman: “Level 6 inspection done.”
Follow-up: Which inspection? Passed, failed or conditional? Can you attach the report?
Record pending evidence: Attended; result unconfirmed.
Review: Confirm outcome and any hold-point or reinspection requirement.

Common questions

What should be included in a construction inspection log?

Area, work, inspection type, request and attendance dates, result source, conditions, corrective action owner, attachments and reinspection or closure evidence.

Does inspection completed mean the work passed?

No. Completion of the visit does not establish the result. Obtain the report or authorized outcome and record conditions separately.

Can Magra update inspection records from a text?

Magra’s field-update workflow can help prepare records from supplied messages and evidence. Confirm report fields; a responsible person verifies the outcome and permission to proceed.

Sources & editorial note

By Magra editorial. Examples are illustrative, not customer results. Not legal advice; executed documents, amendments and applicable law govern. Product availability can change.

Put the record to work.

Magra is the AI project manager for contractors, on your phone.

Explore Magra’s missing-record and follow-up checks · Text Magra

Keep reading