.jpg){kind=link}
- Published
- Updated
Initial records at a new site show how processes connect in real use more than they measure long-term performance. Activation training may be complete, yet the first visit, sample and data entry can expose different bottlenecks. Review should focus on evidence from that transition.
Scope of the decision
Choose a limited and explicit scope for the first data wave. Examples include the sequence of critical activities, handovers between teams and visibility of investigator assessments. Do not automatically label a new site as underperforming; distinguish opportunities for learning from important problems requiring action.
Worked review
Suppose the first participant sample is collected correctly, but its laboratory work order lacks the new site code. Results are delayed. Instead of assigning a general data-quality score, the review corrects the handover between code activation and dispatch, then checks matching at the next suitable shipment.
Practical checks
- Compare initial real activities with training and activation assumptions.
- Assess participant impact independently of whether the site is still learning.
- Define a verification point at the next appropriate activity for each gap.
Acceptance and limits
Complete the review when critical start-up flows can be traced and open issues have owners. A few problem-free records cannot provide long-term assurance about a site. Reconsider monitoring as activity increases and further evidence changes the relevant risks or assumptions.
Frequently asked questions
- Must every initial record be reviewed?
- Scope should reflect critical activities and study risks; there is no universal number.
- Does a start-up error prove training failed?
- Not always. Configuration or handover may be responsible; do not attribute it solely to an individual without evidence.