Tasks
Only items blocking the rollout or requiring your approval appear here.
Needs your attention
6
You have 6 items that need your attention
Blocked by client input
6
Rollout waits on input or approval
Waiting on delivery team
8
Handled outside the client action feed
Only items blocking progress
These are the only items currently blocking progress or requiring your approval.
Needs your attention
6
You have 6 items that need your attention
Blocked by client input
6
Input, access, approval, or clarification needed
Waiting on delivery team
8
Tracked outside the client feed
Required before rollout
Why it matters
The delivery team needs this to confirm decision rights, locations, launch constraints, support expectations, and access requirements.
Needed from you
Submit the onboarding form before rollout begins.
If nothing happens
Kickoff and rollout preparation stay limited to assumptions until this is submitted.
Required before rollout
Why it matters
Discovery cannot move cleanly until the delivery team knows how approved access will be granted.
Needed from you
Confirm who will send system invites or provide the approved secure access path.
If nothing happens
System review and workflow validation remain blocked.
Required before rollout
Why it matters
Launch readiness cannot be confirmed until the reinforcement path and missing location details are clarified.
Needed from you
Confirm missing San Antonio location details or assign the correct reviewer.
If nothing happens
San Antonio readiness stays blocked.
Required before rollout
Why it matters
Launch readiness cannot be confirmed until the reinforcement path and missing location details are clarified.
Needed from you
Confirm missing Tucson location details or assign the correct reviewer.
If nothing happens
Tucson readiness stays blocked.
Required before rollout
Why it matters
Approved assets prevent the team from using stale copy, screenshots, or brand assumptions.
Needed from you
Add approved brand files, scripts, training docs, or links in the onboarding form.
If nothing happens
Draft deliverables may need revision once source assets arrive.
Required before rollout
Why it matters
Location details keep rollout assumptions from turning into incorrect client-facing work.
Needed from you
Confirm the current location list, managers, phone numbers, booking links, and market details where known.
If nothing happens
Location-specific readiness stays in review instead of moving into final rollout prep.