Prepare a CAD Handoff With Units and Reference Points

A CAD handoff is easier to review when the recipient can tell which file is current, what its dimensions mean and which features still need a decision. Put those details in a short companion record rather than expecting a filename or a screenshot to explain the model. The record can reveal a missing answer; it cannot make an unverified drawing ready for fabrication.
This guide uses an invented flat display bracket as a paper exercise. Nobody has designed, measured, manufactured or inspected that bracket for a client. The numbers below are examples of how to label a question, not dimensions to build from. The drawing owner and the intended recipient must agree on any actual specification.
Start with the file and the next decision
Write the name of the working file, its revision label and the person expected to respond. Then identify what the recipient is meant to do: review the shape, answer a measurement question, or provide an approved file for a later step. A review request and a production authorization are different outcomes. A document that combines them should make the difference visible.
Suppose a fictional exhibit team receives bracket-review-B and a separate image named bracket-review-A. The two labels suggest different revisions, but a filename alone doesn't establish which one the author intended to send. Mark the image as potentially out of date and ask the author whether it belongs with revision B. Don't update the record to “matched” because the outlines look similar.
List the deliverables separately: a working design file, an image intended for a quick visual discussion, and the companion questions. Record whether each item was supplied or merely requested. That distinction gives the recipient a way to notice a missing attachment before commenting on the shape.
The graphic asset handover addresses an approved visual asset and its uses. This CAD record addresses a different risk: the recipient may not yet know how the drawing's measurements and reference points are meant to be interpreted.
Put the unit beside every reported measure
Use the unit stated by the drawing owner. If the owner has not identified one, leave the unit unresolved. A number such as 120 isn't useful as a physical width until its unit and measurement endpoints are known. Don't infer millimetres from the size of an object on a screen or from a colleague's informal label.
For the fictional bracket, write “overall width: 120, unit and endpoints to confirm” when those details are missing. Once the author supplies both, record the exact answer and the revision it applies to. If a later revision changes the object, the answer may need another review; don't silently carry it forward as an approval of the new drawing.
If someone supplies a conversion, show the starting value, starting unit, calculation and resulting unit next to one another. The arithmetic can be checked separately from the question of whether the original unit was correct. A converted number is not evidence that the source drawing was measured accurately.
Mark the origin and the view used for a question
Give each observation a place. A question about a slot near one edge can refer to a named view and an agreed reference point instead of “the left hole,” which can become ambiguous when the drawing is rotated or viewed from the other side. A simple sketch with labels can accompany the question; describe it as a sketch, not as a measured survey.
In the invented example, the reviewer could ask: “In the front view of revision B, is the slot intended to be 12 units from the edge marked A?” This sentence deliberately leaves the unit unresolved. It also identifies the view and edge whose meaning the author needs to confirm. It does not state a tolerance, an acceptable material or a safe construction method.
When a feature is hidden, overlapping or absent in the view supplied, use a question rather than a guessed measurement. Ask for the relevant view or for a written explanation of the relationship. If the recipient cannot open the working file, record that limitation before treating a screenshot as an equivalent inspection.
Decide who can review the working file
Sharing a file and approving its contents are separate actions. Google Drive's access guidance distinguishes viewer, commenter and editor roles, while organization settings can limit sharing. Use those distinctions only when that service is actually being used; they don't tell you who has authority to approve a design.
Agree which person can receive the design, which person can propose a change, and who can answer the dimension question. A reviewer may be able to leave a comment without being the person who accepts the final specification. Avoid attaching unrelated client records to the question merely because the same folder is convenient.
For the imaginary bracket, the handoff might list the author as the person to answer the unit question and an organizer as the recipient of the visual review. Those roles are examples. No actual access grant or review has occurred.
Tie each question to a named revision
Google Docs' version-history guidance describes named versions and the access needed to inspect earlier edits. If the companion record is kept in that service, a named stage can identify the exact wording sent for review. It doesn't verify the design file or establish that a question was answered.
Use a small status table for each question: revision, feature, question, answer and decision owner. An empty answer remains empty. If the author revises the file before responding, link the response to the new revision and retain the earlier question as context. Don't mark every issue resolved because one file was replaced.
The project change log covers a broader assignment after a change is proposed. This record has a narrower job: keep an unanswered geometry or interpretation question attached to the drawing being reviewed.
Close with a review boundary
Before forwarding the handoff, check that the named files exist, the unit and reference points are either confirmed or explicitly open, and the intended reviewer can access the material. Ask whether the record needs a new review when a file changes. If any required detail is unavailable, say what is missing and who is expected to answer.
An approved-looking note is not a substitute for the drawing owner's specification, an engineer's review, a fabrication check or an inspection. Stop at the decision the record can support: the next person can see what was supplied and what remains unresolved.