Quality & safety
Inspect work and close a non-conformance
Inspect the work against its acceptance criteria, raise a non-conformance the moment it fai…
3 steps10 minOpen
Cases / Quality & safety
Quality & safety
Run the submittals register
Log shop drawings and submittals, check them against spec, issue for review, and flag anything overdue before it stops procurement.
How it works, step by step
4 steps across the platform - what you do at each one, and why it matters.
1
Log the submittals
SubmittalsIn Submittals, log each shop drawing and technical submittal and set the date approval is needed by.
Why: A submittal approved late holds up the order, and a late order holds up the trade on site. The register is where you see that coming.
InShop drawingsTechnical submittalsOutSubmittals registerRequired-by dates
2
Attach the spec
QMSFrom QMS, attach the specification clause the submittal is checked against.
Why: A reviewer needs the spec next to the submittal, or the approval is just an opinion. It also settles later arguments about what was actually specified.
InLogged submittalSpecification documentOutAttached spec clauseReview baseline
3
Issue for review
CorrespondenceIn Correspondence, issue the submittal for review and record the status that comes back, approved, approved with comments or rejected.
Why: The returned status is the trigger to order or to resubmit, so it has to be recorded against the item. A spoken yes does not release the procurement.
InSubmittal packageDesign reviewerOutReview statusReview comments
4
Report what is overdue
ReportsIn Reports, publish the submittals log and pull out anything overdue that is blocking procurement.
Why: The people ordering materials need one clear list of what is stuck and why. Overdue submittals are the quiet reason a programme slips.
InSubmittals logReview statusesOutPublished logOverdue blockers list
Modules in this playbook
4 / 184 platform modules
