Common questions we hear everyday.

Our QMS passes audits. Why should we change it?

Passing audit shows you meet the minimum. It doesn't show the system is working for the business. Repeat deviations, rework, slow release and last-minute audit panics all cost money that a better system would save. "Good enough for audit" usually costs more than doing it well.

How do we get leadership engaged every day, not just before inspections?

Give quality a short, standing slot in the regular leadership meeting. Bring a one-page view of the few metrics that matter, any early warning signs and one decision you need. Leaders engage with choices and risks far more than with compliance updates.

How do we bring regulator, customer and third-party requirements into one QMS?

Map every requirement from every source into one requirements matrix, then link each one to the process that meets it. Where requirements overlap, meet them once. You end up with one structure that satisfies everyone, instead of separate systems for each audience.

How can we strengthen quality without adding headcount?

Share the load. Move routine quality activities into operations with clear responsibilities, train quality champions on each shift, and cut work that adds no value, such as duplicate checks and unused documents. Many teams find they have capacity once quality stops being one department's job.

How do we grow quality skills from the people we already have?

Define the skills each quality role needs, assess where people are now, and build development plans around the gaps. Use practical on-the-job coaching as well as courses. Growing your own people is faster than recruiting in a tight market, and it helps you keep them.

How do we stop quality depending on one or two people?

Write down who owns what in a simple RACI, cross-train so every key task has a backup, and capture critical know-how in short work instructions. Spreading ownership protects you from absences and leavers, and stops your best people burning out.

How do we make risk assessments more than paperwork?

Use them before decisions are made, not after. Keep them short, involve the people who know the process, and link each high risk to a control and an owner. Review the risk register in management review so it stays live. ICH Q9 expects risk management to support decisions, not just sit on file.

How can we speed up change control?

Sort changes by risk. Low-risk changes get a short, fast route with fewer approvals, and high-risk changes get the full assessment. Agree target times for each step and track them. When change control is quick and simple, people use it instead of working around it.

How do we know we could handle a recall?

Test it. Run a mock recall at least once a year, timing how quickly you can trace a batch, contact customers and account for stock. A tabletop exercise with the recall team is a good first step. The gaps you find in a test are far cheaper than the ones you find in a real recall.

What does good data integrity look like?

Good data integrity means records are complete, accurate and trustworthy from the moment they are created to the moment they are archived. The ALCOA+ principles sum it up: attributable, legible, contemporaneous, original and accurate, plus complete, consistent, enduring and available. The MHRA's GxP data integrity guidance sets out what inspectors expect.

Do we need an eQMS, or can we manage on paper and spreadsheets?

You can run a robust QMS on paper and spreadsheets if the controls are sound. What matters is version control, clear ownership, secure records and data you can trust. An eQMS helps as you grow, but it won't fix weak processes. Get the processes right first, then choose the system.

How do we clear our document review backlog?

Triage the backlog by risk and use. Review the critical documents first, merge duplicates and retire anything nobody uses. Then spread future reviews evenly across the year, so the backlog doesn't build again.

How do we prove staff are competent, not just trained?

Add a practical assessment. Read-and-understand shows someone has read the SOP, not that they can do the task. Have a trained supervisor watch the person carry out the task and sign it off against clear criteria. That record is your evidence of competence.

How do we get new and agency staff competent quickly?

Use a short, standard induction for every starter, focused on the critical tasks and quality rules for their area. Pair them with an experienced buddy, use visual work instructions and assess competence before they work alone. Consistency matters more than length.

How do we stop SOP changes creating a training backlog?

Match the training to the size of the change. A minor wording change needs a short briefing, not a full retrain. Use shift-start briefings for small updates, and save formal training for changes that affect how a task is done. Set a time limit for completing training after each change.

How can we qualify suppliers without delaying launches?

Start supplier qualification at the start of the project, not near the end. Use a risk-based route: a full audit only for critical suppliers, and desktop assessments or questionnaires for the rest. Standard templates for questionnaires and quality agreements save weeks.

How do we gain confidence in overseas suppliers we can't easily visit?

Combine remote audits, third-party or shared audit reports, certificates and your own incoming testing. Set clear requirements in a quality agreement and track their performance closely. Where risk is high, plan an on-site audit, even if it's less frequent.

How do we get faster agreement on quality agreements?

Start from a proven template that sets out standard responsibilities, and only negotiate the points that really differ. Agree the template with your own legal and commercial teams first. Most delays come from starting from a blank page each time.

How do we get decision-ready quality data without expensive tools?

Agree one source for each key metric, automate what your existing systems can already do, and build a simple one-page dashboard. Most of the data already sits in your eQMS, ERP or spreadsheets. Prove the value first, and investment in better tools becomes much easier to justify.

How do we clear our investigation backlog?

Triage open investigations by risk. Close the simple ones quickly, group similar deviations into one investigation, and set aside dedicated time for the complex ones. Then fix the cause of the backlog, which is often unclear ownership or too few trained investigators.

How do we investigate properly and still close on time?

Match the depth of the investigation to the risk. Low-risk events need a short, structured review. High-risk or repeat events need a full root cause analysis. Start straight away, bring the right people together early, and use a standard method so time isn't lost deciding how to start.

How do we audit without taking people away from their jobs?

Keep audits short and focused on the highest risks. Plan them into the schedule well ahead, split larger audits into shorter sessions, and use a small, trained pool of auditors. Where capacity is tight, bring in independent auditors for some areas.

How do we keep internal audits independent in a small team?

Make sure nobody audits their own work. Swap auditors between departments or sites, join an audit swap network with other companies, or use independent auditors for the areas you can't cover objectively.

How do we stop CAPA extensions piling up?

Set realistic due dates at the start, and agree a clear extension policy with a limit and senior approval for repeat requests. Review overdue actions monthly with leadership. When extensions are visible and need a good reason, they become the exception.

How do we show a return from quality improvements?

Measure a baseline before you start, such as deviations, rework or release time, and put a cost against it. Track the same measure afterwards and report the saving in pounds. Improvements with a clear return are far easier to fund next time.