Knowella

Extent of Condition Review

Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us. Completed for any serious event. Carried out by the investigation lead with area supervisors. Turns one incident into prevention across the whole site.

EllaGeneralRecordFDN-018
Completed by
Carried out by the investigation lead with area supervisors
Raised
At the moment the event happens, rather than reconstructed

Summary

In short

  • An extent of condition review is a record used in General that asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us. It is built against Nuclear operating experience practice and forms part of the Incident and Investigation programme.
  • Completed for any serious event. Carried out by the investigation lead with area supervisors.
  • The template holds 22 fields across 4 sections.
  • Nuclear operating experience is nuclear operating experience practice. The nuclear industry discipline of learning from events elsewhere before they happen to you.
  • It connects to the rest of the library: linked from Root Cause Analysis.

What it is

What it is

What is an extent of condition review?

An extent of condition review is a record used in General that asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us. It is built against Nuclear operating experience practice and forms part of the Incident and Investigation programme.

When is an extent of condition review completed?

An extent of condition review is completed at the moment the event happens, rather than reconstructed afterwards. Completed for any serious event.

When to use it

When to use it, and when not to

This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.

Use it for

  • The event or activity this record covers has occurred, or is about to
  • The workspace is being set up, or the register needs an entry added or retired
  • You are running the Incident and Investigation programme and this is one of its steps
  • A linked record needs this one to exist: linked from root cause analysis

Not for

  • Risk Assessment, which the single risk assessment used across the whole business.
  • Root Cause Analysis, which finds out why something happened rather than who was involved.
  • Corrective and Preventive Action, which the single action record used everywhere.
  • Anything outside General, which belongs in the workspace that owns that process

Standards

What it is built against

Nuclear operating experienceNuclear operating experience practice

The nuclear industry discipline of learning from events elsewhere before they happen to you.

FAQ

Frequently asked questions

What is the extent of condition review template based on?+

It is built against Nuclear operating experience practice. Nuclear operating experience is nuclear operating experience practice. The nuclear industry discipline of learning from events elsewhere before they happen to you.

What sections does the extent of condition review contain?+

There are 4 sections: header, extent of condition, extent of cause, outcome. Together they hold 22 fields, 16 of which are required.

How many extent of condition review records should we have?+

This is a singleton. One record per workspace, set up once and maintained, rather than one per event. Other templates refer back to it.

Which programme does the extent of condition review belong to?+

It is part of Incident and Investigation, Master Data and Foundations. A single case thread from the event to a verified corrective action, with regulatory reporting handled.

Can the extent of condition review template be changed?+

Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.

The agents

What the agents do with it

The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.

Ella

Holds the extent of condition review library against your registers, routes each record to its owner, and keeps the evidence trail together.

Ella

Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.

This template lives in Generalcontrol tower. The orchestration layer. Registries and engines every other workspace reads from.

Meet General

Sources

Sources

  • Nuclear operating experience — Nuclear operating experience practice

General

Also in Engines

6Browse the whole library
EllaAssessment

Risk Assessment

The single risk assessment used across the whole business. Choose a method to suit the work, from a simple matrix through to FMEA, LOPA, bowtie or exposure assessment. Completed by a trained assessor with the people who do the task. Produces a score that can be compared with any other risk in the organisation.

EllaRecord

Root Cause Analysis

Finds out why something happened rather than who was involved. Opened after any incident, failure or nonconformance where the potential loss justifies it. Led by a trained investigator with a team drawn from the areas involved. Produces coded causes and feeds actions that address the real weakness.

EllaAction

Corrective and Preventive Action

The single action record used everywhere. Captures what will be done, who owns it, when it is due and how you will know it worked. Raised from any incident, finding, audit or assessment. Completed by the action owner and checked later by someone independent.

EllaRecord

Finding

Records a single deficiency picked up during an audit, inspection or check. Raised whenever an item fails a check. Completed by the person carrying out the check. Each finding carries its own severity and links to the action that closes it, so nothing is lost in a long report.

EllaRecord

Effectiveness Verification

Checks whether an action actually worked, some time after it was put in place. Scheduled 30 to 180 days after the action is completed. Carried out by someone other than the action owner. If the check fails, the action reopens and a fresh investigation is triggered.

EllaRecord

Just Culture Determination

Separates a system problem from a genuine choice to take a risk, using a consistent set of questions. Completed during any investigation involving a person's actions. Carried out by a manager with HR input. Protects workers from unfair blame and keeps people willing to report.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.