Skip to main content

DEPRECATED: This SOP has been superseded by SC Task Management Workspace Setup SOP, which is the single canonical reference for configuring the full SC ClickUp workspace (workspace-level config, Client Delivery space, SC Operations space, status template sc-status-01, and a migration appendix for moving to a different task-management system). All content below is retained for historical context only; do not act on it.

ClickUp SC Operations Space Setup SOP

1. Purpose & Scope​

This SOP defines the setup and configuration of the SC Operations ClickUp space for Symphony Core internal work that is not client-deliverable.

In scope:

  • Agency platform configuration (GHL sub-account setup, pipeline creation, automation builds)
  • Internal tools and infrastructure work tracked outside GitHub Issues
  • Documentation projects requiring task coordination
  • Sales prospecting and pipeline tasks tracked outside GHL

Out of scope:

  • Client deliverables -- use the Client_Delivery space
  • General business operations (invoicing, scheduling) -- those are handled in Google Workspace
  • Software development tasks -- use GitHub Issues in the relevant repository

This space complements (not replaces) the Client_Delivery space. The two spaces share the same status model and list pattern for consistency, but use different custom fields appropriate to their domains.


2. Prerequisites​

  • ClickUp workspace admin access
  • Familiarity with the SC Task Data Standard
  • Context: The ClickUp Scope Reduction PRD reduced ClickUp to a single Client_Delivery space. This SOP re-introduces a second space narrowly scoped to SC internal operations.

3. Space Configuration​

3.1 Create the Space​

  1. Open ClickUp workspace sidebar
  2. Click + Create Space
  3. Name: SC Operations
  4. Visibility: Private (team members added individually)

3.2 Status Sets​

Statuses are defined canonically in SC Task Data Standard §1. ClickUp list configuration mirrors that model. Status names are lowercase to match the live workspace convention.

active-work list:

StatusColorType
to doGrayOpen
in progressBlueOpen
blockedRedOpen
completeGreenClosed

completed list:

StatusColorType
completeGreenClosed

archive list:

StatusColorType
archivedGrayClosed
cancelledRedClosed

reference list:

StatusColorType
activeGreenOpen
outdatedGrayClosed

There is no review status. Validation is self-attested at complete via the Evidence bullet on acceptance criteria; client-facing deliverables additionally use an AM-review subtask (see Markdown Task File to ClickUp SOP §3c). Post-hoc sampling by the Account Manager (see SC Contractor Task Quality Review Standard §Post-hoc sampling) is the accountability mechanism.

3.3 Custom Fields (Space-Level)​

Create these fields at the space level so they are available on all lists.

FieldTypeOptions / Notes
Work DomainDropdownAgency Platform, Internal Tools, Documentation, Infrastructure, Sales
Sub-AccountShort TextGHL location ID when applicable; leave blank for non-GHL work

Fields intentionally excluded (these belong to Client_Delivery only):

  • Client
  • Delivery Role
  • Billable

3.4 Default Views​

Create these views at the space level:

ViewTypeGroup ByFilter
All Active WorkBoardStatusStatus not in (complete)
By DomainBoardWork DomainStatus not in (cancelled, archived)
My TasksListDue DateAssignee = Me

4. Folder & List Setup​

4.1 Initial Structure​

SC Operations (Space)
|-- Agency Platform (Folder)
| |-- active-work (List)
| +-- completed (List)
|-- Sales (Folder)
| |-- active-work (List)
| +-- completed (List)
|-- [additional folders created as needed]
|-- archive (List, folderless)
+-- reference (List, folderless)

4.2 Create the Agency Platform Folder​

  1. Inside SC Operations, click + New Folder
  2. Name: Agency Platform
  3. Create two lists inside the folder:
    • active-work -- uses active-work status set
    • completed -- uses completed status set

4.3 Create Folderless Lists​

These sit at the space root (not inside any folder):

  1. archive -- uses archive status set. Receives tasks that are done and no longer need visibility.
  2. reference -- uses reference status set. Holds standing reference items (e.g., recurring checklists, environment notes).

4.4 Adding Future Folders​

When a new work domain requires its own task tracking:

  1. Create a new folder named after the domain (e.g., Internal Tools)
  2. Add active-work and completed lists inside it
  3. Use the same status sets defined in Section 3.2
  4. No changes needed to archive or reference -- they are shared across all domains

5. Task Standards​

5.1 Naming Convention​

Use the pattern: [verb]-[component]-[item]

Examples:

  • configure-agency-prospecting-pipeline
  • migrate-dns-records-to-cloudflare
  • document-email-forwarding-setup

5.2 Description Format​

All tasks should follow the SC Operations Task Template. The template defines:

  • Business Context (why this matters)
  • Scope (verifiable deliverables)
  • Reference Documents (links to SOPs/guides)
  • Notes (constraints, dependencies)

5.3 Required Fields​

Every task must have:

  • Title (following naming convention)
  • Work Domain (dropdown)
  • Priority
  • Assignee — exactly one. See Markdown Task File to ClickUp SOP §3d for the single-assignee rule that applies to all spaces. Workspace-level enforcement (target): disable the "Multiple Assignees" ClickApp.
  • Description (following template structure)

Sub-Account is required only when the task involves a specific GHL location.


6. Permissions​

RoleAccess Level
AdminFull access to all lists, settings, and automations
Team MemberCreate and edit own tasks in active-work and completed lists
ContractorCreate and edit own tasks in active-work and completed lists
Archive accessRead-only for non-admins
Reference accessRead-only for non-admins

7. Maintenance​

Weekly Quality Sampling​

Every Monday, the Account Manager samples a slice of the previous week's closed tickets per SC Contractor Task Quality Review Standard §Post-hoc sampling. Defects get the qa:work-missed tag and either reopen or open a linked follow-up per the AM's judgment.

Monthly Archive Cycle​

On the first business day of each month:

  1. Move all tasks in complete status older than 30 days from completed lists to the archive list
  2. Review blocked tasks -- resolve or cancel if stale
  3. Verify Work Domain dropdown values are still relevant

Quarterly Folder Review​

Every quarter, review folder structure:

  • Are there domains with enough tasks to warrant a new folder?
  • Are any folders empty or unused? Remove if so.
  • Update this SOP if the folder structure changes.

8. Reference Documents​