WEBVTT

1
00:00:00.450 --> 00:00:06.142
Keep the service connected after launch. Britixo
brings agreed support, maintenance

2
00:00:06.233 --> 00:00:10.361
and service coordination together so your team
knows where to go and who owns

3
00:00:10.374 --> 00:00:11.285
the next action.

4
00:00:13.383 --> 00:00:17.889
Start by agreeing the result you need from
accountable managed it support & continuous

5
00:00:17.902 --> 00:00:23.138
improvement. Identify the people involved, the
information and systems already

6
00:00:23.151 --> 00:00:28.490
in use, and the decisions that require evidence.
The need for responsibility does

7
00:00:28.503 --> 00:00:34.076
not end when a project goes live. An incident
may involve an application, server,

8
00:00:34.297 --> 00:00:40.065
connection or device, and the user needs a clear
route to help. We define the support

9
00:00:40.078 --> 00:00:44.375
boundary and escalation process so the service
can be investigated and coordinated

10
00:00:44.388 --> 00:00:47.174
without losing the context of the original
requirement.

11
00:00:49.250 --> 00:00:54.380
Before work begins, agree the scope, priorities,
responsibilities and the checks

12
00:00:54.393 --> 00:01:00.020
that will demonstrate a useful result. Clarify
the information, access, supplier

13
00:01:00.033 --> 00:01:05.554
dependencies and commercial terms involved. Keep
assumptions and exclusions visible,

14
00:01:05.789 --> 00:01:09.695
so everyone understands what is included and
what needs a separate decision.

15
00:01:11.783 --> 00:01:17.254
A clear support entry point. Users and
administrators know how to raise an issue,

16
00:01:17.462 --> 00:01:21.434
which information to provide and how to follow
progress through the support desk.

17
00:01:22.332 --> 00:01:27.996
Defined service ownership. Supported components,
access permissions, escalation

18
00:01:28.009 --> 00:01:32.293
contacts and maintenance responsibilities are
documented for the agreed service.

19
00:01:34.383 --> 00:01:39.424
A route for improvement. Recurring issues and
new requirements can be reviewed

20
00:01:39.437 --> 00:01:44.919
alongside service priorities. Approved changes
feed back into a scoped delivery

21
00:01:44.932 --> 00:01:51.898
plan. Supported operation. Your proposal
confirms the scope, responsibilities and

22
00:01:51.911 --> 00:01:53.786
evidence for this part of the service.

23
00:01:55.883 --> 00:02:00.545
Review the agreed work against representative
examples and the acceptance criteria.

24
00:02:01.445 --> 00:02:07.331
Check the information, access, hand-offs and
exceptions relevant to the scope. Record

25
00:02:07.344 --> 00:02:11.875
any unresolved limitations with an owner and a
next action, so acceptance remains

26
00:02:11.888 --> 00:02:14.336
an informed decision about the actual service.

27
00:02:16.417 --> 00:02:21.117
Agree what happens after the initial work: who
uses the result, who maintains the

28
00:02:21.130 --> 00:02:26.328
relevant records and how questions or changes
are raised. The operating arrangement

29
00:02:26.341 --> 00:02:31.718
follows your proposal. Review evidence from use
and support, then agree the next

30
00:02:31.731 --> 00:02:34.765
proportionate improvements as your organisation
develops.

31
00:02:36.850 --> 00:02:42.097
Britixo brings planning, software, integration,
infrastructure and support into

32
00:02:42.110 --> 00:02:47.816
a connected delivery approach. Your proposal
identifies what is included, who owns

33
00:02:47.829 --> 00:02:52.464
each dependency and how the service will be
supported. That gives your team a

34
00:02:52.477 --> 00:02:55.719
clear route from the original requirement to
everyday operation.

35
00:02:57.783 --> 00:03:02.276
Explore the matching Britixo service page for
the details and related guidance.

36
00:03:03.176 --> 00:03:07.785
Tell us what your organisation needs to achieve,
then discuss an appropriate scope,

37
00:03:07.994 --> 00:03:11.002
the responsibilities involved and a practical
next step.
