Unified Task Management for Freelance Designers - A Complete Workflow
As a freelance designer, your work lives in multiple places by design (pun intended).
Your actual designs live in Figma. Your client feedback is in Figma comments. Your project deliverables are in Google Drive.
Your revisions are tracked... Your timeline and deadlines are in Asana or Airtable. Your invoices come from a different system.
You're not using too many tools. You're using the right tools for each part of the work. The challenge is connecting them into a coherent workflow so nothing falls through cracks.
The Designer's Multi-Tool Reality
Unlike developers who can consolidate most work into one issue tracker, designers work across fundamentally different systems.
Figma is for design. It's where feedback happens, where iterations live, where the actual work exists.
Drive/Dropbox is for file handoff. It's where you store final deliverables.
Email is where contracts and approvals happen.
Calendar is where deadlines live.
Asana or Airtable is where you track projects and timelines.
Invoice tool is where you track payment.
This isn't tool sprawl. This is the reality of design work. Each tool serves a specific purpose.
The Workflow: From Kickoff to Delivery
Here's how to structure it:
Week 0 - Project Kickoff
- Create project in Asana with timeline, phases, deliverables
- Create folder in Drive with client name and project name
- Create Figma file and share with client
- Document what feedback looks like (we'll take feedback in Figma comments, approve via email)
Week 1-2 - Design Phase
- Work in Figma. Iterate. Collect feedback in Figma comments.
- When a round of feedback is complete, summarize it in Asana. "Round 1 feedback - 3 revisions requested"
- Update Asana with current status and next review date
Week 3-4 - Revision Phase
- Incorporate feedback
- Upload revised versions to Figma (new frames or pages)
- Notify client in Figma comments "Revisions uploaded"
- Update Asana: "Round 2 - revisions addressed, sent for approval"
Final - Handoff
- Get written approval (email or explicit Figma comment)
- Export final files
- Upload to Drive in client's deliverables folder
- Create invoice in your invoice tool
- Mark complete in Asana
This structure is clear. Each tool has a role. Work flows through them systematically.
Managing Feedback Loops in Figma
This is where designers usually struggle. Feedback is scattered across Figma comments, Slack, email, and phone calls.
Establish a rule: "All feedback must be documented in Figma comments."
If a client calls you with feedback, take notes and ask them to also comment in Figma. This keeps everything in one place.
In Figma, use threads. Client feedback becomes a thread.
Your response becomes a thread. It stays associated with the specific design frame.
At the end of a revision round, export the threads (or screenshot them) and keep them in Drive as documentation. This protects you if there's disagreement later about what was requested.
Tracking Changes Across Tools
You need to bridge Figma (where the work is) and Asana (where the timeline is).
Create a simple system:
In Asana, for each project, have subtasks for:
- Design phase - feedback round 1
- Design phase - feedback round 2
- Final revisions
- Deliverable handoff
As you move through Figma feedback, you move these tasks through Asana. This gives you a visible timeline and helps you track how many revision rounds you're in.
When a client is giving feedback, they can see in Asana: "We're in revision round 2 of 3 planned revisions." This sets expectations.
The Version Control Problem
Figma versions are automatic, but they're not always clear. You need a version system that's visible to clients.
Create a naming convention:
- V1 - Initial design
- V1.1 - Round 1 revisions
- V1.2 - Round 1 revisions (second batch)
- V2 - Major direction change
- V2.1 - Round 2 revisions
Use pages or frames in Figma to separate versions. Keep old versions visible so client can reference them.
This prevents the confusion of "which version had the red design?" or "I liked something from an earlier version, can we incorporate it?"
Managing Multiple Client Feedback
When you have multiple clients, you need to juggle different Figma files simultaneously.
Create one master Asana project called "Designs - All Clients" with sections for each client. Within each section:
- Active projects (in progress)
- Awaiting feedback (waiting on client)
- Final review (ready for approval)
- Delivered (complete)
This one view shows you what's happening across all clients. You can instantly see: three projects waiting on client feedback, two in active revision, one ready to deliver.
Without this, you'll lose track of which client is where in their timeline.
Invoicing and Delivery
Once work is approved, you need to deliver and invoice.
Create a checklist for final handoff:
- Client approval received (email or Figma)
- Final files exported from Figma
- Files organized in Drive per contract
- Client sent a link/access to deliverables
- Invoice created and sent
- Mark project complete in Asana
This prevents the scenario where you delivered files but forgot to invoice, or you invoiced but client never got the files.
Using a Dashboard for All Your Work
With projects scattered across Asana, Figma, and Drive, you need a unified view of what you're actually working on.
Create a simple dashboard (could be a Notion page, a spreadsheet, or a task aggregator) that shows:
- All active projects
- Current phase (design, feedback round 1, revisions, final review, delivered)
- When feedback is expected
- When next deliverable is due
Check this each morning. You'll instantly know what needs attention today.
If you use a tool like Huddle, it can aggregate your projects from Asana across all your clients into one view.
Handling Scope Creep
Scope creep is where freelance designers get burned. A client starts asking for "just one more thing" and suddenly you're delivering twice what you quoted.
Protect yourself:
In Asana, define what's included in the project upfront. "3 design concepts, 2 revision rounds, final delivered files."
When scope changes, create a change order. "Additional round of revisions = $X." Update Asana and update the invoice.
This might feel awkward, but it prevents the scenario where you've spent 30 hours on a project you quoted at 15.
The Tools You Actually Need
- Figma - Your design tool and feedback medium
- Asana (or Notion, or Airtable) - Project tracking and timeline
- Google Drive - File storage and deliverables
- Email or Calendly - Scheduling and approval
- Invoice tool (Wave, FreshBooks, etc.) - Billing
That's it. You don't need additional tools. You need to structure these five so they work together.
FAQ
Should I present work via Figma or upload static images?
Figma, definitely. Client can zoom, explore, leave comments in context. It's cleaner than static images.
How many revision rounds should I include?
Usually 2. Some clients try to get unlimited revisions. Define it upfront and charge for additional rounds.
What if a client doesn't want to use Figma?
Offer alternatives. Some clients want Dropbox links with image files.
Some want PDF exports. But try to get them in Figma if possible - it's better for feedback.
How do I prevent clients from requesting changes after final approval?
Get written approval. Email confirmation or explicit "Approved" comment in Figma. Then: "Changes after approval are outside the original scope and require a change order."
Should I track time on design projects?
Only if you bill hourly. For project-based work, time tracking doesn't matter for invoicing, but it's useful for understanding your own productivity.
What if a client wants to make changes to delivered files later?
That's a support/maintenance conversation. Usually billed separately.
Set expectations upfront about what's included in the project vs. what's support.
How do I organize Drive when I have dozens of clients?
Create a folder per client. Inside, create subfolders: Active Projects, Completed Projects, Assets, Invoices. This scales to unlimited clients.