Clarity before commitment.
State what is included, what needs separate agreement and what still needs confirmation. A proposal should give the customer a usable account of the service they are buying.
In practice: define the scope before the order.Our values
What we stand for.
How it shows up.
Values become useful when they change a decision. These are the standards we want our work to be measured against.
Judgment over excess.
More capacity is not always a better answer. Explain how the options change cost, performance and operating effort. Recommend a configuration for a reason that the customer can understand.
In practice: make the trade-offs visible.A record worth keeping.
Capture the decision, its reason and the person responsible for the next step. Good documentation lets someone else pick up the work without reconstructing the conversation.
In practice: leave context for the next person.Responsibility that travels.
Make responsibilities clear across customers, 3NT and other providers. When an issue crosses a boundary, identify the next action and who needs to take it.
In practice: make every handover actionable.Respect for what depends on us.
Behind a resource allocation is someone’s work, data and trust. Consider security, recovery and the effect of a change while planning the service. Say what is known and what still needs checking.
In practice: plan the way back before moving forward.Read the principles. See the terms.
Our values describe how we approach the work. Service scope, responsibilities and any commitments are set out in the agreed order and applicable policies.
Legal & trust →