What to collect before the work starts

Check the requirements of the first agreed deliverable. Confirm that essential business facts are verified, required access works and the approver is known. Other tasks may have different dependencies and can become ready later. This is more useful than treating every account as either entirely complete or entirely blocked based on whether one long form has been submitted.

Receiving an invitation indicates that a grant was initiated. Verification means the authorized agency account can reach the correct asset with the permission needed for the agreed task. Confirm that without making an unnecessary production change. Record the result so the delivery teammate does not discover on launch day that the invitation concerned the wrong property or an insufficient role.

Request the access needed for the agreed work and explain its purpose. The checklist should support the engagement rather than become a reason to collect unrelated permissions. If scope expands, add the appropriate request then. A focused access plan is easier for the client to understand and makes later reviews simpler because each grant has a clear connection to a task.

Record the uncertainty and ask for the relevant business contact or existing administrator who can clarify ownership. Keep tasks requiring that access pending until the correct route is established. Do not solve the ambiguity by asking someone to share a personal password. Meanwhile, continue independent work that has verified inputs and does not depend on controlling the unknown account.

Keep confirmed facts in a shared client record and identify their source and date. Before contacting the owner, check whether another teammate already collected the answer. When facts change, update the working reference rather than leaving conflicting versions in separate messages. A short, maintained record of services, contacts and approvals can prevent more repeated questions than a much longer form nobody consults.

Name the exact item, explain the deliverable it supports and identify the action the recipient should take. Include the agreed timing or next review point where relevant. For example, asking for the approved location photographs for a draft page is clearer than asking for all remaining assets. Focused requests help the client complete one meaningful step without reconstructing the entire project.

Yes, where the necessary inputs and authorization for that specific work are already available. Make dependencies explicit and keep assumptions visible in drafts. Do not publish or change an account based on unverified information simply to maintain momentum. Separating independent tasks from blocked ones lets the team make useful progress while preserving a clear record of what still needs the client's input.

Use the named person authorized to approve that material for the business. The day-to-day contact may collect feedback without having final authority, so clarify the distinction during onboarding. Agree how feedback is consolidated and how approval is recorded. This prevents the delivery team from treating a casual comment as final acceptance or publishing while another decision maker still expects to review the draft.

Identify the conflict and ask the appropriate owner to confirm the current fact. Keep the question specific, such as which phone number should appear publicly or which locations offer a service. Avoid choosing whichever version is easiest to copy. Once resolved, update the shared working record and any affected draft so the same conflict does not return at the next handoff.

Confirm their intended use, relevance and the client's authority to provide them for publication. Keep that confirmation with the asset handoff through the normal process. If something is unclear, request clarification or an appropriate replacement before publishing. The fact that a file arrived in an email does not explain who created it, whether it remains current or where it should appear.

Separate shared brand information from location-specific facts such as hours, services, contacts and profile identities. Name the person who can verify each branch's details and decide how approvals are coordinated. A single central contact can organize the process, but the working record should preserve the differences. Otherwise, a correct fact about one branch can easily be copied to the wrong location.

Include the agreed first deliverable, verified inputs, access status, responsible contacts, approval route and outstanding dependencies. Add relevant baseline observations and the next client communication. Keep it concise enough for the delivery team to use. The purpose is to make the next action obvious, rather than repeat every answer collected during discovery without showing how it affects the work.

Give each missing dependency an owner and a clear next step, then review it through the team's ordinary task process. Explain any effect on the deliverable before a deadline passes. Avoid vague labels such as waiting on client when several distinct items are involved. Specific records help both sides resolve the actual obstacle and understand which parts of delivery can still proceed.

The access structure and ownership decisions made at the beginning affect how cleanly the relationship can end. Keep the client's assets and authorized agency access clearly identified, and record the relevant grants. That makes later review or removal easier to organize. It also helps new teammates understand which systems the agency uses for the client without relying on a former colleague's memory.

Review the specific gap that caused delay or rework, then adjust the question, verification step or handoff that would have prevented it. Avoid making every future form longer because one unusual account had a problem. A good checklist distinguishes common requirements from engagement-specific needs and remains understandable enough for clients and teammates to complete accurately.