All use cases

Turn a procedure into a process.

Give neil an SOP and review the steps, checks and approval gates it prepares in Seal.

Book a demo
Illustration of a seal beside a procedure unfolding into execution checks and review evidence.

You: Turn SOP-QA-017 into a process we can test. Configure the capture fields and checks, not just a summary.

neil

I would configure three linked controls: prior-batch clearance, equipment eligibility and authorised QA approval. Each needs its own evidence. The procedure does not identify the equipment-status source, so that connection remains an explicit design decision.

Three proposed controls from the SOP
Three proposed controls from the SOP. §4.2 Clearance, §4.4 Equipment, §5.3 QA gate. Example records.§4.2Clearance§4.4Equipment§5.3QA gate

You: What stops this becoming three tick boxes?

neil

The proposed configuration captures the prior batch reference, equipment identity and approval identity alongside each decision. It should refuse completion when a required reference is missing or the reviewer lacks the approved role. A tick alone cannot establish equipment eligibility; the owner must define the authoritative status source and how stale or unavailable status is handled.

You: Configure the proposed fields and verification cases. Keep the unresolved decisions visible.

neil

Here is the design proposal, with source-linked fields and expected test behaviour. The tests are not executed; the configuration still needs owner review and verification.

SOP-QA-017 process and verification specificationReview draft · source evidence and assessment

SOP-QA-017 process and verification specification

The three clauses imply distinct checks: a prior-batch clearance record, an equipment-status reference and an authorised QA decision. A form with three tick boxes would not establish those relationships. The proposed configuration should identify the source of each check and preserve the procedure clause behind it. Test missing, restricted and unauthorised paths as well as an otherwise complete execution.

Source evidence and search scope

SOP-QA-017 revision 06; proposed line-clearance configuration.

SOP-QA-017 §4.2 / Procedure v06 / clearance

Requirement
Confirm previous batch clearance
Evidence
Previous batch reference
User entry
Clearance confirmation
Source
SOP-QA-017 v06

SOP-QA-017 §4.4 / Procedure v06 / equipment

Requirement
Equipment must be released
Equipment identifier
Required
Status source
Not specified in supplied text
Mapping
Requires owner decision

SOP-QA-017 §5.3 / Procedure v06 / approval

Requirement
QA approval before execution
Approver
Authorised QA role
Evidence
Recorded approval
Gate
Before execution

Line-clearance draft / Proposed configuration

Clearance
Batch reference + confirmation
Equipment
Identifier + status check
QA
Approval gate
State
Draft; not released
Inputs needed for your own records
  • The procedure, batch record or form
  • The equipment, roles and controls it refers to
  • A relevant Seal blueprint as the starting point

Your team checks intended use, resolves ambiguities, tests the configuration and approves what goes live.

Fictional source snapshots. No live query, assignment or approval.

Proposed configuration and verification4 fields · 4 test cases

Capture and conditions

previous_batch Record reference
Required before recording clearance
SOP-QA-017 §4.2
clearance Recorded decision
Required; an unresolved clearance does not satisfy the prerequisite
SOP-QA-017 §4.2
equipment Equipment reference
Required; eligibility source and freshness rule await owner decision
SOP-QA-017 §4.4
qa_approval Authenticated approval event
Require authorised QA scope before execution; retain identity, time and reviewed version
SOP-QA-017 §5.3

Verification cases

QA-01 / No previous-batch reference
Prevent clearance completion and identify the missing reference
QA-02 / Equipment restricted or its status unavailable
Do not record equipment eligibility as passed; use the reviewed exception path
QA-03 / Approval attempted by a user without QA scope
Refuse the approval action; do not progress to execution
QA-04 / Clearance and eligibility evidenced; authorised QA approves
Record approval evidence and allow only the defined next workflow state

Expected behaviour, not executed tests. This is a design specification, not a native import file or published process.

Decisions before implementation

Resolve the equipment-status contract
Process owner
Identify the authoritative record, eligible states, permitted age and unavailable-source behaviour for clause 4.4 before implementing its condition.
Test the three independent controls
Configuration reviewer
Verify missing clearance, ineligible or unknown equipment and an unauthorised QA attempt. Record the tested configuration version and observed result for every case.
Example conversation · prepared replies

See this job with your team.

Tell us how your team handles this job today. We’ll walk through the analysis, supporting evidence and review steps in a demo.

Book a demo
What to bring for this job
  • The procedure, batch record or form
  • The equipment, roles and controls it refers to
  • A relevant Seal blueprint as the starting point

Source access, permissions and permitted actions are agreed for your environment.

Source excerpt

SOP-QA-017 §4.2

Procedure v06 / clearance

Requirement
Confirm previous batch clearance
Evidence
Previous batch reference
User entry
Clearance confirmation
Source
SOP-QA-017 v06

Selected fictional record, not a live source-system view.

Browse all use cases