What a Drawing Transmittal Note Should Contain on a Steel or Conveyor Job
A drawing transmittal note on a steel or conveyor job should act as an ordering pack. It should tell the customer what to order, give them the drawings and files they need to order from, and show every drawing at its current revision. It should not be treated as a simple list of drawings.
For a fabricated job, that difference matters. One conveyor or platform assembly can include laser cut plates, folded items, steel sections from a stockholder, and fixings from a separate schedule. If the drawing issue is wrong, the wrong thing can be ordered.
I have seen the same problem crop up on busy projects: the design work is under control, the drawings are being issued, but the transmittal becomes a manual admin job at the worst possible time. Someone checks file names, revision letters, PDFs, DXFs, folded part drawings, steel section details, and the fixings schedule. Then they build the email, attach the right files, and hope nobody has picked up an old revision from the job folder.
That is why we treat the drawing transmittal note as part of the production route, not a document control afterthought.
The transmittal is an ordering pack, not a drawing list
On a small job, a drawing list might get the job done. On a fabricated steel or conveyor job, it usually is not enough.
A proper transmittal needs to answer practical buying and manufacturing questions:
What is being issued?
What revision is each drawing at?
Which files are for ordering?
Which parts go to the steel stockholder?
Which parts go to laser cutting?
Which items need folding?
Where is the fixings schedule?
What is the customer expected to do next?
That last point is often missed. A transmittal note is not just evidence that drawings were sent. It should give enough context for the customer to place orders from the right issue.
If a conveyor side plate has moved from Rev A to Rev B, that matters. If a folded guard bracket has changed bend detail, that matters. If a steel section drawing has been updated after a clash or setting-out change, that matters.
The customer may be ordering from several suppliers. The pack needs to hold those routes together.
That is why the note should show the current revision for each drawing, not just the drawing number. A drawing number without the revision is only half the answer.
What should be included
The content should match the way the job will be bought and made. A fabricated conveyor or platform is rarely one neat drawing package. It is usually a mix of items, each with a different ordering route.
Pack item | What the transmittal should contain | What the customer does |
Steel | Current revision steel fabrication drawings, section details, quantities where shown, and the files needed to order stockholder material for cutting and drilling on an auto or CNC line | Orders the correct sections from the current issue and passes the right information to the stockholder or processor |
Laser cuts | Current revision drawings and cutting files for plates, brackets, cleats, guards, or conveyor parts that go to laser cutting | Sends the right issue to the laser cutter and checks that the file issue matches the drawing issue |
Folded items | Current revision drawings for folded parts, with the related files needed for manufacture | Orders folded parts against the correct revision, including any changed bend, hole, or profile detail |
Fixings schedule | A separate current schedule for bolts, nuts, washers, anchors, and other fixings where required | Orders fixings from the schedule rather than expecting them to be drawn |
What the customer does | A clear instruction on the purpose of the issue, such as for approval, for pricing, for ordering, for manufacture, or for record | Acts on the issue for the stated purpose and avoids mixing it with older packs |
This is the heart of a good transmittal note steel fabrication process. It is not trying to explain the job. It is making sure the right people order from the right information.
For steel and conveyor work, I would expect the pack to include:
Project name or reference
Customer name
Issue date
Purpose of issue
Drawing number
Drawing title or description
Current revision
File type or package type where useful
Notes on included supporting files
Separate reference to the fixings schedule
Clear sender details
A short instruction for the customer’s next action
The note should also make clear what has been issued now. That sounds obvious, but it is where a lot of confusion starts. If only three drawings changed since the last issue, say so. If the full pack has been reissued, say that instead.
There is no need to make it elaborate. A transmittal note template that forces the same fields every time is usually better than a long free-text email.
Why revision control on drawings is the real issue
On fabricated work, revision control drawings are not just a quality record. They are purchasing control.
A wrong revision can mean the wrong plate gets cut, the wrong fold gets ordered, or the wrong steel section detail goes to a processor. Once that order is placed, the transmittal has already done its job, either well or badly.
This is why I prefer the transmittal to show every drawing at its current revision, even where only part of the package has changed. It gives the customer one place to check the issue they should be using.
A typical conveyor package might contain:
General arrangement drawings
Conveyor fabrication drawings
Platform or support steelwork drawings
Laser cut part drawings
Folded item drawings
Cutting or profiling files
A fixings schedule
Issue notes and purpose
The risk is not only the formal drawing revision. It is also the loose file in the job folder, the old PDF saved in a downloads folder, or the DXF that no longer matches the drawing. A drawing transmittal note should bring those items back into one controlled issue.
That does not mean the transmittal does engineering work. It does not decide whether a design is right. It records what has been issued, at what revision, and for what purpose.
Engineering and sign off stay with people.
The manual version works, but it costs time
The old way is familiar.
A project manager or engineer finishes a batch of drawings, then spends an hour building the transmittal. They check the drawing register, open the folder, compare revisions, attach files, write the email, and send it out.
On one issue, that is manageable.
Across a live project, it adds up quickly. At around an hour per issue, a project with repeated drawing drops can easily use about 20 hours just compiling and issuing packs.
That time is often taken from the same people needed for checking, coordination, supplier calls, and customer updates. It also tends to happen when everyone is already busy.
I have no problem with manual checks. They are essential. The problem is manual assembly. Copying drawing numbers, checking file names, and building the same pack format again and again is not the best use of an engineer’s or project manager’s time.
The transmittal needs discipline, but it does not need drama.
How we automate the pack and keep the human check
The automation we use is deliberately narrow. It does not carry out engineering. It does not approve drawings. It does not replace sign off.
It builds the branded transmittal from fixed inputs, prepares the email, and leaves a person to check it before anything goes out.
The process works like this:
Drawings go into the job folder inbox
The team saves the drawings and related files into the correct incoming folder for that job. This keeps the source in one place rather than spread across emails, downloads, and personal folders.
A short form records the purpose
The person issuing the pack records why the drawings are being sent. For example, the issue might be for approval, for pricing, for ordering, for manufacture, or for record.
The hour check picks up the issue
On the hour, the agent checks the inbox for new issue-ready content. It works from the fixed folder route and the fixed form inputs.
The branded transmittal is built
The system creates the drawing transmittal with each drawing listed at the correct revision. It uses the agreed template, so the layout and fields stay consistent.
The email is set up
The email is prepared with the pack and wording in place. The person responsible for the issue does not have to build it from scratch.
A person checks the pack
Before sending, a human checks the transmittal, the attachments, the revisions, and the purpose of issue.
The email is sent only after that check
The issue goes out after the responsible person is satisfied. Engineering judgement and project sign off stay where they belong, with people.
That is the full scope. Fixed template. Fixed inputs. Human check.
This is useful because the task is repetitive and rule-bound. It is not useful because software is clever. I do not want a tool making assumptions about a fabrication package. I want it to follow a controlled path and then stop for a person to review it.
The guardrails matter more than the automation
Most people in fabrication and automation have heard too much hype around AI. That is fair. A live engineering project is not the place for vague promises.
The only way this works is with tight guardrails.
The template is fixed. The inputs are fixed. The job folder route is fixed. The purpose of issue comes from a short form, not from guesswork. The person sending the issue still checks it.
That means the automation handles the dull assembly work. It does not decide whether the drawing should be issued. It does not alter the drawing. It does not sign off the package. It does not create fixings drawings. Fixings come through a separate schedule.
That separation is important.
The value is in getting a consistent fabrication drawing package ready for review without someone spending an hour assembling it by hand every time. The human review remains part of the issue process, rather than a nice extra if there is time.
For document control engineering projects, this is the sensible middle ground. Use automation where the work is structured. Keep responsibility with the person who understands the job.
What I would not put in the transmittal
A transmittal should be clear, not bloated.
I would avoid adding long explanations that belong in an email or design note. I would also avoid mixing old and new issues in the same pack unless the reason is very clear.
A transmittal is not the place for:
Design calculations
Commercial negotiation
General project history
Informal comments that change the meaning of the issue
Supplier instructions that conflict with the drawing
Unchecked files
Old revisions kept in the same issue pack without explanation
It also should not become a substitute for a drawing register. The transmittal records what is being issued now. The drawing register records the wider drawing history.
Both have a role, but they are not the same document.
A drawing issue notification can be short and still be complete. It needs the right fields, not more words.
The customer should see a clear next action
The best transmittals make the next step obvious.
If the issue is for ordering, the customer should know which files to send to which supply route. If it is for approval, they should know that no ordering should take place from that pack. If it is for manufacture, they should know it is the live issue for production.
This matters on conveyor and platform jobs because one assembly may be split across several routes:
Steel sections from a stockholder
Sections cut and drilled on an auto or CNC line
Plates sent for laser cutting
Components sent for folding
Bought-out fixings ordered from a schedule
The transmittal joins those routes together. It gives the customer a controlled pack rather than a folder of parts.
That is also why revision letters need to be visible. The customer should not need to open five drawings just to work out whether they have the current issue. The transmittal should tell them.
The cost to the customer
This process adds no cost to customers.
It sits inside the way we issue work. The customer receives the branded pack and email in the usual way, but the preparation is handled through a fixed process before the human check.
For the customer, the benefit is simple: they receive a clear issue pack showing what has been sent and what revision each item is at.
For the project team, the benefit is time. A task that can take about an hour per issue no longer needs to be built by hand from a blank email and a folder search. On a project with repeated issues, that can account for roughly 20 hours of admin assembly.
The check still happens. The responsibility still sits with the project team. The difference is that the person checks a prepared pack rather than constructing the whole thing manually.
FAQ
Should a transmittal include every drawing or only changed drawings?
For ordering packs, I prefer showing every drawing in the current issue, with its current revision. If only changed drawings are attached, the note should make that clear. The customer needs to know what they can order from.
Should fixings be shown on drawings?
On this process, fixings are not drawn as separate fixings drawings. They are issued through a separate fixings schedule. The transmittal should reference that schedule clearly.
Can the transmittal replace the drawing register?
No. The transmittal records what has been issued at a point in time. The drawing register records the broader drawing history across the project.
Does the automation approve or check the engineering?
No. It builds the pack from fixed inputs and prepares the email. A person checks it before sending. Engineering and sign off stay with people.
What is the main thing to get right?
The current revision. If the wrong revision goes out for ordering, the wrong thing can be ordered.
The takeaway
A good transmittal is not fancy. It is controlled, clear, and built around how the job will be ordered.
For steel fabrication drawings and conveyor fabrication drawings, the pack needs to cover steel, laser cut parts, folded items, and the fixings schedule. It needs to show the current revision for every drawing. It needs to tell the customer what action to take.
The automation should only do the repeatable part: assemble the branded pack, list the drawings at the right revision, and prepare the email. The person still checks it. The person still signs off the issue.
That is the balance I trust on a live fabricated job: controlled inputs, a fixed template, and a human check before the pack leaves the building.
Comments