Handbook · Practitioner review

Review the Handbook

An invitation, not a track record. These chapters are author drafts. Nobody outside the project has reviewed them yet, and this page will say so until someone does.

Review status

ChapterVersionIndependent reviewsStatus
Ch 04 · Resource and Capacity PlanningAuthor draft, 2026-10-110 completedReview invited
Ch 06 · Dry Run and Database Lock ReadinessAuthor draft, 2026-10-110 completedReview invited
Ch 08 · Dependency, Risk and Escalation ManagementAuthor draft, 2026-10-110 completedReview invited

The counts update only when a review is completed and the reviewer agrees to its being recorded. Until then the number is zero.

What a review looks like

A focused review of one written chapter, about 45 minutes, using only the synthetic scenario in the chapter. You do not need to share anything from a real study, and you should not.

04

Resource and Capacity Planning

About 45 minutes · synthetic scenario only

Enter the synthetic ZEPHYR-101 counts from the chapter into the Capacity Estimator. Does the method leave out a capacity constraint you routinely plan for (for example vendor oversight, tool validation or onboarding time)? Would your own calibrated ranges fall inside the example's P10 to P90 band? Which change-order trigger would you add or remove?

Open the chapter

06

Dry Run and Database Lock Readiness

About 45 minutes · synthetic scenario only

Read the synthetic decision log and dry-run triage in the chapter. Which decision type would a real lock have that this one lacks? Would you classify any finding in a different class? Is the latest-acceptable-date arithmetic realistic for the team size you work with, and which gate would you move?

Open the chapter

08

Dependency, Risk and Escalation Management

About 45 minutes · synthetic scenario only

Read the synthetic register and escalation brief. Would the options and recommendation give a study lead enough to decide in one meeting? Which escalation trigger or response time would you change? What risk statement is missing from a real programming-led milestone?

Open the chapter

How a review is recorded

  • The reviewer, the chapter version and the date are recorded with the findings and what was changed in response.
  • A reviewer is named, or their organization, only with their explicit permission. A review of one chapter is never presented as validation of the whole Handbook or the Navigator.
  • Findings that change a chapter are listed in the changelog.
  • Counts, quotes and names are published only when they can be substantiated.

Express interest in reviewingShare a generalized lesson instead

In the form, choose the review area “Handbook chapters”. Do not include patient information, named studies, sponsor-confidential material or proprietary documents.