Close projects cleanly: files, access, instructions, and proof the client received everything.
8 min readIntroduction
Most project handoff stress comes from things nobody wrote down. This guide is for Filipino VAs reading on a phone between tasks. Short steps, everyday words, no fluff.
Why this matters
When project handoff goes wrong, you lose time, pay, or sleep. Small structure early saves awkward fights later. Good clients actually prefer clarity.
Salag's ANCHOR Protocol framework
Five steps you can reuse on calls, in email, and before you invoice.
Step 1: Capture facts
Write the request, prior agreement, and deadline in plain words.
Checkpoint: Is it out of your head and into text?
Step 2: Compare to agreement
Open your quote, SOW, or last recap email.
Checkpoint: Does this fit what they already approved?
Step 3: Name the tradeoff
Offer: keep scope, defer work, or add fee and time.
Checkpoint: Did you give clear choices?
Step 4: Confirm in writing
Send a short recap and wait for approval before billable work.
Checkpoint: Do you have a dated reply?
Step 5: Save the record
Archive emails, files, and invoices for the same client or next job.
Checkpoint: Could you rebuild the timeline quickly?
Step-by-step guide
- List all deliverables with links and version.
- Document logins handed over (never share your personal accounts).
- Write a short how-to for anything the client must maintain.
- Email the handoff pack and ask for written receipt.
- Invoice final balance with the same email thread.
- Set support boundary: "Bug fixes 7 days; new work is quoted."
Common mistakes
| Missing item | Risk |
|---|---|
| No receipt email | "Never got files" |
| Mixed personal/client logins | Security nightmare |
| No support window | Free forever fixes |
| Final invoice separate thread | Payment delay |
Real-world example
VA finishes a Shopify tweak pack, sends Loom + doc + zip, asks client to reply "received." Final invoice attached. Client approves. No March argument about missing assets.
Final thoughts
You do not need perfect systems. You need repeatable ones. Start with one client, one template, one week of proof.
How Salag helps
- Late Fee Calculator: Model late terms
- Project Scope Calculator: Confirm scope closed
- Scam Pattern Detector: Verify client at close
Move safer. Not faster.
In short
project handoff freelance in plain terms: Close projects cleanly: files, access, instructions, and proof the client received everything. Use Salag's ANCHOR Protocol as your five-step checklist.
See what to include in a welcome packet for the flip side of onboarding.
Common questions
project handoff freelance in plain terms: Close projects cleanly: files, access, instructions, and proof the client received everything. Use Salag's ANCHOR Protocol as your five-step checklist. See what to include in a welcome packet for the flip side of onboarding.
Write what was asked, what was agreed, and what changed. Do not bill on vague terms.
Use plain English, written recaps, and calm boundaries. Trust beats being the cheapest.
Yes for anything billable. At minimum, email a confirmed recap before work starts.
Offer flexibility inside a clear process: change orders, milestones, or a short alignment call.
ANCHOR is Salag's five-step flow: facts, agreement, tradeoffs, written yes, saved records.
When patterns repeat: unpaid add-ons, approval delays, or refusal to confirm in writing.
Yes. Deliverables, dates, price, and limits in email beat chat-only agreements.
Protection-first tools, agreement builders, and scope checkers help you set terms early.
Use Salag checklists and calculators that match your task, linked in the article.
Most setups fit in one kickoff call plus a five-minute recap email.
Retainers need ongoing habits. Projects need milestone checkpoints. Both need writing.
Pause billable work on unclear items and send a narrow written summary they can approve.