Asana is the right project management tool for fitness businesses that need structure but do not want ClickUp's complexity. The challenge is most owners set it up in a way the VA cannot use. Boards rot, tasks pile up, and within 60 days nobody touches it.
This setup is what a Fitness VA can deploy in 30 minutes and run for 12 months without rebuilding. Four core projects, simple structure, working automations.
For where Asana fits in the broader VA scope, our Fitness VA tasks list covers the responsibility split.
The four core projects
Build only these four. Resist adding a fifth in week one.
- Weekly Ops Board. The VA's daily and weekly worklist.
- Content Calendar. Editorial planning, status, and publish dates.
- Hire Pipeline. Applicant tracking and onboarding (used episodically).
- Renewal Tracker. Software contracts, equipment warranties, important dates.
Each project gets its own template structure. Adding others (member onboarding, etc.) only after these four are running smoothly for 30 days.
Project 1: Weekly Ops Board
Structure:
- Sections: Today, This Week, Waiting On, Done.
- Custom fields: Priority (High/Medium/Low), Owner, Due Date.
- Recurring tasks: Monday weekly KPI report, Friday weekly wrap, daily lead reply check.
Workflow:
- VA pulls from "This Week" into "Today" each morning.
- Tasks blocking on someone else go to "Waiting On" with a note.
- Done tasks move to "Done" but stay visible for 7 days then auto-archive.
This single project handles 80 percent of the VA's work.
Project 2: Content Calendar
Structure:
- Views: Calendar, List, Status board.
- Sections by status: Idea, Drafting, Scheduled, Published.
- Custom fields: Channel, Topic Cluster, Owner, Publish Date.
- Recurring task: Monday content planning block (90 minutes).
Each piece of content moves through the four sections. Calendar view shows the publishing month at a glance.
For pieces with longer production cycles (long-form blog, podcast episodes), add subtasks for outline, draft, edit, publish, promote.
Project 3: Hire Pipeline
Used episodically. Structure:
- Sections: Applied, Screened, Interviewed, Offer, Onboarding, Hired.
- Custom fields: Role, Source, Owner, Status Notes.
- Tasks per candidate move through sections.
When a hire round is not active, the project sits dormant. Reuse the same project for each round; do not create new ones.
Project 4: Renewal Tracker
Structure:
- Sections by month (Jan through Dec).
- Custom fields: Vendor, Renewal Date, Auto-renew (Y/N), Cost, Owner.
- Tasks for each renewal placed in the appropriate month's section.
A single Asana view sorted by month catches every renewal. Pair with the Vendors base in Airtable for full vendor data.
Automation rules
Three high-leverage Asana automations:
- Auto-assign by section. Tasks dropped into "This Week" auto-assign to the VA. Tasks in "Drafting" auto-assign to the content owner.
- Due date reminders. 24 hours before due, send reminder via Slack integration.
- Recurring tasks. Weekly KPI report, monthly content planning, quarterly business review.
Skip complex automations on day one. Add them after 30 days when you know what is missing.
Permissions and access
For most setups:
- Founder: admin on all four projects.
- VA: editor on all four.
- Anyone else: commenter or viewer per scope.
Avoid adding clients or external parties to internal Asana workspaces. Use guest projects for external work.
Daily and weekly rituals
The VA operates Asana with two rituals:
- Morning. 5 minutes pulling from "This Week" to "Today," reviewing "Waiting On."
- Friday. 15 minutes archiving completed tasks, prepping next week's "This Week" section.
Without these rituals, Asana decays. A board nobody curates is just clutter.
Common Asana mistakes
Three patterns this setup guards against:
- Too many projects. Four is the right number; eight is unmanageable.
- No archive discipline. Done tasks stay forever and clutter views. Archive weekly.
- Bypassing Asana for "quick" Slack tasks. Anything taking more than 10 minutes belongs in Asana.
The third is the most insidious. Quick Slack-only tasks slip through the cracks and create the "I forgot" pattern.
Asana vs ClickUp vs Trello
- Asana. Best for fitness teams of 1 to 5 with moderate workflow needs. The default for solo coaches and small studios.
- ClickUp. Better when you need hierarchy and database fields. Steeper learning curve.
- Trello. Lighter weight, better for kanban-only workflows. Less structured.
- Monday.com. Visual-first alternative for non-technical teams.
Most fitness VAs end up on Asana because the structure is enforced enough to scale and light enough to stay used.
Pricing and tier
- Free tier supports up to 15 users. Most fitness teams fit.
- Premium ($10/month per user) unlocks timeline view, advanced search, custom rules. Worth it once you cross 3 active users.
- Business tier rarely needed for fitness; reserve for multi-location operations with complex reporting needs.
When to migrate off Asana
Two signals:
- You cross 8 active projects and reporting becomes painful.
- You need cross-project automation that Asana does not support natively.
Migration is non-trivial. Plan a 30-day overlap and a clean export of historical tasks.
For pricing on a VA running Asana, see our Fitness VA cost guide. For the broader hire, our hiring playbook covers the candidate fit.
Frequently asked questions
How long for a VA to learn Asana?
Three to five days for productive use. Two to three weeks for confident automation building.
Can I use Asana for member CRM?
No, not well. Use Airtable or a dedicated CRM. Asana is for project management, not relationship management.
What is the biggest setup mistake?
Building too many projects. Stick to four for the first 30 days; expand only if there is a real gap.
Should the VA build the templates or should I?
You build initially with the VA shadowing. After 30 days, the VA owns template iteration with founder review.
Does Asana integrate with MindBody/ABC?
Not natively. Use Zapier or webhooks. Most fitness teams keep MindBody/ABC for member ops and Asana for project work without trying to integrate them deeply.