Client-supplied dependency
Something only the client can provide, such as copy, access, assets, or approval, that blocks your work until it arrives.
See it
What it is
A client-supplied dependency is an asset, answer, access grant, approval, or decision the client must provide before your work can continue. Copy, brand files, analytics access, legal approval, and one final product owner decision all qualify. Calling them dependencies makes the schedule impact visible before they go missing.
List each dependency in the statement of work with an owner, required format, due date, and the milestone it blocks. Track it like a deliverable and confirm receipt. Construction contracts have a name for this category, owner-furnished contractor-installed, and they schedule the owner's tiles with the same rigour as the tiler. Yours deserve the same row on the plan. For anything on the critical path, state that a late handoff moves dependent dates by at least the same amount and may require rescheduling around other booked work.
Gotcha: writing 'client to provide content' as one line. That can mean copy for three pages or approved copy for fifty pages in a specified template. Make the item countable, name the approver, and define what ready means, or the dependency becomes an argument about whose delay it was.
Ask AI for it
Convert the project plan below into an Asana dependency register. For every client-supplied asset, access grant, answer, and approval, create a task with one owner, a due date in YYYY-MM-DD form, required format, acceptance check, blocked milestone, and escalation date. Use Asana task dependencies so downstream work is marked blocked, and define a rule that flags any incomplete client task 48 hours before it is due. Then write the statement-of-work clause that shifts affected dates when a dependency is late, plus the reminder messages for seven days before, two days before, and one day after the deadline.