How to work with a regulatory affairs consultant

The first time you bring in a regulatory consultant, it’s tempting to treat the engagement like delegation — hand over the problem, get back an answer, move on. That’s not what makes an engagement work, and it’s not how responsibility actually functions once the consultant’s report lands on your desk. The work can be outsourced. The decision, and what you’ll have to defend later, can’t.

Scoping the work before it starts

The engagements that go well have a deliverable defined in specific enough language that both sides would recognize “done” the same way — a drafted response, a completed gap assessment, a defensible position on a specific question, not a vague mandate to “help with the submission.” They also settle decision authority up front: what the consultant is empowered to conclude on their own, and what has to come back to someone internal before it’s final. Project-based engagements suit a single, bounded deliverable; a retainer suits a sustained program where the value is continuity and availability rather than one output. Picking the wrong model for the work is a common reason an engagement feels like it underdelivered when the scoping, not the consultant, was the actual problem.

What a consultant can’t take off your plate

Signatory responsibility doesn’t transfer. Even when a consultant drafts the rationale behind a regulatory position, someone inside the company has to be able to explain and defend that reasoning years later — in an inspection, in a meeting with FDA, to a new hire who inherits the file with no memory of how the call was made. A consultant’s engagement has a start date and an end date; your quality system and your submission history don’t. That’s a strong argument for capturing the reasoning behind a consultant-informed decision the same way you’d capture any other judgment call — in writing, at the time it’s made, not reconstructed afterward. The practice is worth its own habit; see the case for a regulatory decision log.

None of this is an argument against using consultants — a good one brings depth and pattern-recognition an internal team building expertise for the first time simply doesn’t have yet, the same depth described in building expertise in one product area. It’s an argument for treating the engagement as a tool you direct rather than a black box you defer to, because the box you eventually have to open — the file, the rationale, the decision — is still yours.