Client-Facing Workspace Provisioning (Onboarding)

Client-Facing Workspace Provisioning (Onboarding)

1. 01

   Map the client's decision rights before creating a single board

   List who approves scope changes, who reviews deliverables, and who only needs read access. Permissions designed after the workspace exists get patched forever.

2. 02

   Confirm the client's own tooling constraints in writing

   Some clients mandate their internal stack for anything touching their data. Capture that constraint at kickoff, because it decides whether the shared workspace is the system of record or a mirror of one.

3. 03

   Choose the shared surface deliberately, not by agency default

   A lightweight board such as Basecamp suits a retainer where the client wants discussion threads and files, while a structured build in Wrike or monday.com fits multi-workstream programs with dependencies and approvals.

4. 04

   Define the client-visible field set and hide the rest

   Internal margin notes, resourcing debates, and rate cards stay in the internal view. Publish only status, owner, due date, and deliverable link.

5. 05

   Set the update cadence and name the person who owns it

   A weekly written status with a named author beats a live dashboard nobody opens. Put the cadence in the retainer agreement so it survives staff turnover.

6. 06

   Run a 20-minute walkthrough with the client's actual daily users

   Train the people who will log in on Tuesday, not only the sponsor who signed. Adoption failures usually trace to a viewer who was never shown where to click.

7. 07

   Log the workspace in the agency's client register with its owner and review date

   Every shared workspace needs an internal owner and a scheduled review, otherwise orphaned client boards accumulate access nobody is tracking.