SC Task Management Workspace Setup SOP
1. Purpose & Scope
Single rebuild-from-scratch reference for the Symphony Core task-management workspace. Anyone with workspace-admin access should be able to follow this SOP top-to-bottom and reach a fully-configured workspace that matches the canonical SC operating model.
In scope:
- Workspace-level configuration (ClickApps, tags, members, integrations)
- Status template
sc-status-01— the canonical status set used by every list - Client Delivery space — per-client folder + list pattern
- SC Operations space — internal work
- Smoke-test sequence to verify the setup
- Tool-portability appendix — what to preserve when migrating off ClickUp
Out of scope:
- Per-client list customizations (handled by the client onboarding flow, not workspace setup)
- GHL pipelines (a different system; see
05-platform/platforms-config/) - Workflow-level automation builds (separate PRDs)
- Sales prospecting space (its own configuration, not covered here)
This SOP is the implementation of the SC Task Data Standard. The standard is tool-agnostic; this SOP shows how the abstract model lands in ClickUp specifically.
2. Data Model (abstract — tool-agnostic)
The SC ClickUp workspace is organized as a hierarchy:
Client Delivery uses per-client folders; SC Operations uses flat folderless lists — the two spaces deliberately have different structures because their work patterns differ. See §5 and §6.
The canonical task data model is defined in SC Task Data Standard:
- Statuses — §1 of the standard. Five states:
TODO,IN PROGRESS,BLOCKED,COMPLETE,CANCELLED. - Fields — §2 of the standard. Task ID, Title, Description, Status, Assignee, Creator, Start Date, Due Date, Completion Date, Priority, Tags, Relationships, Estimate, Time Tracked.
- Relationships — §3 of the standard. Parent/Subtask, Blocked By/Blocking, Follows/Precedes, Duplicate Of/Original, Related To.
- Transitions — §4 of the standard.
Every implementation in any tool must satisfy that model. The rest of this SOP describes how ClickUp is configured to do so.
3. Status Template — sc-status-01
sc-status-01 is the named ClickUp status template applied to every list in the Client Delivery and SC Operations spaces. It is the single source of truth for status configuration in the workspace.
3.1 Template content
| Status | ClickUp group | Visibility behavior | Maps to abstract |
|---|---|---|---|
to do | Not started | Visible | TODO |
in progress | Active | Visible | IN PROGRESS |
blocked | Active | Visible | BLOCKED |
cancelled | Done | Visible (intentional — AM can spot abandoned work during sampling) | CANCELLED |
complete | Closed | Auto-hidden from default views (terminal, no longer needs attention) | COMPLETE |
The complete → terminal transition uses the Closed group to auto-hide from default views; cancelled stays visible because abandoned work is a signal worth noticing during AM sampling.
3.2 ClickUp-specific notes
- One-status-in-Closed limitation. ClickUp restricts the Closed group to exactly one status. The two terminal states (
completeandcancelled) are therefore split:completein Closed (auto-hide),cancelledin Done (stays visible). This is a tool constraint, not a model deficiency. - Lowercase names. All status names are stored lowercase. ClickUp's UI displays them in uppercase, but the API and filters use the lowercase form. Documents should use lowercase to match.
- No
reviewstatus. Validation happens via the Evidence bullet on acceptance criteria atcomplete, plus a QA-Review subtask for client-facing deliverables (see Markdown Task File to ClickUp SOP §3c). Post-hoc sampling by the AM (per SC Contractor Task Quality Review Standard) is the accountability mechanism.
3.3 Applying the template
- Workspace Settings → Status templates →
sc-status-01— create if absent. - Configure the five statuses per §3.1 above. Order top-down: TO DO → IN PROGRESS → BLOCKED → CANCELLED → COMPLETE.
- Save the template.
- In each space (Client Delivery, SC Operations), set the space-level template to
sc-status-01. - For any list that has list-level status overrides (custom statuses), open its status settings and choose Use space template so it inherits.
4. Workspace-level configuration
4.0 Subscription & seats
The SC workspace runs on ClickUp Business plan, billed yearly (verified 2026-05-18). Several features documented in this SOP depend on the plan tier:
| Feature | Required plan | Why SC uses it |
|---|---|---|
| Timesheet Approvals (submit / approve / lock workflow) | Business or higher | Vendor-team weekly billing flow per ClickUp Timesheet Approval SOP. Fallback for downgrade scenarios documented in §8 of that SOP. |
| Custom fields | Business or higher | Per-space fields per §5.3, §6.3. Required for Client routing and Sub-Account tracking. |
| Workload view | Business or higher | The capacity-next-7d view recipe in Views Guide §6.6. |
| Status templates | All plans | sc-status-01 per §3. |
| Guest seats (10 free per paid Member seat) | All plans (with limits) | Vendor team developers; see Project Partner Team Onboarding SOP §5. |
Seat-cost math. Member seats consume the paid count; Guest seats are free up to 10 per Member. If SC has N Member seats, the workspace can host up to 10N Guests at no incremental cost. Cross this threshold and Guest seats start consuming paid headroom.
Plan downgrade is not a routine ops move. Downgrading from Business loses Timesheet Approvals and Custom Fields — both load-bearing for the vendor flow and the routing logic. If a downgrade is being evaluated for cost reasons, first audit which workflows depend on those features.
Plan-tier verification. Settings → Billing — should show "Business" or higher. Run this check at workspace setup, after any billing event, and as the first step in §10 disaster-recovery procedures.
For who can edit billing: see ClickUp Permissions Matrix §3 Workspace level — Owner-only.
4.1 ClickApps
| ClickApp | State | Why |
|---|---|---|
| Multiple Assignees | Disabled | Single-assignee-per-ticket is canonical (see working-rules.md#single-assignee-per-ticket and Markdown Task File to ClickUp SOP §3d). Disabling at workspace level mechanically prevents reintroducing multi-assignment. |
| Progress icons | Enabled | Visual cue for status group; supports linear workflow visualization. |
| Time Tracking | Enabled | Used for the timesheet approval flow (see ClickUp Timesheet Approval SOP). |
| Tags | Enabled | Required for the SC ClickUp Tag Taxonomy. |
| Custom Fields | Enabled | Required for per-space fields (§5.3, §6.3). |
4.2 Tags
Provision the full canonical tag set at each space level before any tickets are created. The complete taxonomy lives in SC ClickUp Tag Taxonomy. Categories:
client/<slug>— one tag per active client in09-clients/. When to apply (required on SC Operations + Client Delivery shared lists; optional on per-client lists where theClientcustom field in §5.3 is the canonical identifier) is defined in SC ClickUp Tag Taxonomy §Client identity.domain:wordpress,domain:seo,domain:dns,domain:billing,domain:ghl,domain:designqa:work-failed-review,qa:work-missed,qa:work-partialblocked-on:client,blocked-on:vendor,blocked-on:hosting-support
Tags are space-scoped in ClickUp — provision them in both Client Delivery and SC Operations spaces.
4.3 Members & roles
| Role | Scope | Who |
|---|---|---|
| Owner | Full workspace | Symphony Core principals |
| Admin | Full workspace | Account Managers |
| Member | Spaces granted explicitly | Internal SC team |
| Guest | Single Folder, scoped permissions | External project partners — see Project Partner Team Onboarding SOP |
Capability detail for each tier — workspace / space / folder / list / task / time-tracking levels — lives in ClickUp Permissions Matrix. User-lifecycle procedures (add / revoke / promote / demote) live in §9 below.
4.4 Integrations
| Integration | State | Notes |
|---|---|---|
| GitHub | Enabled | Used for linking PRs to tickets |
| Slack | Enabled | Used for @AM ready for review notifications |
5. Client Delivery space
5.1 Purpose
Tracks all work delivered to clients. Every active client has exactly one folder under this space.
5.2 Structure
Client Delivery (Space)
├── <client-slug>/ (Folder, one per active client)
│ ├── active-work (List)
│ └── reference (List)
├── client-delivery-operations (List, folderless) — cross-client AM coordination
└── reference (List, folderless) — standing reference items
- active-work — every ticket for this client, in every status (
to do,in progress,blocked,complete,cancelled). Thecompletestatus sits in the Closed group (see §3.1), so default views auto-hide it; opt-in views (see §5.5) surface completed work when needed. - reference — per-client standing reference items (canonical links, evergreen specs, etc.). Not work in flight; never appears in "open work" views.
Note on retired lists. The completed-work and archive lists were retired in v1.2 of this SOP. Rationale: the Closed-group hide on complete already keeps finished work out of default views (no separate list needed), and per-folder lists with identical names (completed-work, archive) made cross-folder views impossible to build with list-name filters. Cold storage is now handled by ClickUp's native task archive (right-click → archive) via a monthly UI sweep — see §5.6. See the changelog (§10) for the full rationale.
5.3 Custom fields (space-level)
| Field | Type | Notes |
|---|---|---|
| Client | Reference / Dropdown | The client served by this task. Required on every Client Delivery ticket. Populated per markdown-task-file-to-clickup-sop.md §3. See also the tag–field correspondence rule in SC ClickUp Tag Taxonomy §Client identity — the Client field value and the client/<slug> tag (when present) must match. |
| Delivery Role | Dropdown | AM / Specialist / Project Partner / Other |
| Billable | Checkbox | Toggles whether time logged is invoiced to the client |
| Assignee | Built-in | Exactly one, per working-rules.md#single-assignee-per-ticket |
Field scope across the two spaces:
The Client custom field exists only in Client Delivery — SC Operations uses the client/<slug> tag as its sole client identifier (no field). On any task where both are populated, they must match (no drift). The detail rule lives in SC ClickUp Tag Taxonomy §Client identity.
5.4 Status template
sc-status-01 (see §3). All lists in this space inherit from the space template — no list-level overrides.
5.5 Default views
All views are status-based — no list-name filters. List-name filters are an anti-pattern in this workspace because per-folder list names previously collided (e.g., the retired completed-work and archive lists shared their names across every client folder).
| View | Scope | Type | Group by | Filter |
|---|---|---|---|---|
| All Open Work | Workspace (Client Delivery space) | Board | Client | Status not in (complete, cancelled) |
| Recently Completed (30d) | Workspace (Client Delivery space) | List | Client | Status = complete AND date_done > today − 30d |
| By Client | Workspace (Client Delivery space) | Board | Client | Status not in (complete, cancelled) |
| My Tasks | Workspace | List | Due Date | Assignee = Me |
| Per-folder Completed (this month) | Folder-scoped | List | Status | Status = complete, sorted by date_done desc |
Full filter expressions and naming conventions are documented in ClickUp Views and Filters Guide §6.7–§6.9. The guide is the source of truth for view recipes; this section lists the standard set that should exist after setup.
5.6 Cold storage: monthly native-archive sweep
No automation here. Earlier versions of this SOP referred to an auto-move rule (complete → completed-work); on inspection during the 2026-06-08 migration, no such automation existed — ClickUp does not support workspace-scoped automations, and no equivalent space- / folder- / list-level rule was found in the configuration. The behavior was always manual. With v1.2's retirement of the completed-work and archive lists, the architecture is now explicitly declarative: status filters + ClickUp's native task archive, no automation surface.
Hot to cold pipeline:
- Active state (any duration): ticket lives in
active-work. Status drives visibility —completeis in the Closed group (§3.1), so it auto-hides from default views. - Recently completed (under ~30 days): still in
active-workwith statuscompleteorcancelled. Surfaced by the "Recently Completed (30d)" view in §5.5 when the AM or contractor needs to look back. - Cold storage (older than ~30 days): Account Manager moves the task to ClickUp's native task archive (right-click → Archive Task, or bulk-select in the Recently Completed view and use the bulk action). Native archive hides the task from all default and opt-in views but keeps it recoverable from the list's "Show archived" toggle.
Monthly UI sweep: on the first business day of each month, the Account Manager opens the "Recently Completed (30d)" view, sorts by date_done ascending, bulk-selects tasks older than 30 days, and runs the native-archive action. Estimated 5 minutes/month at current task volume. This sweep is tracked under the pending workspace-cleanup ticket (see 10-people-operations/backlog.md if logged there; otherwise the recurring AM-ops task).
Per rules-first-automation: any future proposal to automate this sweep would need (a) a rule documented here naming the trigger condition (e.g., "tasks with complete status older than N days are auto-archived") and (b) a separate PRD per automation-requires-prd. Until then, the sweep is manual.
6. SC Operations space
6.1 Purpose
Tracks SC-internal work that is not delivered to a client. Examples: agency platform configuration, internal tooling, sales prospecting, documentation projects.
6.2 Structure
SC Operations (Space, id 901313535576)
├── people-operations (List, id 901326049401) — contractor onboarding, payments, access, offboarding
├── sc-marketing (List, id 901327163043) — SC brand, website, social, marketing content
├── sc-sales (List, id 901326361161) — leads, prospects, pipeline work
├── platform (List, id 901326052561) — ClickUp, tooling, internal platform
├── client-delivery-operations (List, id 901327216662) — cross-client delivery work that isn't per-client
├── sc-admin (List, id 901327593867) — SC administrative and back-office work
├── archive (List, id 901326052522) — cold storage for retired SC-Ops items
└── reference (List, id 901326052523) — long-lived reference notes
Flat structure — no folders. Each list is its own work domain; the list name IS the domain label (no separate Work Domain dropdown needed). If a new domain emerges, add a new list (do not nest under a folder). Status filtering (sc-status-01's Closed-group auto-hide on complete) replaces per-list "completed" lists; cold storage uses ClickUp's native task archive (see §5.6 for the analogous Client Delivery sweep, applied identically here).
6.3 Custom fields (space-level)
| Field | Type | Notes |
|---|---|---|
| Sub-Account | Short Text | GHL location ID when applicable; blank for non-GHL work |
| Initiative | Short Text | Engineering initiative ID (ENG-NNN) from 11-engineering/portfolio/. Blank on ops, admin and procurement work — it binds engineering tasks only. Field id 3d5cc126-8814-48c8-9fd1-19ef2f451b25; also attached to the Operations space so Internal Docs Hosting can carry it |
| Work Domain | Dropdown | Agency Platform / Internal Tools / Documentation / Infrastructure. Predates the flat-list model and is largely unused; the list name is the primary domain signal |
| Assignee | Built-in | Exactly one |
Fields intentionally excluded (these belong to Client Delivery only): Client, Delivery Role, Billable.
6.4 Status template
sc-status-01 (see §3) — identical to Client Delivery.
6.5 Default views
| View | Type | Group by | Filter |
|---|---|---|---|
| All Active Work | Board | Status | Status not in (complete) |
| By List | Board | List | Status not in (cancelled, complete) |
| My Tasks | List | Due Date | Assignee = Me |
| Recently Completed (30d) | List | List | Status in (complete, cancelled), date_done within last 30 days |
6.6 People-operations list
People-ops tickets (under 10-people-operations/ — contractor onboarding, payments, access provisioning, registry maintenance, offboarding) default to the people-operations list (901326049401). See 10-people-operations/README.md §Task Tracking.
6.7 Per clickup-structure-sync
Any future addition/removal/rename of a list in SC Operations MUST ship paired with: (a) an update to §6.2 above, (b) a refresh of memory reference_sc_operations_clickup_lists.md, (c) closure of any tracking ticket. Do not let live state diverge from this diagram.
7. Smoke tests (post-setup verification)
Run after every setup pass — initial workspace creation, status-template edit, or list-pattern change. Each test takes under a minute.
- Create ticket — in any active-work list, create a new ticket. Confirm it lands in
to dostatus. - Status transitions — flip the ticket through
in progress→blocked→in progress→complete. Confirm each transition succeeds. The ticket stays inactive-work;completeis auto-hidden from default views by the Closed group (§3.1). - Completed-view surfacing — open the "Recently Completed (30d)" view (see §5.5). Confirm the just-completed test ticket appears.
- Cancellation path — create a second ticket, mark
cancelled. Confirm it stays inactive-workand is visible (Cancelled is intentionally not hidden — see §3.1). - Native-archive recovery — on the test ticket from step 2, right-click → Archive Task. Confirm it disappears from default views AND from the Recently Completed view. Toggle "Show archived" on the list, confirm it reappears. Un-archive.
- Single-assignee enforcement — try to add a second assignee. Confirm ClickUp blocks the action (Multiple Assignees ClickApp disabled).
- Tag application — apply one tag from each category (
client/<any>,domain:wordpress,qa:work-failed-review,blocked-on:client). Confirm no "tag does not exist" errors. - QA-Review subtask path — on a client-facing parent ticket, add a
qa-review-<parent-slug>subtask. Confirm subtask shows up with its own single assignee. (Legacyam-review-*form remains valid; see Markdown Task File to ClickUp SOP §3c.) - Cleanup — delete the test tickets.
If any test fails, revisit the relevant section before declaring the setup complete.
8. Migration to a different task-management system
If SC ever moves off ClickUp (to Linear, Asana, Jira, Notion, or a custom system), the following are portable and should be preserved:
| Layer | Source of truth | Tool-agnostic? |
|---|---|---|
| Data model (statuses, fields, transitions) | SC Task Data Standard | Yes — re-implement against the new tool's primitives |
| Tag taxonomy | SC ClickUp Tag Taxonomy | Yes — names and semantics carry over; rename file when moving |
| Single-assignee-per-ticket rule | working-rules.md#single-assignee-per-ticket | Yes — enforce via whatever mechanism the new tool offers |
| QA-Review subtask pattern | Markdown Task File to ClickUp SOP §3c | Yes — re-implement using the new tool's subtask/dependency primitive |
| Workspace → space → folder → list → task hierarchy | This SOP §5 / §6 | Mostly — most tools have an equivalent 3-or-4-level hierarchy; map by name |
sc-status-01 template name | This SOP §3 | Concept yes, name no — the new tool may not support named templates; configure each project/list directly |
| Native task archive (cold storage) | This SOP §5.6 | Concept yes — most tools have an "archive" or "soft-delete" verb that hides without losing data |
| ClickApps (Multiple Assignees, Progress icons) | This SOP §4.1 | No — ClickUp-specific. The intent (single assignee) carries; the mechanism differs |
The doc structure of this SOP intentionally separates abstract spec (§2–3.1, §5–6 list of fields and lists) from ClickUp-specific implementation (§3.3, §4.1, §5.6, §7). When migrating, the abstract sections inform the new tool's configuration; the ClickUp-specific sections become reference material.
9. User lifecycle (add / promote / demote / revoke)
Procedures for managing the workspace member roster. Capability detail per tier lives in ClickUp Permissions Matrix; this section is the how (the operational steps).
9.1 Adding a new Member
For SC internal team members who need cross-space visibility (FT + retained Members).
- Verify there's an available paid seat. Settings → Billing — confirm Member count < licensed seat count. If at cap, decide whether to (a) revoke an inactive Member (§9.3), (b) reassign work to a Guest (lower-cost option for single-folder use cases), or (c) request a seat bump from the Workspace Owner.
- Invite via email. Settings → Members → Invite → Member role. Use the person's
@symphonycore.comaddress for FT; personal address for retained contractors who don't have an SC mailbox (per Google Workspace Configuration Standard). - Grant space access. After they accept, grant access to both Client Delivery and SC Operations spaces (SC convention — see Permissions Matrix §2). For partial access (e.g., a Member who only works in one space), grant only the relevant space.
- Add to the relevant
#vendor-*Slack channel for async coordination. - Run smoke test #1 from §7 (create a ticket in any list they should see). Confirm they can read + create.
- Onboard them via ClickUp First Week Walkthrough.
9.2 Adding a new Guest (vendor team developer)
Follow Project Partner Team Onboarding SOP §5 — that SOP is the canonical source for the Guest-provisioning checklist (folder scope, Can track time permission toggle, dual-tracking trial period). The summary: scope to one folder, grant Can track time, never grant Space-level access.
9.3 Revoking access (departing team member / contractor)
Order matters. Revoke external surfaces first so the person can't act on the workspace mid-revocation.
- Reassign their open tickets to a delegate (per Role Handoff sub-section in Ways of Working §Roles). Don't reassign in the middle of a status flip; let the current state settle, then reassign.
- Capture their pending time entries. For Members on the timesheet flow, export approved entries via Timesheet Approval SOP §6. For unapproved entries, decide per case — approve-and-export OR reject-with-note.
- Revoke Slack + GitHub + Drive access (in that order). These surfaces touch ClickUp via integrations; revoking them first prevents drift during the ClickUp revocation.
- Remove from ClickUp. Settings → Members → that person → Remove. Their assigned tickets become unassigned (visible in views); their authored comments and time entries persist (audit trail).
- Reassign unassigned tickets immediately (next AM sweep or as part of this revocation if known).
- Update Contractor Registry entry — set
Engagement EndandStatusper 10-people-operations/contractor-registry.md.
9.4 Promoting / demoting
- Member → Admin: when a Member needs to manage spaces or status templates. Keep the active-Admin count ≤3 per Permissions Matrix §2. Settings → Members → that person → role dropdown → Admin.
- Admin → Member: when an Admin no longer needs the admin capability. Same path, opposite direction. Demoting is reversible; no tickets are lost.
- Member → Guest: when a Member's scope has narrowed to one folder. Cost saving (frees a paid seat). They lose cross-space visibility — confirm with them before demoting.
- Guest → Member: when a Guest's scope has widened to multiple clients. Consumes a paid seat.
- Any tier → Owner: succession-level change. Two-Owner steady state is fine if intentional (e.g., spouse / partner co-ownership). Adding a third Owner is rarely correct — Admins can do everything except billing.
9.5 Cadence
- Run a roster audit quarterly alongside the SC ClickUp Tag Taxonomy §Quarterly audit. For each Member and Guest, confirm: still active, role still right-sized, last activity within 90 days.
- For Guests on ended engagements: revoke promptly (within 1 week of engagement end). Lingering inactive Guests are a security smell.
10. Partial-loss disaster recovery
This section covers failure modes short of a full workspace wipe (§1 already covers rebuild-from-zero). For full restoration, this entire SOP top-to-bottom IS the recovery procedure.
10.1 Failure-mode catalog
| Failure | Symptom | Recovery path |
|---|---|---|
| Accidental list deletion | A list disappears from a folder; its tasks are gone from views | §10.2 — list recovery |
| Accidental task deletion | A specific task can't be opened by URL | §10.3 — task recovery |
| Accidental status-template change | All tickets in a space suddenly show wrong status names | §10.4 — status-template restoration |
| Accidental tag deletion | A tag is gone from the picker; existing tasks still carry it | §10.5 — tag re-creation |
| Custom-field schema drift | Field options disappeared OR a new option appeared without a PR | §10.6 — schema reconciliation |
| Workspace integration broken (GitHub / Slack) | PR auto-links not appearing OR Slack notifications silent | §10.7 — integration reauth |
| ClickUp service outage | Workspace inaccessible; all SC operational dependencies blocked | §10.8 — outage runbook |
10.2 List recovery
ClickUp's Trash retains deleted lists for 30 days. Workspace Settings → Trash → find the list → Restore. Tasks restore with their full state (status, assignees, comments, time entries). If the list was deleted more than 30 days ago: it's gone; rebuild from the canon in §5.2 / §6.2 and re-create any tasks from their markdown source files (per Markdown Task File to ClickUp SOP). Lost time entries: irrecoverable; reconstruct from the contractor's local notes if possible.
10.3 Task recovery
Same 30-day Trash window. Settings → Trash → search by task name → Restore. The task returns to its original list at its last state. Subtasks restore with the parent.
If the task URL still loads but shows "Archived," it's in the native task archive (not deleted) — toggle "Show archived" on the list to surface it (§7 smoke test #5).
10.4 Status-template restoration
If sc-status-01 was edited destructively (e.g., a status was renamed or deleted):
- Don't panic. Existing tickets keep their status data even if the template definition changed — they just display the new label.
- Settings → Status templates →
sc-status-01→ restore the 5 statuses per §3.1 exactly. - For each space using the template: confirm space-level template is still set to
sc-status-01(§3.3 step 4). If a list slipped to a list-level override, set it back to "Use space template." - Run smoke tests §7 #1–#4 to verify.
10.5 Tag re-creation
Tags are space-scoped. If a tag was removed from the space-level picker:
- Identify the missing tag from the canonical set in SC ClickUp Tag Taxonomy §Approved tags.
- Re-create at space level: Space settings → Tags → New → exact name + lowercase + correct namespace separator (
:or/). - Existing tasks that lost the tag: only recoverable if the tag was visible somewhere (markdown source, comment, audit log). Otherwise, accept the loss; re-tag manually only if telemetry depended on it.
If a tag was removed intentionally per the Tag removal procedure: leave it removed; this is not a recovery scenario.
10.6 Schema reconciliation
If a custom field's option list shows new values not in canon:
- Check the source — was the change committed via PR amending §5.3 or §6.3 above? If yes, this is canonical; update memory if it lags.
- If not — someone with Admin permissions made an ad-hoc change. Decide: (a) revert (Space settings → Custom fields → remove the orphan option), or (b) ratify (open a PR adding it to canon).
- Cross-reference
clickup-structure-sync— this rule prevents future drift but doesn't auto-fix existing drift.
10.7 Integration reauth
GitHub / Slack integrations occasionally lose auth (token expired, account permissions changed). Workspace Settings → Apps → that integration → "Reconnect." If the integration is partly broken (e.g., notifications work but PR links don't), disconnect and reconnect cleanly rather than tinkering.
10.8 Outage runbook
ClickUp service outages happen. The recovery is: wait. But operational dependencies don't stop:
- Detect. status.clickup.com — bookmark and check first.
- Communicate. Post in the team Slack channel: "ClickUp is down (per status page); expect status flips / task creates to fail; will update on restore."
- Local fallback. Time tracking moves to local notes (timestamped log file or Toggl scratch) — entries can be reconciled into ClickUp post-restore. Task creation queues in markdown task files (per Markdown Task File to ClickUp SOP) — they push to ClickUp post-restore.
- Verify post-restore. Run smoke tests §7 #1, #2, #5 to confirm full functionality before declaring resolution.
10.9 What this section does NOT cover
- Full workspace wipe — §1–§7 above ARE the recovery procedure.
- Data exfiltration before a planned migration to another tool — see §8.
- Per-client data isolation issues — see SC Archive & Retention Standard.
11. Per-client folder creation runbook
Run this when SC signs a new client and needs a folder under Client Delivery space. Aligns the folder's structure to canon (§5.2) and seeds the per-client view layer.
11.1 Pre-flight
- Client slug decided. Format: lowercase, hyphenated, matches the directory name under
09-clients/in the repo. - Client custom-field option exists. Settings → Custom Fields →
Client(in Client Delivery space) → confirm the slug is in the dropdown. If not: add it before creating the folder. -
client/<slug>tag exists at space level (both Client Delivery and SC Operations). If not: add per Tag taxonomy §Approved tags. - Client profile exists at
09-clients/<slug>/<slug>-client-profile.md. Required forClickUp List IDstorage (per next steps).
11.2 Create the folder + lists
Duplicate the template — never create a blank folder. Automations live at folder level and are the one thing a blank folder does not inherit. This step is manual UI work and cannot be done via the ClickUp MCP tools:
clickup_create_folderwill happily produce a folder with the right lists and the right statuses (statuses come from the space) and no automations at all, with no error to warn you. See working ruleclickup-client-folder-duplicate-template.
- Client Delivery space → right-click
CD Folder Template→ Duplicate. - Rename the duplicate to
<client-slug>(exact, lowercase, hyphenated — must match09-clients/<slug>/andClient_Delivery/<slug>/). - Confirm the folder shows exactly two lists,
active-workandreference. Do NOT createcompleted-workorarchivelists (retired 2026-06-08 — see §5.2 historical note). - Verify the Automations came across — open the folder's Automations tab and confirm it is not empty. This is the check that distinguishes a duplicated folder from a blank one; the list and status structure looks identical either way.
- Clear any placeholder tasks the duplicate carried over from the template.
11.3 Capture list IDs
Capture these after §11.2 is confirmed complete, not before. IDs recorded from a folder that later gets recreated are worse than no IDs — they point at something that no longer exists while looking authoritative.
- Open the new
active-worklist → URL bar → list ID is the last numeric segment of the URL. - Open
<slug>-client-profile.md→ set theClickUp List ID:field to that ID. Commit the profile change. - Optional: capture the
referencelist ID alongside if any per-client reference docs will live there.
11.4 Provision team access
Per Permissions Matrix §3 Folder level:
- Members on the SC team: already have Client Delivery space access, so they see the new folder automatically.
- Guests assigned to this client: grant folder-level access via Settings → Members → that Guest → "Add to folder" →
<client-slug>. They get scoped to that folder only.
11.5 Seed the per-client views
Build the per-client views per Views Guide §6.2: active-work-<client-slug> etc. Don't rebuild ad-hoc filters next week — save them now.
11.6 Smoke test
Run §7 smoke tests #1, #2, #5 against the new active-work list. Confirm the test ticket carries the correct Client custom-field value (matches the folder slug) and that the client/<slug> tag is applied correctly.
11.7 Cross-link
- Add the client to
09-clients/README.mdactive-clients index. - Add the new ticket markdown folder structure in Drive:
Client_Delivery/<slug>/work-in-progress/<YYYY-MM>/(per CLAUDE.md §Content Routing).
12. References
- Standards:
- SC Task Data Standard — abstract data model
- SC ClickUp Tag Taxonomy — canonical tag set
- SC Contractor Task Quality — Pre-Work Standard — what a well-formed task looks like
- SC Contractor Task Quality — Review Standard — review and sampling
- SOPs:
- Markdown Task File to ClickUp SOP — converting markdown task files to ClickUp tickets; QA-Review subtask pattern (§3c); single-assignee rule (§3d)
- ClickUp Timesheet Approval SOP — time tracking and approval flow
- Project Partner Team Onboarding SOP — guest-role provisioning for vendor teams
- Working rules:
13. Changelog
| Date | Version | Changes | Author |
|---|---|---|---|
| 2026-06-02 | 1.0 | Initial consolidation. Replaces clickup-sc-operations-space-setup-sop.md (deprecated). Adds workspace-level config, Client Delivery space spec, smoke-test sequence, and tool-portability appendix. Names sc-status-01 as the canonical status template. | Symphony Core Systems Team |
| 2026-06-04 | 1.1 | Reconciled client/<slug> tag vs Client custom field. §5.3 now names the population source (markdown-task SOP §3) and the tag–field correspondence rule. §4.2 cross-references the tag taxonomy's refined when-required rule. The two constructs are now scoped non-overlappingly (field = mandatory in Client Delivery; tag = mandatory in SC Operations + Client Delivery shared lists, optional on per-client lists). | Symphony Core Systems Team |
| 2026-06-08 | 1.2 | Per-client folder simplified from 4 lists to 2 lists (active-work + reference). Retired completed-work and archive lists. Status filtering (Closed-group auto-hide on complete) now does the work the completed-work list previously did. Native ClickUp task archive replaces the archive list via a manual monthly UI sweep (§5.6). Default views §5.5 rewritten to use status + custom-field + date filters; no list-name filters. Drivers: (a) cross-folder views were impossible because per-folder list names collided (e.g., every folder had a list named completed-work), (b) the 2026-06-08 Tanu/Rohit meeting confirmed the friction with a hand-built "list include completed" workaround for rotary-sports, (c) Business plan's Timesheet Approvals removed the need for list-movement as a billing-cycle signal. Note: earlier text in §5.6 referred to a complete → completed-work "workspace automation" — on inspection during the migration no such automation existed (ClickUp doesn't support workspace-scoped automations, and no equivalent space/folder/list rule was found); the behavior was manual. Smoke tests §7 updated to include native-archive recovery path. | Symphony Core Systems Team |
| 2026-06-14 | 1.3 | SC Operations flattened from folder-based to flat sc-* lists (§6.2 fully rewritten). Retired the Agency Platform/ and Sales/ folder layer; live list set is now people-operations, sc-marketing, sc-sales, platform, client-delivery-operations, archive, reference — all folderless. §6.3 removed Work Domain dropdown (list = domain); §6.5 updated views (By List instead of By Domain, added Recently Completed (30d)). New §6.7 cross-references the new clickup-structure-sync working rule. Driver: live UI change made 2026-06-13; SOP lagged 24h until caught by screenshot comparison (tracking ticket 86aj1aaz6). | Symphony Core Systems Team |
| 2026-06-14 | 2.0 | Admin-completeness pass. Added §4.0 Subscription & seats (plan-tier dependencies, seat math). Added §9 User Lifecycle (add/promote/demote/revoke Members, Guests, Admins; cadence). Added §10 Partial-loss disaster recovery (list/task/template/tag/schema/integration recovery + outage runbook). Added §11 Per-client folder creation runbook. Embedded 3 mermaid diagrams: workspace hierarchy (§2), status lifecycle (§3.1), custom-field scope (§5.3). Renumbered: old §9 References → §12; old §10 Changelog → §13. workflow_owner: Implementation Lead → Workspace Owner per reference-roles-strictly. | Symphony Core Systems Team |
| 2026-08-31 | 2.1 | Structure sync after the engineering-portfolio pass. §6.2: added sc-admin (901327593867), which was live but undocumented, and filled in the ids for archive and reference. §6.3: added the Initiative short-text field (3d5cc126-8814-48c8-9fd1-19ef2f451b25) that binds ClickUp tasks to 11-engineering/portfolio/, and corrected the Work Domain entry — v1.3 recorded it as removed, but the dropdown is still live on the space, so the SOP was describing a state ClickUp never reached. Out-of-scope structural changes made the same day and deliberately not added here: the SCA Platform Development and SCA Product Development spaces, the SC Sprints folder (29 lists), three empty Operations folders, the Zakir list and SOP LibraryV2 were all archived. None of them were ever documented in this SOP, which covers Client Delivery and SC Operations only; the legacy Operations space remains undocumented. Tracking ticket 86ak8xxjg. | Symphony Core Systems Team |