CRF Completion Guidelines (CCG) — In Practice

Why this matters

What is a CCG? A CRF Completion Guideline (CCG), also called eCRF or form completion guidelines (FCG), is the site-facing playbook that explains how to fill every field on the Case Report Forms (CRFs) inside your Electronic Data Capture (EDC) system. The protocol and the CRF say what to collect; the CCG tells sites how to enter it correctly and consistently.

Without a clear, current CCG:

• Each site invents its own approach → inconsistent data, rework, and lock delays.
• “Easy” entries (like adverse events or units) drift the fastest, generating recurring queries.
• Training gaps compound after amendments unless the CCG is updated and re‑rolled out.

Key terms used (plain language)

• CRF: The eCRF pages in EDC where site staff enter study data.
• CCG: Step‑by‑step instructions for completing each CRF field.
• EDC: The software used for data entry (e.g., Rave, Medrio, REDCap).
• AE/SAE: Adverse Event / Serious Adverse Event.
• CRA: Monitor who verifies source vs. eCRF and gives feedback to the study team.
• DM: Data management, the sponsor or CRO team that usually writes the CCG, reviews entered data and raises queries (sites own entry and corrections).
• Expectedness / window notes: Rules for time‑critical pages: whether a page is due at a visit (expectedness as set by the Schedule of Assessments, not the safety term), what counts as “on time,” and what to do if data are captured outside the window.

What to include

Design your CCG so a new coordinator can open it on Day 1 and succeed. For each form, repeat a consistent mini-structure:

1. Purpose & timing

• Why this form exists and when to complete it (e.g., “At each screening/Day 1 visit before dosing”).
• Who completes it (role) and primary data source.

2. Field‑level instructions

• Units & precision: Allowed units, decimal places, rounding rules (do not convert unless instructed).
• Posture/device rules: When posture, position, or device type affects the value (e.g., Blood pressure seated, upper arm cuff).
• Date/time rules: date format (e.g., DD‑MMM‑YYYY), 24‑hour clock, time zones if applicable, and what to do if the time or part of a date is unknown.
• Missing/unknown handling: When to use “Unknown” or “Not Done” (with the reason), which fields stay blank by design (e.g., skipped by a branching question), and how to add a site comment. Queries come from DM or the CRA; the site answers them.

3. “Good verbatim” examples (AEs and ConMeds)

• Capture the specific clinical description from source.
• Avoid vague terms (“pain,” “infection”: give the location and type the source records), a procedure when the source gives its reason (enter “Appendicitis,” not “Appendectomy”), and severity or causality in the verbatim field.
• Enter one event per entry, and the diagnosis rather than its symptoms once the investigator has made one.
• Expand abbreviations (e.g., enter “Myocardial infarction,” not “MI”).
• For ConMeds (concomitant medications), enter the drug name as in source (trade or generic, no abbreviations), with dose, route and frequency in their own fields.

4. Expectedness & window notes (time‑critical pages)

• What counts as on‑time vs. out‑of‑window and how to record both.
• If late/early, where to document reasons (e.g., Deviation page) and which date to enter on the CRF.

5. FAQs & common pitfalls

• Short Q&As that reflect your most common queries (update these mid‑study).

Reusable snippet template (example style)

Form: Vital Signs – Blood Pressure
When: Pre-dose at each Treatment Visit (before infusion start).
Who: Study Coordinator | Source: Clinic vitals sheet

Fields:
- Systolic (mmHg): Enter as whole number. Device: automated upper-arm cuff.
- Diastolic (mmHg): Enter as whole number. Patient posture: seated, feet flat ≥5 min rest.
- Heart rate (bpm): Whole number after the same rest.
- If posture deviates, select “Other” and specify in free text.
- If value not obtained, select “Not Done” and record reason.

Worked examples

These examples are self‑contained. Use them as models when writing your CCG.

1) AE “good verbatim”

Context. Verbatim means the exact clinical description from the source record (progress notes, discharge summary). Do not interpret or shorten to vague terms.

• Poor entry: “Pain”

• Better entry: “Headache”

• Best (from source): “Migraine with aura”

• Poor entry: “Infection”

• Best (from source): “Right lower lobe bacterial pneumonia”

Why it matters: Specific verbatims reduce coding queries and downstream recoding. (Coding matches each AE verbatim to a MedDRA term and each ConMed to a WHODrug entry.)

CCG text to include: “Enter the clinical term as written in source; expand abbreviations; enter one event per entry and the diagnosis rather than its symptoms when one is made; do not add severity/causality in the verbatim field.”

2) Vital signs: posture & device

Scenario. Sites sometimes record BP with the patient standing or using a wrist cuff. Your analysis requires seated, upper‑arm measurements.

CCG instruction (ready to paste):

• “Record BP seated after ≥5 minutes rest, upper‑arm automated cuff.
• Enter systolic/diastolic as whole numbers in mmHg.
• If a different posture/device is used, select ‘Other’ and specify.
• If rest time <5 minutes, complete the rest and measure again before dosing; if that is not possible, enter the value, note the actual rest time in a comment, and follow the protocol’s deviation process.”

Outcome: Fewer posture/device queries; BP data are comparable across sites.

3) Labs: units and conversion

Scenario. Local labs report glucose in mmol/L, but your CRF defaults to mg/dL.

CCG instruction (ready to paste):

• “Select the unit exactly as reported by the lab. Do not convert locally.
• If the lab’s unit is not listed, choose ‘Other’ and specify the exact unit string from the report; notify the DM team to add the unit if recurring.
• Record the reference range as shown on the same report.”

Outcome: Eliminates mismatched units and manual conversion errors while preserving traceability. Any conversion to a standard unit for analysis is then done centrally in the derived data under documented rules; the site’s entry is never overwritten.

4) Dosing date/time and window notes

Scenario. First dose must start on Day 1; late starts require deviation documentation.

CCG instruction (ready to paste):

• “Enter Infusion Start Date and Start Time in 24‑hour format.
• If date known but time unknown, enter date and select ‘Time Unknown.’
• If dosing occurs outside the visit window, complete the Protocol Deviation page and proceed with the actual date/time on the Dosing page.”

Outcome: Clear handling of unknown times and out‑of‑window dosing, with proper deviation linkage.

Versioning & roll‑out

Treat the CCG like a controlled document linked to protocol and CRF versions: DM usually drafts it, clinical operations and other functions review it, and each version is approved before release.

Version linkage

• Include in the header: CCG version, effective date, protocol version, CRF build/version, summary of changes, and the version it supersedes.
• Withdraw superseded copies (including printed ones) and archive every version with its effective dates in the trial master file (TMF), so you can show which instructions applied on any date.
• For global studies, localized translations keep the same version ID; track language in the footer (e.g., “v1.2 (ES)”).

Roll‑out steps

1. Pre‑go‑live: Send release notes and a short training (slides or 10‑minute recording).
2. Acknowledgements: Capture site acknowledgements (e‑signature or completion in the learning management system, LMS) before site activation or form unlocks.
3. Activation gates: Configure EDC so new/changed forms unlock only after the site acknowledges the CCG update where feasible.
4. Change log: Maintain a one‑page, plain‑language change log at the front of the CCG.

Minor vs. major updates

• Minor (v1.1): Clarifications, added examples, no CRF field changes.
• Major (v2.0): New/retired fields, protocol amendments impacting data entry. A version tied to a protocol amendment takes effect at a site only after the ethics committee (IRB/IEC) responsible for that site, and the regulator where required, has approved the amendment, so effective dates can differ by site or country.
• Always state what sites must do differently and from which date.

Monitoring adherence

Early and targeted QA saves months later.

First 4 weeks after go‑live

• Focused spot checks: Review the first 3–5 subjects per site on high‑risk pages (AEs, Dosing, Labs, Vital Signs).
• Targeted metrics: Track CCG‑related query rate (e.g., “missing posture,” “wrong unit”) per 100 eCRF pages entered (12 such queries on 400 pages give 3.0), counted by the reason category each query carries in the study’s query taxonomy (its agreed list of query types).

Feedback loops

• Query taxonomy review: Every 2–4 weeks, analyze the top recurring query types and add/adjust examples in the CCG.
• CRA input: Add a standing agenda item to monitoring calls for “CCG pain points” and capture decisions into the next release.
• Site spotlight: Share anonymized good examples to set the bar.
• Site follow‑up: A site whose rate stays high gets documented, targeted retraining (via its CRA or a DM call), then a repeat spot check.

Evidence

• Store training decks, attendance, and acknowledgements alongside the CCG (same document location), making inspection readiness straightforward.

Pitfalls & misconceptions

• Posting updates without training/acknowledgement. If sites don’t know it changed, behavior won’t change.
• Assuming protocol text governs transcription. The CCG governs how to enter; the protocol governs what to collect. If the two conflict, the protocol prevails and the CCG is corrected.
• Allowing unit variability without guidance. Specify allowed units and what to do when different units appear.
• Hiding rules in footnotes. Put critical rules (posture, device, rounding) in the field instruction itself.
• No plan for unknowns. If time or posture is unknown, say exactly how to document it.

Practice in the wild (checklist)

• Header shows CCG version, effective date, protocol & CRF version links, and the version it supersedes; superseded copies withdrawn.
• Each form has purpose, timing, who, source, and field‑level rules.
• Units/precision and posture/device rules are explicit per field.
• Good verbatim examples provided for AE/ConMed.
• Expectedness/window rules explained for time‑critical pages.
• FAQs reflect real queries; updated mid‑study.
• Release notes + training sent; site acknowledgements captured.
• Targeted QA in first 4 weeks; CCG updated based on findings.
• Localization uses the same version ID; differences tracked.
• CCG, change log, training records stored together for inspections.

Key points to remember

• Treat the CCG as a living, controlled document. Version it with every protocol/CRF change, state the effective date, and keep a plain‑language change log.
• Tie versions together. Explicitly link CCG ↔ protocol ↔ CRF build; keep a single version ID across translations and mark the language in the footer.
• Roll out with training and proof. Publish concise release notes, deliver training, and collect site acknowledgements before activating new/changed forms; where feasible, gate form unlocks on acknowledgement.
• Clarify impact and timing. Distinguish minor clarifications from major content changes; state exactly what sites must do differently and from which date.
• Mirror field behavior in the CCG. For each form, specify who enters the data, when to complete it, primary source, and reflect the CRF’s type, prompt, and response format.
• Make operational rules explicit. Spell out units & precision (generally do not convert locally), posture/device, date/time (24‑hour, time‑unknown handling), missing/unknown conventions, and expectedness/window handling, including out‑of‑window steps.
• Require specific clinical verbatim on AEs/ConMeds. Expand abbreviations; enter one event per entry and the diagnosis rather than its symptoms once the investigator has made one; do not include causality or severity in the verbatim field.
• Use concrete examples. Include “good vs. poor” entries and paste‑ready snippets for high‑risk pages to reduce recurring queries.
• Verify early, fix fast. In the first 4 weeks post‑go‑live, run targeted spot checks on AEs, Dosing, Labs, and Vitals; track CCG‑related query rates and adjust instructions.
• Close the loop. Review query taxonomy and CRA feedback on a regular cadence; feed lessons learned into the next CCG release.
• Keep evidence together. Store the CCG, release notes, training materials, attendance/acknowledgements, translations, and change history in one inspection‑ready location.
• Avoid common pitfalls. Don’t post updates without training/acknowledgement; don’t hide critical rules in footnotes; don’t rely on protocol text to govern transcription; set clear guidance for unit variability.
• Aim for first‑time‑right entry. Consistent, example‑driven instructions cut queries and accelerate database lock.