A LITTLE HELP WITH THE HANDOFF

Make the next step obvious.

Useful guidance for the agency collecting content and the client making it happen.

GUIDE 01 · FOR WEB DESIGNERS

Collect website content without the scramble.

The most useful content request mirrors the website you are building. Start with the pages you agreed on, then give each one a small, specific set of requirements.

  1. Give every page a purpose. Instead of “send your copy,” ask for the homepage headline, a short introduction, and the action visitors should take.
  2. Explain the useful shape. Share a rough length, audience, tone, and example. Make it clear whether a rough draft is welcome.
  3. Separate words from files. Use written-answer items for copy and file items for photos. Ask who owns the image rights and how the image should be credited.
  4. Keep access out of answers. Ask the client to invite your agency-owned email from the platform itself. Never request their password.
  5. Review one version at a time. Accept content that is ready. Where a change is needed, explain the next action instead of sending a general “please revise.”

Submitted content is ready for your review. It should not appear in the next client reminder. Only missing requirements and requested changes belong there.

Start with a website template
GUIDE 02 · FOR CREATIVE AGENCIES

Give your client a handoff they can follow.

A request works best when a client can answer three questions at a glance: what is this for, what do you need from me, and what happens after I send it?

  1. Lead with the project. Include the agency identity, a plain-language purpose, and a realistic deadline. Explain why each required item matters.
  2. Make optional mean optional. Useful inspiration should not block a project if it is not essential. Use required flags thoughtfully.
  3. Leave space for drafts. A client may have half an answer. Let them save it without marking it submitted or pretending it is ready.
  4. Name the version being approved. A decision should point to a specific reference. “Looks good” is ambiguous when the design has changed.
  5. Close the loop. Review what arrives, ask for clear changes, and complete the request only when every required item is accepted or properly waived.

Keep reminders polite and limited to outstanding client actions. Check permission before sending, pause when asked, and never mistake silence for approval.

Try both sides of the handoff

Common questions.

Do my clients need another account?

No. Clients use a focused request link to provide answers, files, and project approvals. They do not need an agency account. Anyone holding a valid link can act on that request, so share it carefully.

What happens after a client submits something?

You review the submitted version and either accept it or request a specific change. Submitted and accepted progress are shown separately, so an upload never silently becomes an approval.

Will reminders chase work that is already submitted?

No. Reminders include only required items that are missing or need changes. Work awaiting your review is your next action, not your client's. Reminders also require notification permission and a configured email service.

Can I use my own checklist?

Yes. Start with an original template, then edit its sections, instructions, required items, and order to fit the project. You can also build a request from scratch.

What counts as an active request?

Requests collecting client information or awaiting agency review count toward your active limit, including requests with paused reminders. Archived requests stop using active capacity, but their files still count toward storage.

Can I try it without sending anything?

Yes. The public demo uses fictional project data and stays in your browser tab. Its uploads and reminder previews are simulated. It cannot contact clients, charge a card, or change a real workspace.

Still need a hand? Find the contact details