Everything we need to switch on your Deviance Logger, in one intake.
Tell us once. The take-on portal gathers your business information — how it is structured, who must be enabled, the deviances your teams expect to log, and how those deviances are approved. From it, NodeOne configures your Deviance Logger platform, enables your users, and puts your own name, logo and colours on every screen they touch.
A new intake opens the same seven-step process with every step shown across the top, so you always know where you are. It is filed against the business named in step 1 and appears in the management portal under that customer. Customers do not sign in here either — each one can also receive their own branded take-on link, created and sent from the management portal.
What we need from the client steps 1 – 4
- Business informationRegistration and market, size band, sites and quantities, and departments.
- User informationMain contact, every user to enable with their role and permission level, and the approvals team with the ambit each one holds.
- Deviance specificsDeviance types in scope, the P1–P4 severity model, the P1–P4 urgency model, the Low/Medium/High impact scale, the locations the logger may be used from, and the escalation matrix.
- Process management informationThe internal approvals process in the client's own words, its owner, service levels, delegation, policies, measures, retention and change control.
What the client can expect from us steps 5 – 7
- Enablement and rolloutUsers will be able to sign in to the Logger Platform via mobile (for logger users) and to the backend Platform (for management users). Training for operations on the platform will be provided. The implementation team will prepare the platform for use, and communications regarding readiness will be sent to all users when ready.
- Business engagement rulesCarla Vorster, Axsel Botha, or Kobus Botha from the Node One Group will be in contact with you shortly after the take-on of information for implementation purposes. The scope of the implementation is taken into consideration, and the Node One Group representatives will address your queries within one working day, and all data gathered is handled under agreement.
- Commercial guidancePlease refer to the Channel Partner Agreement, where Pricing is maintained and agreed.
More information The next step process · How a deviance is graded · Deviance types
The next step process from link to live
Every take-on follows the same path. Each step below says what happens, who does it and when it happens, so a customer always knows what comes next.
| Step | What happens | Who | When |
|---|---|---|---|
| 01 The take-on is opened | A link is created in the management portal for the customer and sent to them, or an intake is started directly. The link carries that customer's own logo, colours, wording and support details. | NodeOne | Day 0 |
| 02 The intake is completed | Seven steps, each shown across the top of the page: business information, user information, deviance specifics, process management information, enablement and rollout, what the client can expect of us, and review. Answers save as they go, and a step can be skipped and returned to if the information is not to hand. | The customer | About 12 minutes |
| 03 It is submitted | The declaration is signed, anything useful is attached, and a reference is issued immediately — for example NO-TA-2026-0001. The submission can be checked again later with that reference, and the steps and sections still outstanding are shown against it. | The customer | On submission |
| 04 NodeOne reviews it | Sites, locations, departments, users and the ambit each approver holds are checked against the deviance profile. Anything unclear comes back as a clarification request rather than an assumption. | NodeOne | Within two working days |
| 05 The logger is configured | Sites, locations, departments, deviance types, the P1–P4 severity and urgency models, the impact scale, the escalation matrix and the approval workflow are loaded exactly as the customer described them. | NodeOne | After approval |
| 06 Users are enabled | Every named user is created at the permission level, site and department given, with the approvals team and the ambit each one holds. | NodeOne | With configuration |
| 07 Go-live | Users sign in and start logging, with two weeks of hypercare behind them and support per the agreement thereafter. | Both | The target go-live date |
Steps 02 and 03 happen on the customer's own branded link. Everything from step 04 onwards happens in the management portal, where the intake, its outstanding sections and its enablement pack are held.
How a deviance is graded severity and urgency
| Level | Severity | Urgency |
|---|---|---|
| P1 | Critical — imminent risk to life, licence or continuity. | Deal with it now; work stops and it escalates by telephone. |
| P2 | High — significant impact that worsens if unattended. | Deal with it today, with an interim control holding the position. |
| P3 | Medium — localised disruption with a workable interim control. | Schedule it into the current work cycle. |
| P4 | Low — minor or an improvement opportunity. | Batch it with other work in the next planned cycle. |
Impact is recorded on every deviance as Low, Medium or High. Each severity carries its own response and resolution target, and each level its own escalation.
Deviance types expanded catalogue
Thirty types ship with the portal, each with a code, a category, a default severity and an owner department. A customer ticks what applies, adds anything missing, and the whole taxonomy travels into the enablement pack.