GuidePackHow to create a
step-by-step guide
A useful guide gives the reader a clear starting point, one action at a time and a way to recognize the result. Here is a short example: finding unpaid orders in a browser tool
1 · Start with the result
Use a specific title such as “Find unpaid orders”, rather than “Orders”. Tell the reader what must already be true: they are signed in, can access the order list and have permission to view the relevant data
Keep one procedure in one guide. If the task branches into different approval or payment processes, explain where this guide ends and link to the next one in the system where you share it
2 · Capture one action per step
In the sample workspace, open the filter, choose unpaid orders and apply it. Use the screenshot from the moment before the action, so the reader can see the control they need to click
Open the filter
Orders1042 · Field Studio · Pending
1041 · Form Design · Paid
Click Filter in the order list
Choose unpaid orders
Payment status✓ Unpaid 2
Select Unpaid to keep orders that still need payment
Apply and check the list
Payment status · UnpaidClick Apply, then check that the resulting order list matches the status you selected
Illustrated example with fictional data · Try these controls in the interactive demo
3 · Explain what matters
Lead with the action and name the control the reader sees. Add the reason only when it helps someone make a decision. “Select Unpaid to see orders that need payment” is more useful than “Click here”
Keep names and values consistent with the screenshot. If the tool changes its labels, update the wording too. Do not add a step that you did not verify
You say: “Okay, open the filter… we only want the unpaid orders here”
The guide says: “Open the filter to select unpaid orders”
Explain each action as you record. GuidePack connects your voice to the right step and turns it into an editable instruction. See the illustrated voice demo
4 · Check the guide from the reader’s starting point
- Can the reader reach the first screen with their own account?
- Does each screenshot show the right control and marker?
- Have you removed unnecessary clicks and hidden private information?
- Does the final step explain how to recognize success?
- Will the guide still make sense without your spoken explanation?
Open the exported file before sharing it. PDF works well for a fixed handout, Word allows further editing, and HTML opens in a browser. Keep an editable backup so you can update the guide when the process changes
Make and download your own example
Try the GuidePack guide creator on a fictional order workflow. Your clicks become steps; you can then download the result without using real business data or a microphone
Try the guide creator →