Planning guides
Business Automation Guides, Tools & Examples
A guide can explain a task. A tool can carry it out. An example can show what the finished job might look like. The useful part is putting those three things together around work you actually do.

Key takeaways
Describe one repeated job.
Choose a guide that answers your next question.
Check the exact action your tool supports.
Pick one repeated job and write down how it starts and what a correct result looks like. Read a guide for that job, check that the tool supports your exact steps, then try a small sample. Use the result to decide whether to continue.
- Describe the task
- Choose a small test
- Check the result
- Agree the next step
Start with a job you can describe
Think of the last time you copied the same information between two places. Perhaps a staff member emailed a supply request, and you typed it into a shared list. Write down that job in one sentence before opening a tool.
For example: when a staff member asks for supplies, add the request to our list and let the office manager know. That sentence gives you a clear start, a place for the information and a person responsible.
If you have several ideas, use our first-automation guide to narrow them down. This article shows how to turn the advice you find into a test you can actually run.
Use a guide to answer the next question
Read the part that matches the decision in front of you. If you cannot describe the steps, start with a process guide. If the steps are clear but the software is uncertain, use the tools guide. If you need to judge the cost, write down the task volume and use the cost worksheet.
Keep a short note while you read: what applies to our work, what needs changing, and what is still unknown. A guide written for an online shop may have a useful stock-checking rule, but its order fields may not fit an office supply request.
You can find the full collection on our Guides page. Follow the practical examples when you need to picture a task, then return to your own one-sentence plan.
Read an example by looking for four things
Find the event that starts the job, the information it needs, the result it creates and the person who checks a problem. These are more useful than the number of apps shown in a diagram.
Take our supply-request example. A completed form starts the job. It needs an item, quantity, requester and delivery location. The result is one entry in a shared list. The office manager handles missing details.
Copy the idea into your worksheet using your own fields. Decide whether anyone must approve the request before an order is placed. In this example, the automation only records and passes on the request; the manager still decides what to buy.
Check the exact steps before choosing a tool
First check whether your current software already offers the rule you need. Then check any connection between apps. A tool listing your email service does not prove it can perform every email task you have in mind.
In Microsoft Power Automate, saved workflows are called flows. They can connect services for tasks such as collecting information and sending notifications. In Zapier, a Zap starts with a trigger and then runs actions. A trigger is simply the event that starts the work.
For the supply request, check whether your form can start the workflow, whether your shared list can receive all four fields, and whether a notification can reach the manager. Check access, usage limits and any plan requirements before committing.
Choose the option your team can maintain. A clear record of completed runs and a way to find failed requests matter when the person who built it is away.
Try five requests before expanding
Use made-up test details. Send one complete request, one with a missing location, the same request twice, one with an unclear quantity and one while the destination is unavailable.
The complete request should create one accurate entry. The missing location and unclear quantity should be easy for the manager to find. Repeating the same request should not quietly add a second order. An unavailable destination should leave the request recoverable.
Record what happened beside each test. If the tool cannot tell you whether a request was saved, fix that gap before relying on it. Keep the original request until the result has been checked.
Decide what the test has shown
Check the actual list entries against your test requests. Count how many needed manual correction. Ask the manager whether the notification includes enough information to act.
For a small live trial, note how long the job takes before and after, including the time spent fixing mistakes. A faster notification is useful only if the right request reaches the right person.
Use the worksheet below to keep the guide, tool check and test results together. If you want help turning it into a working setup, send Automations For Business your task and current tools on WhatsApp.
Your ready-to-use checklist
0 of 6 checked
Make the next step clear.
Business Automation Guides, Tools & Examples worksheet
Free templateSources and notes
Sources checked on October 21, 2026.
- Business automation guides
Find the first-task, cost and practical examples guides mentioned here.
- Microsoft: Power Automate overview
Flows, connected services and learning resources.
- Zapier: what is a Zap?
Triggers, actions and testing a workflow.