CRC ToolboxBlogs

100% client-side & Zero-PHI:Data stays in your local browser storage. Client-side processing by design — avoids server-side PHI ingestion. No login required.

BlogsMonitoring brief

What CRAs Actually Check When They Review a Site’s Records

May 13, 2026Administrative reference · Zero-PHI examples only

For CRAs & monitors

CRAmonitoringdestruction logAWBdeviationsite readiness

What thorough monitors look for in kit destruction logs, AWB shipment records, and deviation documentation — contemporaneous entries, lot/accession traceability, and timestamps that were not rebuilt the night before the visit.

Monitoring visits are not mystery theater. Experienced CRAs arrive with a short list of questions that sound simple and become hard when the site’s records were assembled under pressure: What left the closet? What left the building? What went wrong, and when was it written down?

This piece is written for monitors — and for site staff who want to know what “ready for monitoring” actually means in kit, shipment, and deviation paperwork. It is guidance first. Tool mentions appear only where they map to the artifact a CRA typically requests.

None of this replaces your monitoring plan or sponsor SOPs. It names the patterns that repeatedly separate contemporaneous control from reconstruction.

Kit destruction and disposition: can you walk the trail?

On the closet walk, CRAs are not only counting boxes. They are testing whether disposition language matches physical reality: which lots are usable, quarantined, used, or destroyed — and whether the site can show that without inventing the story mid-aisle.

What looks weak: a destruction log dated the morning of the visit, lot numbers that do not match shelf labels, missing quantities, or quarantine stock still living in the “available” mental model. What looks strong: lot-level lines with dates, disposition status, and an export that could have been generated before the CRA opened their laptop.

Accession- or lot-level traceability matters more than a pretty spreadsheet. If the site cannot answer “which earliest-expiration lot was destroyed and when?” without email archaeology, the finding writes itself — even when the physical closet is orderly.

Related: Kit Expiration Tracker · Cohort Kit Tracker

Shipments and “missing sample” emails: prove the box left

Central-lab missing-sample queries are where memory fails sites. A CRA (or the site preparing for one) needs a boring chain: visit label, sample type, ship date, who handed it off, and a tracking / AWB number — shipments, not patients.

Reconstructed AWB lists from inboxes read differently than a contemporaneous shipment log. Timestamps and tracking numbers that pre-date the query are the difference between “we think it shipped” and “here is the courier record.”

Sites that keep that log current spend less monitoring time arguing with the past. Sites that do not often burn the visit on scavenger hunts that look like process gaps even when the specimen actually left the building.

Related: Lab Specimen Workbench

Deviations: contemporaneous notes beat perfect prose

Deviation and CAPA / NTF review is less about literary quality and more about whether the site noticed, contained, and documented on a believable timeline. A zero-deviation binder can raise more questions than a binder with several clear, timely notes.

Monitors look for completeness of the operational story — what happened, immediate action, prevention thought — and for the absence of identifiers that do not belong in an administrative draft. Vague notes written weeks later are harder to defend than plain notes written the same day.

When sites hand over a structured CAPA or NTF draft that was scrubbed of PHI and exported from a working session, the conversation stays on process. When the only artifact is a paragraph rebuilt from memory the night before, the conversation stays on credibility.

Related: Deviation Log Assistant

The meta-test: was this kept, or rebuilt?

Across kit, shipment, and deviation records, the same CRA instinct applies: contemporaneous systems beat heroic reconstruction. Exports with dates, lot/accession codes, and consistent status language are easier to trust than binder inserts that only appear when monitoring is on the calendar.

If you are a CRA, ask for the current export and the story of how it is maintained — not only the paper that was printed for your visit. If you are a site, keep the operational view current so monitoring week is confirmation, not invention.

Related: CRA pre-visit checklist

Good monitoring rewards sites that can show control without scrambling. Lot-level destruction trails, AWB-backed shipment proof, and timely deviation drafts are not “extra credit” — they are how a visit stays about the protocol instead of about missing paperwork.

For printable visit prep, use the CRA checklist. For day-to-day logistics that feed those exports, the Guides section goes tool by tool.

Open CRA pre-visit checklist

All blogsFAQZero-PHI architecture

Administrative reference only. Browser-local tools — not a medical device, CDSS, or Part 11 system. Verify outputs against protocol SOPs and primary site records. Zero-PHI local mode: do not enter names, MRNs, DOBs, or subject IDs. Study / kit / lab / deviation / IP accountability / equipment / regulatory / visit drafts use this workstation's localStorage until you clear them. On shared clinic PCs, clear all local site data when finished.