Resolve an access issue, move work forward, and watch the delivery dashboard update. Every task has a deliverable and a definition of done.
Client onboarding launch
Northstar Studio · Fictional project · Baseline: September 6, 2026
Project complete
33%
4 of 12 tasks
Work in progress
3
Needs attention
3
Risk, change, or on hold
Launch target
Sep 18
Sample project deadline
Try changing a task’s status. Open its acceptance criteria to see what “done” means.
Next up3
on hold
Test duplicates, missing data, and failed handoffs
Quality reviewer · Sep 14
Acceptance criteria
No duplicate records on replay; failed runs are visible; manual recovery is documented.
Upstream: Build · Connect lead routing and duplicate checks
Priority: high
to do
Run operator training and recovery drill
Operations lead · Sep 16
Acceptance criteria
An operator can identify a failed run, correct input, retry safely, and confirm completion.
Upstream: QA
Priority: normal
to do
Launch readiness review
Project lead · Sep 18
Acceptance criteria
Acceptance tests pass; client-facing actions are approved; monitoring and rollback are assigned.
Upstream: Handover
Priority: high
In motion5
in progress
Connect lead routing and duplicate checks
Automation engineer · Sep 9
Acceptance criteria
Submitting the same sample twice creates one CRM contact; missing owner goes to review.
Upstream: Prototype
Priority: high
in progress
Configure onboarding tasks and handoff
Operations lead · Sep 10
Acceptance criteria
A confirmed client gets the correct checklist, role owner, due dates, and kickoff next step.
Upstream: Scope
Priority: normal
in progress
Build the delivery dashboard
Reporting specialist · Sep 11
Acceptance criteria
Dashboard counts match the underlying task records and exclude cancelled tasks.
Upstream: Scope
Priority: normal
at risk
Resolve missing CRM sandbox access
Project lead · Sep 7
Acceptance criteria
Sandbox access is confirmed without sharing production credentials; if unavailable, use sample-only environment.
Upstream: Client decision
Priority: urgent
update required
Confirm revised welcome-email scope
Project lead · Sep 8
Acceptance criteria
Record the requested change; agree include, defer, or decline before implementing.
Upstream: Client decision
Priority: high
Complete4
complete
Map the current lead-to-client process
Business analyst · Sep 2
Acceptance criteria
Lead sources, handoffs, and manual re-entry are documented; delivery owner reviews the map.
Upstream: None
Priority: normal
complete
Agree requirements and acceptance criteria
Project lead · Sep 3
Acceptance criteria
Define required contact fields, duplicate rules, ownership, and what is out of scope.
Upstream: Discovery
Priority: high
complete
Design the CRM field map
Systems architect · Sep 4
Acceptance criteria
Each required input has a destination, type, validation rule, and fallback.
Upstream: Scope
Priority: normal
complete
Build the intake form
Implementation specialist · Sep 5
Acceptance criteria
Required inputs validate correctly; a test submission has a traceable record ID.
Upstream: Data
Priority: normal
Project loaded: 12 sample tasks, with 4 complete.
The actual ClickUp build
A dedicated space holds this project’s list, board, dates, and task-level acceptance criteria.
Actual ClickUp sample project, captured September 6, 2026. Fictional business and role-based example owners.The native dashboard reads the same sample space. Tasks are unassigned to real team members; role responsibilities are in each task’s description.
Built around your business
Where does your process get stuck?
Tell me the handoff, tool, or recurring problem. We can scope the system around it.