CCRC: Study Management

Study Management

The Study Management domain tests whether you can operationalize a protocol from site selection through close-out. The CRC is the operational hub: translating feasibility commitments into workflows, maintaining essential documents, coordinating monitoring visits, and ensuring every study task is delegated, trained, and documented.

Core rules

• The protocol is the operating manual. Eligibility, visit windows, assessments, investigational product (IP) handling, and safety reporting follow it. Deviations need documentation and, when required, sponsor and IRB/IEC notification.
• Use a delegation of authority log. Staff may perform study tasks only after principal investigator (PI) delegation, protocol training, and documented qualifications.
• Maintain the site regulatory binder/ISF with current approvals, CVs, training records, laboratory certifications and normal ranges, monitoring logs, and correspondence.
• IP accountability covers receipt, storage temperature, dispensing, participant compliance, and return or destruction. Temperature excursions need immediate quarantine and sponsor instruction.
• Prepare continuously for monitoring: resolve queries, have source documents ready, and track action items to closure.
• Close-out requires final reconciliation of IP, samples, documents, and outstanding queries.

Worked example

A protocol requires a fasting lipid panel at screening. The participant reports eating two hours before the visit. The CRC should not collect the sample and label it fasting. The correct action is to reschedule within the allowed screening window or follow any protocol-permitted non-fasting rule with documentation. If the visit cannot be repeated, document a protocol deviation and notify the sponsor per policy. Reasoning: the protocol defines the assessment; collecting a non-fasting sample as fasting creates false source data and an undocumented deviation.

Traps

Treating the protocol as flexible; allowing untrained staff to perform study visits; missing delegation or training records; storing IP without temperature logs; discovering at a monitoring visit that deviations were never documented; confusing monitoring with audit.

Key points

• Protocol, GCP, and SOPs govern every study task.
• Delegation and training must precede task performance.
• Essential documents must be current and retrievable.
• IP accountability includes temperature and compliance records.
• Monitoring readiness is continuous, not a last-minute task.

Participant Management

Participant Management

Participant Management tests recruitment, screening, enrollment, randomization, retention, and participant care across the trial. The exam emphasizes protecting participants while meeting enrollment goals and documenting every eligibility decision from source.

Core rules

• Informed consent must be obtained before any study-specific procedure, including screening assessments. Pre-screening for feasibility may use limited existing information only when permitted by the IRB/IEC and privacy rules.
• Eligibility is determined from source documents, not from memory or a participant's self-report alone. Inclusion criteria must all be met; exclusion criteria must all be absent unless the protocol explicitly allows an exception.
• Maintain screening and enrollment logs. Record screen failures and the reason without exposing unnecessary protected health information.
• Randomization must follow the protocol and IRB-approved process. Never open an assignment early or substitute a randomization code.
• Retention begins at consent: confirm contact preferences, visit reminders, travel burden, and caregiver support without coercion.
• Vulnerable populations require additional safeguards, assent where applicable, and compliance with local rules.

Worked example

A screening laboratory value falls just outside the protocol range, and the investigator says the participant is 'basically fine.' The CRC should not enroll unless the protocol permits a waiver or the value meets the stated criterion. The CRC documents the out-of-range result, discusses it with the investigator, and records the participant as a screen failure if no protocol allowance exists. Reasoning: investigator enthusiasm does not override eligibility criteria; enrolling an ineligible participant is a serious protocol deviation.

Traps

Performing screening tests before consent; using an expired laboratory result; accepting verbal eligibility confirmation without source; enrolling under pressure to meet targets; failing to document screen-failure reasons; losing track of re-consent needs when new information arises.

Key points

• Consent precedes study-specific procedures.
• Eligibility must be source-documented against every criterion.
• Screening and enrollment logs must be accurate and current.
• Randomization follows the protocol exactly.
• Retention planning starts at the first consent discussion.

Data Management

Data Management

Data Management tests how the CRC creates, corrects, enters, and reconciles study data. The exam focuses on source integrity, ALCOA-C principles, electronic data capture, query resolution, and Part 11 compliance.

Core rules

• Source documents are the original records: clinic notes, laboratory reports, ECG tracings, dispensing logs, and participant diaries. Source must be attributable, legible, contemporaneous, original, accurate, and complete (ALCOA-C).
• Enter data into the eCRF within the sponsor's timeline. Do not enter data before the source exists; do not create source after the fact to match the eCRF.
• Correct errors with a single line, initial and date, and a reason when needed. Never obscure, overwrite, or backdate an entry. Electronic corrections must preserve the audit trail.
• Never share eCRF passwords or leave an active session unattended. Part 11 requires unique accounts and secure access.
• Resolve queries by checking source first, correcting the source if appropriate, then correcting the eCRF. Document the resolution.
• Reconcile source to eCRF before monitoring visits and database lock.

Worked example

A paper source record shows a blood pressure of 148/92, but the eCRF entry is 138/92. The CRC checks the source, confirms 148/92 is correct, corrects the eCRF, and documents the reason for the change. The CRC does not change the source to match the eCRF. If the source itself was written incorrectly, the correction follows the site's source-correction policy with a single line, initials, date, and reason. Reasoning: source is the reference standard; the eCRF must reflect it, and the audit trail must explain the change.

Traps

Correcting the eCRF without checking source; backdating entries; using another person's login; destroying original source after entry; answering queries with guesses; entering data outside the protocol-defined window without documenting the deviation.

Key points

• ALCOA-C governs all source documentation.
• The eCRF must match source; source is not rewritten to match the eCRF.
• Corrections must be transparent and traceable.
• Unique eCRF accounts and audit trails are mandatory.
• Query resolution starts with source verification.

Safety Management

Safety Management

Safety Management tests adverse event (AE) identification, seriousness assessment, reporting, follow-up, and unblinding. The CRC must recognize safety information, escalate it promptly, and document the medical course without judging causality first.

Core rules

• An AE is any untoward medical occurrence in a participant administered a study intervention, whether or not related. An SAE meets at least one seriousness criterion: death, life-threatening event, inpatient hospitalization or prolongation, persistent disability, congenital anomaly, or an important medical event requiring intervention to prevent one of these outcomes.
• Severity and seriousness are different. Grade 3 severity does not automatically make an event serious; hospitalization does not automatically mean the event is related.
• Report SAEs to the sponsor per protocol, often within 24 hours of site awareness, and to the IRB/IEC per local policy. Do not wait for causality assessment or final laboratory results.
• Document start date, stop date, severity, seriousness criteria, relationship assessment, treatment, and outcome. Follow the event until resolution or stabilization.
• Emergency unblinding follows the protocol and is documented; routine unblinding is prohibited.

Worked example

A participant is hospitalized for pneumonia three weeks after starting IP. The CRC learns of the admission on Monday morning. The event is an SAE because it caused inpatient hospitalization. The CRC notifies the PI, reports to the sponsor within the protocol's 24-hour window, and documents the hospital course. The CRC does not wait to decide whether the pneumonia is related to IP. Reasoning: seriousness triggers reporting; causality is a separate assessment that can be updated later.

Traps

Reporting only 'related' events; waiting for a discharge summary before the initial SAE report; confusing severity with seriousness; failing to follow up until resolution; missing concomitant medication changes; unblinding without authorization.

Key points

• Report SAEs promptly; do not wait for causality.
• Seriousness criteria are distinct from severity grades.
• Document the full event course and follow-up.
• Follow protocol and IRB/IEC timelines for safety reports.
• Emergency unblinding must be justified and documented.

Regulatory Management

Regulatory Management

Regulatory Management tests the CRC's ability to keep the site inspection-ready: IRB/IEC approvals, essential documents, delegation records, protocol deviations, amendments, and corrective actions. The exam focuses on what must be approved, documented, and reported before and after study activities.

Core rules

• Obtain IRB/IEC approval for the protocol, consent forms, recruitment materials, and amendments before implementation, except when implemented to eliminate an immediate hazard to participants.
• Maintain essential documents in the regulatory binder/ISF. Know which documents must be current: approvals, PI CV, training records, delegation log, laboratory certifications, and financial disclosures where required.
• The delegation log must match who actually performs tasks. Add staff before they perform study activities and document training.
• Protocol deviations must be documented, assessed for participant safety and data integrity, and reported per sponsor and IRB/IEC requirements. Serious or continuing noncompliance may require prompt reporting.
• CAPA addresses root cause, not just the symptom. Document the corrective action, the preventive action, and effectiveness checks.
• Prepare for audits and inspections by keeping documents retrievable and consistent.

Worked example

A new sub-investigator starts seeing participants on Monday. On Wednesday the CRC adds the name to the delegation log and files a training record. The sub-investigator's Monday and Tuesday visits are now undocumented delegation. The correct approach is to complete delegation and training before any study task, and to document the gap and corrective action if it occurred. Reasoning: retrospective delegation compromises GCP compliance and inspection readiness.

Traps

Using an amended consent form before IRB approval; missing annual continuing review; failing to report deviations; creating delegation entries after tasks are performed; treating CAPA as a one-time fix without root-cause analysis.

Key points

• Approvals must precede implementation, except for immediate-hazard exceptions.
• Essential documents must be current and retrievable.
• Delegation and training precede task performance.
• Deviations require assessment and reporting per policy.
• CAPA must address root cause and effectiveness.

Communication Management

Communication Management

Communication Management tests how the CRC documents, escalates, and coordinates information among participants, the PI, sponsor/CRO, IRB/IEC, laboratories, and vendors. The exam emphasizes that undocumented communication is difficult to defend and that safety and compliance issues require prompt escalation.

Core rules

• Document substantive communications: protocol clarifications, safety reports, enrollment updates, monitoring findings, and IRB interactions. Use confirmatory emails after verbal discussions.
• Escalate safety issues, deviations, unblinding, and compliance concerns to the PI and sponsor according to the protocol and site SOPs. Do not make independent medical or eligibility decisions.
• Protect confidentiality. Share only the minimum necessary participant information and use secure channels approved by the site.
• Keep the PI informed even when the sponsor communicates directly with the CRC. The PI remains responsible for the conduct of the study.
• Track action items from monitoring visits, emails, and calls through closure so nothing is lost between team members.
• Use clear, neutral language with participants; avoid promising benefit or pressuring enrollment.

Worked example

The sponsor calls to clarify that a protocol-required assessment may be performed by telehealth. The CRC writes a contemporaneous note of the call, sends an email summarizing the guidance, forwards it to the PI, and files the correspondence. If the clarification changes participant procedures, the CRC confirms whether IRB/IEC approval is needed before implementing it. Reasoning: verbal guidance without documentation cannot be verified at monitoring or inspection, and protocol changes may require approval.

Traps

Relying on verbal instructions without written confirmation; failing to inform the PI; copying participant identifiers into unsecured email; ignoring an escalation because another team member was copied; assuming a sponsor instruction overrides the protocol or IRB requirements.

Key points

• Document substantive communications and confirm verbal guidance in writing.
• Escalate safety and compliance issues promptly to the PI and sponsor.
• Share only the minimum necessary participant information.
• The PI remains responsible even when the sponsor contacts the CRC directly.
• Track communication action items to closure.