ClickUp’s problem is not that it lacks features. It is that it ships with almost all of them switched on, and a small team that starts clicking around ends up with a workspace nobody wants to open by week three.
This guide sets up ClickUp in the order that avoids rework. The sequence matters: hierarchy first, then a single view, then automation, then everything else. Teams that do it in the other order spend their second month undoing their first.
Budget about ninety minutes for the core setup, then a week of running real work through it before you add anything else.
Before You Touch the App
Answer two questions on paper first.
What is a “task” for your team? A client deliverable? A single sub-step? A whole project? Teams that never agree on this end up with some people logging two tasks a month and others logging twenty a day, and no report means anything.
A workable default: a task is a unit of work one person can finish and hand off. Bigger than that is a List. Smaller than that is a checklist item inside a task.
What question do you want the tool to answer? Usually it is one of: what is everyone working on this week, what is blocked, or what is late. Pick the primary one. It determines which view you build first.
Step 1: Set Up the Hierarchy
ClickUp nests: Workspace → Space → Folder → List → Task. Small teams routinely use all five levels and drown.
Use three. One Workspace. A Space per major function. A List per project or client. Skip Folders entirely until you have enough Lists that you cannot see them all at once.
For a ten-person agency, that looks like:
- Space: Client Work — one List per active client
- Space: Internal — Lists for Marketing, Hiring, Admin
- Space: Sales — one List for the pipeline
Create Spaces from the left sidebar. When ClickUp offers to add templates and ClickApps during creation, decline all of them. You can enable specific ones later when you have a reason.
Step 2: Cut the Statuses Down
ClickUp’s default status set is longer than most small teams need, and every extra status is a decision someone has to make on every task.
Start with four: To Do, In Progress, Blocked, Done.
“Blocked” earns its place because it is the only status that prompts someone to act. If work is stuck, you want it visible without a meeting.
Set statuses per Space rather than per List, so reporting works across projects. Space settings → Statuses. If your client work genuinely needs a review step, add one status — not four.
Step 3: Add Only the Custom Fields You Will Filter On
This is the step where workspaces get ruined. The test for any custom field: will I filter, sort or group by this? If not, it belongs in the task description.
For most small teams, three fields cover it:
- Priority — use ClickUp’s built-in priority flag rather than a custom field
- Due date — built in
- Assignee — built in
That is often the whole list. Add a Client dropdown if you run multiple clients in one List, or an Effort field if you do capacity planning. Stop there.
Step 4: Build One View That Answers Your Question
Go back to the question from the start. Build the one view that answers it, and make it the default.
“What is everyone working on this week?” Create a List view, group by Assignee, filter to due date within the next 7 days and status not Done.
“What is blocked?” List view, filter status is Blocked, sort by date updated ascending so the stalest sits at the top.
“What is late?” List view, filter due date is before today and status is not Done, group by Assignee.
Save it as a Space-level view so everyone sees the same thing. Do not build six views on day one. Build one, use it for a week, then add a second if you genuinely miss something.
Step 5: Set Up Two Automations
ClickUp’s automation builder can do a great deal. Two rules cover most of the value for a small team.
Rule one: when status changes to Blocked, post a comment mentioning the List owner. This turns a status into a notification without anyone chasing.
Rule two: when a due date passes and status is not Done, change priority to High. Late work surfaces itself.
Both are built from Automations in the top-right of a List or Space. Set them at Space level so they apply everywhere.
Resist adding more until these two have run for a fortnight. Automations that fire unexpectedly are the fastest way to lose team trust in a tool.
Step 6: Connect Only What You Use Daily
Integrations are worth adding when they remove a step, not when they look useful.
The two that usually pay off: Slack or Teams, so task notifications land where people already are, and your calendar, so due dates show up alongside meetings. ClickUp documents native integrations for both.
Email-to-task is worth enabling if client requests arrive by email. Everything else can wait.
Step 7: Onboard the Team in Fifteen Minutes
Do this live, once, with everyone. Cover four things:
- Where their work lives (the default view you built)
- What a task is (the definition you agreed)
- The four statuses and when to use Blocked
- That they should not create new Spaces or statuses without asking
That last point prevents most of the sprawl. One person owns the structure for the first month.
Common Mistakes to Avoid
- Using all five hierarchy levels immediately. Depth makes things hard to find. Add Folders only when the List count genuinely demands it.
- Importing your entire backlog on day one. Bring in active work only. A workspace opening onto 400 stale tasks teaches people to ignore it.
- Creating custom fields you never filter on. Each one is friction on every task, forever.
- Letting everyone create statuses. Cross-project reporting breaks the moment statuses diverge.
- Turning on every ClickApp. Time tracking, sprints, points and dependencies are all useful eventually. On day one they are noise.
- Skipping the “what is a task” conversation. Without it your data is inconsistent from the first week and no report is trustworthy.
- Building views nobody asked for. One good default view beats eight competing ones.
FAQs
How long does it take to set up ClickUp for a small team?
About ninety minutes for the structure described here, then roughly a week of real use before you should change anything. Teams that spend a full day configuring upfront usually rebuild it later anyway.
Should we use Folders?
Not initially. Folders help when you have more Lists than fit on one screen. Below that they add a click without adding clarity.
How many statuses should we have?
Four is a good starting point: To Do, In Progress, Blocked, Done. Add a fifth only when you can name the decision it helps someone make.
Is the free plan enough for a small team?
It depends which features you need — ClickUp’s plan limits change periodically, so check the current pricing page rather than relying on any figure quoted elsewhere. The structure in this guide works on any tier.
How do we stop the workspace getting messy?
One person owns structural changes for the first month. Anyone can create tasks; only the owner creates Spaces, statuses and custom fields. Revisit after 30 days.
Can we migrate from Trello or Asana?
ClickUp documents importers for both. Import active work only, not archived boards. Expect to rebuild views and automations by hand — those do not carry across cleanly.
Key Takeaways
- Set up hierarchy first, then one view, then two automations. Order prevents rework.
- Three hierarchy levels, four statuses, three custom fields is enough for most small teams.
- Agree what counts as a task before anyone creates one.
- Import active work only.
- Give one person ownership of the structure for the first month.
Next Steps
Run real work through this for two weeks before changing anything. The instinct to add fields and views is strongest in week one and almost always wrong.
If you are still deciding between tools, our ClickUp vs Notion comparison covers where each one fits, and the best ClickUp alternatives is worth reading if the feature depth here sounds like more than you want to manage.