Resource / Worksheet
Automation Discovery Worksheet
Map triggers, data, decisions, exceptions, ownership and recovery before choosing a workflow automation tool.
Use this worksheet to understand a process before choosing Make, Google Apps Script, an API or custom code. The goal is to document what happens today, identify stable parts worth automating and expose exceptions that need a person or recovery path.
1. Name the process and owner
Record the process name, business owner, day-to-day operator, affected teams and the reason the process is being reviewed. State the outcome in terms of what should improve: fewer manual transfers, clearer status, fewer duplicate records or more reliable notifications. Avoid defining success only as “use automation.”
2. Map the current steps
For each step, record the trigger, responsible role, system, input, decision, output and approximate frequency. Note where information is copied manually or re-keyed. Capture the normal path and at least one real exception. If the process varies widely from case to case, define the variation before deciding whether to automate it.
3. Define input and validation rules
List required and optional fields, formats, accepted values, identity and access checks, consent, duplicates and invalid-input handling. Confirm which system owns the original data and which fields can be stored in each destination. Decide how long records should be retained and who can access logs, exports and error queues.
4. Document decision points
Separate deterministic rules from judgement. If a rule can be written as a testable condition, document the condition and its owner. If interpretation is required, consider a review step or an AI-assisted suggestion with explicit evaluation criteria. Record what happens when information is incomplete, two rules conflict or the automated system cannot decide safely.
5. Design exception handling before the happy path
- What happens when an API or connected service is unavailable?
- How are timeouts, quotas and rate limits surfaced?
- Can an event arrive twice, and how will duplicates be prevented?
- What if a record is saved but the notification fails?
- Who receives a failure alert, and who can pause the automation?
- How can an operator retry a partial run without repeating completed actions?
6. Choose a proportionate implementation
Use a native tool when it covers the required process with understandable maintenance. A visual automation platform can fit a short chain of SaaS actions; Apps Script can fit Google Workspace; a custom integration may be preferable when branching, permissions, idempotency, volume or testing needs exceed an off-the-shelf module. Document vendor limits, costs, export options and what happens if the provider changes its offering.
7. Plan the handover
Record the workflow owner, credentials owner, monitoring location, alert recipient, recovery instructions, expected operating cost, review cadence and removal plan. Credentials belong in a managed secret store rather than a worksheet. Use a staging environment and representative test data before connecting live systems.
Discovery worksheet
| Prompt | Answer |
|---|---|
| Trigger and frequency | What starts the process, how often, and can events repeat? |
| Inputs and data owner | Which fields are required and which system is authoritative? |
| Decision rules | Which steps are deterministic, ambiguous or high impact? |
| Exceptions | What fails, how is it identified, and who owns it? |
| Action and result | Which systems change and how is success verified? |
| Controls | Logging, privacy, retries, access, retention and rollback |
Use the Lead Intake & Routing flow as an example of separating record storage from notification delivery. The Apps Script failure recovery guide expands on retries and partial runs.
Need a tailored version?
We can shape a resource, workflow or content system around your team and process.
Get in touch