Who the profile reaches, what it covers and where it stops.
Home / The register
40 practices, 120 evidence items
The transition register
One testable practice per row. Each states the practice in our words, labels its basis, and names the evidence, the common gap and the questions to ask. The FDIS body is not public; the register does not pretend to be a clause-by-clause reading of the draft.
One row, one testable practice
The register has six groups: scope, business management, project management, system definition and realisation, acquisition management, and transition. Every practice belongs to one group, carries a basis label, and about three evidence items. The basis label is the honest part: public-record means the ISO abstract states it, series-structure means the process area is named in the abstract and the practice is our reading of how a VSE works it, and our-reading means the practice is ours and is not attributed to the text.
- Ref is our practice number. It is stable across editions and is not an ISO clause.
- Basis is where the practice comes from, so you can check it.
- Evidence is the number of artefacts an assessor asks for, not a score.
The four processes and the two frames
The business the projects serve, the capacity across them and the process assets.
From the acquirer's needs to a delivered, verified system.
Decide to acquire, select a supplier, agree the technical content, accept and close.
Move from the 2019 Technical Report to the Intermediate profile and keep the file assessable.
All 40 practices
| Ref | Practice | Process | Basis | Evidence |
|---|---|---|---|---|
| SC-01 | Who the profile is for | Scope and applicability | public-record | 3 |
| SC-02 | The non-critical systems limit | Scope and applicability | public-record | 3 |
| SC-03 | More than one project and more than one work team | Scope and applicability | public-record | 3 |
| SC-04 | Where the Intermediate profile sits | Scope and applicability | public-record | 3 |
| SC-05 | What the guide adds to the Basic profile | Scope and applicability | public-record | 3 |
| SC-06 | What the guide does not do | Scope and applicability | public-record | 3 |
| BM-01 | State the business the firm is in | Business Management | series-structure | 3 |
| BM-02 | Set the objectives the projects must serve | Business Management | our-reading | 3 |
| BM-03 | Own the process assets and the tailoring rule | Business Management | series-structure | 3 |
| BM-04 | Allocate people across parallel projects | Business Management | public-record | 3 |
| BM-05 | Review business performance and act | Business Management | our-reading | 3 |
| BM-06 | Decide which work to take and which to decline | Business Management | our-reading | 3 |
| PM-01 | Start the project with an approved plan | Project Management | series-structure | 3 |
| PM-02 | Define scope, deliverables and acceptance criteria | Project Management | series-structure | 3 |
| PM-03 | Estimate effort, cost and schedule | Project Management | our-reading | 3 |
| PM-04 | Build the work breakdown and the schedule | Project Management | series-structure | 3 |
| PM-05 | Assign roles and responsibilities | Project Management | public-record | 3 |
| PM-06 | Manage risks, issues and changes | Project Management | our-reading | 3 |
| PM-07 | Monitor progress and take corrective action | Project Management | series-structure | 3 |
| PM-08 | Close the project and capture lessons | Project Management | series-structure | 3 |
| SR-01 | Establish the system requirements baseline | System Definition and Realisation | series-structure | 3 |
| SR-02 | Define the system architecture | System Definition and Realisation | series-structure | 3 |
| SR-03 | Allocate requirements to elements | System Definition and Realisation | series-structure | 3 |
| SR-04 | Design and realise the elements | System Definition and Realisation | series-structure | 3 |
| SR-05 | Integrate and verify the system | System Definition and Realisation | series-structure | 3 |
| SR-06 | Validate against the acquirer's needs | System Definition and Realisation | public-record | 3 |
| SR-07 | Manage configuration and change | System Definition and Realisation | series-structure | 3 |
| SR-08 | Control externally supplied elements | System Definition and Realisation | series-structure | 3 |
| SR-09 | Deliver the system and the evidence pack | System Definition and Realisation | series-structure | 3 |
| AC-01 | Decide to acquire rather than build | Acquisition Management | public-record | 3 |
| AC-02 | Select the supplier on stated criteria | Acquisition Management | series-structure | 3 |
| AC-03 | Agree the technical content of the contract | Acquisition Management | our-reading | 3 |
| AC-04 | Monitor the supplier and accept deliverables | Acquisition Management | series-structure | 3 |
| AC-05 | Close the acquisition and integrate the result | Acquisition Management | our-reading | 3 |
| TR-01 | Record the transition decision | Transition and evidence | our-reading | 3 |
| TR-02 | Compare current practice with the Intermediate profile | Transition and evidence | our-reading | 3 |
| TR-03 | Re-baseline work products and templates | Transition and evidence | our-reading | 3 |
| TR-04 | Retrain the roles that change | Transition and evidence | our-reading | 3 |
| TR-05 | Set the review and re-baseline trigger | Transition and evidence | our-reading | 3 |
| TR-06 | Keep the evidence file assessable | Transition and evidence | our-reading | 3 |
Every practice has an owner in the evidence index, a dated artefact and a recorded answer to the questions. The owner is a named person, not a committee.
The table is server rendered. The same rows drive the practice pages, the kit, the API and the free check, so a change to one row changes every output.
The transition kit, USD 149 one off.
The 40-practice register, the 120-item evidence index, the dated plan and the board brief, as PDF, CSV and XLSX. Five labelled rows are free on the specimen page.