Relay04 / How we work

A calm handover.
A visible working relationship.

You should understand what changes, what stays with your business and how the service will run before anyone takes over the queue.

The question behind the change

“Can we move providers without losing what the last person knew?”

A useful transition starts with knowledge, responsibility and consent—not a rushed credential transfer.

Explore the working sequence

Clear steps.
Useful handover evidence.

Timing follows the estate, access readiness and current contracts. The sequence below shows the decisions, not a fixed-day promise.

Stage 01 / Discover

Understand the working day.

Identify people, sites, devices, applications, current suppliers and recurring requests. Agree who can approve information sharing.

What should exist after this step
Business context, initial inventory and open questions.
Who is involved
Operations owner + Relay service lead

Each stage closes with an agreed output before responsibilities move on.

After the transition

A service rhythm
people can follow.

Explore the sample service desk
Day-to-day

Requests with a next action.

Clear descriptions, appropriate priority, named ownership and visible approvals. Actual response commitments are set in the service agreement.

Planned changes

Business approval before disruption.

Scope, dependencies, an approved window and a reversal approach proportionate to the change.

Service reviews

Decisions instead of slide volume.

Recurring issues, unresolved dependencies, lifecycle decisions and upcoming plans, with owners attached to the resulting actions.

A useful first conversation

Start with the handover questions.

Whether you are appointing a first IT partner or changing providers, begin by making ownership and the next step clear.

Plan my IT review

A practical first conversation

Let's understand your IT.

Frontend preview. Use example details; nothing is sent or saved.

Relay Guide

Find your next step in IT

AI feature preview · Prepared responses, no live AI

Tell me what you're trying to improve: everyday IT, new starters, security ownership or recovery planning. I'll point you to the right service and starting questions.

Use general examples. Never share passwords, account details or sensitive incident information.