Initiation and Authorization / Initiating / Paid beta preview
Project charter
Authorizes the project or phase and defines purpose, success criteria, assumptions, constraints, authority, and governance.
Use when: Concept approval, protocol strategy, rescue restart, major phase transition.
Inputs: Sponsor business reason, protocol concept, target population, endpoints, countries, vendor model, decision rights, initial risks.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Project charter when concept approval, protocol strategy, rescue restart, major phase transition. 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.
Decision rule: Escalate the Project charter 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.
Output: A completed Project charter record that turns authorizes the project or phase and defines purpose, success criteria, assumptions, constraints, authority, and governance 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Initiation and Authorization / Initiating / Paid beta preview
Phase charter
Refreshes authority and objectives at a lifecycle boundary.
Use when: Startup launch, enrollment rescue, database-lock push, closeout.
Inputs: Phase objective, entry criteria, exit criteria, accountable owners, constraints, escalation thresholds.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Phase charter when startup launch, enrollment rescue, database-lock push, closeout. 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.
Decision rule: Escalate the Phase charter 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.
Output: A completed Phase charter record that turns refreshes authority and objectives at a lifecycle boundary 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Initiation and Authorization / Initiating / Paid beta preview
Stakeholder register
Identifies people and groups affected by or able to affect the project.
Use when: Any new trial, vendor transition, inspection, country expansion.
Inputs: Stakeholder, influence, concern, desired engagement, owner, confidentiality note.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Stakeholder register when any new trial, vendor transition, inspection, country expansion. 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.
Decision rule: Escalate the Stakeholder register 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.
Output: A completed Stakeholder register record that turns identifies people and groups affected by or able to affect the project 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Initiation and Authorization / Initiating / Paid beta preview
Governance and decision-rights map
Defines who decides what and when issues escalate.
Use when: Complex cross-functional work or divided leadership.
Inputs: Decision type, decision maker, required evidence, quorum, escalation path, record location.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Governance and decision-rights map when complex cross-functional work or divided leadership. 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.
Decision rule: Escalate the Governance and decision-rights map 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.
Output: A completed Governance and decision-rights map record that turns defines who decides what and when issues escalate 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Initiation and Authorization / Initiating / Paid beta preview
Assumption log
Captures planning beliefs that need confirmation.
Use when: Early planning, rescue, budget reforecasting.
Inputs: Assumption, basis, owner, validation date, impact if false, status.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Assumption log when early planning, rescue, budget reforecasting. 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.
Decision rule: Escalate the Assumption log 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.
Output: A completed Assumption log record that turns captures planning beliefs that need confirmation 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Scope and Work Definition / Planning / Paid beta preview
Scope baseline
Documents approved project scope and boundaries.
Use when: Protocol finalization, vendor contracting, amendment planning.
Inputs: Included work, excluded work, deliverables, assumptions, acceptance criteria.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Scope baseline when protocol finalization, vendor contracting, amendment planning. 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.
Decision rule: Escalate the Scope baseline 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.
Output: A completed Scope baseline record that turns documents approved project scope and boundaries 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Scope and Work Definition / Planning / Paid beta preview
Work breakdown structure (WBS)
Decomposes trial work into manageable work packages.
Use when: Building the integrated project plan.
Inputs: Protocol, startup, country/site activation, enrollment, treatment, monitoring, data, safety, supply, vendors, TMF, CSR, closeout.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Work breakdown structure (WBS) when building the integrated project plan. 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.
Decision rule: Escalate the Work breakdown structure (WBS) 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.
Output: A completed Work breakdown structure (WBS) record that turns decomposes trial work into manageable work packages 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Scope and Work Definition / Planning / Paid beta preview
WBS dictionary
Defines each work package so teams share the same meaning.
Use when: When scope is complex or delegated.
Inputs: Description, deliverable, owner, acceptance criteria, dependencies, assumptions.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the WBS dictionary when when scope is complex or delegated. 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.
Decision rule: Escalate the WBS dictionary 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.
Output: A completed WBS dictionary record that turns defines each work package so teams share the same meaning 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Scope and Work Definition / Planning / Paid beta preview
Deliverables register
Lists controlled deliverables and owners.
Use when: Vendor-heavy or submission-facing studies.
Inputs: Deliverable, owner, due date, reviewer, approval, quality criteria, record location.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Deliverables register when vendor-heavy or submission-facing studies. 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.
Decision rule: Escalate the Deliverables register 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.
Output: A completed Deliverables register record that turns lists controlled deliverables and owners 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Scope and Work Definition / Planning / Paid beta preview
Protocol-to-operations traceability map
Connects protocol requirements to operational work.
Use when: Protocol review, startup, amendment impact.
Inputs: Protocol section, operational activity, owner, system/vendor, evidence, risk.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Protocol-to-operations traceability map when protocol review, startup, amendment impact. 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.
Decision rule: Escalate the Protocol-to-operations traceability map 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.
Output: A completed Protocol-to-operations traceability map record that turns connects protocol requirements to operational work 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Scope and Work Definition / Planning / Paid beta preview
Requirements and interface matrix
Defines handoffs among functions, vendors, systems, and sites.
Use when: eCOA, IRT, central lab, imaging, EDC, safety database.
Inputs: Interface, data/object transferred, format, timing, owner, reconciliation, failure mode.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Requirements and interface matrix when ecoa, irt, central lab, imaging, edc, safety database. 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.
Decision rule: Escalate the Requirements and interface matrix 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.
Output: A completed Requirements and interface matrix record that turns defines handoffs among functions, vendors, systems, and sites 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Schedule and Dependency Control / Planning / Monitoring and Controlling / Paid beta preview
Milestone plan
Defines major project events.
Use when: All trial phases.
Inputs: Protocol final, CTA/IND, SIV, FPI, LPI, LPLV, database lock, TLFs, CSR, disclosure, archive.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Milestone plan when all trial phases. 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.
Decision rule: Escalate the Milestone 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.
Output: A completed Milestone plan record that turns defines major project events 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Schedule and Dependency Control / Planning / Monitoring and Controlling / Paid beta preview
Schedule network
Shows dependencies among activities.
Use when: Startup, data lock, rescue planning.
Inputs: Activity, predecessor, successor, lag, owner, constraint.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Schedule network when startup, data lock, rescue planning. 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.
Decision rule: Escalate the Schedule network 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.
Output: A completed Schedule network record that turns shows dependencies among activities 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Schedule and Dependency Control / Planning / Monitoring and Controlling / Paid beta preview
Critical path and float tracker
Identifies activities determining finish date and available flexibility.
Use when: Timeline pressure, executive reporting.
Inputs: Critical task, float, dependency, owner, risk, recovery option.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Critical path and float tracker when timeline pressure, executive reporting. 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.
Decision rule: Escalate the Critical path and float tracker 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.
Output: A completed Critical path and float tracker record that turns identifies activities determining finish date and available flexibility 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Schedule and Dependency Control / Planning / Monitoring and Controlling / Paid beta preview
Dependency log
Tracks cross-functional or vendor dependencies.
Use when: Any matrixed study.
Inputs: Dependency, giving owner, receiving owner, date needed, impact, escalation trigger.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Dependency log when any matrixed study. 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.
Decision rule: Escalate the Dependency log 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.
Output: A completed Dependency log record that turns tracks cross-functional or vendor dependencies 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Schedule and Dependency Control / Planning / Monitoring and Controlling / Free sample
Startup tracker
Controls country/site activation readiness.
Use when: Study startup.
Inputs: Regulatory, contract, budget, training, IP, IRT, EDC, lab kits, TMF, SIV, activation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Startup tracker when study startup. 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.
Decision rule: Escalate the Startup tracker 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.
Output: A completed Startup tracker record that turns controls country/site activation readiness 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.
Worked example: Use the dummy-project story where this tool is linked in the chapter to see the trigger, owner, action, and outcome.
Open play page
Schedule and Dependency Control / Planning / Monitoring and Controlling / Paid beta preview
Enrollment forecast
Models expected enrollment using real site behavior.
Use when: Enrollment planning and rescue.
Inputs: Activated sites, screen rate, screen-fail rate, randomization rate, country/site assumptions, confidence range.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Enrollment forecast when enrollment planning and rescue. 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.
Decision rule: Escalate the Enrollment forecast 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.
Output: A completed Enrollment forecast record that turns models expected enrollment using real site behavior 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Schedule and Dependency Control / Planning / Monitoring and Controlling / Paid beta preview
Database-lock readiness plan
Controls the final path to lock.
Use when: Data cleaning and analysis phase.
Inputs: Queries, coding, reconciliation, protocol deviations, external data, medical review, SAP/TLF readiness, approvals.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
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.
Decision rule: 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.
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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Responsibility and Governance / Executing / Monitoring and Controlling / Paid beta preview
RACI / responsibility assignment matrix
Clarifies responsible, accountable, consulted, and informed parties.
Use when: Role confusion, sponsor/CRO/vendor boundaries.
Inputs: Work or decision, R, A, C, I, boundary note.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the RACI / responsibility assignment matrix when role confusion, sponsor/cro/vendor boundaries. 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.
Decision rule: Escalate the RACI / responsibility assignment matrix 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.
Output: A completed RACI / responsibility assignment matrix record that turns clarifies responsible, accountable, consulted, and informed parties 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Responsibility and Governance / Executing / Monitoring and Controlling / Paid beta preview
Escalation pathway
Defines how unresolved or high-risk issues reach authority.
Use when: Safety concern, vendor failure, budget pressure, protocol drift.
Inputs: Trigger, first owner, escalation owner, evidence, timing, decision needed.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Escalation pathway when safety concern, vendor failure, budget pressure, protocol drift. 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.
Decision rule: Escalate the Escalation pathway 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.
Output: A completed Escalation pathway record that turns defines how unresolved or high-risk issues reach authority 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Responsibility and Governance / Executing / Monitoring and Controlling / Free sample
Decision log
Records decisions and rationale.
Use when: Governance meetings, amendments, rescue choices.
Inputs: Decision, owner, evidence, options, rationale, dissent, residual risk, record location.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Decision log when governance meetings, amendments, rescue choices. 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.
Decision rule: Escalate the Decision log 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.
Output: A completed Decision log record that turns records decisions and rationale 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.
Worked example: Use the dummy-project story where this tool is linked in the chapter to see the trigger, owner, action, and outcome.
Open play page
Responsibility and Governance / Executing / Monitoring and Controlling / Free sample
Action tracker
Tracks commitments from meetings.
Use when: Every operating cadence.
Inputs: Action, owner, due date, dependency, status, closure evidence.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Action tracker when every operating cadence. 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.
Decision rule: Escalate the Action tracker 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.
Output: A completed Action tracker record that turns tracks commitments from meetings 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.
Worked example: Use the dummy-project story where this tool is linked in the chapter to see the trigger, owner, action, and outcome.
Open play page
Responsibility and Governance / Executing / Monitoring and Controlling / Paid beta preview
Meeting cadence and agenda map
Aligns forum purpose with decisions and evidence.
Use when: Busy teams with too many meetings.
Inputs: Forum, purpose, audience, inputs, outputs, decision rights, frequency.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Meeting cadence and agenda map when busy teams with too many meetings. 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.
Decision rule: Escalate the Meeting cadence and agenda map 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.
Output: A completed Meeting cadence and agenda map record that turns aligns forum purpose with decisions and evidence 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Responsibility and Governance / Executing / Monitoring and Controlling / Paid beta preview
Dissent and residual-risk record
Documents unresolved concern after a decision.
Use when: High-pressure governance.
Inputs: Concern, owner, decision, residual risk, monitoring plan, revisit trigger.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Dissent and residual-risk record when high-pressure governance. 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.
Decision rule: Escalate the Dissent and residual-risk record 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.
Output: A completed Dissent and residual-risk record record that turns documents unresolved concern after a decision 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Risk, Issue, and Change Control / Monitoring and Controlling / Paid beta preview
RAID log
Integrates risks, assumptions, issues, and dependencies.
Use when: Routine project control.
Inputs: Type, item, CTQ impact, owner, due date, status, escalation trigger.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the RAID log when routine project control. 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.
Decision rule: Escalate the RAID log 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.
Output: A completed RAID log record that turns integrates risks, assumptions, issues, and dependencies 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Risk, Issue, and Change Control / Monitoring and Controlling / Free sample
Risk register
Tracks uncertain future events.
Use when: Planning and monitoring.
Inputs: Risk, cause, consequence, probability, impact, trigger, mitigation, contingency, owner.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Risk register when planning and monitoring. 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.
Decision rule: Escalate the Risk register 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.
Output: A completed Risk register record that turns tracks uncertain future events 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.
Worked example: Use the dummy-project story where this tool is linked in the chapter to see the trigger, owner, action, and outcome.
Open play page
Risk, Issue, and Change Control / Monitoring and Controlling / Free sample
Issue log
Tracks current problems.
Use when: Any realized blocker.
Inputs: Issue, date opened, impact, owner, action, due date, escalation, closure proof.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Issue log when any realized blocker. 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.
Decision rule: Escalate the Issue log 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.
Output: A completed Issue log record that turns tracks current problems 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.
Worked example: Use the dummy-project story where this tool is linked in the chapter to see the trigger, owner, action, and outcome.
Open play page
Risk, Issue, and Change Control / Monitoring and Controlling / Paid beta preview
Change request form
Captures proposed changes.
Use when: Protocol, scope, vendor, schedule, budget, system, monitoring changes.
Inputs: Change, reason, requester, impact, options, approvals.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Change request form when protocol, scope, vendor, schedule, budget, system, monitoring changes. 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.
Decision rule: Escalate the Change request form 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.
Output: A completed Change request form record that turns captures proposed changes 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Risk, Issue, and Change Control / Monitoring and Controlling / Paid beta preview
Change impact assessment
Analyzes consequences before approval.
Use when: Amendments, rescue, rebaseline.
Inputs: Scope, schedule, cost, quality, participant, data, regulatory, vendor, TMF impact.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Change impact assessment when amendments, rescue, rebaseline. 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.
Decision rule: Escalate the Change impact assessment 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.
Output: A completed Change impact assessment record that turns analyzes consequences before approval 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Risk, Issue, and Change Control / Monitoring and Controlling / Paid beta preview
Change-control board / governance record
Documents approval or rejection.
Use when: Major change decisions.
Inputs: Decision body, evidence, decision, conditions, communication plan, implementation owner.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Change-control board / governance record when major change decisions. 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.
Decision rule: Escalate the Change-control board / governance record 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.
Output: A completed Change-control board / governance record record that turns documents approval or rejection 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Risk, Issue, and Change Control / Monitoring and Controlling / Paid beta preview
Rebaseline log
Records authorized reset of baseline.
Use when: Old plan no longer represents credible work.
Inputs: Baseline changed, reason, old/new values, approval, residual risk.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Rebaseline log when old plan no longer represents credible work. 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.
Decision rule: Escalate the Rebaseline log 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.
Output: A completed Rebaseline log record that turns records authorized reset of baseline 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
Critical-to-quality (CTQ) map
Identifies what matters most to participant protection and data reliability.
Use when: Quality-by-design, RBQM, protocol review.
Inputs: CTQ, threat, control, owner, evidence, review cadence.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Critical-to-quality (CTQ) map when quality-by-design, rbqm, protocol review. 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.
Decision rule: Escalate the Critical-to-quality (CTQ) map 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.
Output: A completed Critical-to-quality (CTQ) map record that turns identifies what matters most to participant protection and data reliability 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
RBQM plan
Defines risk-based quality management approach.
Use when: Study planning and monitoring.
Inputs: CTQs, risks, KRIs, QTLs, monitoring focus, review cadence, response rules.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the RBQM plan when study planning and monitoring. 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.
Decision rule: Escalate the RBQM 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.
Output: A completed RBQM plan record that turns defines risk-based quality management approach 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
QTL/KRI dashboard
Monitors important quality signals.
Use when: Ongoing conduct.
Inputs: Metric, threshold, trend, owner, action, documentation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the QTL/KRI dashboard when ongoing conduct. 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.
Decision rule: Escalate the QTL/KRI dashboard 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.
Output: A completed QTL/KRI dashboard record that turns monitors important quality signals 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
Deviation trend log
Tracks patterns and impact.
Use when: Conduct and inspection readiness.
Inputs: Deviation type, site/country, root cause, endpoint/safety impact, corrective action.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Deviation trend log when conduct and inspection readiness. 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.
Decision rule: Escalate the Deviation trend log 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.
Output: A completed Deviation trend log record that turns tracks patterns and impact 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
Root-cause analysis
Identifies the underlying process, ownership, training, system, vendor, protocol, or feasibility cause behind a recurring or high-impact issue.
Use when: A deviation trend, vendor failure, data-quality signal, safety-process concern, recruitment miss, inspection observation, or repeated site issue cannot be solved by assigning another action item.
Inputs: Issue log, deviation trend, monitoring findings, vendor metrics, data-query aging, safety reconciliation, TMF evidence, site feedback, protocol assumptions, and decision history.
Owner model: Quality or the accountable process owner leads the RCA method; the PM coordinates evidence, owners, timing, decision forums, and follow-through.
How to run it: Define the problem narrowly, separate symptoms from evidence, collect cross-functional facts before blame language appears, test candidate causes against records, document why causes were accepted or rejected, and connect the confirmed root cause to corrective and preventive actions.
Decision rule: Escalate when the root cause affects participant protection, primary endpoint credibility, safety reporting, protocol compliance, inspection evidence, repeated vendor underperformance, or a process owner cannot accept accountability.
Output: A controlled RCA record that links the problem, evidence, root cause, actions, owners, due dates, and effectiveness check.
Closure evidence: Closed only when the accountable owner accepts the root cause, actions are completed, effectiveness has been checked, and records are filed in the appropriate quality/project location.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
CAPA tracker
Controls corrective and preventive action.
Use when: Audit findings, recurring issues, inspection observations.
Inputs: Root cause, correction, prevention, owner, due date, effectiveness check.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the CAPA tracker when audit findings, recurring issues, inspection observations. 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.
Decision rule: Escalate the CAPA tracker 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.
Output: A completed CAPA tracker record that turns controls corrective and preventive action 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
TMF/evidence map
Connects obligations to retrievable records.
Use when: Startup through closeout.
Inputs: Obligation, record, system/TMF location, owner, completeness, gap, action.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the TMF/evidence map when startup through closeout. 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.
Decision rule: Escalate the TMF/evidence map 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.
Output: A completed TMF/evidence map record that turns connects obligations to retrievable records 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Quality and Inspection Readiness / Planning / Delivery / Monitoring and Controlling / Paid beta preview
Inspection request/response tracker
Controls inspection requests and responses.
Use when: Inspection preparation and conduct.
Inputs: Request, owner, source system, response, QC, submission time, follow-up.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Inspection request/response tracker when inspection preparation and conduct. 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.
Decision rule: Escalate the Inspection request/response tracker 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.
Output: A completed Inspection request/response tracker record that turns controls inspection requests and responses 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Communications and Stakeholders / Initiating / Planning / Executing / Paid beta preview
Communication plan
Defines audience, message, cadence, owner, channel, and escalation.
Use when: All trials.
Inputs: Audience, information need, message, cadence, channel, owner, escalation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Communication plan when all trials. 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.
Decision rule: Escalate the Communication 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.
Output: A completed Communication plan record that turns defines audience, message, cadence, owner, channel, and escalation 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Communications and Stakeholders / Initiating / Planning / Executing / Paid beta preview
Site communication plan
Controls site-facing instructions.
Use when: Startup, amendments, safety updates, rescue.
Inputs: Message, site role, version, required acknowledgement, monitoring follow-up.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Site communication plan when startup, amendments, safety updates, rescue. 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.
Decision rule: Escalate the Site communication 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.
Output: A completed Site communication plan record that turns controls site-facing instructions 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Communications and Stakeholders / Initiating / Planning / Executing / Paid beta preview
Participant-facing communication review
Checks participant clarity and burden.
Use when: Consent, recruitment, retention, PLPS.
Inputs: Material, audience, comprehension risk, approval owner, implementation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Participant-facing communication review when consent, recruitment, retention, plps. 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.
Decision rule: Escalate the Participant-facing communication review 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.
Output: A completed Participant-facing communication review record that turns checks participant clarity and burden 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Communications and Stakeholders / Initiating / Planning / Executing / Paid beta preview
Executive briefing template
Turns complexity into decision-ready narrative.
Use when: Governance and senior leadership.
Inputs: Situation, evidence, options, recommendation, decision needed, risk, next step.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Executive briefing template when governance and senior leadership. 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.
Decision rule: Escalate the Executive briefing template 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.
Output: A completed Executive briefing template record that turns turns complexity into decision-ready narrative 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Procurement and Vendor Management / Planning / Executing / Monitoring and Controlling / Closing / Paid beta preview
Procurement strategy
Defines what to outsource and why.
Use when: Vendor planning.
Inputs: Service, make/buy rationale, selection criteria, budget, risk, oversight model.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Procurement strategy when vendor planning. 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.
Decision rule: Escalate the Procurement strategy 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.
Output: A completed Procurement strategy record that turns defines what to outsource and why 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Procurement and Vendor Management / Planning / Executing / Monitoring and Controlling / Closing / Paid beta preview
RFP and bid-defense checklist
Standardizes vendor selection.
Use when: CRO/vendor award.
Inputs: Scope, assumptions, deliverables, staffing, systems, timelines, quality expectations, pricing.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the RFP and bid-defense checklist when cro/vendor award. 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.
Decision rule: Escalate the RFP and bid-defense checklist 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.
Output: A completed RFP and bid-defense checklist record that turns standardizes vendor selection 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Procurement and Vendor Management / Planning / Executing / Monitoring and Controlling / Closing / Paid beta preview
Vendor qualification checklist
Assesses vendor capability and compliance.
Use when: Vendor onboarding.
Inputs: Experience, SOPs, systems, validation, security, quality history, references.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Vendor qualification checklist when vendor onboarding. 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.
Decision rule: Escalate the Vendor qualification checklist 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.
Output: A completed Vendor qualification checklist record that turns assesses vendor capability and compliance 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Procurement and Vendor Management / Planning / Executing / Monitoring and Controlling / Closing / Paid beta preview
SOW/deliverables tracker
Controls contracted scope.
Use when: Vendor oversight.
Inputs: Deliverable, SOW reference, due date, acceptance criteria, owner, status.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the SOW/deliverables tracker when vendor oversight. 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.
Decision rule: Escalate the SOW/deliverables tracker 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.
Output: A completed SOW/deliverables tracker record that turns controls contracted scope 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Procurement and Vendor Management / Planning / Executing / Monitoring and Controlling / Closing / Paid beta preview
SLA/KPI/KRI tracker
Measures vendor performance and risk.
Use when: Ongoing oversight.
Inputs: Metric, target, actual, trend, root cause, action, governance path.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the SLA/KPI/KRI tracker when ongoing oversight. 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.
Decision rule: Escalate the SLA/KPI/KRI tracker 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.
Output: A completed SLA/KPI/KRI tracker record that turns measures vendor performance and risk 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Procurement and Vendor Management / Planning / Executing / Monitoring and Controlling / Closing / Paid beta preview
Change-order tracker
Controls vendor cost/scope changes.
Use when: Budget pressure.
Inputs: Request, contract basis, assumption change, cost, timeline, decision, approval.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Change-order tracker when budget pressure. 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.
Decision rule: Escalate the Change-order tracker 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.
Output: A completed Change-order tracker record that turns controls vendor cost/scope changes 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Procurement and Vendor Management / Planning / Executing / Monitoring and Controlling / Closing / Paid beta preview
Vendor closeout checklist
Confirms obligations are closed.
Use when: Study or vendor closeout.
Inputs: Final deliverables, data transfer, reconciliation, invoices, records, lessons learned.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Vendor closeout checklist when study or vendor closeout. 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.
Decision rule: Escalate the Vendor closeout checklist 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.
Output: A completed Vendor closeout checklist record that turns confirms obligations are closed 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Cost and Resource Control / Planning / Monitoring and Controlling / Paid beta preview
Cost baseline
Approves the budget plan.
Use when: Budget authorization.
Inputs: Budget category, assumptions, contingency, approval, change-control threshold.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Cost baseline when budget authorization. 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.
Decision rule: Escalate the Cost baseline 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.
Output: A completed Cost baseline record that turns approves the budget plan 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Cost and Resource Control / Planning / Monitoring and Controlling / Paid beta preview
Forecast tracker
Shows expected final cost.
Use when: Monthly finance review.
Inputs: Actuals, commitments, forecast, variance, driver, mitigation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Forecast tracker when monthly finance review. 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.
Decision rule: Escalate the Forecast tracker 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.
Output: A completed Forecast tracker record that turns shows expected final cost 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Cost and Resource Control / Planning / Monitoring and Controlling / Paid beta preview
Accrual tracker
Estimates earned but unpaid costs.
Use when: Finance close and vendor management.
Inputs: Service period, work performed, invoice status, accrual amount, owner.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Accrual tracker when finance close and vendor management. 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.
Decision rule: Escalate the Accrual tracker 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.
Output: A completed Accrual tracker record that turns estimates earned but unpaid costs 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Cost and Resource Control / Planning / Monitoring and Controlling / Paid beta preview
Resource plan and capacity heatmap
Shows whether team capacity matches work.
Use when: Startup, rescue, closeout.
Inputs: Function, FTE need, available capacity, gap, mitigation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Resource plan and capacity heatmap when startup, rescue, closeout. 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.
Decision rule: Escalate the Resource plan and capacity heatmap 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.
Output: A completed Resource plan and capacity heatmap record that turns shows whether team capacity matches work 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Cost and Resource Control / Planning / Monitoring and Controlling / Paid beta preview
Contract obligation tracker
Connects payment to work and evidence.
Use when: Vendor/site budget control.
Inputs: Obligation, trigger, evidence, amount, approver, invoice status.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Contract obligation tracker when vendor/site budget control. 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.
Decision rule: Escalate the Contract obligation tracker 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.
Output: A completed Contract obligation tracker record that turns connects payment to work and evidence 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Protocol feasibility checklist
Tests whether the protocol can work at real sites.
Use when: Protocol review and rescue.
Inputs: Eligibility, visit burden, endpoints, procedures, competition, site capacity, participant access.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Protocol feasibility checklist when protocol review and rescue. 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.
Decision rule: Escalate the Protocol feasibility checklist 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.
Output: A completed Protocol feasibility checklist record that turns tests whether the protocol can work at real sites 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Protocol synopsis and expanded synopsis review
Converts the early scientific concept into a cross-functional operational readout before protocol drafting goes too far.
Use when: Concept review, governance authorization, protocol drafting, startup handoff.
Inputs: Indication, population, objectives, endpoints, design, countries, visit burden, functional comments, open decisions.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Protocol synopsis and expanded synopsis review when concept review, governance authorization, protocol drafting, startup handoff. 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.
Decision rule: Escalate the Protocol synopsis and expanded synopsis review 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.
Output: A completed Protocol synopsis and expanded synopsis review record that turns converts the early scientific concept into a cross-functional operational readout before protocol drafting goes too far 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Protocol lifecycle planning summary (PLPS)
Captures protocol-level planning assumptions, milestones, ownership, and downstream operational consequences.
Use when: Before full protocol finalization, during amendment planning, or when assumptions change.
Inputs: Protocol version, key assumptions, endpoint dependencies, startup gates, system needs, functional owners, unresolved risks.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Protocol lifecycle planning summary (PLPS) when before full protocol finalization, during amendment planning, or when assumptions change. 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.
Decision rule: Escalate the Protocol lifecycle planning summary (PLPS) 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.
Output: A completed Protocol lifecycle planning summary (PLPS) record that turns captures protocol-level planning assumptions, milestones, ownership, and downstream operational consequences 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Schedule of assessments operational review
Tests whether visits and procedures can be executed.
Use when: Protocol review, startup, amendments.
Inputs: Visit, procedure, window, owner, vendor/system, participant burden, failure mode.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Schedule of assessments operational review when protocol review, startup, amendments. 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.
Decision rule: Escalate the Schedule of assessments operational review 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.
Output: A completed Schedule of assessments operational review record that turns tests whether visits and procedures can be executed 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Endpoint/evidence traceability map
Protects endpoint credibility.
Use when: Design, conduct, data cleaning, CSR.
Inputs: Objective, endpoint, SOA, source, vendor/system, edit check, SAP/TLF, CSR.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Endpoint/evidence traceability map when design, conduct, data cleaning, csr. 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.
Decision rule: Escalate the Endpoint/evidence traceability map 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.
Output: A completed Endpoint/evidence traceability map record that turns protects endpoint credibility 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Statistical planning and estimand alignment tracker
Links operational conduct to estimands, analysis populations, missing data strategy, and interpretability.
Use when: Endpoint planning, protocol review, enrollment rescue, database-lock readiness.
Inputs: Estimand, intercurrent events, analysis population, missing-data concern, operational trigger, Claire Jiang/statistics owner.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Statistical planning and estimand alignment tracker when endpoint planning, protocol review, enrollment rescue, database-lock readiness. 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.
Decision rule: Escalate the Statistical planning and estimand alignment tracker 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.
Output: A completed Statistical planning and estimand alignment tracker record that turns links operational conduct to estimands, analysis populations, missing data strategy, and interpretability 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
SAP and TLF dependency plan
Connects SAP, TLF shells, data cleaning, coding, programming, and database-lock dependencies.
Use when: Before database lock, CSR planning, interim analysis planning.
Inputs: SAP version, TLF shell status, data sources, programming owner, review dates, blockers.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the SAP and TLF dependency plan when before database lock, csr planning, interim analysis planning. 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.
Decision rule: Escalate the SAP and TLF dependency 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.
Output: A completed SAP and TLF dependency plan record that turns connects sap, tlf shells, data cleaning, coding, programming, and database-lock dependencies 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Safety escalation pathway
Defines how safety concerns move.
Use when: All interventional studies.
Inputs: Event type, first recipient, medical/safety owner, reporting clock, escalation, evidence.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Safety escalation pathway when all interventional studies. 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.
Decision rule: Escalate the Safety escalation pathway 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.
Output: A completed Safety escalation pathway record that turns defines how safety concerns move 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Safety management and reporting plan
Defines safety review, reconciliation, reporting clocks, medical review, and urgent communication paths.
Use when: Interventional trial startup, safety signal response, inspection preparation.
Inputs: AE/SAE flow, PV owner, medical reviewer, reporting timelines, reconciliation, escalation route.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Safety management and reporting plan when interventional trial startup, safety signal response, inspection preparation. 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.
Decision rule: Escalate the Safety management and reporting 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.
Output: A completed Safety management and reporting plan record that turns defines safety review, reconciliation, reporting clocks, medical review, and urgent communication paths 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Data transfer and reconciliation tracker
Controls third-party data.
Use when: Lab, eCOA, imaging, IRT, safety.
Inputs: Source, destination, frequency, expected records, rejects, reconciliation owner.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Data transfer and reconciliation tracker when lab, ecoa, imaging, irt, safety. 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.
Decision rule: Escalate the Data transfer and reconciliation tracker 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.
Output: A completed Data transfer and reconciliation tracker record that turns controls third-party data 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
IRT/eCOA/EDC readiness checklist
Verifies systems before use.
Use when: Startup and amendments.
Inputs: Configuration, UAT, access, training, validation, support, reconciliation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the IRT/eCOA/EDC readiness checklist when startup and amendments. 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.
Decision rule: Escalate the IRT/eCOA/EDC readiness checklist 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.
Output: A completed IRT/eCOA/EDC readiness checklist record that turns verifies systems before use 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
eCRF/EDC requirements and build readiness checklist
Makes eCRF requirements, edit checks, UAT, release criteria, and data ownership explicit before site use.
Use when: EDC build, protocol amendment, database-lock preparation.
Inputs: Forms, fields, edit checks, UAT evidence, defect status, release approver, training.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the eCRF/EDC requirements and build readiness checklist when edc build, protocol amendment, database-lock preparation. 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.
Decision rule: Escalate the eCRF/EDC requirements and build readiness checklist 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.
Output: A completed eCRF/EDC requirements and build readiness checklist record that turns makes ecrf requirements, edit checks, uat, release criteria, and data ownership explicit before site use 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Supply accountability tracker
Controls investigational product.
Use when: Blinded, vaccine, BA/BE, DCT, global studies.
Inputs: Shipment, receipt, storage, dispensing, return/destruction, excursion, reconciliation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Supply accountability tracker when blinded, vaccine, ba/be, dct, global studies. 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.
Decision rule: Escalate the Supply accountability tracker 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.
Output: A completed Supply accountability tracker record that turns controls investigational product 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
IMP/pharmacy and supply readiness plan
Confirms investigational product release, pharmacy workflow, storage, dispensing, returns, and excursion handling.
Use when: Startup, blinded trials, vaccines, BA/BE and biosimilar trials.
Inputs: Release status, labeling, temperature controls, pharmacy delegation, accountability, IRT link.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the IMP/pharmacy and supply readiness plan when startup, blinded trials, vaccines, ba/be and biosimilar trials. 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.
Decision rule: Escalate the IMP/pharmacy and supply 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.
Output: A completed IMP/pharmacy and supply readiness plan record that turns confirms investigational product release, pharmacy workflow, storage, dispensing, returns, and excursion handling 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Functional readiness matrix
Requires every function to define what ready means before initiation or activation.
Use when: Study initiation, startup, country launch, rescue restart.
Inputs: Function, deliverable, ready evidence, dependency, accountable owner, due date, escalation.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Functional readiness matrix when study initiation, startup, country launch, rescue restart. 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.
Decision rule: Escalate the Functional readiness matrix 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.
Output: A completed Functional readiness matrix record that turns requires every function to define what ready means before initiation or activation 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Integrated study startup plan
Combines WBS, schedule, dependencies, readiness criteria, and governance into one startup operating plan.
Use when: Before site activation and first participant in.
Inputs: Workstream, deliverable, predecessor, owner, target date, risk, evidence, green-light criteria.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Integrated study startup plan when before site activation and first participant in. 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.
Decision rule: Escalate the Integrated study startup 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.
Output: A completed Integrated study startup plan record that turns combines wbs, schedule, dependencies, readiness criteria, and governance into one startup operating plan 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Clinical Trial Specialty Tools / All phases / Paid beta preview
Training and competency readiness plan
Verifies that sites, vendors, and sponsor users are trained on the right version before performing controlled work.
Use when: Startup, amendments, rescue retraining, inspection preparation.
Inputs: Audience, curriculum, version, completion evidence, competency check, follow-up owner.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Training and competency readiness plan when startup, amendments, rescue retraining, inspection preparation. 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.
Decision rule: Escalate the Training and competency 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.
Output: A completed Training and competency readiness plan record that turns verifies that sites, vendors, and sponsor users are trained on the right version before performing controlled work 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Closeout and Learning / Closing / Paid beta preview
Closeout checklist
Controls final obligations.
Use when: Study closeout or early termination.
Inputs: Participants, sites, vendors, data, safety, TMF, CSR, disclosure, archive.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Closeout checklist when study closeout or early termination. 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.
Decision rule: Escalate the Closeout checklist 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.
Output: A completed Closeout checklist record that turns controls final obligations 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Closeout and Learning / Closing / Paid beta preview
Participant transition plan
Protects participants when a study ends or changes.
Use when: Early stop, closeout, rescue.
Inputs: Participant group, obligation, communication, medical follow-up, owner.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Participant transition plan when early stop, closeout, rescue. 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.
Decision rule: Escalate the Participant transition 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.
Output: A completed Participant transition plan record that turns protects participants when a study ends or changes 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Closeout and Learning / Closing / Paid beta preview
Site closeout tracker
Confirms site-level closure.
Use when: Closeout.
Inputs: Visits, drug return, queries, documents, payments, archive, follow-up.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Site closeout tracker when closeout. 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.
Decision rule: Escalate the Site closeout tracker 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.
Output: A completed Site closeout tracker record that turns confirms site-level closure 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Closeout and Learning / Closing / Paid beta preview
Final reporting and disclosure tracker
Controls public and regulatory reporting.
Use when: Post-database lock and closeout.
Inputs: CSR, registry, publication, regulatory submission, owner, due date.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Final reporting and disclosure tracker when post-database lock and closeout. 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.
Decision rule: Escalate the Final reporting and disclosure tracker 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.
Output: A completed Final reporting and disclosure tracker record that turns controls public and regulatory reporting 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page
Closeout and Learning / Closing / Paid beta preview
Lessons-learned register
Turns experience into future change.
Use when: End of phase/study, rescue, inspection.
Inputs: Lesson, evidence, owner, changed process/template, follow-up date.
Owner model: PM integrates the artifact; the accountable functional lead owns technical content where applicable.
How to run it: Use the Lessons-learned register when end of phase/study, rescue, inspection. 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.
Decision rule: Escalate the Lessons-learned register 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.
Output: A completed Lessons-learned register record that turns turns experience into future change 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.
Worked example: Paid beta members unlock the full clinical project example.
Open play page