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
How we carry out work
How we reduce risk when changing a critical system
A critical infrastructure change does not begin with a production click. We begin by understanding the current state, dependencies, risks and expected result — without assuming that every situation has the same safe path.
State and risk
We review services, access, backups, documentation and the elements that cannot be stopped without business impact.
Plan and tests
We select the approach: diagnosis, backup, testing, change window and rollback plan. Specific functional tests are agreed with the client or application developer.
Delivery and verification
After agreement, we make the change, verify the agreed outcome and report further risks or care that may be needed.
This describes a way of working, not a story about a particular client. We protect the confidentiality of client environments and do not publish their names, configurations 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.