Test a co-managed IT arrangement by walking through four scenarios together: a support ticket, a security alert, a failed backup and a planned production change.
Write down the owner before the drill
For each task, name a primary owner, a backup, the hours each covers and the person who approves changes. Confirm where the ticket lives and who tells the business what happened. Agree to simulate events using test records and examples so the exercise does not disrupt production.
| Scenario | Question to answer | Record before finishing |
|---|---|---|
| Ticket escalates | Can first line reach the right engineer with the history attached? | Ticket route and the owner who accepts it |
| Alert after hours | Who can approve containment and who needs an update? | Primary and backup contact, with the agreed action limits |
| Backup failure | Who investigates and who can approve a restore? | Workload, restore owner and acceptance check |
| Production change | Who requests, approves and rolls back a change? | Change window, verification and exception path |
Review the first handoff that fails
If both teams wait for the other to approve a change, add the approval owner to the matrix and repeat the same scenario. If staff are unsure where to open a ticket, change the instructions and test it again. A short successful drill with a named backup owner is more useful than a long responsibility list that no one has exercised.
Use the co-managed responsibility worksheet to capture the split before the exercise.
Bring your internal IT lead and the duties you want help covering. Explore NetSys co-managed IT.
Discuss co-managed it for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.