Freelancers and consultants · Deliveries

A delivered project shouldn’t disappear while you wait for approval.

You sent the work. The client said they would review it, but the decision you need and the right time to follow up are still unclear. The delivery should remain readable while you wait.

A practical method · 6 min read

A delivery folder, an approval sphere and a reminder linked by the Avanlio thread.

The scene

The work was sent. The decision stayed behind.

You send the final project on Friday afternoon. The client replies, “I’ll review it properly,” and the conversation stops. A few days later you know you should write, but first you have to find the file, check whether it was truly the final version and reconstruct what you asked them to approve.

The problem is not only the delayed reply. The delivery has lost its status: you cannot see whether it was received, whether a question is blocking the review, whether another person must decide or whether the job can be closed.

Before the follow-up

What should stay attached to the delivery?

You do not need to preserve every exchange. You need four references that let you write without starting over and without assigning a decision the client has not made.

1
The delivered versionThe exact file or result you sent, with its date and delivery channel.
2
The decision requestedFinal approval, a choice between options, a clarification or receipt confirmation: one precise question.
3
The real statusWaiting, receipt to confirm or blocked by a question. Silence does not become approval.
4
The next contactWhen to follow up, what you need to achieve and who is expected to decide.

The method

A good reminder restores context and asks one thing.

Open with one line that identifies the delivery: what you sent and when. Then state the one decision you need instead of stacking three questions in the same message. If a doubt may be blocking the client, make it easy for them to say so.

The message does not need artificial urgency. You can refer to the agreed date or suggest a realistic new point, but do not read silence as disinterest. If the reply introduces a change, bring it back into the job as a new decision or revision rather than leaving it hidden in the follow-up.

With Avanlio

The delivery, open decision and next contact stay on one thread.

Avanlio is designed so a delivery does not live apart from the client, the job and the step that should follow it. Assist can prepare a draft using the sources you choose, but it sends no messages and saves no changes without clear confirmation.

The point is not to chase a client automatically. It is to reopen the situation and immediately see what was delivered, which answer is missing and why the follow-up makes sense.

If the client replies through several channels, read how to keep feedback and versions together. If the reply changes the agreed scope, see how to separate a revision from a change request. Or explore Avanlio for freelancers and consultants.

Questions

Short answers.

What should you record when you send a client delivery?

The version you sent, the date, the decision you asked for and the next follow-up point, without treating silence as approval.

How do you follow up for approval without sounding pushy?

Briefly identify what you sent, ask one concrete question and leave room for the client to explain a blocker or concern.

Does Avanlio send the follow-up automatically?

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

Open beta

If every pending delivery makes you rebuild the context, tell us how you work.

The beta is open: sign up, confirm your address and get the link to join. No card required.

Join the beta