CRNO common mistakes
CRNO · Understand the traps and how to avoid them.
Treating ICH-GCP E6(R2) as the only version in force and answering questions about risk-based quality management, centralized monitoring, or the required sponsor oversight documentation as if they were optional add-ons rather than E6(R2) expectations.
Many candidates trained on older SOPs or summary courses that predate the 2016 addendum; the exam tests the current integrated expectation, so old mental models produce answers that sound reasonable but are out of date.
What to do instead
Build a one-page comparison of E6(R1) versus E6(R2) changes (quality management, risk-based monitoring, computerized systems, noncompliance escalation) and rehearse, for each, what the sponsor and the investigator must now document. Practice explaining why each change exists, not just naming it.
Confusing the roles of the sponsor, the CRO, the investigator, and the IRB/IEC when asked who holds a given obligation (e.g., who submits the annual report, who makes the safety reporting decision, who approves protocol deviations in advance).
In real trials these duties are delegated and documented in contracts and delegation logs, so candidates learn the local arrangement of their own site rather than the regulatory default allocation tested on the exam.
What to do instead
Make a four-column table (sponsor, CRO, investigator, IRB/IEC) and place each core obligation from ICH-GCP and the applicable regional regulation into it. For any obligation that can be transferred, note that transfer requires written documentation and that ultimate responsibility remains with the sponsor.
Writing or critiquing an endpoint that is not operationally defined: for example, accepting 'time to improvement' or 'clinically significant change' without specifying the instrument, assessor, threshold, and time window.
Candidates focus on whether the endpoint is clinically meaningful and skip the measurement-specification step, which is where most protocol weaknesses actually lie.
What to do instead
For every endpoint you review, force answers to five questions: what is measured, with which instrument or assay, by whom, at what time point, and how is it summarized. If any answer is missing, the endpoint is not yet acceptable. Practice on three published-style endpoints per study session.
Assuming a protocol amendment can take effect at the site as soon as the sponsor approves it, without accounting for IRB/IEC approval and, where required, regulatory authority approval, and without distinguishing changes that may be implemented early to eliminate immediate hazard to participants.
Amendment workflows differ by site and by country, and candidates generalize from a single experience where the IRB approval arrived before the site needed to act.
What to do instead
Learn the standard sequence: sponsor decides and documents, amendment is submitted, approvals obtained, site trained and implementation date recorded. Memorize the narrow exception for reducing immediate risk to participants and the requirement to document the reason and report promptly.
Answering recruitment and enrollment questions with generic tactics ('use social media', 'advertise more') instead of tying the recruitment plan to the eligibility criteria that actually drive screen failure and to the documented recruitment and retention plan the protocol requires.
Candidates treat recruitment as a marketing problem rather than a protocol-feasibility problem, so they miss the exam's focus on eligibility criteria, recruitment timelines, and prescreening documentation.
What to do instead
For any recruitment scenario, first identify which eligibility criterion causes the most screen failures and propose a targeted remedy (widening a window with justification, adding a prescreening step, changing referral source). Always state where recruitment materials require IRB/IEC review before use.
Describing prescreening as if it were screening: collecting and recording participant-specific health information before an IRB-approved informed consent has been obtained and documented.
Sites want to avoid burdening ineligible people with a full screening visit, and the boundary between general questions and participant-specific data collection is easy to blur.
What to do instead
Apply the rule that any collection of identifiable, participant-specific information for determining eligibility requires consent under an approved process. Learn to distinguish general inquiries (asking whether a clinic treats the condition) from prescreening questions and confirm what the local IRB/IEC has approved.
Treating informed consent as a signature event: describing the form as the consent, or accepting a consent discussion that omits the elements the participant must understand, such as alternatives, risks of not participating, and the voluntary nature of participation.
Consent is often taught as a documentation task, and busy sites emphasize completing the form correctly rather than the process of understanding.
What to do instead
Rehearse consent as a process with three checkpoints: adequate information, opportunity for questions and sufficient time, and freely given agreement documented before any study procedure. For each required element, state what the participant must be able to explain back, and note when a witness, impartial witness, or legally acceptable representative is required.
Recording a protocol deviation without classifying it and without assessing whether it affects participant safety, rights, or data integrity, then failing to report it within the required timeframe.
Deviations are frequent and sites normalize them; without a classification habit, every deviation gets the same minimal treatment and significant ones are missed.
What to do instead
Use a fixed triage for every deviation: what happened, why, effect on safety, rights, and data integrity, whether it is major or minor, who must be notified, and by when. Document the corrective and preventive action and the retraining or system change that follows.
Confusing the investigational product accountability chain: assuming dispensing records alone satisfy accountability, or failing to reconcile returned, unused, and destroyed product and to document temperature excursions and their assessment before further use.
Accountability is often split between pharmacy and coordinator, so candidates know their own fragment of the process but not the full reconciliation and disposition requirements.
What to do instead
Learn accountability as a closed loop: receipt, storage conditions and excursion assessment, dispensing to named participants, return or destruction, reconciliation of quantities, and documented authorization for destruction. For devices, add accountability for device receipt, use, return, and malfunction reporting.
Conflating serious with severe, or assuming every serious adverse event must be reported immediately to the sponsor and the IRB/IEC regardless of expectedness and causality.
The words sound interchangeable in ordinary language, and candidates memorize reporting timelines without the decision logic that determines which timeline applies.
What to do instead
Work the decision tree explicitly: is it an adverse event, is it serious by one of the defined outcomes, is it expected given the reference safety information, and is there a reasonable possibility it was caused by the investigational product. Then state who is notified and by when. Rehearse with borderline cases such as hospitalization for a pre-existing condition.
Treating source documents and the case report form as interchangeable: entering data directly into the CRF with no underlying source, or 'correcting' source to match the CRF after a query.
Electronic systems blur the line, and sites under time pressure backfill source from the database rather than verifying the database against source.
What to do instead
Apply the principle that source is the original record and the CRF is a transcription, with exceptions only when the protocol or a validated system defines the CRF as source. Practice documenting corrections as a single strike-through with initials, date, and reason, and never destroying the original entry.
Answering monitoring questions from the site perspective only: describing monitoring as checking CRFs for completeness rather than as ongoing oversight of participant safety, protocol compliance, and data quality, with documented findings, follow-up, and escalation.
Coordinators mainly experience monitoring as a visit that generates queries, so they never learn the monitoring plan, the rationale for on-site versus centralized monitoring, or the escalation pathway.
What to do instead
Study the monitoring plan structure: what is monitored, how, how often, by whom, and what triggers increased monitoring. For each finding type, state the expected follow-up and the point at which it escalates to the sponsor. Separately learn what auditors and inspectors ask for and how inspection findings are classified.