Map a client approval workflow before buying automation
Turn a messy feedback loop into one readable diagram and a clear decision about what needs automating.
An editable approval map, a shareable image and one evidence-based decision about whether another tool is needed.
Start with a real job: a client receives a draft, requests changes or approves it, and gets the final files. One whiteboard is enough to expose unclear handoffs. The illustration below is a fictional FreeStack example, not a tested client process. Provider sources checked 13 October 2026.
Free boundaries before you start
Source checks for this workflow. These notes clarify older catalogue summaries; they do not change your saved toolkit.
Excalidraw · checked 2026-10-13
Free browser whiteboard with local saving and PNG, SVG and editable file exports. The manual guide does not use AI credits. Excalidraw Plus is a separate paid workspace for cloud organisation. The editor software is MIT-licensed; hosting and imported assets have separate terms.
Account requirement not confirmed in this source check.
A small example to aim for
FreeStack example output · illustrative, not a provider screenshot or a tested export.
Jump to a step
Write the start and the finish
Choose one deliverable, such as a café menu. Start when the first draft is ready and finish when the client has the approved files. Write who owns each action: designer, client or printer. Leave invoicing and marketing outside this map unless they change approval. Keep names and private client material out of anything you plan to share publicly.
Draw actions and one decision
In Excalidraw, create boxes for Send draft, Review and Deliver approved files. Add a decision labelled Approved? Give both outgoing arrows a word: Yes leads to delivery; Changes leads to Revise, then returns to review. Put an owner and the expected file beside each action. Use words before colour so the diagram still makes sense without its styling.
Add the exception that costs you time
Choose one real snag: no reply, conflicting feedback or an old file being approved. Add a small note describing the next action, its owner and when it should happen. For example, after two working days without a response, the designer follows up with the current draft link. Agree that timing with your client rather than treating this example as a service promise.
Save the source and check the handoff
Export an editable .excalidraw file and a PNG or SVG for review. Use filenames with a date or version. Reopen the editable file, then ask a colleague to trace one approval and one revision using only the map. Note where they cannot tell what happens next. Browser autosave is convenient, but keep a separate source-file backup. A shared picture is not an automated workflow.
Buy only for a named requirement
Run the clarified process manually first and record repeated delays. FreeStack editorial upgrade trigger: consider a managed diagram workspace only when team organisation or dependable cloud access is a recurring requirement. Consider a separate automation service only when a specific handoff repeats enough to justify its setup and ongoing cost. An arrow on a whiteboard sends no emails and stores no approvals. Keep the map even if you decide to buy nothing.
Your workflow, connected.
Follow the steps and carry the output into the next stage. These are suggested handoffs, not automatic integrations.
Provider information
Check current plans and documentation before committing to a workflow.
A couple of useful questions
Do I need an account or another subscription?
This manual workflow uses the free whiteboard, not a paid subscription. Account requirements were not explicitly confirmed in the retrieved plan documentation. Save this toolkit in FreeStack if you want to keep its tool link; that does not upload or back up your diagram.
Is this the same as setting up automated approvals?
No. It is a process map. Any future automation must separately handle identity, permissions, notifications, records and failures.
What should make me pay?
A requirement you can name and test: shared management, a delivery constraint or a repeatedly costly manual action. More available features alone are not a reason to subscribe.
What would you try?
Share your result or ask a specific question about this workflow.
Join the conversationKeep building
TallyValidate one product idea with a short waitlist
Build a focused Tally form, show a clear confirmation and learn what people actually need.
Tally
Toggl TrackA small free stack for a calmer freelance project
Connect a clear intake form, a simple project board and time tracking without creating another system to maintain.