01 / 06
SECTION 2

What nobody
tells you.

The cost that no vendor's quote includes - and the reason most pharmaceutical sites are still printing today.

SCROLL
02 / 06
THE SIMPLEST CHANGE

A small change to a Word document
you already use.

📝
The trigger: Your validated analytical method now requires pH monitoring. You need to add one extra column to the in-process monitoring table in your batch record.

In Word, this takes thirty seconds. Right-click, insert column, type "pH", save.

On your site, this takes one week.

01
Raise change control request
DAY 1
02
Impact assessment - does this affect other documents?
DAY 1–2
03
Draft new version of the template in Word
DAY 2
04
Route for review - QA, department head, subject matter expert
DAY 2–4
05
Approve new version
DAY 4–5
06
Train all affected personnel (often 80%+ of site)
DAY 5–7
07
Reconcile old copies, make new version effective
DAY 7
~1 WEEK - FOR ONE COLUMN
Batch record with 'Include pH' annotation pointing to the in-process monitoring table
SCROLL
03 / 06
NOW IMAGINE

That was one column in one document.
Now imagine changing everything.

Your documents

New editor, new templates, new format. Every document on site needs to be recreated, reviewed, and approved.
192
DOCUMENT TYPES
×

Your workflows

New routing, new approval logic, new training requirements. Every SOP that governs how you work needs rewriting.
∞
SITE-SPECIFIC VARIATIONS
The one-column change took a week. Replacing the whole thing - rebuild, rewrite, retrain, revalidate - takes years. That's what "going digital" has meant for thirty years.
SCROLL
04 / 06
THE REAL PROBLEM

Your workflows are unique.
That's what makes this so hard.

Every site has evolved its own version over years - sometimes decades. This is your crystallised wisdom.

DELEGATION OF AUTHORITY
Who can approve what, and up to what level - shaped by your org structure, your audit history, your people
REVIEW SEQUENCES
Sequential or parallel, who goes first, what happens on rejection - codified in SOPs but often lived in people's heads
TRAINING REQUIREMENTS
Who must be trained before they can touch which document - linked to qualifications, roles, and specific procedures
INSTITUTIONAL KNOWLEDGE
"Always check with Sarah first" - the unwritten rules that no system captures but everyone follows
This isn't configuration. This is the accumulated intelligence of your site. Replace it, and you're starting from zero.
SCROLL
05 / 06
THE COMPROMISE

No vendor can build a system
that fits every site.

What you do today

Your unique review sequences
Your delegation of authority
Your training prerequisites
Your document templates
Your institutional knowledge
NEGOTIATE
THINGS YOU LOSE. THINGS YOU GAIN.

What the platform expects

Its own routing logic
Its own approval structures
Its own training model
Its own document format
Its own idea of "best practice"
You're not just adopting software. You're negotiating a compromise between your site's evolved intelligence and someone else's idea of how a pharmaceutical site should operate.
SCROLL
06 / 06

This is why we're
still printing today.

Not because better software doesn't exist. But because the cost of changing everything - your documents, your workflows, your people, your culture - has been too high for too long.

Make sure you understand what "replace the whole thing" actually means before you commit to a path. The vendor's demo won't show you this. Their quote won't include it. But your site will live it - for years.

Continue to Section 3 →