Understanding the situation
- establishing the business impact of the issue
- an inventory of services, access and dependencies
- setting responsibility boundaries and priorities
SysGroup / IT delivery process
diagnosis, safe change, confidentiality
How we work
We do not publish client case studies or details of their environments. Instead, we clearly show the repeatable way we carry out diagnosis, changes and follow-up work.
Client confidentialityDiagnosis before changeSafe deliveryClear next steps
Safe change
- backup, tests and an agreed maintenance window
- a cutover plan and a way to revert the change
- clarity on what we need from the client or application developer
After delivery
- concise documentation of the work done
- review of agreed services after the change
- a recommendation for further care, monitoring or next actions
Operational schematic - not a client story
An example change involving a domain, mail and a service
This schematic shows the order of work for a change that can affect several services. It does not describe a particular client and is not a promise of an outcome, time or no interruption.
Owners and dependencies
First we confirm who has access to the registrar, mail and service, which services depend on DNS, whether a usable copy exists and who can test.
Plan, test and cutover approval
We agree the scope, change window, way to test mail and the service, and the conditions for reverting. Functional tests are performed by the nominated client contact or application developer.
Change and record of state
After the agreed cutover, we check only the agreed services, record the completed steps and identify open risks or further actions.
This is a work schematic, not a public case study. We do not publish client names, configurations, metrics or operational results. Responsibility for application code remains with its developer unless separately agreed otherwise.
How we start
First we establish the current state and the required diagnostic scope. For ongoing subscription support, we then agree responsibility, SLA, ticket flow and a plan for taking over access, documentation and monitoring.