Mac client handoff checklist: files, load, access
A handoff is complete when the final file set, destination copy, and client access agree. Local system activity and a finished upload bar are supporting evidence, not proof on their own.
The short answer: record the final source folder and expected file set, use system load only as context for unfinished local work, stage the send-now files, verify the destination copy, and confirm the client can access it before cleanup.
A useful acceptance record has five fields: source folder, expected filenames or count, local task status, destination account and path, and access result. Each field answers a different question. None substitutes for another.
Disclosure: I build TeenyApps, including TeenyStat for CPU, memory, and fan visibility and TeenyShelf for temporary file staging. My bias is toward small native Mac utilities. Apple's Activity Monitor and Finder still own the deeper diagnosis and permanent file system.
Keep the handoff evidence separate
| Evidence | What it proves | What it does not prove |
|---|---|---|
| Final source folder | Which local folder owns the deliverables. | That every expected file is present or current. |
| Expected file set | Which names, versions, or file count should leave the Mac. | That the destination received the same set. |
| CPU and memory snapshot | Aggregate system load at a stated time. | Which task caused it or whether an export finished. |
| Staged send-now set | Which files you intend to move next. | That a copy exists at the destination. |
| Destination receipt and access | Where the files landed and whether the client can open them. | That local scratch files are safe to remove under your retention policy. |
01Record load without treating it as completion proof
An export, compression job, preview render, or archive build can keep the Mac busy. Record system load if you need context, but check the responsible app and its output before deciding that the task finished.
TeenyStat is useful as a first signal because it keeps CPU usage, memory usage, and fan speed visible from the menu bar. Its local Swift source reads CPU through host_processor_info, reads memory through macOS host statistics, polls every 3 seconds by default, and reads fan RPM through SMC on Macs with fans.
Those are aggregate signals. They do not identify the process causing the load, show disk or network progress, or confirm that a deliverable is complete. Open Activity Monitor when you need process names, CPU time, or memory pressure. Then verify the expected output in the app or destination.
For a repeatable pre-call record, use the Mac demo performance baseline for CPU and memory. It separates the workload, observation window, aggregate readings, and Activity Monitor follow-up.
02Define the final set in Finder
Make the permanent project folder the source of truth before you create a temporary send-now set. Record the expected filenames, versions, or file count. If size matters, record that too. A destination check is much easier when you know what must match.
Use names that identify the client, project, date, and version, such as acme-dashboard-2026-08-13-v04-review.zip. Avoid renaming a file after staging it because the source record and staged set will no longer agree.
If a local task still appears stuck, use the narrower wait-or-quit guide before touching Force Quit. A high aggregate reading alone is not a quit or wait rule.
03Check the final set before staging
Open the source folder and compare it with the expected set. Check the file names, count, versions, and any required readme or notes. For an archive, confirm you selected the intended folder before compressing it.
If the handoff is a compressed archive, verify the ZIP file on your Mac before sending it. Expand a clean copy, compare it with the source set, and record the destination identity before cleanup.
Apple's Finder guidance covers creating folders, keeping related files together, tagging, and drag-and-drop movement. That is still the baseline. If Desktop is already acting as the handoff queue, use the Desktop clutter evidence check to separate visual organization, iCloud transfer state, storage, and live system load before moving the final set.
04Stage only the send-now set
A project folder can hold old drafts, exports, source files, working notes, screenshots, installers, PDFs, and invoices. The handoff set is smaller. It is the set of files that needs to leave your Mac now.
TeenyShelf fits that short window. Normal Finder drops are stored as local bookmark-backed references, not duplicate deliverables. File promises from apps that generate a file during the drop are materialized under TeenyShelf's Application Support folder. In both cases, a shelf item proves local availability for the next drag. It does not prove destination receipt.
Use the shelf for the final zip, PDF, images, readme, or installer while you switch to a client portal, browser upload form, email draft, or chat thread. Then clear the shelf after the destination is verified. For the file-staging version of this workflow, read prepare client handoff files on Mac without using Desktop.
05Verify destination receipt and client access
A 100 percent progress bar is a local application state. Open the destination and confirm the account, folder, portal, or message thread. Compare the received names and count with the expected set. Open or preview a destination copy when the service allows it.
Client access is a separate check. Confirm the intended account or recipient has permission to open the destination, not merely that you can see it while signed in as the owner. Record the result and any exception.
Clear temporary staging only after receipt passes. Keep the final project folder until client access is confirmed or your documented retention policy permits archival or removal.
Mac client handoff acceptance record
- Write down the permanent source folder.
- List the expected filenames or record the file count and version.
- Confirm the local export, build, archive, or compression result in the responsible app.
- If load needs investigation, record the time and aggregate readings, then use Activity Monitor for process details.
- Stage only the expected send-now set.
- Record the destination account and path before upload or transfer.
- Compare the destination names, count, and preview with the expected set.
- Confirm client access, then clear temporary staging under your retention policy.
Common questions
What should I check before sending files to a client from a Mac?
Record the final source folder and expected file set, use system load only as context for unfinished local work, stage the send-now set, verify the destination copy, and confirm the client can access it before cleanup.
Can CPU or memory usage prove that a client export is finished?
No. Aggregate CPU and memory values show system load, not whether a specific export, upload, or archive has completed. Check the responsible app or process and verify the resulting file or destination separately.
Where should client handoff files live on a Mac?
Keep final client files in a named Finder project folder. Use temporary staging only for the smaller send-now set, and keep the source folder until destination receipt and client access are confirmed.
Sources checked
- TeenyStat claims were checked against the TeenyStat homepage and local Swift source for CPU reads, memory reads, fan reads, polling interval, and menu bar visibility.
- TeenyShelf claims were checked against the TeenyShelf homepage and local Swift source for file references, security-scoped bookmarks, file promises, Quick Drop, capacity, duplicate handling, local persistence, and file-promise cleanup.
- Apple Support: View CPU activity in Activity Monitor on Mac.
- Apple Support: View memory usage in Activity Monitor on Mac.
- Apple Support: View information about Mac processes in Activity Monitor.
- 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.
Make client handoffs less fragile.
TeenyApps are small native Mac menu bar utilities for clipboard history, per-app audio, mic mute, screen time, displays, colors, screenshots, system stats, local tools, and file staging.