1
00:00:01,000 --> 00:00:05,050
Automation often begins with a handover between people, rather than

2
00:00:05,080 --> 00:00:06,010
with a new tool.

3
00:00:06,920 --> 00:00:10,010
A fictional installation company receives an enquiry.

4
00:00:10,520 --> 00:00:14,650
Sales calls it approved, but scheduling lacks the address and expected

5
00:00:14,760 --> 00:00:15,890
job duration.

6
00:00:16,120 --> 00:00:20,010
The request was forwarded, yet nobody knows who should fill the gaps.

7
00:00:20,920 --> 00:00:23,930
Start at receipt and finish at the agreed outcome.

8
00:00:24,360 --> 00:00:28,730
For each transition, record the information required, who supplies it

9
00:00:28,920 --> 00:00:32,410
and who retains responsibility when something is missing.

10
00:00:32,840 --> 00:00:36,330
Received, complete and scheduled mean different things.

11
00:00:36,760 --> 00:00:39,450
Define when each state may change.

12
00:00:39,880 --> 00:00:43,530
A forwarded email alone does not confirm that another team has

13
00:00:43,760 --> 00:00:46,090
accepted the work or taken ownership.

14
00:00:46,520 --> 00:00:50,495
Fixed fields and explicit decisions often need only rules or an

15
00:00:50,520 --> 00:00:51,650
integration.

16
00:00:51,960 --> 00:00:56,170
AI can help interpret free text, but it cannot reliably invent

17
00:00:56,200 --> 00:01:00,090
a missing address or resolve unclear responsibilities.

18
00:01:00,520 --> 00:01:04,170
Decide what happens when a request is rejected, cancelled or

19
00:01:04,200 --> 00:01:04,970
incomplete.

20
00:01:05,560 --> 00:01:09,290
Make its current owner visible and show how staff can continue

21
00:01:09,320 --> 00:01:12,730
after a correction without starting everything again.

22
00:01:13,160 --> 00:01:17,530
Run through an ordinary request, repeated delivery and an interrupted

23
00:01:17,560 --> 00:01:18,450
connection.

24
00:01:18,680 --> 00:01:21,610
Check state, owner and destination.

25
00:01:22,040 --> 00:01:26,730
Measure waiting and recovery work too; making one stage faster may

26
00:01:26,760 --> 00:01:28,890
create extra work elsewhere.

27
00:01:29,320 --> 00:01:33,130
Begin with one recurring handover and the teams involved.

28
00:01:33,160 --> 00:01:35,450
Clarify the agreements first.

29
00:01:35,600 --> 00:01:39,930
Then automate the stages whose inputs, responsibilities and intended

30
00:01:39,960 --> 00:01:43,210
outcomes are sufficiently clear to test.

31
00:01:43,240 --> 00:01:48,330
Read OXIAE’s business process automation guide for practical handovers

32
00:01:48,360 --> 00:01:49,850
and exception paths.