Total Projects
0Projects
Open a Project to work in its DECIDE Change Register, or create a Project to start a new one.
| ID | Project name | Project owner | Target date | Registered Changes |
|---|
Change Register
Define each new way of working before detailed impact assessment begins.
Total Changes
0Change status status measures
- 0Draft
- 0Pending Validation
- 0Validated
- 0Revalidation Required
- 0Withdrawn
- 0Superseded
Criticality overlapping risk measure
0 of 0 Critical / High
| ID | Change | Change Group (TYPE) | Owner | Timing | Status | Relationship | Related Change | Criticality | Actions |
|---|
Advisory · practitioner confirms
Artificial Intelligence (AI) Guidance
DEFINE captures high-level Change Groups. Detailed impact dimensions belong in EVALUATE.
Consider stating who will work differently in each Change description.
CHG-001 and CHG-002 may be dependent. A practitioner must confirm or reject this relationship.
Not available in this release
EVALUATE
Assess impact and readiness
Assess who and what the Change affects, how significant those impacts are, and which capability or behaviour gaps must close before the Change is committed.
Not available in this release
EVALUATE is not available in this release. No impact assessment records can be created, and nothing shown here implies that EVALUATE is complete or approved.
01
Impact Assessment
Identify each impacted group, the current and future state, impact dimension, significance, timing and supporting evidence.
- Impacted Groups
- People, Process, Technology and Data dimensions
- Current state → future state
- Evidence and practitioner validation
02
Behaviour / Capability / Culture & Change Behaviour
Understand the behaviours and capabilities required to adopt and sustain each Change.
- Current and required behaviour
- Knowledge, skill and confidence gaps
- Culture and ways-of-working conditions
- Consequence of non-adoption
Impacted Groups
The groups this Project's Changes impact, chosen from the organisation's own groups on each Change and read back here.
Total Impacted Groups
0Read-only report. Its rows are DERIVED: each line is a group a Change in this Project has selected, and the numbers are counted from the Stakeholder register. Groups are chosen on the Change, in the Impacted Groups field of the Change form. Nothing here is added, edited or deleted.
| Group | Defined by | Population | Estimate date | Known people | Changes |
|---|
Stakeholders
Stakeholders are people, groups and organisations who can influence, or be affected by business changes. The stakeholder register records their details so every impacted person can be tracked through till change adoption. Records with duplicate email addresses are flagged, warnings appear before any deletion is confirmed, and a stakeholder linked to a communication cannot be deleted.
Total Stakeholders
0| Stakeholder | ID | Internal or External | Category | Business unit | Department | Team | Job title | Changes |
|---|
Change Network
Whether this Project needs a Change Network, who is in it, and what each member still needs to develop.
Total Members
0A Change Network Required
| Name | Nominated by | Nominated on | Capability | Status | Actions |
|---|
Communications & Engagement
This Project's communications and engagement, from Project initiation onward. Each communication states the DECIDE stage it relates to and the date it is planned for.
Communications
0By status
| Communication | Kind | Stage | Channel | Change | Owner or sender | Planned | Status | Actions |
|---|
Duplicate and overlap detection
Possible duplicate, overlapping, related, enabling, dependent or replacement Changes, proposed from this Project's own records. A practitioner confirms or dismisses each proposal.
Proposals to review
0Changes one relationship per Change record
- 0No relationship recorded
- 0Relationship recorded
| Change | Proposed relationship | Possible related Change | Why this is proposed | Actions |
|---|
Roles in this Project
Read only. A role is held on this Project, and this matrix says what applies here.
Deliverable
| Reference | Deliverable |
|---|
This deliverable is named by the functional model and is not built in this release. No data is created, displayed or implied here, and nothing here implies that it works.
DEFINE
Stakeholders
Stakeholders linked
0Assessed
0| Stakeholder | Influence | Interest | Impact | Current position | Desired position | Engagement need | Assessment date | Actions |
|---|
Application area
Application area
Not available in this releaseWhat this area will provide
No data is created, displayed or implied here. The working DEFINE scope is unaffected.
Value Lists
The lists the Stakeholder register uses. Renaming an entry carries every record with it. Withdrawing marks an entry inactive and keeps it, so nothing is deleted from these lists.
These lists belong to the whole organisation, so only the Product Owner may add, rename or withdraw an entry.
The organisation's three levels: a business unit, the departments in it, and the teams in each department. Every number below is counted from the Stakeholder register when this screen is drawn, never stored, and the taxonomy's own order is kept.
| Name | Contains | People | Actions |
|---|
People are counted from the stakeholder register. A dash means nobody is assigned yet.
A group is any node above, a business unit, a department or a team. How many people it holds is a query over the Stakeholder register's own Business unit, Department and Team fields, counted when this screen is drawn. Nothing about a group is stored, so a Stakeholder edited elsewhere moves these numbers and none can drift.
An entry is a department and the business unit it sits in. The usage count and whether it is still in use are read from the register, never typed.
| Business unit | Department | In use | State | Actions |
|---|
An entry is a name and whether it is Internal or External. The category the Stakeholder form offers is read from this one list.
| Category | Internal or External | In use | State | Actions |
|---|
Users & Roles
The accounts that may use this application. A person is identified by their email, and their roles are assigned per Project.
The Product Owner creates the accounts, assigns roles, resets passwords and disables accounts. A right is enforced against the Project being viewed.
A role is assigned to a Project, not to the person in general. The Product Owner holds every role everywhere.
| Name | Roles | State | Actions |
|---|
Backup
One encrypted file holds everything this application keeps: every register, every Project, every Change, and the accounts. Keep a copy on this machine and a copy on your server.
The passphrase seals the copy and opens it again. It is held only while this page is open: it is never saved and never sent. Write it down beside your recovery code, because a lost passphrase means a lost backup.
Passphrase
Repeat the passphrase
No passphrase is set in this page yet. Enter one to take a copy.
Writes the encrypted file to this machine, named with the date and time so two copies never collide. The file is sealed before it is written, so it is safe on disk.
The application posts the same encrypted file to your own server. The server holds the sealed file only, so it never sees the passphrase. The write token is not the passphrase and is never written into a copy.
Server address
Write token
No server address is set yet, so there is nowhere to send a copy.
A restore replaces everything this browser holds, the accounts included, so it changes who can sign in. It states what it will replace, with counts, and asks you to confirm before anything is written.