Process Automation · Part 7 of 7
Learning series
Process Automation: From Manual Task to Running Workflow- 1Process Automation: Where Should Your Business Start?
- 2Process Mapping Before Automation: Draw It as It Runs
- 3Automating Internal Approvals: A Path and a Deadline
- 4Manual Data Entry: When the System Reads the Document
- 5Connecting Your Systems: The End of Copy and Paste
- 6Automation Controls: Logs, Permissions and Data Protection
- 7A 90-Day Plan to Automate Your Business Processes (you are here)
A 90-day plan to automate business processes splits the work into 3 blocks of 30 days: in the first you choose 2 processes, map them and set their controls; in the second you automate the approvals and the most repetitive data entry with a human review queue; in the third you connect the systems and switch off the manual copies after a period of running side by side. In part 6 you set the controls that watch what runs on its own. This seventh and final part of the series puts the exercises of the first 6 parts on one timeline, states which decisions belong to the owner and which to the operations lead, and lists what must be ready at the end of each block before you move to the next.
Before day one: who decides what
Most automation projects stall because decisions are unclear, not because the technology is hard. So assign the decisions before you start:
- The owner decides: which 2 processes go first, who owns each automation, the financial authority limits in approval paths, where data is stored if a tool runs outside the Kingdom, and the date the manual way stops.
- The operations lead decides: the detailed steps of each process, the rules and exceptions, who reviews the cases the system stops on, the side-by-side schedule, and team training.
- The people doing the work today: they are the source of the process map and the first to test the automation and review its results. Involving them from day one is what makes the map right.
Agree on one weekly 30-minute meeting between the owner and the operations lead to review what is done, what broke, and to take pending decisions.
Block 1 (days 1 to 30): choose, map and control
- Week 1: run the 10-task exercise from part 1, score each task on the 4 criteria, and pick only 2 processes: one approval process and one data entry process.
- Weeks 2 and 3: map each process as it really happens, with the people who run it: the steps, who does each one, where requests wait, and the exceptions. Time the process yourself from start to finish today; that is the figure you will compare against later.
- Week 4: run the automation and shared account inventory from part 6, name an owner for each chosen process, and note whether it carries personal data.
Ready on day 30: 2 mapped processes, a measured time for each, a named owner for both, and a list of the shared accounts that will be closed.
Block 2 (days 31 to 60): approvals and data entry
- The approval path: turn the first process into a path with authority limits by amount or type, a deadline for each step, and escalation when the deadline passes, as in part 3.
- Data entry: have the system read the document or form in the second process, and send every unclear or low-confidence case to a human review queue instead of letting it pass on its own, as in part 4.
- Controls with it, not after it: the run log, permissions, alert and manual fallback are built in the same week as the automation.
Ready on day 60: 2 processes running the new way, a named reviewer for the exceptions queue, and a log showing every request that went through the system.
Block 3 (days 61 to 90): connect and switch off the manual copies
- Integration: connect the automation to the programs staff copy into today, so an approved request or a read document reaches the accounting or warehouse program without being re-keyed, as in part 5.
- Running side by side: for a set period agreed by the owner and the operations lead, the new way and the manual copy run together, and results are compared weekly.
- Switching off: once results match, the owner announces a date when the manual copy stops, and the old file is kept read-only.
We explained the same method in more detail for moving data out of spreadsheets in What to Move First: An Order That Does Not Stop Work, and The First Thirty Days After the Move covers what usually fails after the switch and how to prepare for it.
Ready on day 90: 2 automated and connected processes, manual copies switched off, and a new measured time to compare with the one you took in block 1.
The Origami view
We are a Saudi technology company that builds systems, apps, integrations and AI solutions. We start any automation with 2 processes, not 10, because the first process shows how the business really works, and what the team learns there makes every process after it faster and clearer.
We build the controls, the human review queue and the side-by-side run inside the project itself, not as a later phase, so the owner can switch off the old way with confidence. You will find the details of what we build on our services page.
After day 90: closing the series
After 7 parts you have a complete method: choose the process, map it, turn its approvals into a path, let the system read documents with a human review, connect the systems, and control it all with logs and permissions. On day 91, go back to the list of 10 tasks, pick the next 2 processes and repeat the same cycle. Keep the inventory table from block 1 updated with every new automation; it is a good start for the record of processing activities that Article 31 of the Personal Data Protection Law requires when an automation carries people's data. Confirm how it applies to your case with SDAIA or a lawyer.
Sources
- Personal Data Protection Law — Saudi Data and Artificial Intelligence Authority (SDAIA) — Article 31 on records of personal data processing activities.
- Implementing Regulation of the Personal Data Protection Law — SDAIA
Frequently asked questions
How many processes should I automate in the first 90 days?
Only 2: one approval process and one data entry process. The first process shows how the business really works, and what the team learns there makes the next ones faster.
Which decisions does the owner take in an automation plan?
Choosing the 2 processes, naming the owner of each automation, the financial authority limits in approvals, where data is stored if a tool runs outside the Kingdom, and the date the manual way stops.
What does running side by side mean before switching off the manual way?
The new way and the manual copy run together for a set period and results are compared weekly. Once they match, the owner announces the date the manual copy stops and the old file is kept read-only.
How do I know the automation worked after 90 days?
Time the process yourself in block 1 before any change, time it again on day 90 after integration and switching off the manual copies, and compare the two figures.







