The difficult part of sending a CAD model is often not the upload. It is making sure the recipient knows which file to use, what it represents and what still needs confirmation. A folder called “latest” is not a revision policy.
Start with the recipient's task. A quote review, a fit check and a manufacturing release do not necessarily require the same package. Agree the file format and supporting documents before sending a collection of alternatives.
Identify the delivery in one short note
Put the part or assembly name, source revision, units, intended use and contact for questions in the handoff message. State whether the model is complete or a selected subset. If a drawing controls dimensions or requirements, identify its revision too.
An illustrative note might say: “Bracket Rev.B, millimeters, for quotation review. STEP and source CAD are from the same configuration. The fixture is excluded. Please raise questions against Rev.B rather than the earlier sample.”
This is not a legal approval template. It is a practical way to avoid two people discussing different files under the same project name.
Send the file set, not just the top-level assembly
Native assemblies may rely on external parts and subassemblies. Use an appropriate collecting workflow and keep the folder structure when references depend on it. SOLIDWORKS Pack and Go is one documented example of gathering related design files. Pack and Go overview.
For a neutral export, verify that the assembly scope and placements survived. A single file is convenient but not proof that the package is complete. List excluded or unresolved components instead of leaving the recipient to infer them from a picture.
A useful delivery layout is simple:
bracket-rev-b/
source/
exchange/
drawings/
delivery-note.txt
processing-report.csv
These folders are suggestions. Do not invent missing drawings or export logs merely to fill the structure.
Provide a preview and a source for different purposes
A lightweight preview helps someone inspect the shape before downloading an engineering file. It should not silently replace the agreed source or neutral deliverable.
A web visualization format can carry a renderable scene, but it is not a native CAD design environment. Khronos describes glTF as an asset-delivery format for loading scenes and models. glTF overview. Keep the preview labelled and link it to the exact version represented.
A colleague who only needs to review orientation may use the preview. A CAM or inspection workflow may need the engineering file and additional specifications. Give each recipient the required artifact rather than one format for every job.
Use fixed versions for externally shared work
A shared review should open the same version tomorrow that it opened today, unless the link was explicitly created to follow updates. Changing the contents behind a link can make an earlier comment appear to refer to geometry the reviewer never saw.
Treat a new upload as a new snapshot. Version systems such as Onshape distinguish saved versions from an active workspace; that separation is a useful model even for a much lighter file handoff. Versions and history.
When a replacement is issued, identify the new revision and make the relationship clear. Do not just overwrite a file named final.step.
Check permissions before sending the link
Confirm whether the recipient may view, measure, download the original, download a derivative or forward the link. Use the narrowest access appropriate to the task. An expiring link can limit future access, but it cannot recall a file already downloaded.
Search exclusion is not confidentiality. A page with noindex can still be accessible to anyone who knows its address unless there is actual access control. Google's indexing guidance.
If the organization does not allow cloud upload, use an approved transfer route. A tool cannot waive a customer's data-handling restrictions.
Finish with a recipient check
Open the link as a recipient or in a separate session. Confirm that the intended files and revision are visible and that unrelated versions are not. Test the allowed downloads and make sure the message explains any remaining limitations.
Do not treat a logged visit as formal acceptance. Ask for an explicit response through the agreed review or approval process when one is required. A clean delivery package helps that conversation; it does not replace it.
