Freelancers and consultants · Dependencies

Missing client materials shouldn’t leave a project blocked without a next checkpoint.

The copy, access or files were promised, but they never arrived. Unless the dependency is made visible, the job stays open while the next move gets lost across email and chat.

A practical method · 6 min read

A project folder, a missing tile and a green checkpoint are connected by the Avanlio thread.

The scene

The work is ready, but the promised input still lives inside a conversation.

You built the plan, reserved the time and explained what you need to start. The client promised copy, images, credentials or an internal decision. The date passes, nothing arrives, and the project keeps taking up space as if it were moving.

The problem is not just delay. The dependency remains implicit: nobody can see what is missing, which activity it blocks or when waiting should turn into a decision.

Before you write

What does the project actually need to move again?

A generic “are we still missing anything?” only sends the uncertainty back to the client. Build a short, verifiable picture instead: the necessary items, the part of the work that depends on each one and the decision you will make if they do not arrive.

1
Name the missing inputList each file, access credential or approval in concrete terms. When versions exist, identify the one you need and where it should be delivered.
2
Connect it to the workExplain which task cannot start or finish. If another part can continue, separate it instead of calling the whole project blocked.
3
Ask for a usable answerOffer a realistic date and invite the client to reply even when delivery is not possible. Silence is not a revised plan.
4
Choose the checkpointSet when you will review the situation and what follows: reschedule, reduce scope or agree on a new working window.

The message

A useful follow-up reduces uncertainty instead of turning up the pressure.

A clear request can fit into a few lines: what is missing, why it matters, the practical effect and the next decision point. You do not need to assign blame or retell the entire project history.

If the client cannot deliver by the suggested date, ask them to choose an alternative: partial delivery, a replacement input or a new schedule. Even a “not yet” can move the work forward when it frees you from protecting capacity nobody has confirmed.

With Avanlio

The material, the blocked task and the next checkpoint stay on the same thread.

Avanlio is designed to keep a dependency close to the client, the project and the action it is holding back. Assist can prepare a draft from the sources you choose, but it sends no messages and saves no changes without clear confirmation.

The value is not having software chase the client for you. It is seeing what is missing, separating the work that can continue and recovering the context when it is time to decide.

If the dependency shifts the whole schedule, read how to give a postponed project a new start date. If the work has already been delivered, see how to manage the wait for approval. Or explore Avanlio for freelancers and consultants.

Questions

The short answers.

What should you record when client materials are missing?

Record the exact items, who needs to provide them, where they should be delivered, what they block and the date of the next checkpoint.

How do you follow up without sounding pushy?

Send a short request that names what is missing, why it matters, the effect on the work and a concrete date for deciding what happens next.

Does Avanlio send the reminder automatically?

No. Assist can prepare a draft from the sources you choose, but it sends no messages and saves no changes without clear confirmation.

Beta open

If missing inputs keep your projects stalled, tell us how you handle them.

Join the beta, confirm your email and receive the link to get started. No card required.

Join the beta