Skip to guide
GrowthubDocsOpen Growthub

Client work over days

Carry a managed-service engagement across days and providers with a current brief, specialist ownership and verified saved work.

Illustrated example, not an exact screenshot. Enlarge for the details; follow the current instructions below for the controls in your account.

Explore this guide

Give the engagement a home

Choose the client Project and Brand Kit. Keep the agreed deliverables, review cadence, source material and next decision on a working Page inside the client’s Space.

Read the full section

Give the engagement a home

Choose the client Project and Brand Kit. Keep the agreed deliverables, review cadence, source material and next decision on a working Page inside the client’s Space.

For a wellness-client engagement, that might be a source-backed audit, landing-page recommendations, approved creative and a reviewable distribution plan. Define the actual service scope and commercial agreement with the client.

Give each part an owner

Use saved specialists and independent parallel work when the parts can proceed separately. Keep shared destination edits and the engagement’s current record coordinated.

Example request · adapt to your work
Read the current client Page and accepted work. Ask Creative Studio for the next bounded visual revision and our content Character for matching draft copy. Preserve approved elements, existing destination IDs and earlier versions. Return source files and a concise handoff for review.

Resume from saved reality

  1. Read the current working Page, prior result and pending review decision.
  2. Continue the same Character conversation when it owns the work.
  3. Open existing destination records before retrying a send or upload.
  4. Keep useful revision notes and current links with the engagement.
  5. Record a precise unresolved question when a genuine human decision is needed.

Put a correction where it belongs

Add missing facts to the appropriate source or Page. Put a repeatable role-specific technique in the Character or playbook. Use Naming Conventions for scoped naming preferences, and a reviewed Routine for recurring execution.

Keep the operating method small and useful. Better continuity comes from current context, accepted examples and verified outcomes, while preserving the provider’s native capabilities.

Keep going