A useful drawing handover tells the next person what the source is, what has changed and what they must issue. A folder full of attachments is not enough if the drafter has to guess which revision controls the work. Use this checklist before handing over an MEP drawing for production.
Start with one clear drawing task
Record the drawing number, title, discipline and source revision in the task. Give the marked-up PDF the same identity. If your mark-up was made on a different issue, explain the difference explicitly; do not assume the drafter will recognise a changed background from its appearance.
- Name the native drawing that is to be edited.
- Name the PDF containing the instructions.
- State the requested output revision and issue purpose.
- Identify the person who can answer design queries.
- State any deadline and dependencies before agreeing the programme.
Package the references, then check the package
Autodesk's eTransmit can collect a drawing and its referenced support files into a transmittal package. The official guide explains how to review the files and transmittal settings. A package still needs a practical check: confirm the required backgrounds and plotting resources are present, and open the drawing from the packaged location to look for missing references. See source 1.
Do not bind, flatten or remove references solely to make the folder smaller. That can change the structure someone needs for the next revision. Agree the receiving team's requirements first, including file format, units, plot style and whether reference paths should be relative.
Make the mark-up answerable
Use an arrow or cloud to identify the exact area. Give dimensions, levels, equipment references and intended connections where they matter. “Move this over” leaves both distance and direction open to interpretation. A clearer instruction identifies the item, destination, controlling dimension and any related drawing.
Separate confirmed changes from questions. For example: “Move grille G-14 to the dimensioned position shown; keep the existing reference. Confirm the branch route before drafting.” The first instruction is actionable; the second is an unresolved design decision. Neither should silently become the other.
Put recurring rules in project notes
Keep layer naming, title-block conventions, drawing numbering and output requirements in one project record. Keep task-specific changes beside the drawing. Copying a long standards paragraph into every upload makes it harder to tell which version is current.
- Confirm drawing units and sheet size.
- Identify the approved title block and revision convention.
- List the backgrounds and their revisions.
- State how superseded files should be identified.
- Specify the required editable and issued formats.
Define what a successful issue contains
Agree whether the task is a mark-up revision, an as-built update or a separately scoped redraw. These have different input needs. For an as-built update, the person supplying the site records must confirm the installed information; a drawing-office update does not itself verify concealed services.
Before final approval, compare the proof against the marked instructions. Check drawing identity, revision, legends, clipped text and the changes around revised areas. Resolve open queries or record the agreed exclusion. Retain the supplied pack and issued revision together so the next change starts from a known record.
The two-minute handover check
Ask someone who did not prepare the pack to identify the source drawing, changes, output and query contact. If any answer requires a phone call just to establish the basics, clarify the task before it enters production. This is a practical check, not a substitute for engineering review.