Skip to main content

ClickUp First Week Walkthrough

Purpose​

This is your navigational orientation to Symphony Core's ClickUp workspace. It comes before the rules. By the end you should be able to: log in, find your tasks, read what you need to do, log your time, move the task forward, and know who to ask when stuck.

Once you've worked through this guide, move on to ClickUp Ways of Working — that's the rules layer. This walkthrough plus that playbook plus the role-specific docs (per doc finder) cover everything you need to operate.

Time estimate: 30 minutes to read; another 30 minutes to do the practice steps in §4 against a real (or test) ticket.

Who this is for​

Two audiences, slightly different paths:

You are…ReadSkip
An SC internal team member (FT or retained)All sections + Appendix AAppendix B
An external contractor (Project Partner vendor team developer)All sections + Appendix BAppendix A

The numbered steps in §4 are identical regardless of role; the appendices fill in role-specific differences (cross-space visibility, time tracking, who reviews your work).


1. The mental model​

Two spaces, two patterns:

  • Client Delivery has one folder per client. Inside each folder are two lists: active-work (every task in every status) and reference (standing reference items only). If you're working on something for client acme, your task is in Client Delivery > acme > active-work.
  • SC Operations is flat. No folders. Lists are domain-named: sc-marketing, sc-sales, platform, people-operations, client-delivery-operations. If you're working on SC's own website, you're in sc-marketing. If you're configuring something in ClickUp itself, you're in platform.

If you're a contractor scoped to one client, you'll only see that client's folder (per ClickUp Permissions Matrix §3). You won't see SC Operations at all — that's by design, not a bug.


2. Logging in for the first time​

  1. Open your invitation email from ClickUp. Click "Accept invitation." This creates your account against the email address the workspace admin invited.
  2. Set a strong password + enable 2FA. Settings → Security. 2FA is non-negotiable — anything you can see in ClickUp is sensitive enough to require it.
  3. Set your timezone to your local zone. Settings → Profile → Timezone. ClickUp shows all due dates in your timezone; the canonical zone for SC is EST per canonical-timezone-for-due-dates-est, so know the EST offset from yours.
  4. Confirm you're in the right workspace. Top-left dropdown should say "Symphony Core Workspace." If it says something else, ping your onboarding contact.

3. Finding your work — the 3 default views​

These three views cover 90% of daily navigation. Build them as personal saved views or use the team-saved versions if available — see Views and Filters Guide §6 for the full recipe set.

3.1 "My Tasks" — what you should be working on now​

Recipe (per Views Guide §5):

  • Scope: Everywhere
  • Filter: assignee = me + status is not (complete, cancelled)
  • Sort: due date ascending
  • Save: my-tasks-open

This is your daily landing view. Everything assigned to you, not done.

3.2 "My Recent Closures" — what you closed in the last 14 days​

Recipe:

  • Scope: Everywhere
  • Filter: assignee = me + status in (complete, cancelled) + date_done > today − 14 days
  • Sort: date_done descending
  • Save: my-tasks-recent-closures

Useful for: weekly self-retrospective ("what shipped"), invoice support ("here's what I billed for"), and remembering what you did when someone asks.

3.3 "My QA-Review queue" (only if you are a QA Reviewer)​

If your role includes QA-Review responsibilities (typically the Account Manager — see QA Reviewer SOP), set up:

  • Filter: name contains "qa-review-" OR name contains "am-review-", assignee = me, status is not complete
  • Save: qa-review-queue

Skip this if your role is purely Assignee.


4. Working a task end-to-end​

Pick a real or test ticket assigned to you. Walk through these steps.

Step 1 — Open the ticket and read it​

  1. Click the ticket from your my-tasks-open view.
  2. Read the description top-to-bottom. The description is the source of truth for what you're doing.
  3. Find the ## Acceptance Criteria block. This is what done means for this ticket. If there's no AC, stop — comment on the ticket asking the Creator to add AC. Don't proceed.
  4. Find the Evidence: bullet (usually the last AC item). This names the artifact you'll attach when you close: a screenshot, a deploy URL, a PR link, a log link.

Step 2 — Move to in progress​

Click the status pill (top-left of the ticket, usually "TO DO"). Pick IN PROGRESS.

Rule: If you're about to log time, you MUST move to in progress first. A task with logged time cannot stay in to do. See Ways of Working §2 Invariant 1.

Step 3 — Do the work​

This guide can't help you with the actual work — but a few ClickUp habits:

  • Update the description as you go if anything material changes (scope, approach, blockers). The description is current state; comments are audit trail. Both matter.
  • Use comments for context — decisions, hand-offs, things you'd otherwise lose to Slack.
  • Add a blocked-on:* tag if you hit an external dependency, and move the status to blocked. See Tag Taxonomy §External-dependency state.

Step 4 — Log your time (if applicable to your role)​

Only if your role logs time in ClickUp (vendor team developers + hourly contractors — see Appendix B). FT internal SC team members typically don't track time here. Per Ways of Working §5:

  • Click the timer icon on the ticket (top-right area) to start. Click again to stop.
  • Or use manual entry: ... > Add time entry with start/end times.
  • Description is required on every entry. Built outlined Client Login button in header is good. WP work is not.
  • Round to 0.1h (6-minute) increments.
  • End-of-day batch logging is fine; end-of-week is not (descriptions decay).
  • The full timesheet submission flow is in ClickUp Timesheet Approval SOP.

Step 5 — Attach the Evidence and close​

  1. The AC's Evidence: bullet tells you what to attach: a screenshot (drag-drop into the ticket OR comment), a URL (paste into a comment), a PR link (the GitHub integration auto-attaches when you reference the ticket from the PR description).
  2. Check every AC bullet is satisfied — re-read the description's AC block and confirm each one.
  3. If the ticket is client-facing: a qa-review-<parent-slug> subtask exists. You cannot close the parent until the subtask is closed. Notify the QA Reviewer (typically the AM) that the parent is ready for review — usually via a comment + the @ mention if needed. They'll review and either approve (closing the subtask) or send back. Per Ways of Working §7.
  4. If the ticket is internal/non-client: no QA-Review subtask. Move status to complete yourself — the Evidence bullet on the AC is the validation artifact.

That's it. The ticket disappears from your my-tasks-open view and stays searchable forever.


5. When you get stuck​

Stuck on…Where to go
What's the rule for X?ClickUp Ways of Working — the rules layer
Where do I find the saved view for Y?ClickUp Views and Filters Guide §6
Which doc covers question Z?ClickUp Doc Finder — question → doc map
Can I do X? (permissions)ClickUp Permissions Matrix
Time tracking didn't workClickUp Timesheet Approval SOP §8 — fallback flow
ClickUp seems broken / I can't see what I expectSlack the team channel + check status.clickup.com before assuming it's your config
Who reviews my work?The QA Reviewer per Ways of Working §Roles. Default human is the Account Manager.

Appendix A — For SC internal team members​

You can see both spaces (Client Delivery + SC Operations) by default. You can navigate freely between client folders and SC's own lists.

You don't typically track time in ClickUp. Internal time tracking happens via Google Sheets per Timesheet and Invoice Submission SOP. Skip §4 step 4 unless your specific engagement says otherwise.

You might hold multiple roles per ticket — Creator (you wrote the ticket) AND Assignee (you're doing it), or Assignee AND eventual QA Reviewer (for tickets you authored, you delegate the QA Reviewer role to someone else — see QA Reviewer SOP §8 Q: "I'm the AM AND the Creator"). Hold one role at a time on a given ticket; switch hats deliberately.

Tag literacy matters for you. You'll be applying client/<slug>, domain:*, and possibly qa:* tags. Read SC ClickUp Tag Taxonomy once end-to-end.


Appendix B — For external contractors (Project Partner team developers)​

You're a Guest scoped to one folder. You'll only see that folder's lists + tasks. You won't see other clients, SC Operations, or the broader workspace. This is intentional (per Permissions Matrix §3) — it's how SC isolates your access.

Your "assigned to me" view is Home → My Tasks → Assigned to me. Guests do not get the Everywhere (Everything) scope, so the §3.1 recipe does not work for you. In the left sidebar open Home, then My Tasks, then Assigned to me, and bookmark it. Then, once: click the Subtasks icon at the top left of that page (or Customize → Subtasks) and choose As separate tasks. Most tickets you receive are subtasks of a parent assigned to someone else, and ClickUp hides those by default, so without this the list can look empty. It then lists every task assigned to you, in every list shared with you, grouped by due date. Assigning a task to you shares it with you, so a ticket in any client or operations list shows up there. If a ticket you were told about is missing, ping the AM.

You DO track time in ClickUp. Step 4 of §4 applies to you. The full weekly submission flow is in ClickUp Timesheet Approval SOP §4:

  • Log time as you go (live timer) OR end-of-day batch (manual entries).
  • Every entry needs a description (no "WP work" / "meetings").
  • Submit weekly via My Work → Timesheets → "Submit for Approval." Deadline: Monday 07:00 EST for the previous Monday–Sunday week.
  • An Approver reviews within 2 business days. Approved entries lock and become billable.

Skip §6 Tags in Ways of Working beyond the basics — you typically don't apply qa:* tags (those are QA Reviewer's job) or client/<slug> (the folder already encodes the client). You will apply blocked-on:* if you hit an external dependency, and domain:* if relevant to your work.

Skip §Roles in Ways of Working beyond knowing that you are the Assignee and the AM is the QA Reviewer. The other roles (Creator, ClickUp Admin) aren't yours to worry about.

If something looks wrong (you can't see a ticket you should, the timer's missing, you got a permission denied) — ping the AM via Slack. Don't try to fix it from your end.


Revision History​

DateVersionChangeAuthor
2026-10-071.3Appendix B: set Subtasks to "As separate tasks" in Assigned to me; contractor tickets are usually subtasks and are hidden otherwise.Symphony Core Systems Team
2026-10-061.2Appendix B: corrected the path to Home → My Tasks → Assigned to me (v1.1 said "My Work", which is only a card on that page).Symphony Core Systems Team
2026-10-061.1Appendix B: external contractors on guest seats use Home → My Work as their assigned-to-me view, since guests have no Everywhere scope.Symphony Core Systems Team
2026-06-141.0Initial release. Navigational onboarding walkthrough — mental model (Client Delivery vs SC Operations), login, 3 default views, end-to-end task walk (read AC → in progress → work → log time → attach Evidence → close, with QA-Review subtask gate for client-facing). Two appendices for SC-internal vs external-contractor differences. Prose + 3 mermaid diagrams (workspace hierarchy, status lifecycle, time-tracking flow).Symphony Core Systems Team