Skip to content

Systems and records

Engineering submittal revision data: tie each approval to its revision

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Record the approval on the submittal number and revision number together, with a hash of every file in that revision, the reviewer's verbatim action, their authority and any variations the submitter declared in writing. Never overwrite a revision when the next arrives, and point field work to the revision that governed it. That makes it possible to prove which package an approval covered.

Document stack

Engineering submittal

This page covers engineering submittal revision data: tie each approval to its revision.Illustrative

Key takeaways

  • An approval belongs to one revision of one submittal, together with the variations disclosed in it, not to the submittal number.
  • Platforms differ on what carries forward; Procore, for example, does not carry attachments into a new revision.
  • Hash both the submitted files and the stamped return, and keep raw stamp wording beside a normalized action.
  • Partial approvals, changed-sheet resubmittals, approvals by email and reused numbers need their own flags.
  • Reviewer authority and project agreements decide what the records can be used for, so specialists check both before sharing.

How do you tie a construction submittal approval to its exact revision?

Store the approval on the pair of submittal number and revision number, and fingerprint the files that pair contained when the reviewer acted. An approval is a fact about one package of drawings, product data or samples on one date; it is not a property of submittal 08 44 13-003 in general. Every revision gets its own row, its own review action, its own reviewer and its own file hashes, and the record that work was built from points to the revision that governed it.

Most submittal logs blur this. The log shows the latest status against the submittal number, earlier revisions sit in a history tab, and the stamped PDF lives in a folder named after the submittal rather than the revision. When the data leaves the system as a flat export, the approval on revision 1 can look like an approval of revision 2, which is exactly the error an AI model or an auditor must not learn.

The rest of this guide gives a version and approval task structure an engineering or construction firm can use to prepare revision-level submittal records, a worked example with an exception, and the points where a specialist should look before the records go further.

Why does an approval stop at the revision it was stamped on?

Because the contract treats each approval as a decision on what was actually submitted, including any variations the submitter disclosed. The federal construction clause at FAR 52.236-21 is a clear public example. It requires the contractor to coordinate and review shop drawings and mark its own approval on them, says work done before the Contracting Officer's approval is at the contractor's risk, and says approval does not relieve the contractor of responsibility for errors or for meeting the contract, except for variations described and approved under the clause.

The same clause requires the contractor to describe any variation from the contract in writing, separate from the drawings, at the time of submission. That makes the variation statement part of what was approved. If revision 2 adds a substitution that revision 1 did not declare, the approval of revision 1 says nothing about it.

Private contracts and project specifications use their own wording, and many projects split approval authority. Unified Facilities Guide Specifications, for example, mark submittals that need Government approval with a G because of their complexity or criticality, while other items go through the contractor's quality control review. A revision-level record has to capture who had authority to act on that item, not only what the stamp said.

The practical consequence is a timeline, not a status. For any date on the project, the record should answer which revision of each submittal governed, whether that revision was approved outright or with conditions, and whether any work in place was built from a revision that was later superseded. A log that holds only the current status cannot answer those questions after the fact.

How do submittal platforms number and carry forward revisions?

Each platform increments a revision number, but what carries forward differs, and that decides what your export can prove. Check the behavior of the system your projects used before trusting any revision field.

Exports are where revision detail usually disappears. A list view or spreadsheet export often carries one row per submittal with the current revision number and status, while the history of earlier actions and their files sits behind each item. Ask for the item history and the files of every revision, or export them through the platform's own tools, before deciding that a project has usable revision data. Projects archived when a firm changed platforms deserve the same check, since migrations commonly carried only the latest revision forward.

  • Never rebuild revision history from file modified dates; a re-saved PDF looks newer than the review it records.
  • Keep voided and withdrawn revisions as rows with a status, so revision numbers have no unexplained gaps.
How do submittal platforms number and carry forward revisions?
SourceDocumented revision behaviorWhat it means for the recordCheck before export
Procore SubmittalsRevision number increases by one; a revision can be created only from the most current one; attachments are not carried overEach revision's files must be read from that revision, not inheritedConfirm every revision row has its own attachments or a stated reason it has none
Autodesk BIM 360 and Build SubmittalsA package revision is offered when an item is Rejected or Revise and Resubmit; approved items move to Closed; package and item revision numbers increase by oneItem and package revision numbers can divergeExport item-level revisions, not only the package number
ISO 19650 practice per UK BIM Framework guidanceRevision codes carry a P prefix for preliminary and C for published information, with a version suffixStatus and revision code together show whether a file was for review or publishedKeep the full code, not only the numeric part
Paper or email transmittalsNumbering follows the firm's own transmittal logRevision identity may exist only in a file name or stampRead the stamp and transmittal number from each PDF and record both

The version and approval task structure

The table is the field-level structure for one revision of one submittal. Fill one row set per revision, keep raw values beside normalized ones, and never overwrite a field when a later revision arrives. It has been written for engineering and construction submittals; a qualified reviewer at your firm should confirm the action codes and authority fields against your contract forms before use.

Specification sections are worth normalizing because they are the join key to everything else. MasterFormat has used a six-digit, fifty-division numbering system since 2004, so store the section number as text with its edition year rather than as a number that drops leading zeros.

Once the rows exist, the same structure supports task records that an AI team can test against: each task gives a model the inputs a reviewer had and checks its answer against what the record proves. The tasks below are examples of what revision-level data makes possible and log-level data does not.

  • Governing revision: given a submittal and a date, name the revision in force and its action.
  • Note carry-through: given an approved-as-noted revision and the next one, say whether each note was resolved.
  • Undeclared change: compare two revisions' files and flag changes the cover letter did not disclose.
  • Authority check: given the reviewer and the item's classification, say whether the action could approve it.
  • Field trace: given an installation record, identify which revision it was built from and whether that revision was approved.
The version and approval task structure
FieldWhat it holdsWhere it comes fromValidation rule
submittal_idProject-unique submittal number as issuedSubmittal logNever reused after void
revision_no and revision_codeNumeric revision plus any prefix or suffix usedLog and stampIncrements by one; gaps explained by a voided row
spec_sectionGoverning specification section and paragraphLog or cover sheetText with edition year, leading zeros kept
package_filesEach file in the revision with SHA-256 hash and page countAttachments of that revisionNo file inherited from another revision
declared_variationsWritten deviations or substitutions stated by the submitterTransmittal or cover letterEmpty only if the submitter stated none
review_action_rawStamp or response wording exactly as issuedReviewer stamp or response fieldVerbatim, including firm-specific codes
review_action_normalizedMapped action such as approved, approved as noted, revise and resubmit, rejected, for recordMapping table kept with the dataEvery raw value mapped once
reviewer_role and authorityWho acted and whether they could approve this itemLog, stamp and specification classificationAuthority stated, not inferred from job title
action_date and returned_dateWhen the reviewer acted and when the submitter received itLog historyAction on or before return
supersedes and superseded_byLinks to the previous and next revisionLog historyExactly one governing revision per item at any date

Worked example: a curtain wall anchor submittal through three revisions

This example is illustrative and invented for the purpose; it shows the structure, not a real project. A shop drawing submittal for curtain wall anchors goes through three revisions, and the field installs anchors before the last review is complete.

The exception is the Rev 2 row. The submitter fixed the note the reviewer asked for and, in the same package, changed the anchor spacing without saying so. A log keyed only on the submittal number would show the item as reviewed twice and approved, and a model trained on that log would learn that a note fix is all a resubmittal contains. The revision-level record keeps the undeclared change visible: the file hashes differ on more sheets than the cover letter mentions, the action is for record rather than approved, and the question on spacing stays open until Rev 3.

The field installation sits between the rows. Anchors went in under the conditional approval of Rev 1, so the record links the installation to Rev 1 and its note, not to the final approval. If an inspector later asks what the installers were working from, the answer is a specific set of files and a dated action, which is what the structure is for.

Worked example: a curtain wall anchor submittal through three revisions
RevisionPackage and declared variationsReview actionWhat the record must show
Rev 0Anchor layout and calculations, no variations declaredRevise and resubmit: embed depth not shownNo approval exists for any file in this revision
Rev 1Layout, calculations and embed detail; substitute anchor declared in writingApproved as noted: add edge distance note on sheet 3Approval covers these file hashes and the declared substitute, with the note as a condition
Rev 1 in the fieldAnchors installed from Rev 1 sheetsNo new actionInstallation record points to Rev 1 and its conditional approval
Rev 2Sheet 3 revised with edge distance note; a new anchor spacing appears without a written variationFor record, returned with a question on spacingApproval of Rev 1 does not extend to the new spacing; spacing remains unresolved
Rev 3Spacing reverted to Rev 1 and stated in the cover letterApprovedGoverning revision from this date; field work before it traced to Rev 1

The common failure is a change that travels without a new revision, or a revision that travels without its own approval. The cases below show up in real logs often enough that each deserves its own flag in the data rather than a cleanup by hand.

At a glance

Which exceptions break the link between an approval and its revision

Flag rather than fix. Correcting the source log changes the evidence, and a cleaned record that looks consistent can hide the very gap a reviewer or model should see. Keep the raw rows, add a flag column with the exception type, and write a short note when a person resolved the link by reading documents.

  • Partial approvals: some items in a package approved and others returned, recorded only at package level.
  • Changed sheets only: the submitter resends the sheets that changed, so the revision's files are a subset and the unchanged sheets must be linked from the earlier revision by hash, not copied.
  • Approvals outside the system: an email or meeting minute approves a change that never becomes a revision row.
  • Reused numbers: a voided submittal number reissued for different work.
  • Reverted workflow steps: a platform step reverted to fix a mistake, overwriting what the reviewer saw; Procore's own guidance discourages using reverts to manage revisions.
  • Split authority: the contractor's quality control approval recorded in the same field as the owner's or designer's approval.
  • Delegated design: an engineer's sealed calculations inside a contractor submittal, where the seal and the review stamp are separate approvals.

How should the reviewed files be fingerprinted?

Hash each file in the revision when it is captured, and store the hash beside the review action. A cryptographic hash such as SHA-256 changes when any byte changes, so a later dispute about which drawing the reviewer saw can be settled by comparison instead of memory. Python's standard library, for instance, provides hashlib.file_digest for hashing a file opened in binary mode.

Hash the submitted file and the returned stamped file separately. The stamp alters the PDF, so the two never match, and both matter: the submitted file is what was reviewed, and the stamped file is the evidence of the action. Record which is which, and record the page count, because a missing page is easier to spot by count than by hash.

Compute hashes on files exported from the system of record, not on copies passed around by email, which may have been printed to PDF or compressed along the way. Store the algorithm name with each hash so a later reader knows how to check it.

If the archive holds only stamped files, say so in the data. A dataset built from stamped copies can still teach review behavior, but it cannot prove what the submitter sent before the stamp was applied.

When does the record need a specialist reviewer before it leaves the firm?

Before revision-level submittals are shared outside the project team, a qualified engineer or construction manager should confirm the action mapping and authority fields, and counsel should look at the rights. Submittals combine the firm's work with the submitter's drawings, manufacturers' data and the owner's project information, and each party can have a claim.

Contract terms differ on who may use shop drawings. Under FAR 52.236-21 the Government may duplicate, use and disclose shop drawings delivered under the contract, but that clause applies to federal construction contracts and does not decide what a designer, contractor or fabricator may do with the same drawings on a private project. Read the agreement for each project, and treat de-identification as a privacy and confidentiality step that does not by itself create a right to license.

  • Stop and narrow the scope when the project agreement restricts use of project documents beyond the project.
  • Stop when stamps carry a professional seal and the sealing engineer's consent is unclear.
  • Narrow to the firm's own review comments and action codes when the submitted drawings belong to others.

Preparing revision-level submittal records for AI licensing

Revision-level records are what make submittal history useful to an AI team: each row shows a package, the reviewer's response to exactly that package and what changed in the next one. A log that only shows the latest status teaches far less.

An engineering or construction firm that wants to license revision-level submittal history can do it through SourceX, which handles rights review, contracting, preparation and delivery for the projects the firm chooses. A short company assessment, with no drawings uploaded, comes first, and no record is delivered until the firm has approved the scope and signed. Multi-year logs from one platform are the usual target, two or more years and tens of thousands of records as a rough guide, though a rarer specialty can qualify with fewer.

Frequently asked questions

Does approving a resubmittal approve the earlier revisions too?

No. Each review action applies to the revision it was taken on, and an approval of a later revision does not reach back to earlier packages. Work built from an earlier revision should be traced to that revision's own action, including any notes attached to it.

What should happen to attachments when a new submittal revision is created?

Each revision should hold the files that were actually submitted with it. Procore states that attachments are not carried over between revisions and must be reattached if needed, so an export should be checked for revisions with no files before it is used.

Is approved as noted an approval of the revision?

It is an approval subject to the reviewer's notes, so the notes are part of the condition. Store the notes with the action and check whether the next revision or the field work resolved them; mapping approved as noted to plain approved loses the condition.

Can revision history be rebuilt from file names and dates?

Only as a last resort and with a flag. File names are edited by hand and modified dates change when files are re-saved or copied, so a reconstructed history should be checked against stamps and transmittal numbers inside the PDFs.

Who should review a submittal revision dataset before it is shared?

A qualified engineer or construction manager should confirm action mapping and reviewer authority, and counsel should check project agreements for limits on using project documents. Professional seals and third-party drawings need particular care.

Sources

  • FAR 52.236-21 Specifications and Drawings for Construction: shop drawing definition and use rights, contractor review and approval, risk of work before approval, and written disclosure of variations. Source
  • Procore: creating a submittal revision increments the revision number from the most current revision, and attachments are not carried over between revisions. Source
  • Autodesk submittals: a new revision is available when items are Rejected or Revise and Resubmit, approved items close, and revision numbers increase by one. Source
  • Unified Facilities Guide Specifications: items requiring Government approval are marked G for complexity or criticality; other items go to contractor quality control review. Source
  • UK BIM Framework Guidance Part C: P and C revision prefixes separate preliminary from published information containers. Source
  • CSI: MasterFormat expanded in 2004 from a five-digit, sixteen-division system to a six-digit, fifty-division system. Source
  • Procore Best Practices: Submittals: reverting a workflow step overwrites recorded data and is not recommended for managing submittal revisions. Source
  • Python hashlib documentation: file_digest hashes a file object opened for reading in binary mode, and SHA-256 is among the included algorithms. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies