Prepare client handoff files on Mac without using Desktop
Keep the permanent source set in Finder, write a send-now manifest, and treat the shelf as local staging. The destination copy and client access still need their own checks.
The short answer: record the Finder source folder and expected filenames or count, stage that send-now set, check for skipped or missing items, verify the destination copy against the manifest, and confirm client access before clearing temporary staging.
A shelf item proves that TeenyShelf has a local path or reference available for the next drag. It does not prove that the destination received the file or that the client can open it.
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.
Separate the source, staged set, and receipt
| State | What it proves | What it does not prove |
|---|---|---|
| Finder source manifest | The expected names, count, versions, and permanent folder. | That those files were staged or delivered. |
| Normal shelf item | A bookmark-backed reference points to the original local file. | That a duplicate copy or remote upload exists. |
| Promised shelf item | The source app materialized a local file for TeenyShelf. | That it was moved into the permanent project folder. |
| Destination receipt | The expected names, count, or preview appear in the intended account and path. | That the client's account has access. |
01Write the send-now manifest in Finder
A client handoff needs one permanent place before it needs temporary staging. Create the Finder folder first. Record its path plus the expected filenames or file count. Add versions or sizes when they are needed to distinguish the final set.
The folder name should identify the client, project, and handoff date. A name such as acme-dashboard-handoff-2026-08-13 is easy to match with a delivery record later.
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.
02Confirm the final set before staging
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-08-13-v04-review.zip, acme-logo-pack-2026-08-13-final.pdf, or acme-install-notes-2026-08-13.md. If you use "final," make sure it is the version listed in the manifest.
When the handoff is a ZIP archive, use the ZIP staging workflow to expand-check one final archive, stage its Finder reference, and verify destination receipt without creating a Desktop copy.
Do this before staging. A shelf can keep the right files close, but it cannot make a vague filename safe.
03Stage the set, then compare the count
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. For normal Finder drops, its local Swift source stores file URLs with security-scoped bookmarks. The shelf points back to the original; it does not create a second permanent copy.
Compare the visible shelf with the manifest after the drop. Duplicate URLs are skipped. The default shelf capacity is 20, and a larger batch can be partly added when the remaining capacity is smaller than the batch. TeenyShelf reports an "Added X of Y files" capacity message in that case.
Finder remains the source of truth. If the original moves or disappears, a normal shelf reference can become unavailable. For browser portals, the Mac upload staging guide adds a portal-queue comparison before cleanup.
04Move promised files into the permanent set
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.
Each promised file is copied into a unique directory under TeenyShelf's Application Support folder, which prevents two same-named imports from overwriting each other. That app-managed copy is different from a normal bookmark-backed reference.
If the promised file belongs in the permanent client record, move or copy it into the Finder project folder and add it to the manifest before delivery. Unreferenced promised-file directories older than 30 days are eligible for the app's launch-time cleanup.
05Verify receipt and client access separately
Do not mark the handoff done when the drag finishes. Open the destination and confirm the account and path. Compare the visible names and count with the manifest. Check size or preview when it helps distinguish versions.
Then test or confirm access for the intended client account or recipient. Your owner view proves only that you can see the destination. Keep the Finder project folder until client access is confirmed or your documented retention rule permits archival.
Clearing the shelf removes TeenyShelf's staged items and local references. It is not a destination receipt. Clear it only after the receipt and access fields are complete.
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 context. When delivery follows a live review, record the pre-call workload and recovery with the TeenyStat Mac demo performance baseline. If an app looked frozen during the work, the TeenyStat guide on whether to wait or quit when CPU is high covers that decision.
Mac client handoff manifest checklist
- Record the Finder source folder and expected filenames or count.
- Confirm each expected file is final before staging.
- Stage the send-now set and check for skipped or missing items.
- Move promised files into the permanent Finder folder when needed.
- Record the destination account and path before transfer.
- Compare destination names, count, and preview with the manifest.
- Confirm client access before clearing temporary staging.
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 send-now set needs to move into an upload form, email, chat, or review tool.
Can the TeenyShelf item count prove that every handoff file is staged?
No. Duplicate URLs are skipped, and a batch can be partly skipped when the shelf reaches its capacity. Compare the shelf with an expected filename or file-count manifest and read any capacity message.
Does TeenyShelf upload or copy client files to the cloud?
teenyshelf does not upload client files. Normal Finder drops are stored as local bookmark-backed references. A file promise from an app such as Mail or Photos is materialized as a local copy in TeenyShelf's Application Support folder.
Sources checked
- TeenyShelf homepage and TeenyShelf Swift source for bookmark-backed normal drops, duplicate skipping, the default 20-item capacity, partial-add messages, unique file-promise directories, removal behavior, and unreferenced promise cleanup.
- 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.