Can SOP content be used to answer process questions?

Yes. Document Intelligence structures the procedure, scope, references, and available revision information. Once connected in the Context Layer, that content can support questions about the process and the records that refer to it, with sources available for review.

How does Katalyze handle SOP revisions?

It reads the version supplied and the revision information available in that record. Your controlled document system remains the authority for effective versions. If the number, revision, or history is missing, your team needs to resolve it before relying on the procedure for a particular batch or date.

How are SOP instructions related to a batch record?

Procedure references in the batch record can connect the work to the relevant SOP and its steps in the Context Layer. Reviewers use the document identity, revision, and scope to check the relationship. A matching title alone does not establish that the procedure applied to the batch.

How can SOPs support a technology transfer?

The sending site's procedures describe how activities are performed and which related documents they depend on. Tech Transfer can use that knowledge with other connected evidence to prepare transfer documentation and proposed follow-up. The receiving team assesses applicability and the changes its site needs.

Standard operating procedure · Cell culture · in forceIn your schema

DocumentStandard operating procedurep. 1 · header
TitleCell culturep. 1 · header
StatusIn forcep. 1 · header
Kept inSharePoint · controlled documentp. 1 · header
ScopeP-14 · fed-batch culture · Site Ap. 1 · section 1
ProcedureNumbered steps · read in orderp. 1 · section 3
ReferencesMaster batch record P-14 Rev 3 · the harvest SOPp. 1 · section 4
ApprovalsRevision history · not shownp. 1 · section 5

8 of 12 fields · page 1 · source-linked

SOPs

The procedure behind the work, easier to trace.

An SOP defines how work is performed within a stated scope and revision. Document Intelligence structures its instructions, references, and document history, so your teams can review the procedure alongside the batches, equipment, and site knowledge relevant to an investigation or transfer.

Book a Demo Explore Document Intelligence

Inside SOPs

What the record holds, and where it matters.

The details your team needs are spread across fields, tables, notes, and signatures. Katalyze makes them easier to use while keeping them connected to the record.

Explore Document Intelligence

01
Document identity and status
The title, document number, revision, and status identify the procedure, with missing identifiers left for review.
Needed for Procedure review · document traceability
02
Purpose and scope
The purpose and scope define which product, processes, activities, and sites the procedure covers.
Needed for Procedure review · Tech Transfer
03
The numbered procedure
The procedure sets out the sequence of work, with the instructions retained alongside their step references.
Needed for Process review · Tech Transfer
04
Referenced documents
References identify the related master batch record and other procedures needed to understand how the work fits together.
Needed for Procedure review · Tech Transfer
05
Revision history and approvals
The history records changes, effective dates, and approvals that help reviewers establish which version applied to the work.
Needed for Document review · Tech Transfer

Structured data

Organized around the way your operation works.

Katalyze maps extracted information to your terminology and field definitions, retaining links to the original page, table, field, or note.

Explore the Context Layer

Entity

Procedure

cell culture

Titletextheader
Numberidentifierheader
Revisionidentifierheader
Statustextheader
Kept intextheader · SharePoint

Entity

Scope

P-14 · Site A

Processtextsection 1
Productreferencesection 1
Sitetextsection 1

Table

Steps

section 3

Stepidentifiercolumn 1
Instructiontextcolumn 2
Referenced fromreferencethe batch record's procedure references

Entity

Reference

P-14 Rev 3 · harvest SOP

Documentreferencesection 4
Revisionidentifiersection 4

Table

Revision history

section 5

Revisionidentifiercolumn 1
Effectivedatecolumn 2
Changetextcolumn 3
Approvalsignaturecolumn 4

Entity

Approvals

in force

Authorsignature · datesection 5
Reviewersignature · datesection 5
Approversignature · datesection 5

Checks and review

A clear path from a flagged value to its source.

Defined checks flag information for review. Your experts inspect the source, confirm or correct the extracted information, and leave a record of the decision.

Review and traceability

The cell culture standard operating procedure as a controlled document: the header with its title and status, purpose and scope, the numbered procedure, the references, the revision history and approvals

Kept in · SharePointControlled document · as recordedChecked

Title · cell cultureNamed on the batch record · procedure referencesChecked

Status · in forceAs recorded · revision not shownChecked

Scope · P-14 · Site AMatches the batch record's headerChecked

Procedure · numbered stepsRead in order · each step wholeChecked

Master batch record P-14 Rev 3Current revision · Rev 3Checked

After review

Document data, connected to the wider operation.

Reviewed data can go to a configured destination or join system data through Connectors in the Context Layer, linking records to the materials, batches, and processes they describe.

Explore Connectors

Read from the record
Status · in force · SharePoint
Scope · P-14 · fed-batch culture · Site A
References · master batch record P-14 Rev 3
Reference · the harvest SOP
Procedures on the master batch record · cell culture · harvest
Site A · procedures in force

In the Context LayerWhat is known · what the record adds

Product P-14procedurescell culture · harvest · in forcerecipemaster batch record · Rev 3batches12 · BR-0410 to BR-0421

Procedure · cell culturestatus scope references referenced frombatch record BR-0412 · procedure references

Procedure · harveststatusin force · SharePointreferenced from

Master batch record P-14 Rev 3procedures effective2026-01-15

Site Aprocedures equipmentproduction bioreactor · 2000 L

Transfer · P-14 · Site A to Site BproceduresSite A's · Site B's under reviewitems4 · 4 open

6 things read · every value with its page · source links retained

Put to work

Evidence for the work that follows.

Agentic Solutions use the Context Layer to investigate operational questions and draft supporting documents and action plans for your experts to review.

Explore all solutions

01
Tech Transfer
Assemble process knowledge and supporting evidence to prepare transfer documentation and action plans.
- Procedures · cell culture · harvest · in force
- Feed strategy · defined in the master batch record
- Bioreactor operation · equipment differences under review
→

Questions

Questions about SOPs.

How these records are read, checked, and put to use.

Less time preparing data. More time using it.

Bring the job you want to move forward and the records you'd like connected. Thirty minutes on how Katalyze would do the work, and where your experts come in.

Or, just a quick chat to run through the product, your call.

Explore Document Intelligence

The procedure behind the work, easier to trace.

What the record holds, and where it matters.

Document identity and status

Purpose and scope

The numbered procedure

Referenced documents

Revision history and approvals

Organized around the way your operation works.

Procedure

Scope

Steps

Reference

Revision history

Approvals

A clear path from a flagged value to its source.

Document data, connected to the wider operation.

Evidence for the work that follows.

Tech Transfer

Questions about SOPs.

01Can SOP content be used to answer process questions?

02How does Katalyze handle SOP revisions?

03How are SOP instructions related to a batch record?

04How can SOPs support a technology transfer?

Less time preparing data. More time using it.