How to Deliver Files to a Client Safely (VA Handoff Checklist)

Why "I sent it already" fails so often

Filipino VAs usually work across US time zones. Delivery happens while the client sleeps. By morning, three things go wrong:

• The link was in Slack/Viber and scrolled away
• The Drive file was still named final_FINAL_v3
• Edit access stayed open, so someone "fixed" your work and blamed you later

Safe delivery closes those gaps before the invoice.

This guide is about the file handoff. For the wider proof system (time logs, approvals, weekly summaries), use How to Document Your Work So Clients Can't Dispute It.

---

The safe handoff checklist (copy this)

Use this for every milestone, not only "big" projects.

ScriptCopy

Subject: Delivery — [Client] — [Milestone / Week of YYYY-MM-DD]

Hi [Name],

Uploaded the final files for [milestone]:

• [File 1 name + version]
• [File 2 name + version]

Folder: [link] Access: View only (comment if you need notes)

Please review by [Day, Date, Timezone]. If I do not hear otherwise by then, I will treat this delivery as accepted per our agreement and send the invoice for [amount / period].

Thanks, [Your name]

Send that email even if you also ping them on chat. Chat is the reminder. Email is the record.

---

Step 1: Agree the delivery channel once

During onboarding, pick one primary channel:

Write the channel into the agreement or welcome packet so nobody invents a fourth place mid-month.

---

Step 2: Separate drafts from Final Delivery

A clean tree beats a clever naming scheme:

CodeCopy

ClientName/
  2026-09/
    01-Drafts/
    02-For-Review/
    03-Final-Delivery/
    04-Client-Uploads/

Rules that prevent fights:

• Only put billed outputs in 03-Final-Delivery
• Never overwrite a final file — upload Report_v2.pdf beside Report_v1.pdf
• Keep client source files in 04-Client-Uploads so their assets are not mixed with your deliverables

If the client insists on one flat folder, still prefix finals with FINAL_ and keep a private archive copy.

---

Step 3: Lock access when work is final

Open edit access is useful during collaboration. It is dangerous after delivery.

Before you send the delivery email:

1. Confirm the files in Final Delivery are the ones you will invoice
2. Switch share settings to Viewer (or Commenter if they must annotate)
3. Remove "anyone with the link can edit" unless the agreement says otherwise
4. Screenshot or note the share settings if the client is dispute-prone

You are not being difficult. You are stopping silent edits that rewrite history.

---

Step 4: Name files like an adult

Bad: asdf.docx, newlogo.png, presentation (1).pptx

Better pattern:

[Client]_[Deliverable]_[YYYY-MM-DD]_v1.ext

Examples:

• Acme_WeeklyReport_2026-09-15_v1.pdf
• Acme_ShopifyProductCopy_Batch03_2026-09-15_v2.docx

Version in the filename, not only inside the doc. Clients forward files; metadata gets stripped.

---

Step 5: Send a delivery receipt, not just a link

Your delivery email should answer four questions without a reply:

1. What was delivered?
2. Where is it?
3. What version is official?
4. When does review end?

Optional fifth line for retainers: "Hours for this package: [X] — see time log export attached."

That single habit pairs cleanly with invoice line items later.

---

What about sensitive files?

Client brand kits, customer lists, medical PDFs, payroll CSVs — treat them as confidential by default.

Practical rules for Filipino freelancers:

• Prefer client-owned storage over your personal Drive for confidential packs
• Do not forward sensitive files to your personal Gmail "for backup"
• Do not upload client PII into random AI tools to "summarize faster"
• If you must use WeTransfer/similar, use expiring links and still send the delivery email with the file list
• After the job, ask whether to delete local copies — and follow their written instruction

If a client emails passwords in plain text, move credentials to their password manager and confirm in writing that you will not store them in chat forever.

---

WhatsApp, Viber, and "quick send" traps

Common PH VA pattern: client asks for a file at 11pm, you send it on WhatsApp, they say thanks, then next week finance asks for "the official delivery."

Fix:

1. Send the quick chat file if speed matters
2. Within 24 hours, place the same file in Final Delivery
3. Send the delivery email referencing the chat ("Confirming the file sent on WhatsApp is now in the delivery folder as v1")

Now chat speed and email proof both exist.

---

Review windows that close the loophole

Without a deadline, "still reviewing" can last forever — and so can payment delays.

Put review windows in the agreement, then repeat them on every delivery:

• Small tasks: 24–48 hours
• Weekly retainer packs: 2 business days
• Large design / site builds: 5 business days (or milestone-specific)

Example clause language you can adapt:

ScriptCopy

Client will review deliverables within [X] business days of written delivery notice. Absence of written objections within that window counts as acceptance for invoicing that milestone.

Not legal advice — have them accept it in your Agreement Builder packet before work starts.

---

Mini example: two handoffs, two outcomes

Maya (unsafe): Drops final.pptx in a shared Drive, texts "uploaded," invoices Friday. Client edits the deck Monday, claims Maya delivered the wrong version, delays payment two weeks.

Jonas (safe): Uploads Client_Q3Deck_2026-09-15_v1.pptx to Final Delivery, sets view-only, emails the file list + Wednesday review deadline, archives the thread, invoices after silence. Client asks for a tweak Thursday — Jonas bills revision time under the revision clause instead of arguing about what "final" meant.

Same skill. Different paper trail.

---

Common mistakes

1. Personal Drive forever — client loses access when you change passwords or leave the engagement
2. Edit left open — your "final" mutates after delivery
3. No file list in email — link-only notices are weak proof
4. Mixing drafts and finals — client cherry-picks an old draft during a dispute
5. Deleting the thread after payment — keep archives for BIR, loans, and chargebacks

---

30-minute setup for your next client

1. Create the four-folder tree (or client Drive equivalent)
2. Add the delivery channel + review window to your agreement
3. Save the delivery email template in your notes
4. Practice one dry-run handoff on a dummy folder
5. Attach the habit to invoicing: no delivery email → no invoice

---

How Salag helps

• Agreement Builder — lock delivery channel, revision rules, and review windows before work starts
• Work receipt / executive update tools — weekly summaries that point to the same delivery links
• Invoice Generator — invoice only after the handoff email exists
• Document work clients can't dispute — full proof-trail system around this handoff

Safe delivery is boring on purpose. Boring handoffs get paid.

Move safer. Not faster.