All use cases

Find the procedure that applied.

Answer a version-specific question from the run record and its release history.

Book a demo
Illustration of a seal following successive procedure versions and the version used for a batch.

You: Which procedure applied to RUN-215? The document system now shows v05.

neil

RUN-215 started on 12 August at 09:00 with SOP-014 v04 linked at initiation. v05 became effective on 13 August at 08:00. The run's recorded instruction is v04, not today's latest revision.

The run retains its recorded version
The run retains its recorded version. SOP, RUN-215 v04, New runs v05. Example records.SOPRUN-215v04New runsv05

You: Does the new 30-minute limit apply retrospectively?

neil

The supplied release record applies v05 to new runs from its effective time and retains earlier runs' assigned revision. I would assess RUN-215 against v04's 45-minute limit. Any separately authorised retrospective assessment would need its own scope and rationale; it should not rewrite the execution history.

You: Write this up for review, with the sources and the follow-up work we need.

neil

Here is the draft. I have kept the supported finding separate from the open questions, and prepared the evidence requests for the responsible roles.

RUN-215 procedure applicability noteReview draft · source evidence and assessment

RUN-215 procedure applicability note

The current document version and the version applicable to a particular execution are not necessarily the same. RUN-215 records v04, while v05 explicitly applies to new runs. Retain that applicability rationale with the answer. If the question extends to another execution, check its start and version references separately rather than inheriting RUN-215's conclusion.

Source evidence and search scope

RUN-215 procedure link; SOP-014 release history and v05 applicability rule.

RUN-215 / Execution record

Started
12 Aug / 09:00
Procedure
SOP-014 v04
Version link
Recorded at initiation
Status
Execution record retained

SOP-014 v04 / Procedure revision

Revision
v04
Maximum hold
45 minutes
Temperature
2–8 °C
Run link
RUN-215

SOP-014 v05 release / Release and applicability record

Effective
13 Aug / 08:00
Applicability
New runs from effective time
Maximum hold
30 minutes
Earlier runs
Keep recorded revision
Inputs needed for your own records
  • The run or record you are asking about
  • Its linked procedure and version
  • Available release history and applicability rules

The answer reflects the available records. An incomplete release history or missing version link needs an owner to resolve it.

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

Follow-up work and evidence requests2 proposed tasks · not assigned

Evidence to request

Verify the effective-use record
Document controller
Retain the v04 initiation link and v05 release record, including timestamps and the scope of the transition.
Review execution against its assigned instruction
Run reviewer
Use v04's limits and evidence requirements. Record any retrospective assessment separately from the version used to execute the run.
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 run or record you are asking about
  • Its linked procedure and version
  • Available release history and applicability rules

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

Source excerpt

RUN-215

Execution record

Started
12 Aug / 09:00
Procedure
SOP-014 v04
Version link
Recorded at initiation
Status
Execution record retained

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

Browse all use cases