What is a submittal package?
A submittal package is a batch of drawings or documents delivered together for review or handover, checked against the engineering drafting standard before it is accepted. On an infrastructure project it is how an as-constructed set, or any controlled issue of documents, moves from the party that produced it to the asset owner who has to accept it.
Also called: submission · handover package · drawing submittal
The unit of handover.
For the asset owner, a submittal package is the unit of handover. The contractor or draftsperson assembles the drawings, models, and supporting documents into one package and delivers it, usually under a transmittal that records exactly what was sent, and when.
Before the package is accepted, someone checks it against the drafting standard: the file names, the title blocks, the metadata tags, and whether every referenced file is present. If the package does not comply it is returned for correction and resubmitted, and it is common for a package to make three or four round trips before acceptance. Every rework cycle costs drafting time, and it costs more once the original draftsperson has moved to another project.
Validated on upload, not in an audit.
Lunr runs submittal packages through automated validation. The submitter uploads the package, Lunr runs the checks over it, and if it complies with the standard it is imported for QA review, otherwise it is rejected and returned to the submitter for correction. The rules are drawn from your CAD standard: file name validation, XRef validation, title-block validation, tag validation, and document number validation against pre-allocated placeholders.
Every package is validated against a manifest at handover, so a missing file is caught on upload rather than in an audit two years later. Title-block tags are read from the drawing itself and applied as metadata, so nobody retypes them, and packages are delivered and received as tracked transmittals with a cover sheet that lists exactly what was issued.
Keep reading.
How automated validation cuts the loop from handover to acceptance.
HandoverValidate every package against a manifest, and issue tracked transmittals.
As-constructed project deliveryBringing an as-constructed drawing project to completion in Lunr.
TransmittalThe controlled record of issuing documents to another party.
Questions about submittal packages.
- What goes in a submittal package?
- A submittal package holds the drawings, models, and supporting documents that make up one controlled issue, most often an as-constructed set at handover. Alongside the files it carries the information needed to check them: the file names, title blocks, and metadata tags the drafting standard calls for. It is usually delivered under a transmittal that records exactly what was sent, and when.
- What is the difference between a submittal package and a transmittal?
- A submittal package is the batch of documents itself, the drawings and files delivered together for review or handover. A transmittal is the controlled record of issuing that package to another party, listing what was sent, to whom, and when. In practice a package is delivered under a transmittal, so the two travel together: the package is the content, the transmittal is the proof of issue.
- Why are submittal packages rejected?
- Most rejections come down to the package not meeting the engineering drafting standard: file names that do not match the naming rule, a missing or non-standard title block, metadata tags that do not comply, or a referenced file left out. Manual checking catches these late, which is why a package can take three or four rounds before it is accepted. Validating the package against the standard on upload catches the defects early, while the draftsperson who produced the drawings is still on hand to fix them.
Validate every submittal package on the way in.
Book a walkthrough and watch Lunr validate a submittal package on upload, so defects are caught while the draftsperson is still on hand to fix them.
10M+ documents under management · Hosted in Australia and the US · SAML · Full audit trail · Export anytime
- entity
- Lunr Labs Pty Ltd
- location
- Melbourne AU
- workspace
- documents.lunr.app
- rev
- 2026