1. The Hidden Split Inside Your Own Facility
Imagine this picture:
- Production A runs on a modern electronic batch record (eBR) system. Processes are automated, times and dates are captured automatically, and every hold time, sample status, and signature is traceable at a click.
- Production B still runs on paper. Operators record times by hand, calculate hold times manually, and later transfer the data into the same central system that Production A already feeds electronically.
On paper (and in Controlling dashboards), both areas belong to “one site”. In reality, you are running two different centuries under one roof.
Now give your experienced Non-Conformity Owner from Production A the task to support or even fully take over deviation work and daily QA decisions for Production B.
- New SOP sets
- Different data structures
- Manual processes instead of automated checks
And yet, the products, specs, and regulatory expectations have not become any kinder. This is where many companies lose efficiency, knowledge, and money without even noticing.
2. Same SOP Title, Completely Different World
A classic example we see:
Both Production A and B use the same Sample Management SOP for in-process and release testing. On a global level, it looks aligned:
- Same definition of sample types
- Same limits and storage conditions
- Same rules for dirty hold time, clean hold time, sterile hold time, etc.
But the implementation differs dramatically:
- In Production A, the LIMS or eBR calculates sample hold times automatically. Time stamps from equipment, sampling, and testing are pulled directly from the system. Alerts fire when limits are reached or exceeded.
- In Production B, sample times are written by hand on batch records, sampling lists, or log sheets. An operator or supervisor calculates hold times manually. Then, someone transfers the data into the central system afterward.
So when a deviation pops up because a hold time might be exceeded:
- The Non-Conformity Owner from Production A is used to system-generated audit trails, automatic time stamps, clear workflows.
- In Production B, the same person must:
- Hunt for paper records
- Reconstruct timelines from handwritten entries
- Trust manual calculations done under time pressure
The SOP number is identical. The actual process, risk profile, and investigation effort are not.
3. When Experts Turn into “Beginners” Overnight
From a human perspective, this mismatch is brutal.
A QA specialist who has mastered the deviation process in a fully digital area suddenly has to:
- Learn a completely different way of documenting
- Navigate forms that were never digitized
- Understand local “tribal knowledge” on how things are really done in Production B
This has several consequences:
- Quality risk
People hesitate to support areas where they feel insecure about the process and documentation model. That hesitation can delay investigations, CAPAs, and timely decisions. - Burnout and frustration
High performers from digital areas may feel “demoted” when they move into a paper based world. Their expertise is still there – but they need to fight the system instead of using it. - Unequal expectations
Management often assumes that a deviation owner is a deviation owner. In practice, the same role behaves very differently depending on whether the environment is digital or paper-based.
The sad part: this is not a personal competence issue. It is a structural problem in the way your processes and systems are aligned (or not aligned).
4. Where Misalignment Shows Up Beyond Sample Management
The disconnect between Production A and B will surface in many other areas:
- Cleaning documentation
- Digital line: automatic status of equipment (“available for use”, “due for cleaning”, “locked”).
- Paper line: cleaning logs, line clearance checklists, manual sign-offs.
- Change control and impact assessment
- In digital areas, many dependencies are modeled in systems (e.g., recipes, master data, linked documents).
- In paper areas, dependencies often live in people’s heads or local Excel files.
- Training records
- LMS with clear overview of training status in Area A.
- Mixed HR lists, manual sign sheets, and Excel files in Area B.
- Shift communication
- Structured, system-based logs on one side.
- Free-text paper shift books and oral handovers on the other.
In each case, cross-support and rotation between teams becomes harder than it should be. Leaders wrongly assume “We have one site, one quality standard”. In reality, people are forced to work as translators between two incompatible working worlds.
5. The Cost That Controlling Does Not See
From a budget point of view, both areas might show similar KPIs:
- OEE looks acceptable
- Deviation counts are comparable
- Inspection outcomes appear fine
What is often missing is a transparent cost of complexity:
- Extra time spent on investigations in paper-based environments
- Additional QA review cycles because documentation is harder to follow
- Repeated training and coaching when staff rotates between A and B
- Subtle increase in human error risk where manual calculations replace system logic
Controlling frequently does not see the reality behind the numbers. Budget decisions are then made under the assumption that both production units are equally “mature”, just with different equipment or product types.
That is where wrong conclusions arise:
- “We do not need further digitalization in Production B; performance is OK.”
- “QA staffing is sufficient; the site meets its KPIs.”
In fact, your most experienced people are constantly compensating for process and system gaps. Their time could be spent on improvement and innovation – instead, they are fire-fighting complexity.
6. Quick Self-Diagnostic: Are You Running Two Parallel Realities?
Use this short checklist with your leadership team. Score each item:
- 0 points = not true
- 1 point = partly true
- 2 points = fully true
Questions
- We have at least one production line with eBR / highly digital processes and another that is still heavily paper-based.
- Deviation owners or QA staff are expected to support both areas without a specific onboarding to the different process realities.
- Sample management (including hold times) follows “the same SOP” on paper, but the actual handling and calculation steps differ significantly between areas.
- We do not have one single, visual overview explaining how Production A and B actually run their documentation and data flows side by side.
- Cross-training for operators, supervisors, and QA between A and B is ad-hoc rather than strategically planned.
- Controlling reports do not explicitly distinguish between digital vs paper-based process effort.
- Migration of good practices from the digital area to the paper area (or vice versa) is not part of a structured roadmap.
Your score
- 0–4 points:
You may have pockets of misalignment, but it is still manageable. Now is the moment to act before complexity grows. - 5–8 points:
You are already losing efficiency and knowledge. Expect hidden costs in QA, investigations, and training. - 9–14 points:
You are effectively running two different organizations under one logo. This will show up in inspections, staff turnover, and long-term cost curves if it is not addressed.
7. From Digital Island to Blueprint: Using the Modern Line to Lift the Older One
The good news: Mixed maturity is not just a headache. It is an opportunity. If one production area is already running modern systems, you have a living model of:
- How data can be structured
- How workflows can be controlled
- How hold times, sample statuses, and deviations can be managed with system support
Instead of treating Production B as “the problem child”, you can use Production A as a blueprint:
1. Map the end-to-end process for both areas
Take one core process (e.g., sample management, cleaning, deviation handling) and draw the actual step sequence for A and B side by side. Include:
- Roles
- Systems
- Documents
- Decisions
2. Highlight where the digital line provides built-in controls
Identify every place where the eBR or LIMS prevents errors, calculates times, or provides transparency.
3. Derive “non-negotiables” for the paper area
Even if you cannot digitize immediately, you can translate system-supported controls into smart paper procedures. For example:
- Pre-formatted fields for time stamps
- Simple check tables instead of free-text comments
- Calculators or Excel templates for hold times, attached to the SOP
4. Define a mid-term migration path
Use the ongoing work in Production B as preparation for later digitalization. Clean data structures, standardize terms, align naming conventions. Future system implementation will be smoother and cheaper.
8. Action Plan: 7 Practical Steps for Harmonization
Here is a concrete sequence you can use tomorrow:
1. Select one cross-cutting topic
Start with a process that touches QA, Production, and QC – sample management, deviations, or cleaning status are ideal.
2. Run a joint workshop with both areas
Involve operators, supervisors, QA, and QC. Ask them to map “how we really work” on a whiteboard or digital board.
3. Identify must-have controls vs. local habits
Separate what is GxP-required from what is historical practice. Many paper-based steps exist “because we always did it that way”.
4. Define a harmonized process model
Create one target process that can be applied in both worlds:
- With system support in A
- With smart paper tools in B
5. Create a visual process overview
Produce a one-page “process map” that shows both areas and highlights:
- Where they share the same logic
- Where the implementation differs
This becomes the reference document for onboarding and cross-support.
6. Adapt training and rotation plans
Build cross-training modules that explicitly address the differences. Make sure deviation owners, sample coordinators, and line managers receive role-specific explanations.
7. Align KPIs and controlling
Include a metric that reflects process maturity – not only output. For example:
- Percentage of system-generated time stamps vs manual timestamps
- Number of deviations requiring manual data reconstruction
These metrics help Controlling and senior management see why investment into harmonization pays off.
9. Compliance Clarity: How FDA and EMA Will See This
Regulators do not care whether your site has one or two MES or LIMS systems. They care about consistency, control, and data integrity.
From an FDA / EMA perspective, the risks in mixed-maturity environments include:
- Data integrity gaps
Manual transcription from paper into electronic systems always raises questions:
- How do you ensure completeness?
- How do you avoid transcription errors?
- How do you control and document corrections?
- Unequal risk profiles for similar products
If similar products or batches are handled in different ways in A and B, you must be able to explain:
- Why is this acceptable?
- How do you ensure equivalent control?
- Fragmented deviation and CAPA management
If deviation workflows are heavily system-driven in one area and fully manual in another, inspectors may ask:
- How do you ensure that root causes are analyzed with the same depth?
- How do you aggregate data across areas for trending?
- Inconsistent training and role clarity
When experts move between areas, the site must demonstrate that they are adequately trained for:
- The specific documentation model
- The specific systems and tools used in each area
Handled well, your harmonization effort becomes a positive story during inspections:
- Clear explanation of current maturity levels
- Structured roadmap to harmonize process logic
- Evidence that lessons from the digital area are systematically transferred to the paper area
This shows regulators that you are not only compliant, but also actively managing your risk profile instead of accepting historical chaos.
10. Leadership & Strategy: Turn Mixed Maturity into a Competitive Advantage
Many leaders see mixed digital maturity as a temporary annoyance: “We will fix Production B once budget allows.”
A more strategic view is possible:
- Production A is your innovation lab for digital control.
- Production B is your stress test for how robust your processes really are without system support.
By connecting both worlds deliberately, you gain:
- Better understanding of what truly adds value in your digital tools
- Sharper insight into where human error risk originates
- Clearer business cases for digitalization that Controlling can stand behind
The companies that will win are not the ones with the shiniest systems, but the ones who understand how their systems and people work together across all areas.
If you recognize your own plant in this description, the next step is straightforward:
- Make the split visible.
- Use the advanced area as a blueprint.
- Design harmonization as a structured program – not a side task.
This is exactly where external consultants can help: by bringing best practices from other global projects and turning your daily struggle into an organised improvement journey.
