Execution Log & Feedback Loop — General SOP

SOP ID	SOP-GEN-007
Version	1.0 · Effective TODO(confirm) date
Owner	Site Manager (logging) / Owner (SOP updates)
Applies to	Every task, every site
Review	Quarterly improvement review

1 What to Record (per task)

Field	Notes
Date	YYYY-MM-DD
Site ID	Which job site (e.g. COSTCO)
SOP ID + Version	Which procedure was followed (flags stale versions)
Task / activity	Specific (e.g. "Breaker panel changeout — north wall")
Assigned to	Role + name
Start / end time	Enables productivity baselines
Status	In progress / Complete / Blocked / Failed QC
Quality gate	Pass / Fail / N/A at each critical checkpoint
Issues / deviations	What deviated from the SOP and why
Materials used	Against planned — surfaces waste / rework
Photos	Before / during / after — linked to this record
Sign-off	Worker confirms SOP version followed; site manager signs
SOP feedback	"Hardest/most confusing step?" — routes to improvement queue

📋 Live board does most of this for you

The Live Task Board captures task, assignee, status, type, priority, and SOP reference in real time and persists it. Use it as the working log; export/record the durable per-shift entry from it.

2 Printable Shift Log

Print this page for a paper backup, or use it as the end-of-shift record.

Time	Task	Who	Status	QC	Issues / photos

Shift lead: ____________________ Owner notified: ☐ Site secured + photographed: ☐

3 Feedback Loop (PDCA)

Plan — after each job, the site manager reviews logs for failed QC gates, deviations, flagged issues, and any step that ran 2× expected time.
Do — weekly: triage the week's logs; categorize each flag as (a) training gap, (b) SOP wording, (c) missing step, (d) systemic.
Check — test a proposed SOP change on the next job before issuing; confirm it resolved the flag.
Act — issue the updated SOP version; communicate the specific change (which step, why) at a toolbox talk for major changes; update the revision history.
Close the loop — each log references the SOP version used; track whether the flag rate on the changed step drops.

🔬 After-action review trigger

Any job with 3+ logged issues, a QC failure, or a safety incident gets a short AAR: what was planned, what happened, what caused the gap, what change prevents recurrence.

4 Document Control

Every SOP has an ID (SOP-GEN-00X / SOP-[SITE]-00X) and a major.minor version
Revision history table on each SOP; major bump = procedure change, minor = clarification
Superseded versions marked "SUPERSEDED — Do Not Use"; archived, never deleted (dispute/WorkSafeBC/warranty)
One controlled source of truth (this hub); printed copies are uncontrolled — check the version
Site overlays reference the master SOP version they were written against

Version	Date	Author	Change	Approved
1.0	TODO(confirm)	Liquid Rock	Initial issue	Owner

Related SOPs

🔧

Task Execution Protocol

When logging happens

📋

Live Task Board

The working log