Study the CCRC by mapping each GCP topic to the roles that decide, perform, and document it. Work consent, source documentation, deviation, and safety scenarios as coordinator decisions, and self-check with observable rubric criteria rather than practice-score guesses.
Why Role Boundaries, Not GCP Definitions, Decide CCRC Answers
ACRP describes the CCRC as recognizing professionals who coordinate and facilitate clinical trial activities in adherence to GCP under a principal investigator's direction. Correct answers therefore keep each decision with the role that holds it: the PI for medical judgment, the coordinator for facilitation and documentation.
The credential's scope explains its question style. A coordinator exam item rarely asks you to recite a guideline definition; it describes a site situation — a consent conversation, a missed assessment window, a monitor's finding — and asks what you do next. Several options may describe legitimate actions by someone on the study team. The skill being measured is recognizing which action is yours to take, which belongs to the PI, and which belongs to the sponsor or another party.
Build a study habit around that structure. For every topic you review, write three columns: what the coordinator decides or performs, what requires the PI, and what sits with the sponsor, IRB, or laboratory. For example, eligibility is medically judged by the PI; the coordinator gathers evidence, flags conflicts, and documents the outcome. Monitoring visits are conducted by the sponsor's monitor; the coordinator prepares source and responds to findings. This map becomes your primary study artifact, not a supplement to rereading guidelines.
- PI-level decisions: eligibility approval, medical management of participants, investigator signature on study documents.
- Coordinator-level work: scheduling and tracking, consent logistics, source documentation, regulatory file upkeep, deviation identification.
- Sponsor-level activities: monitoring visits, protocol-level changes, safety distribution decisions.
- Independent oversight: IRB review and approval of the site's study conduct and participant-facing materials.
Who Decides What: A Decision-Rights Map You Can Study From
A decision-rights table converts GCP topics into coordinator judgment. When a scenario offers several defensible actions, check which role initiates each one. The delegation of authority log at the site is the concrete document that records which tasks the PI has assigned to whom.
Use the table below as a template, then rebuild it from your own experience or a paper site model. The point is not memorizing the rows but practicing the lookup: when an option says 'you obtain the participant's medical history for eligibility,' ask whether that task is plausibly delegated to a coordinator under the PI's direction, and what documentation proves it was done and reviewed.
One caution keeps this tool honest: delegation shifts with site SOPs, local requirements, and the protocol. A task that is coordinator work at one site may require specific qualification or PI performance at another. Exam scenarios typically supply the clues — a delegation log reference, an SOP citation, or a participant-safety question — and the correct answer respects those clues rather than assuming universal practice.
| Task | Coordinator typically | PI | Sponsor / other |
|---|---|---|---|
| Eligibility assessment | Collects records, flags inclusion/exclusion conflicts, documents verification | Confirms and approves enrollment decision | Defines criteria in the protocol |
| Informed consent | Schedules, prepares documents, tracks versions, documents process | Obtains consent or oversees delegated obtainers per delegation log and applicable requirements | Develops template consent materials |
| Adverse event follow-up | Detects, documents, and reports internally; collects follow-up data | Assesses severity, causality, and medical management | Receives reports per protocol timelines |
| Monitoring visit | Prepares source and regulatory files, resolves queries | Available for medical questions the monitor escalates | Conducts monitoring and follow-up letters |
| Protocol deviation | Identifies, documents, notifies PI, files reports per SOPs | Reviews impact and any participant-safety action | May require reporting under protocol terms |
| IRB correspondence | Prepares and submits site materials, tracks approvals | Signs as investigator of record | Reviews and approves; correspondence flows per local rules |
Informed Consent Timing: A Worked Scenario About the Process, Not the Form
Consent is an ongoing process evidenced by documentation, and a signature alone does not establish it. A scenario in which a study procedure predates the consent timestamp tests whether you treat the discrepancy as a documented, reported event rather than a paperwork fix.
Worked scenario. A participant signs consent at 10:15; the screening blood draw is time-stamped 09:35 the same morning. The tempting answer is to annotate the consent form or adjust the recorded draw time so the sequence looks correct. The better decision is to leave the source records untouched, write a contemporaneous note describing what actually happened, notify the PI, report the event per your site's deviation SOP and protocol requirements, and confirm with the PI whether the participant's welfare and data integrity are affected. The reason this matters: altering records converts a process lapse into a documentation integrity problem, while an honest, dated account preserves trust and shows the site can self-correct.
Extend the same process thinking across consent events: a new version of the consent form following an amendment triggers re-consent of active participants per the IRB's direction; a participant's later questions that reveal misunderstanding call for re-education and, where willingness is affected, re-consent; and each conversation is documented with who was present, what was discussed, and that questions were answered. The signed, dated form is the anchor, but the audit trail around it — version tracking, process notes, copy given — is what a reviewer uses to confirm consent was valid, not merely executed.
Source Documentation: Late Entries, Corrections, and the Reconstruction Test
Source records must let someone else reconstruct what happened to a participant. That standard drives coordinator habits: contemporaneous notes, transparent corrections, attributed entries, and late entries that say they are late instead of being backdated.
Worked scenario. A coordinator realizes three weeks after a visit that a concomitant medication change was never recorded. The tempting answer is to write the note and date it as if it were made on the visit day, because the information itself is accurate. The better decision is to write the entry now, date it now, explicitly label it a late entry that refers back to the visit, and sign it. The reason this matters: an audit trail exists precisely to show when records were made and by whom, and a backdated entry contradicts the trail even when its content is true. A late entry with an honest date is routine; a manufactured date undermines every other record it touches.
Two habits cover most coordinator documentation work. First, corrections never obscure the original: a single line through the error, the correct value, initials, and date, so the original remains legible. Second, every entry carries attribution — who made it, with initials or signature and date — so that records written by different team members can be distinguished. Then apply the reconstruction test while you study: take a paper participant worksheet and ask whether a reviewer who has never met the participant could follow the visit sequence, dosing, assessments, and deviations from the source alone. Where the answer is no, you have found a documentation gap worth studying.
Deviations and Safety Events: Classify Before You Report
When something departs from the protocol, the coordinator's sequence is identify, document, notify the PI, report per SOP and protocol requirements, and plan prevention. Specific reporting timelines live in the protocol and site SOPs, so strong answers locate the requirement rather than guess it.
A short scenario shows the sequence. A participant takes a prohibited over-the-counter medication for two days before telling the coordinator. Jumping straight to 'notify the sponsor immediately' skips steps the coordinator owns first: document what the participant reported in the source, bring it to the PI for assessment of any participant impact, check the protocol and SOPs for what this kind of event requires and when, and record the outcome. Prevention is part of the same note — for instance, adding the prohibited-medication list to each visit's conversation. A complete answer touches all five steps; an incomplete one performs a single step out of order.
Because timelines and reportability differ by protocol, sponsor, IRB, and applicable requirements, treat any scenario that names a specific deadline as a cue to check the governing document the scenario references. In your own preparation, practice classifying events before reporting them: was it a departure from the protocol, an unexpected event, a participant-safety issue, or some combination? The classification determines who is notified and how it is documented, which is exactly the reasoning an applied coordinator question is designed to surface.
- Identify: what exactly departed from the protocol or process, and when.
- Document: source note with facts, dates, and attribution — no speculation.
- Notify: PI first for medical assessment, then others as SOPs and the protocol require.
- Report: follow the protocol's and SOPs' stated requirements and timelines.
- Prevent: record a corrective action so the same lapse has a documented fix.
Ethics at the Site Level: Language Barriers, Privacy, and Escalation Duties
Coordinator ethics questions test judgment inside the site: protecting participants who cannot use the English consent materials, safeguarding identifiable information in shared spaces, and escalating concerns through the PI and IRB rather than working around oversight.
Consider a micro-scenario: a prospective participant reads little English and a family member offers to translate the consent form on the spot. The protective answer uses IRB-approved translated materials and follows your site's documented process for consent in that situation, with the PI involved per the delegation log — it does not improvise with informal interpretation. The same protective instinct governs confidentiality: identifiable records stay out of shared view, study discussions avoid public spaces, and access follows the roles recorded on the delegation log.
Escalation completes the ethics picture. If a coordinator observes conduct that could affect participant safety or data integrity — pressure to enroll someone with unresolved eligibility questions, records edited after monitoring — the sound pattern is to document the concern factually and raise it through the PI, and through the IRB or compliance channels where the situation calls for it. The professional-standards theme underneath is that the coordinator is accountable for the integrity of what the site records and reports, even when the decision under question belongs to a more senior role.
A Four-Week Sequence, a Rebuild Exercise, and a Self-Check Rubric
Spend four weeks moving from topic review to scenario judgment: week one builds the decision-rights map, weeks two and three run worked scenarios, week four closes gaps the rubric exposes. Treat rubric results as learning milestones, not score predictions.
Suggested sequence. Week one: review each topic on the CCRC content outline available from ACRP and write your decision-rights table for it, marking any task whose ownership you cannot justify. Week two: run one consent-process scenario and one documentation scenario per study session, writing your answer before checking reasoning, and recording the step you skipped. Week three: do the same for deviations, safety events, and ethics situations, and start collecting every protocol-and-SOP-dependent rule you encounter into a single 'check the governing document' list. Week four: retake your weakest scenario types cold, rebuild your delegation-log exercise, and re-score with the rubric.
Exercise and rubric. Take a paper site model — a fictional delegation log, protocol summary, and participant worksheet — and answer five questions: who may obtain consent, who verifies eligibility, who conducts monitoring, who classifies a deviation, and who signs the regulatory documents. Score yourself on observable criteria: every row of your decision-rights table names a role and the document that evidences it; your consent scenario answer includes process documentation and version tracking, not just the signature; your late-entry answer keeps the original date and labels the entry; your deviation answer follows all five steps in order; your ethics answer escalates rather than improvises. A rubric gap marks the next study session's topic — that is how the milestones are meant to be used.
Readiness checks before you schedule anything: you can rebuild the decision-rights table from memory for all six core tasks; you can explain why a backdated late entry is worse than an honest one; you can walk a deviation through all five steps citing which document governs each; and you can state what makes consent a process rather than a form in two sentences. For administrative details — eligibility criteria, fees, testing windows — rely on ACRP directly rather than third-party summaries, since those specifics change and the issuer page is the controlling source.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.