Staff/Privacy Dry-Run Debrief Template
Purpose
Help the operator structure a non-app debrief after a staff/privacy dry-run: what was confusing, what questions stayed unresolved, what evidence was missing, what safety boundaries held, what stop conditions appeared, and what should become future planning work.
Debrief observations must be documented outside the app. This page is static guidance only and does not create records, collect approvals, store evidence gaps, or change implementation status.
Current Debrief Boundary
Debrief status
read-only-debrief-template
Dry-run status
not-conducted
Debrief record status
not-recorded
Observation storage status
not-stored
Evidence gap storage status
not-stored
PDF generation status
not-generated
Export status
not-generated
Decision status
not-recorded
Implementation status
not-started
Live pilot decision
no-go
Intended Audience
Role labels only. No staff names, resident names, emails, direct contact details, or identity details are included.
Debrief Roles
operator-facilitator
walks through the dry-run result and keeps the debrief within no-go boundaries
Boundary: no live approval authority; no app storage
approval authority: noneprivacy-gap-reviewer
identifies privacy, identity, retention, deletion, and distribution gaps
Boundary: gap review only; no decisions recorded
approval authority: nonestaff-workflow-gap-reviewer
identifies review, escalation, harmful-content, and staff workflow gaps
Boundary: gap review only; no staff action created
approval authority: nonetechnical-gap-reviewer
identifies schema, route, API, access, audit, rollback, and migration gaps
Boundary: gap review only; no implementation authority
approval authority: nonelanguage-risk-reviewer
identifies places where wording could imply approval, launch, surveillance, punishment, or clinical claims
Boundary: language review only; no approval authority
approval authority: noneoutside-app-note-taker
records debrief observations outside the app only
Boundary: no notes, observations, approvals, or decisions are stored in the app
approval authority: noneRequired Source Pages
| Route | Debrief purpose | Must confirm | Must not imply | Status |
|---|---|---|---|---|
| /protected-preview/staff-privacy-review-dry-run-checklist/ | Use as the primary source for dry-run sequence, stop conditions, pass/fail criteria, and observation categories. | manual dry-run status; not-conducted rehearsal status; no-go boundary; stop conditions | official review completion; approval recording; decision storage; live workflow activation | manual-reference-only / not-generated / not-recorded / not-stored |
| /protected-preview/review-packet-staff-handoff-notes/ | Use to review whether the non-technical framing stayed clear and no approval was implied. | read-only handoff status; no-go status; what not to claim; after-meeting boundaries | official approval; decision recording; launch readiness; staff action creation | manual-reference-only / not-generated / not-recorded / not-stored |
| /protected-preview/review-packet-visual-qa-checklist/ | Use to review visual, stale-reference, navigation, blocked-chip, print, and safety-boundary findings. | manual visual QA status; content exclusion checks; pass/fail guidance | generated files; approval controls; export/download controls; sensitive content | manual-reference-only / not-generated / not-recorded / not-stored |
| /protected-preview/review-packet-manual-assembly-checklist/ | Use to review packet order, required pages, optional appendices, exclusions, redaction, and distribution boundaries. | manual-only assembly status; required page list; exclusion checklist; sharing boundaries | automated assembly; download generation; approval recording; decision storage | manual-reference-only / not-generated / not-recorded / not-stored |
| /protected-preview/staff-privacy-review-packet-summary/ | Use to review whether the compact packet map was understandable and meeting-ready. | read-only summary status; no-go boundary; evidence and review sequence | approval collection; decision storage; live workflow wording | manual-reference-only / not-generated / not-recorded / not-stored |
| /protected-preview/draft-pilot-evidence-package/ | Use to review missing evidence, unresolved gates, and policy categories before implementation can proceed. | planning-only evidence categories; unresolved decisions; required approvals | live pilot approval; database behavior; identity details; real draft content | manual-reference-only / not-generated / not-recorded / not-stored |
| /protected-preview/staff-privacy-decision-record-template/ | Use to review whether decision areas stayed unresolved and did not look like recorded approvals. | unresolved defaults; not-approved checklist; Primary print layout | approval controls; staff decision records; save controls; stored outcomes | manual-reference-only / not-generated / not-recorded / not-stored |
| /protected-preview/staff-privacy-review-walkthrough-script/ | Use to review presenter language, expected objections, safe answers, and no-go framing. | opening no-go frame; reviewer questions; safe answers; safety reminders | official review completion; approval collection; decision storage; live workflow wording | manual-reference-only / not-generated / not-recorded / not-stored |
Optional Source Pages
Operator is technical appendix/reference only. Demo is product context only. Optional references should not dominate the debrief. The core debrief should remain concise and should document outcomes outside the app.
Demo Hub
Product context only.
optional-referenceOperator Status
Technical appendix/reference only.
optional-referenceDraft Pilot Activation Readiness
/protected-preview/draft-pilot-activation-readiness/
No-go activation readiness reference.
optional-referenceDraft Pilot Implementation Plan
/protected-preview/draft-pilot-implementation-plan/
Future implementation planning reference.
optional-referenceDraft Pilot Architecture Package
/protected-preview/draft-pilot-architecture-package/
Architecture planning reference.
optional-referenceAudit Logging Policy
/protected-preview/audit-logging-policy/
Audit planning reference.
optional-referenceRetention and Deletion Policy
/protected-preview/retention-deletion-policy/
Retention/deletion planning reference.
optional-referenceMorning Sheet Visibility Policy
/protected-preview/morning-sheet-visibility-policy/
Visibility planning reference.
optional-referenceStaff Review Procedure
/protected-preview/staff-review-procedure/
Review procedure planning reference.
optional-referencePull-Up / Push-Up Draft Schema
/protected-preview/pullup-pushup-draft-schema/
Draft schema planning reference.
optional-referenceRecommended Debrief Sequence
- Confirm the dry-run was not an official review. manual-read-only
- Confirm the app recorded no decisions. manual-read-only
- Confirm no approvals were collected. manual-read-only
- Confirm no notes or observations are stored in the app. manual-read-only
- Review whether every required packet page loaded. manual-read-only
- Review whether no-go status was clear. manual-read-only
- Review whether reviewer questions could be answered safely. manual-read-only
- Review whether any wording implied launch, approval, surveillance, punishment, clinical claims, or live storage. manual-read-only
- Review evidence gaps. manual-read-only
- Review privacy gaps. manual-read-only
- Review staff workflow gaps. manual-read-only
- Review technical gaps. manual-read-only
- Review support/incident/rollback gaps. manual-read-only
- Review print/navigation/readability issues. manual-read-only
- Decide what should become a future planning phase. manual-read-only
- Confirm implementation remains no-go. manual-read-only
Debrief Sections
dry-run-summary
What was rehearsed and what remained no-go.
Status: static-read-only; storage: not-stored
reviewer-confusion
Where reviewers might misunderstand the packet as approval, launch, or live workflow.
Status: static-read-only; storage: not-stored
evidence-gaps
Missing proof or policy evidence before implementation can proceed.
Status: static-read-only; storage: not-stored
privacy-gaps
Identity, claims, retention, deletion, distribution, redaction, and consent gaps.
Status: static-read-only; storage: not-stored
staff-workflow-gaps
Reviewer permissions, escalation, harmful content, subject notification, and staff workload gaps.
Status: static-read-only; storage: not-stored
technical-gaps
Schema, migration, route, API, audit, rollback, and access-control gaps.
Status: static-read-only; storage: not-stored
language-risks
Phrases that sound like approval, clinical claims, surveillance, punishment, tracking, or launch readiness.
Status: static-read-only; storage: not-stored
stop-conditions
Any reason the dry-run should stop or remain unresolved.
Status: static-read-only; storage: not-stored
visual-readability-issues
Print layout, navigation, stale references, long tables, blank gaps, and appendix placement.
Status: static-read-only; storage: not-stored
future-planning-candidates
Issues that might become future planning phases only after review.
Status: static-read-only; storage: not-stored
Observation Categories
- observations are not stored in the app
- observations should be documented outside the app
- observations should not become approval records
- observations should not contain real resident/staff data
Evidence Gap Categories
Confusion-Risk Categories
- reviewer thinks the pilot is live
- reviewer thinks approval was recorded
- reviewer thinks decisions are stored
- reviewer thinks a PDF/export was generated by the app
- reviewer thinks drafts are collected
- reviewer thinks identities are stored
- reviewer thinks staff decisions are active
- reviewer thinks Morning Sheet placement is active
- reviewer thinks AI reviews real drafts
- reviewer thinks attendance/participation/scoring exists
- reviewer thinks the app is clinically validated
- reviewer thinks demo/product context is implementation evidence
Stop-Condition Review
Pass/Fail Interpretation
Dry-run debrief passes only if
- the dry-run was clearly understood as unofficial
- no decisions were recorded
- no approvals were collected
- no observations were stored in the app
- no required page implied live workflow
- no sensitive content appeared
- no stale current-next phase references appeared
- no protected live routes or protected APIs exist
- no database reads/writes exist
- all open issues can be turned into outside-app evidence gaps or future planning items
Dry-run debrief fails if
- any reviewer believes the pilot is approved
- any reviewer believes implementation can begin
- any reviewer believes the app stores identities, drafts, decisions, or observations
- any reviewer believes tracking/scoring/analytics exists
- any page contains forms, inputs, selection controls, textareas, buttons, approvals, exports, downloads, or live workflow controls
- required evidence gaps are not clearly captured outside the app
- the app contains protected live routes or protected APIs
Outside-App Documentation Guidance
- document debrief notes outside the app
- do not copy real resident/staff data into the app
- do not create a decision record in the app
- do not store approvals in the app
- do not store evidence gaps in the app
- convert outside-app debrief outcomes into a future planning prompt only after review
- keep debrief notes separate from live resident workflow systems
- keep the current app state no-go
What Not To Document
After-Debrief Boundaries
- do not enter debrief notes into the app
- do not create resident/user/account records
- do not collect draft content
- do not create staff decision records
- do not create approval records
- do not create protected APIs or live routes
- do not activate migrations
- document feedback outside the app
- use Staff/Privacy Evidence Gap Register only as read-only planning guidance for categorizing gaps
- do not store evidence gap rows or owners in the app
- convert feedback into a future planning phase only after review
- keep implementation no-go until approvals and technical gates are complete
What Remains Blocked
Recommended Next Phase
Phase 10.21 — Staff/Privacy Review Packet Handoff Freeze, Planning Only
The debrief template now points through read-only evidence gap register and evidence gap review sequence planning. The next planning phase may freeze packet route order, review status, and handoff instructions as a no-go review artifact while keeping approvals, decisions, protected APIs, protected live routes, reads, writes, storage, and workflow activation blocked.
Boundaries: no note capture; no observation storage; no evidence-gap storage; no PDF generation; no export generation; no download artifacts; no approval recording; no decision storage; no protected live routes; no protected API routes; no database reads; no database writes; no active migrations; no draft storage; no account storage; no actor storage; no identity capture; no staff decisions; no Morning Sheet placement; no tracking; no analytics; no scoring.
recommended-next