Trigger · 1 of 8Start an inspection
An installer or lead opens the build and its inspection form, on the form's pinned version.
- Tool
- Inspection app
- Hands on
- An inspection entry
Step · 2 of 8Record the evidence
Findings, photos, the verdict and the sign-offs are recorded against the build.
- Tool
- Inspection app
- Hands on
- A saved inspection
Decision · 3 of 8Drive folder ready?
Before anything is filed, the build's folder is checked: it must sit on the right shared drive and be writable.
- Tool
- Google Drive
- Hands on
- A place to file, or a hold
- Ways out
- Ready: File the record · Not ready: Filing held
Step · 4 of 8File the record
A versioned record, its PDF and the photos are filed in the build's folder. Each filing is a new version, on the form it was filled in.
- Tool
- Google Drive
- Hands on
- A versioned inspection record
End · 5 of 8Filing held
The filing is kept incomplete until the folder is fixed, so nothing lands in the wrong place.
- Tool
- Google Drive
- Leaves
- A filing to correct
Decision · 6 of 8Clean build?
A clean verdict on a build the system knows can complete its quality gate. Anything else is filed without a stamp.
- Tool
- Postgres
- Hands on
- Stamp the gate, or skip it
- Ways out
- Clean: Stamp the gate · Not eligible: Tell the team
Step · 7 of 8Stamp the gate
The build's quality gate is marked complete, once. If it was already complete, the first date and name are kept.
- Tool
- Postgres
- Hands on
- A completed quality gate
End · 8 of 8Tell the team
The filing is recorded and the team is told in Slack. Slack never holds a filing up: a quiet channel changes nothing.
- Tool
- Slack
- Leaves
- The record, filed and announced