What Should an ePRO Audit Trail Show? Questions to Ask Under 21 CFR Part 11

Tell us about your project

Please reach out to us about your project and see how we can help you accomplish your goals.

We value your privacy and will never share your contact information

Please note that submissions without a valid business email address or business phone number may not receive a timely response

Healthcare Solutions

If you're in healthcare, you owe it to yourself to learn how you can make your everyday business processes more efficient and save money at the same time. We can help in automating many of your routine and repetitive tasks, including Patient Engagement surveys.

Contact us to learn more

Transportation Solutions

If you're in the transportation business, you can automate many of your routine tasks like package notifications, surveys, collection calls and more. Improve your customer satisfaction by extending your service hours without extending your costs.

Connect with us to learn more

A practical checklist for QA and clinical operations teams evaluating patient-reported outcome data

When a sponsor’s QA team reviews an ePRO vendor, the audit trail is usually where the conversation gets serious. It is easy for a vendor to say “we have a full audit trail.” It is harder to show you one, explain what each field means, and produce it on request during an inspection.

This article is a working checklist. It covers what a 21 CFR Part 11 ePRO audit trail should show, the questions worth asking, and an honest note about what any vendor, including us, can and cannot claim about compliance.

First, a note on what “Part 11 compliant” means

21 CFR Part 11 sets FDA expectations for electronic records and electronic signatures. It is important to be precise here: the FDA does not certify software as Part 11 compliant. Compliance depends on how a system is configured, validated, and used within a sponsor’s processes. A vendor can build features around Part 11 expectations and support your validation, but the sponsor’s validation is what confirms the system is fit for its intended use in your study.

Be cautious of any vendor that tells you their product “is Part 11 certified.” Ask instead what controls they provide and what validation support they offer.

The audit trail checklist

Who

Every entry and every change should be attributable. For participant entries, that means the record ties to a specific participant ID and the method used to authenticate them. For any administrative action, the record should show which user account performed it.

What

The audit trail should record exactly what was captured or changed: the question, the answer, and the field affected. Vague entries like “record updated” are not enough.

When

Timestamps should come from the server, not the participant’s device, so they cannot be altered by changing a phone’s clock. Ask what time zone timestamps are stored in and how they are displayed to sites in different regions.

Before and after values

If any value is ever changed, the audit trail should preserve the original value alongside the new one. The original should never be overwritten.

Why

Changes should require a reason, captured at the time of the change. Ask what reasons are available, who can make changes, and whether free-text reasons are allowed.

Questions specific to ePRO

Are survey versions frozen?

Participants should always see a locked version of the questionnaire, and every response should be tied to the exact version they saw. If wording or answer options change mid-study, you need to be able to prove which participants saw which version. Ask how versions are identified and how a new version is released.

Are responses immutable?

In many ePRO designs, participant responses should not be editable at all once submitted. If a correction process exists, ask how it is controlled and how it appears in the audit trail.

Is original audio preserved?

For IVR, ask whether spoken answers are stored as original audio, and if transcripts are produced, whether the audio remains the source record alongside the transcript.

How quickly can you produce an audit package?

During an inspection or a sponsor audit, speed matters. Ask how long it takes to produce a complete audit package for a participant, a site, or the whole study, and in what format.

How does this interact with blinding?

Audit trails and reports should not unintentionally reveal treatment assignments. Our article on collecting patient-reported outcomes without breaking the blind covers this in more detail.

How IVR Lab approaches the audit trail

IVR Lab is a boutique firm that builds hyper-custom voice IVR, SMS, and secure messaging. In clinical trials, we provide patient-facing ePRO only: diaries, check-ins, reminders, adherence tracking, and adverse event prompts to the site.

For regulated studies, we offer a regulated study mode. Survey versions are frozen and fingerprinted with SHA-256, so each response can be tied to the exact questionnaire version the participant received. Responses are immutable once captured. The design is built around 21 CFR Part 11 expectations. We do not claim to meet Part 11 on our own. Compliance is confirmed through the sponsor’s validation, and we support that process.

We are HIPAA compliant and SOC 2 audited, and Canadian data residency is available for studies that need it. You can see more on our audit-enabled surveys page.

Use this checklist with every vendor

The questions above are fair to ask anyone collecting ePRO data in your study. Ask to see a sample audit trail, not just a description. Ask for a demonstration of a version change. Ask how long an audit package really takes. A vendor that can answer clearly is one your QA team will be glad to work with.

If you are planning a study and want to talk through how phone and text ePRO fits your validation approach, visit our clinical trials page.