DealokrKey idea
Client approval
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.
Client approval 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
Client approval: a request that calls for a decision
When sending work, avoid “tell me what you think.” Prefer: “Can you approve the three listed items by Tuesday?” Include the link, version number and what approval unlocks. The client knows what to do; you know which record to keep.
- Name the exact version submitted for approval.
- List criteria to check, not a broad request for feelings.
- State the next step that follows approval.
