Prepare client handoff files on Mac without using Desktop
A client handoff goes wrong when drafts, finals, screenshots, and uploads all share the same messy landing zone. Keep the real files in Finder and stage only the files that need to leave your Mac.
The short answer: keep final client deliverables in a named Finder folder, make filenames unambiguous, stage only the files that need to be sent right now, verify the upload or message destination, then clear temporary staging after the client can access the files.
Disclosure: I build teenyshelf, a Mac menu bar shelf for temporary file staging. My bias is toward keeping Desktop out of client handoffs. Finder is still where finished work belongs.
Quick handoff table
| Step | Use Finder for | Use a shelf for |
|---|---|---|
| Collect finals | Named project folder, final zip, PDF, images, source notes, invoice attachments. | Nothing yet. The file set is not ready to move. |
| Check names | Client, project, date, version, and destination in the filename. | A small staged set after the names are final. |
| Send files | The source of truth if you need to recheck or replace a file. | Drag files into a portal, browser upload form, email, chat, or review app. |
| Clean up | Keep the final project folder until the handoff is confirmed. | Clear temporary staged files after the destination is verified. |
01Start with a Finder folder, not Desktop
A client handoff needs one permanent place before it needs one temporary path. Create the Finder folder first. Put the finished zip, PDF, screenshots, installers, readme, and supporting notes there before anything is dragged into a browser or message.
The folder name should answer three questions without opening it: client, project, and handoff date. A name like acme-dashboard-handoff-2026-06-18 is dull in the best way. Tomorrow, you will know what it is.
Apple's Finder guidance covers organizing related files in folders, using drag and drop, and applying tags. That is the right baseline. TeenyShelf is for the short movement between the folder and the destination, not for replacing the folder.
02Name files for the person receiving them
Client handoff filenames should be boring and specific. The recipient should not need your context to tell which file is current. Include the client, project, date, version, and purpose when those details matter.
Examples: acme-dashboard-2026-06-18-v04-review.zip, acme-logo-pack-2026-06-18-final.pdf, or acme-install-notes-2026-06-18.md. If you use "final," make sure it is truly the version you can defend.
When the handoff is a ZIP archive, use the ZIP staging workflow so the finished archive moves from Finder to the destination without becoming another Desktop leftover.
Do this before staging. A shelf can keep the right files close, but it cannot make a vague filename safe.
03Stage only the send-now set
The project folder may contain drafts, working notes, source assets, exported variants, invoices, and screenshots. The send-now set is smaller. It is the set of files that must move into the client portal, browser form, email, chat, ticket, or review app right now.
teenyshelf fits that narrow job. Its homepage describes a menu bar drag-and-drop staging area with Option+Shift+S to open the shelf and Option+Shift+D to Quick Drop selected Finder files. The local Swift source confirms that normal file drops are stored as local file references with security-scoped bookmarks, not copied into a new permanent folder.
That keeps the source of truth clear. Finder owns the final file. The shelf only holds the short-lived handoff set while you switch apps. For browser portals, the Mac upload staging guide adds a file-count and portal-queue check before cleanup.
04Handle files from Mail, Photos, and review apps carefully
Some Mac apps do not give you a plain file path at the start of a drag. They provide a file promise, which means the source app creates the file when the drop target accepts it.
TeenyShelf accepts file URLs and file promises. Its source uses NSFilePromiseReceiver for promised files, writes them into a unique file-promise directory, stores a shelf item for the materialized file, and later removes stale promise directories that are no longer referenced.
For client work, that matters when a screenshot, attachment, export, or photo needs to move into a delivery channel without first becoming Desktop clutter. If the file should be permanent, move it into the Finder project folder after it materializes.
05Verify the destination before clearing anything
Do not mark the handoff done when the drag finishes. Open the destination. Check the account, folder, thread, recipient, permissions, and visible file name. If the file is a zip, compare the size. If it is a PDF or image set, open one file from the destination when possible.
Then clean up in layers. Clear the shelf first. Delete throwaway duplicates and scratch exports next. Keep the Finder project folder until the client confirms access or your retention rule says the files can be archived.
If the Mac was under load during export or upload, use the TeenyApps hub Mac client handoff checklist to pair file staging with system-load checks. If an app looked frozen during the work, the TeenyStat guide on whether to wait or quit when CPU is high covers that decision.
Seven-step client handoff routine
- Create a named Finder folder for the client handoff.
- Move final files, readme notes, and supporting deliverables into that folder.
- Rename files so the version, date, and destination are clear.
- Stage only the files that need to be sent now.
- Drag the staged files into the portal, browser upload form, email, chat, or review tool.
- Verify the destination, file names, preview, permissions, and account.
- Clear temporary staging after the handoff is confirmed.
Common questions
Where should client handoff files live on a Mac?
Final client files should live in a named Finder project folder. A temporary shelf is useful only for the short handoff window when the same files need to move into upload forms, email, chat, or review tools.
Should I use Desktop as a client handoff folder?
Use Desktop only when visibility is the main need. For client handoffs, Desktop makes it too easy to mix drafts, final files, screenshots, and leftovers. Keep permanent files in Finder and stage temporary files separately.
Does TeenyShelf upload or copy client files to the cloud?
No. The app website states no analytics, no telemetry, and no cloud sync. For normal drops, teenyshelf stores local references to the original files rather than uploading them.
Sources checked
- TeenyShelf homepage and TeenyShelf Swift source for drag-and-drop staging, Quick Drop, file references, security-scoped bookmarks, file promises, capacity, privacy, pricing, and trial details.
- Apple Support: Organize files in folders on Mac.
- Apple Support: Drag and drop items on Mac.
- Apple Support: Use tags to organize files on Mac.
- TeenyApps: Mac client handoff checklist for files and system load.
- TeenyStat: Mac app not responding but CPU is high.
Stage client handoff files without using Desktop.
teenyshelf is $4.99 once with a 3-day free trial. Drop files onto the menu bar icon, switch to the destination, then drag them out.