This is a ready-to-use form for the daily inspection debrief. The overnight window is where a well-run site changes the trajectory of an inspection: a concern raised at the wrap-up that you have visibly acted on by the next morning often softens or closes. This form captures the inspector’s end-of-day summary, reconciles the day’s requests, walks the concern list, and assigns overnight actions with owners and due times. Complete one per inspection day. Replace every <<FILL: ...>> placeholder. A filled specimen follows.
Form header
| Field | Entry |
|---|---|
| Inspection reference | <<FILL>> |
| Inspection day and date | <<FILL: Day n, date>> |
| Debrief attendees | <<FILL: host, back room lead, scribe, SMEs, leadership as needed>> |
| Prepared by | <<FILL>> |
Part 1: the inspector’s daily wrap-up (with the inspector)
Many inspectors give a short end-of-day summary of what they saw and any concerns forming. Capture it precisely; it is your early warning of where observations are heading.
| Field | Entry |
|---|---|
| Did the inspector give a wrap-up? | <<FILL: Yes / No>> |
| Topics the inspector highlighted | <<FILL>> |
| Concerns the inspector voiced | <<FILL>> |
| Any positive feedback noted | <<FILL>> |
| Requests carried to tomorrow | <<FILL>> |
Part 2: request reconciliation (internal)
| Check | Entry |
|---|---|
| Documents requested today (count) | <<FILL>> |
| Documents provided today (count) | <<FILL>> |
| Requests still open | <<FILL: list with owners>> |
| Commitments made today (from scribe log) | <<FILL: list with owners and due>> |
| Discrepancies between scribe log and request tracker | <<FILL: none / detail>> |
Part 3: concern list and overnight actions
For each emerging concern from the day, decide the action: provide additional context tomorrow, pull a document overnight that closes it, prepare a specific SME, or begin remediation now so you can show action by the closing meeting.
| Concern (source) | Decision / action | Owner | Due | Status |
|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL: open / in progress / done>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Part 4: tomorrow’s setup
| Field | Entry |
|---|---|
| Topics expected tomorrow | <<FILL>> |
| SMEs to pre-brief | <<FILL>> |
| Documents to stage overnight | <<FILL>> |
| Leadership decisions needed tonight | <<FILL: none / detail>> |
Acceptance criteria for a good debrief
- The inspector’s wrap-up (if given) is captured verbatim enough to act on.
- The day’s requests are reconciled with the scribe log; nothing is left ambiguous.
- Every emerging concern has a decision, an owner, and a due time, not just a nod.
- Overnight actions that can be closed by morning are closed and evidenced.
- Tomorrow’s SMEs and documents are staged based on where the inspection is trending.
Filled specimen
Header: Inspection Day 2, attendees host, back room lead, scribe, QA lead.
Part 1: inspector gave a wrap-up; highlighted deviation timelines and training records; voiced a concern that a training matrix cited a superseded SOP; requests carried to tomorrow: CAPA effectiveness data for DEV-2026-118.
Part 3 overnight actions:
| Concern (source) | Decision / action | Owner | Due | Status |
|---|---|---|---|---|
| Training matrix cites superseded SOP v5 (wrap-up) | Correct matrix; prepare record of correction to show tomorrow | Training lead | 07:00 | Done |
| One major deviation open >90 days (day’s questioning) | Stage justification memo and interim-controls evidence | QA | 07:00 | Done |
| CAPA effectiveness check pending for DEV-2026-118 | Pull effectiveness data; brief the CAPA owner as SME | CAPA owner | 08:00 | In progress |
In this specimen the site heard the training-matrix concern at the wrap-up and corrected the matrix overnight, so by the next morning it could show the correction rather than leave the concern to harden into a written observation. That is the difference between a debrief that is a formality and one that changes the outcome.
Common inspection findings this form prevents
- A concern raised at the daily wrap-up is heard, nodded at, and nothing is done overnight.
- The day ends with open requests and commitments that no one owns or tracks.
- The scribe log and the request tracker disagree and the discrepancy is never reconciled.
- SMEs walk into the next day cold because tomorrow’s topics were never anticipated.
How to adapt this form
- Set the inspection reference in the header and complete one form per inspection day.
- Feed Part 2 directly from your front room scribe log and back room request tracker.
- Assign a real owner and due time to every concern; a concern without both is not being managed.
- Use Part 4 to drive the next morning’s SME pre-brief and document staging.
- Retain completed debrief forms with the inspection record; they evidence the action you took between days.