DealokrKey idea
Delivery checklist
Use this guide as an operational starting point, then adapt it to the client, the scope and the rules that apply to your work.
Decide the rule before the project moves.
Delivery checklist is easier to manage when both sides can see the expected result, the person who decides and the next action. Start with the facts that affect the project rather than a vague promise.
Put the decision in a shared record.
Write down the scope, date, amount or approval step that applies to this project. A clear record helps a client act and helps you avoid rebuilding the context from scattered messages.
Do not mistake a workflow for legal, tax or financial advice.
This guide offers operational guidance for freelancers. Check the official source relevant to your situation and seek qualified advice whenever the decision has legal, accounting or tax consequences.
Operational example
Delivery checklist: the final check before sending
Before the final link, check at least: correct version, promised formats, working access, clearly stated exclusions and a clear approval request. This takes minutes and avoids many “I cannot find the file” follow-ups.
- Open the link from a session other than your own when possible.
- Check folder names and organisation from a third party’s point of view.
- Keep a copy of the version actually handed over.
