Separate true prerequisites from useful extras
Before promising a start date, list everything the client must provide for the work to move forward. For a website, that might include approved page copy, brand assets and access to the existing site. For a video, it might be source footage, usage permissions and a decision about the intended audience. Then ask which items genuinely block the first task. You may be able to sketch a page layout without final photographs, but you cannot edit footage you have not received.
Keep the list specific enough to act on. “Send content” leaves room for confusion; “send final copy for the home and services pages in an editable document” tells the client what completion looks like. Mark each input as required before kickoff, required before a particular milestone, or optional. This distinction prevents a missing nice-to-have item from holding up work that could proceed.
Give every input an owner, format and handoff date
Put the input list in the project brief or a shared tracker. For each item, name the person responsible for supplying it, the requested format, where it should be delivered and the date you need it. If several stakeholders must approve copy, ask the client to designate one person to gather their feedback and send a consolidated version. A single handoff is easier to plan around than comments arriving through separate messages.
Work backward from the task that needs each input. If a designer needs approved text before building final page layouts, the copy handoff should precede that task by enough time to check whether it is complete. Make that review time visible rather than treating delivery as an instant transfer into production. A student team can use the same approach for interview notes or survey questions; a freelancer can use it for product images or account access.
Show the dependency in the schedule
A project plan should show not just when you intend to work, but what lets that work begin. Write a milestone such as “Begin final designs after approved copy and images are received,” then place the expected handoff ahead of it. If the deadline depends on a timely handoff, say so when sharing the schedule. This makes the relationship between client inputs and delivery visible without implying that every delay will have the same effect.
Plan a useful first phase while you wait, if the project allows it. You might confirm goals, map a site structure, set up a file system or prepare design references. Avoid filling the schedule with work that is likely to be undone once the missing input arrives. For dependencies on the critical path, leave room to inspect files, ask questions and resolve access problems before the next task is due.
Agree on what happens if an input is late or incomplete
Discuss the fallback before there is a delay. Depending on the work, you may be able to move to another task, use clearly labeled placeholders for an internal draft, or pause the affected phase. Agree on who will confirm a revised schedule if the handoff slips. Do not assume that a late input can always be absorbed by working faster; the remaining review and production steps still take time.
Define what counts as received. A folder of images may be unusable if the files are too small for the intended output; copy may still be a draft if decision-makers have not approved it. When an input arrives, acknowledge it and promptly flag anything missing. Keep the request focused: identify the gap, explain which task it affects and state what you need next. This is more helpful than sending a general reminder that the project is waiting.
Keep the plan current and close the loop
Use one shared place to track input status, whether that is a project board, a brief or a simple table. Record what was requested, what arrived and any decisions made about substitutes or revised dates. Link to the accepted files rather than relying on an email thread as the only record. For a small team, this helps the next person know which version to use; for a freelancer, it makes the next client update easier to write.
At each milestone, review the outstanding inputs alongside the upcoming tasks. If a dependency changes, update the schedule and tell the people affected. At delivery, note any client-supplied material that remains provisional and what would be needed to replace it. The goal is not to create a complicated approval system. It is to make the handoffs that control the work clear enough that everyone can act on them.
