PRACTICAL RESOURCES · FOR SMALL AGENCIES

Collect content with a clear next step.

Define the inputs, owners, and decisions before missing content becomes a project blocker.

A website checklist works best when it describes decisions, not just folders. “Send the content” leaves a client to guess what you need, which version matters, and whether a rough answer is acceptable. A useful request makes those choices explicit.

Start with the pages and the people

List the pages that are actually in scope. For each one, name its purpose and the person who can approve its content. A five-page brochure site might need a home page, services, about, frequently asked questions, and contact. A booking page needs different information from a case-study library. Do not send every client the same long inventory just because those fields exist in a template.

Ask the client to nominate one person to coordinate answers and one person to make final decisions. They can be the same person. If legal, leadership, or a partner must approve a claim, record that dependency before design begins. A contact who collects content cannot necessarily authorize its use.

Turn each request into a small, answerable item

Replace “homepage copy” with a prompt the client can answer: What do you do? Who is it for? What should a visitor do next? Add a rough length range and a short example of the form, without writing unsupported claims about the client. Make it clear whether the answer should be polished copy, an outline, or source material for your writer.

Separate content that can be reviewed independently. The company introduction, service descriptions, opening hours, contact details, and call to action rarely need to live inside one enormous document. A smaller item can be submitted and reviewed while another item is still being drafted.

Use a link field for an existing reference, a text field for an answer, and a file field for assets. Ask for access through the relevant platform's invitation process. A project checklist is not a place for passwords, API keys, payment-card details, or identity documents.

Define “usable” before someone uploads a file

For a logo, explain which version you need and which formats your workflow accepts. For photos, explain the intended placement, approximate orientation, and whether the original full-resolution file is needed. If an editable design file cannot be uploaded, ask for a scoped shared link instead.

Ask the client to confirm that they own the material or have permission to use it. A file found online is not evidence of a licence. Record attribution requirements where relevant, and avoid asking the client to place sensitive personal information in image filenames or notes.

For case studies and testimonials, request the approved wording and publication permission. Leave missing proof out of the draft. “We'll add a placeholder quote for now” can accidentally become a published claim if nobody owns the final check.

Distinguish a saved draft, a submission, and an approval

Tell the client how to signal that an item is ready. A saved draft means work is in progress. A submission means the agency should review it. Agency acceptance means that specific version meets the requirement. These are three different states.

Use review notes that give one clear next step. “Please add the Saturday opening hours” is easier to act on than “needs more detail.” If a previously accepted answer changes, reopen the requirement and review the replacement. Do not let an old approval silently cover new content.

An approval item should identify the exact reference, such as “Homepage design v3, dated 12 October.” The record should distinguish an approval from a request for changes. Treat a project approval record according to your actual contract; it is not automatically an identity-verified or certified signature.

Make the next action visible

Show what is still waiting on the client and what is waiting on your agency. A checklist with every item marked “in progress” is not much better than an email chain. Give the client a short list of missing items and requested revisions; keep items awaiting your review out of that list.

Agree on a realistic due date and timezone. If reminders are appropriate and authorized, schedule them around the client's next action. Pause them when the client asks you to, when every required item has been submitted, or when the project changes direction. Do not ask a client to respond to a reminder about an item you already have.

End with a review, not an assumption

Before the content handoff, check that each required, non-waived item has been accepted. If something is intentionally out of scope, record why it was waived. Keep optional inspiration separate so it does not hold up a project that has everything it needs.

Export or summarize the final references, accepted versions, unresolved dependencies, and people responsible for the next step. The aim is simple: another person should be able to open the project and tell what is ready, what changed, and what still needs a decision.

A practical first step

Take one upcoming project. Write its page list, choose five essential content questions, name the decision maker, and agree what counts as a ready submission. That is a useful checklist before any automation is involved.

Readyloom keeps client answers, files, version-specific project approvals, and agency review in a shared checklist. Explore the interactive demo to see the handoff with fictional project data. No client account is needed for an authorized request link.