| A page in the ClickUp project reaches its build stage while its copy document in Google Drive is still empty or marked as a draft. |
Checks the linked Drive document, notes which sections are missing and prepares a reminder naming the page, the requested content and the person who agreed to supply it. |
The project manager edits the reminder and sends it to the client contact; nothing reaches the client automatically. |
The ClickUp task shows the page as blocked on copy, with the request date and owner visible, before a developer runs into placeholder text mid-build. |
| A kickoff checklist item for hosting, domain or analytics access stays open in ClickUp past its agreed date. |
Lists each outstanding access request, the service involved and the responsible client contact, then drafts a follow-up asking for an invitation to the agency account. It never asks for or stores passwords. |
The account lead reviews the follow-up and decides whether to send it or raise the gap on the next client call. |
The team knows which access is missing well before build day, and credentials stay inside the client’s own user management and password tools. |
| New comments appear on a Figma file after the client was asked to approve a specific design round. |
Groups the open comments by frame, separates questions from change requests and records them against that approval round in ClickUp. |
The lead designer decides which comments become revisions, which need a conversation and when the round goes back for review. |
Every round carries a record of what was shown, what was asked and what the designer accepted, so development starts from an approved version. |
| A developer posts in the project Slack channel that a page cannot be finished because an asset or decision is missing. |
Links the message to the matching ClickUp task, labels the blocker type and adds it to the project manager’s review list. |
The project manager confirms the blocker and assigns who resolves it, inside the agency or with the client. |
Blockers raised in chat stop getting buried in a thread; they sit in the same list as every other launch dependency. |
| A launch date in Google Calendar is approaching for a site still on WordPress staging. |
Builds a readiness list from ClickUp and Drive: pages on placeholder copy, unapproved design rounds, redirects the team flagged and the outstanding client sign-off. |
The project manager walks the client through the list, and the client gives written sign-off before a developer moves anything live. |
Launch becomes a decision people make with the open items in front of them. The assistant never deploys, publishes or overwrites the live site. |
| A client email in Gmail asks for a new page or feature that does not appear in the agreed scope document. |
Flags the request as a possible scope change, links it to the scope document in Drive and prepares a short note for the account lead. |
The account lead decides whether the request fits the agreed scope and handles that conversation with the client. |
Additions get noticed when they are asked for, instead of surfacing after launch as work nobody planned. |