When to bring in outside regulatory support

Variations, annual renewals, Union Product Database (UPD) updates and responses to authority questions do not arrive evenly. They bunch, and every one of them runs against a fixed clock.

• Variation waves (VNRA and VRA) and renewals landing in the same quarter.
• Day-120 and Day-180 responses with tight, non-negotiable deadlines.
• No slack in the system: one delayed submission pushes everything behind it.

How support fits: overflow per case, or a short project to clear the peak and hand back a clean queue.

A new marketing authorisation, a line extension, or a feed additive dossier is a large, front-loaded project that lands on top of business as usual.

• New marketing authorisations across national, MRP/DCP or centralised procedures.
• Feed additive authorisations under Regulation (EC) No 1831/2003, with EFSA dossiers compiled to Regulation (EC) No 429/2008.
• The team cannot pause maintenance work to build a dossier, and rarely has the spare capacity to do both well.

How support fits: project-based, with a defined scope and a fixed fee.

When the rules change, the work is rarely one submission. It is the same change repeated across every affected product.

• SPC and label harmonisation, new guidance, and UPD data migration.
• Feed additive re-authorisations, which arrive in clusters as ten-year terms expire.
• A one-time surge that a baseline team was never sized to absorb.

How support fits: a project to run the whole programme, or overflow to absorb the volume alongside your team.

Inspection preparation, and the corrective and preventive action (CAPA) work that can follow, is intense and time-boxed.

• Readiness reviews, document and PSMF checks, and mock inspections.
• CAPA logged and tracked to closure after findings.
• It competes directly with day-to-day deadlines that do not pause for an inspection.

How support fits: a focused project before the inspection, and again for the follow-up.

Sometimes the problem is not volume, it is people. A single absence can leave binding obligations uncovered.

• Parental or sick leave, or a resignation with a hiring lag.
• A named role that must stay filled and available, such as a Qualified Person resident in the EU.
• A specialism the team does not hold in-house, for example feed additives or a specific procedure type.

How support fits: interim cover, a deputy or named role, or a specialist on demand.

Expansion multiplies regulatory work before it multiplies the team.

• Portfolio growth, acquisitions, and marketing authorisation transfers.
• Entering the EU, or moving between the EU and Latin America, where local knowledge is the real bottleneck.
• More products and more markets, each carrying its own ongoing maintenance load.

How support fits: project-based for the market entry, then a retainer for the ongoing load.

The engagement should follow the problem, not a fixed package. In practice it comes down to four shapes:

• Project-based for a defined piece of work with a clear end, such as a registration or a variation programme.
• Overflow, per case, for peaks and backlogs where you need hands, not headcount.
• Interim cover for leave, a vacancy, or a named role for a set period.
• Retainer for a standing, part-time extension of the team.

The point is simple: deadlines get met, and you add capacity only for as long as you need it, without a permanent hire.