SC-02 · our practice ref · public-record

The non-critical systems limit

Practice SC-02 in the Scope and applicability group. The basis is public-record, and the row asks for 3 pieces of evidence.

At a glance

Ref: SC-02
Process: Scope and applicability
Basis: public-record
Source: Public abstract, 1.1 Fields of application
Evidence: 3 items
Gaps: 2 common

Evidence to keep

Scope and applicabilityA system list with a criticality classification and the reason for it
Scope and applicabilityThe classification rule the firm used, agreed with the technical lead
Scope and applicabilityA named route for any system classified critical

Questions before you sign

Which systems could cause serious harm if they failed?
Who is competent to make that classification, and have they signed it?
What route do the critical systems take instead?

The practice, in our words

Check that the systems in scope are non-critical. The public abstract limits the guide to the development of non-critical systems. A system whose failure could cause serious harm, loss of life or a major regulatory breach is outside the intended use and needs a different route.

What it means in a VSE

Sort the live and planned systems into three groups: clearly non-critical, clearly critical, and not yet classified. Only the first goes into the profile file without more work. For the third, classify before the file is built, not after.

In a firm of 25 people or fewer, the non-critical systems limit has to earn its time. The test for SC-02 is not whether the team understands it but whether the artefact exists at the end of the project. Shrink the meeting. Shrink the document. Keep the record.

How to evidence it

Attach the artefacts above to the The non-critical systems limit row with the project name, the owner and the date. The anchor for SC-02 is A system list with a criticality classification and the reason for it. A named person must produce it on request.

For SC-02, the reviewer will sample one live decision and ask for The classification rule the firm used, agreed with the technical lead. No artefact, no evidence. A file that depends on one person's mailbox is not a file for the non-critical systems limit.

What an assessor samples

An assessor reads the the non-critical systems limit practice, asks for its evidence and tests one project against it. For SC-02, the useful sample is the most recent project that used the practice, not the best one. A reconstruction written for the visit is a finding for SC-02 if the practice cannot be shown to have happened when it mattered.

Common gaps

Criticality left blank because nobody wants to own the answer
A safety-related system pulled into the profile because the template was convenient

What changes from the 2019 report. For SC-02, the public record already fixes the scope. The transition work is to write the boundary down and to record the decision if the firm sits outside it.

Where the draft fits

The public abstract places the non-critical systems limit inside one of the four processes the Intermediate profile covers. For SC-02, the draft clause numbering and wording are not public, so this page cites Public abstract, 1.1 Fields of application and does not quote the draft. The basis label for SC-02 says whether the practice is stated in the public record, named as a process in the series, or our reading.

Related practices

Source for this page: Public abstract, 1.1 Fields of application. Open the record and compare it with the SC-02 statement above. Retrieved 2026-10-22.