Clarify the signal, owner, evidence source, and decision deadline. Create or update the tool before the meeting ends.
Tool Play
Database-lock readiness plan
Controls the final path to lock.
When to open it
Data cleaning and analysis phase.
How to run it
Use the Database-lock readiness plan when data cleaning and analysis phase. Confirm the purpose of the review, populate the required fields, test the evidence with the accountable functional owner, document the decision or next action, and assign a review date before the forum closes.
Review whether actions moved, risks changed, vendors or sites responded, and whether the output has become decision-ready.
Escalate the Database-lock readiness plan when evidence shows unresolved ownership, participant-protection risk, CTQ or endpoint impact, critical-path pressure, budget or vendor-scope change, inspection-readiness gap, or a decision beyond study-team authority.
Expected output
A completed Database-lock readiness plan record that turns controls the final path to lock into named owners, evidence, timing, decision logic, follow-up actions, and closure proof.
Closure evidence
Closed when the accountable owner accepts the evidence, downstream handoffs are updated, and the next review date or closure rationale is recorded.
Unlock the full operating system behind this preview.
Members receive the full chapter/tool/packet library, downloadable templates, career drills, update access, and beta release notes.
Unlock Worked Example