ClickUp Client Folder Structure

Overview

The core structural principle for ClickUp is organizing all client work inside permanent Client Folders rather than temporary Sprint Folders. Sprints remain in use, but they become a view of work that originates in client folders — not the primary home for tasks.

This pattern was validated and adopted during the ^[1] with Mark Hope, Melissa Cusumano, and Isalia Ramirez.

The Problem with Sprint-First Organization

When tasks live primarily in Sprint Folders:

• A client's complete work history is scattered across dozens of sprint folders
• Finding past work requires searching by client name across unrelated folders
• There is no single place to store client reference material (brand guides, briefs, past deliverables)
• Closing a sprint effectively buries completed work

The Client Folder Model

Structure

Each active client gets a permanent top-level folder inside the Client Delivery space. Within that folder, lists are created based on the services being delivered for that client. Typical lists include:

• Account Management
• SEO
• Content Production (blogs, social)
• Ad Campaigns (Google, Meta)
• Web / Landing Pages
• Design / CRO

When a new service is added for a client, a new list is added to their folder. Nothing is deleted when a sprint ends — the folder grows as the client relationship grows.

What Lives in a Client Folder

Note: Contact information, points of contact, and CRM data for clients should remain in HubSpot, not ClickUp. See ^[2].

Automated Sprint Integration

Sprints are not eliminated — they are automated.

How it works:

1. Account Managers assign start dates and due dates to tasks inside Client Folders
2. When a task's start date falls within the current sprint window, it is automatically pulled into the Sprint view
3. No manual drag-and-drop between folders is required

This means the Sprint space becomes a real-time, auto-populated view of what is actively in flight across all clients — without anyone having to manage it manually.

Key implication: AMs do their planning work inside Client Folders. The Sprint space is a read-only operational view for the team.

Backlog Management

There is no separate company-wide backlog folder. Instead:

• Each Client Folder serves as its own backlog
• Tasks without start dates sit in the client folder until an AM schedules them
• When scheduled (start date assigned), they surface in the sprint automatically

Connecting SOPs and Templates

Every recurring service type should have two linked artifacts:

• SOP — the "how-to" guide explaining technique, quality standards, and tools
• Task Template — the "what-to-do" checklist with subtasks, linked back to the SOP

When an AM creates a new task for a recurring service (e.g., foundational SEO, landing page build), they apply the relevant template. The template includes:

1. A brief section at the top (filled out by the AM before work begins)
2. Subtasks covering all required steps
3. A link to the corresponding SOP

See ^[3] for the brief format and kickoff process.

Priority: Build SOPs and templates for the top 10 most frequently delivered services first (e.g., landing pages, blog posts, foundational SEO, Google Ads setup). Melissa Cusumano is responsible for finalizing this list.

Client Permissions

Clients who need access to their ClickUp folder (e.g., to comment on tasks or move items through statuses) must not be added as standard Members. Member-level access grants visibility and edit rights across the entire ClickUp account.

The correct approach is a custom restricted permission set that:

• Limits visibility to the client's own folder only
• Allows commenting and status changes
• Prevents access to other client folders, internal spaces, or HR/financial data

The ClickUp team confirmed this is achievable for an additional cost. A proposal for this permission set has been requested.

⚠️ Urgent: As of the blueprint review meeting, at least one client (Mike Stebbins) had full Member access. This should be resolved before the new structure is deployed.

See ^[4] for the full security context and resolution status.

Related

• ^[2]
• ^[3]
• ^[4]
• ^[5]