Request Routing: Current vs. Automated
MAP · PROCESS MODELING
MAP · PROCESS MODELING
This page maps one process two ways: how a scheduling request was handled by hand, and how it runs now that a Google Apps Script workflow handles it. Each swimlane diagram, created in Visio, follows a single request from the moment it’s logged in Google Sheets until it’s either on the calendar or closed as not needing a meeting.
In the manual version, a person opens the tracker, checks whether the request is complete, decides whether it needs a meeting, scans the calendar by eye, creates the event, and goes back to update the tracker. In the automated version, a scheduled trigger reads each new row, applies the routing rules, creates the event when one is needed, and writes the result back to the sheet. A person steps in only when a row has an error.
I built the automation first, then mapped both versions side by side to see exactly which decisions and handoffs the script took over, and where a person still needs to be involved.
A request comes in. Someone opens a tracker, reviews the information, decides where it belongs, checks the calendar, and updates the record. It's familiar work, and when everything goes as expected, the process seems simple enough.
But there are places where things can go wrong. A calendar event gets entered twice. A tracker isn't updated. A routing decision depends on who's handling the request. And when something goes wrong, there's no clear record of what happened or why.
I created two swimlane diagrams in Microsoft Visio that model the same request-routing process as a current state (manual) and a future state (automated).
The current-state model shows the decisions, handoffs, and updates a person manages by hand. The future-state model shows what changes when the Google Apps Script automation I built applies the business rules, creates calendar entries, updates the tracker, and records errors.
Looking at them side by side makes it easier to see not just what changed, but why.
In the manual version, a requester submits information that someone reviews in a Google Sheet. If something is missing, the request goes back for correction, and the review starts again when the information arrives.
Once the request is complete, that person decides where it should go and whether a calendar event is needed. They scan Google Calendar by eye for an existing event, create the event by hand, and return to the tracker to update the record.
In the automated version, a scheduled trigger starts the Google Apps Script. It reads the request rows, skips any that already have a Calendar Event ID, applies the business rules for whether a calendar event is needed, checks that the times are valid, and then creates the event. It records the result in Google Sheets.
If the script can’t process a request, it records an ERROR and the reason. That exception path is where a person steps back in to review the problem and decide what needs correcting.
The important difference is that the decisions haven’t disappeared. I’ve defined the rules so the system knows which actions to take and when a person needs to get involved.
Microsoft Visio · draw.io · Google Apps Script · Google Sheets · Google Calendar
This is what I enjoy about process modeling. Something that appears simple can involve several decisions and handoffs that aren’t obvious until you map the work.
By comparing the two versions, I could see which steps could follow defined rules, where responsibilities would change, and where human judgment still belonged. The diagrams show where those decisions sit in the process, first by hand and then with the automation in place.
The future-state model also serves as the visual model in my Calendar Routing use case. Verifying the two against the script showed one check out of order in the diagram, which I corrected.
Select both images below to enlarge