Engineering Submittal: The Complete Guide to the Construction Submittal Process

An engineering submittal is the documented proof that the materials, equipment, and methods going into a construction project actually match what's required by the contract documents. Not assumed to match. Documented to match.

‍

On a well run project, the submittal process catches problems weeks before they become problems on the job site. On a poorly run project, the submittal process is where projects quietly fall behind.

‍

This guide walks through the engineering submittal process from end to end. What it is, who owns each step, how to manage the review and approval process, and how to use automated workflows to keep things moving.

‍

Quick note: we built SubmittalLink, a digital platform for managing construction submittals and RFIs. We'll point out where it fits, but the principles in this guide apply whether you're using a digital platform, a spreadsheet, or a stack of emails.

‍

Executive Summary of Construction Submittals

‍

What Construction Submittals Actually Do

‍

Construction submittals serve as the quality checkpoint between design and construction. They give the design team a chance to review what the contractor proposes to install before fabrication or delivery, and they give the contractor written confirmation that what they're building matches the design intent.

‍

The benefits show up across the entire project lifecycle:

‍

• Submittals reduce change orders by catching issues early in the construction process, when fixes are cheap.
• Submittals verify that contractors use correct materials and methods specified in contracts.
• Submittals mitigate risks by catching discrepancies before materials are fabricated or ordered.
• Submittals impact the cost, timeline, and risk profile of construction projects.
• Submittals provide a record of compliance for inspections and audits, including closeout and warranty work years later.

‍

The Case for Going Digital

‍

Most construction teams still run submittals through email threads, shared drives, and spreadsheets. It works on simple projects. It falls apart on anything with real complexity.

‍

Modern software can simplify the submittal review process, automated workflows reduce manual handling time significantly, and digital platforms enhance real time collaboration among project teams. Electronic submittals are becoming the industry standard for a reason.

‍

Construction Submittal Process Overview

‍

The construction submittal process is a structured sequence of submission, review, and approval that runs from preconstruction through closeout. Understanding the phases and ownership of each step is the first thing to get right.

‍

The Phases of the Submittal Process

‍

• Preconstruction. Submittals begin during the preconstruction phase, when the general contractor builds the submittal register from the project specifications and assigns responsibility to each subcontractor.
• Submission. The subcontractor or supplier prepares and submits the documentation through the contractor to the design team for review.
• Review. The architect, engineer, and any required consultants conduct a detailed review of the submittal against the contract documents and project specifications. A typical submittal review should take 7 to 14 days.
• Action and approval. The reviewer returns the submittal with one of several actions: approved, approved as noted, revise and resubmit, or rejected. Approved submittals authorize contractors to order materials and proceed with work.
• Resubmission if required. When a submittal comes back as revise and resubmit, the contractor addresses the comments and submits the corrected version for another round of review.
• Procurement and installation. Once approved, the contractor proceeds to order, fabricate, and install. The approved submittal becomes part of the permanent project record.
• Closeout. At project closeout, the full submittal log gets compiled into the owner's record, along with operations and maintenance manuals for installed systems.

‍

Who Owns Each Step

‍

• Subcontractors and suppliers prepare the submittal package and provide the technical data, shop drawings, and product samples required by the spec.
• The general contractor reviews submittals first for completeness and conformance, then transmits them to the design team. The general contractor is ultimately responsible for managing the process across all subs.
• The design team (architect, engineer, and consultants) conducts the technical review and returns the submittal with action.
• The submittal coordinator (usually a project engineer on the GC's side) tracks status across every open submittal, chases late reviews, and keeps the submittal register current.

‍

Types of Engineering Submittals and Required Documents

‍

Not every submittal looks the same. The contract documents define what's required for each spec section, but most engineering submittals fall into a handful of categories.

‍

Product Data

‍

Product data submittals include the manufacturer's product information for a specific material or piece of equipment. This is the most common type of submittal and typically covers technical datasheets, performance specifications, installation instructions, and applicable standards.

‍

Best practices for product data submittals:

‍

• Require manufacturer product data for each item specified in the contract.
• Attach relevant technical datasheets, not just the marketing brochure.
• Mandate version control so reviewers always see the latest revision.
• Flag the specific page or section the reviewer needs to find, especially in long manufacturer documents.

‍

Shop Drawings

‍

Shop drawings show how the contractor or fabricator intends to manufacture and install a specific element. They are not the same as contract drawings. Shop drawings represent the contractor's interpretation of the original design, which is exactly why they need to go through the review and approval process before anything gets built.

‍

Common items requiring shop drawings include structural steel connections, curtain wall systems, prefabricated components, custom millwork, and complex MEP equipment. The engineer reviews these to verify that the contractor's interpretation matches the design intent and the project specifications.

‍

Material Samples and Product Samples

‍

For finish materials, flooring, roofing, cladding, and similar items, physical samples are submitted for review. Samples let the design team verify color, texture, finish quality, and material composition against the specifications before orders are placed. Product samples are required primarily for items where visual or tactile properties matter.

‍

Mock Ups

‍

Mock ups are full scale models used to evaluate design and materials in real conditions. They're common on complex assemblies like exterior wall systems, brick veneer, and unusual roofing details. The mock up gets reviewed, tested, and approved before the assembly goes into production at scale.

‍

Mock up best practices:

‍

• Require mock ups for complex assemblies where the design intent is hard to capture on paper.
• Document test results, including weather exposure, water testing, and structural verification where applicable.
• Get written approval of the mock up before authorizing full production.
• Keep the approved mock up on site as a reference standard for the rest of the assembly.

‍

Test Reports and Certifications

‍

Many spec sections require test reports, factory certifications, or third party verification. Common examples include welding procedure specifications, concrete mix designs, factory test data for equipment, and code listing reports. These get submitted with the related documents as part of the submittal package.

‍

Operations and Maintenance Manuals

‍

Operations and maintenance manuals provide instructions for installed systems and become part of the closeout package delivered to the owner. They're typically submitted later in the construction process, often near substantial completion, and need to cover warranty terms, maintenance schedules, and replacement part information.

‍

The Review Process: How Submittals Get Approved

‍

The review and approval process is where the submittal process either runs smoothly or grinds to a halt. Most of the friction is preventable with clear timelines, defined responsibilities, and disciplined follow up.

‍

Establishing Review Timelines

‍

Every submittal needs a clear review timeline. A typical submittal review should take 7 to 14 days, though complex submittals (curtain wall, structural steel, custom equipment) often need longer. The contract documents should specify review periods for each category, and the project schedule should account for them upfront.

‍

When timelines aren't set, reviews drift. Two weeks becomes four. Four becomes six. By the time the approval comes back, procurement has slipped, fabrication has slipped, and the whole project is chasing a deadline that's no longer realistic.

‍

Reviewer Responsibilities by Discipline

‍

Different submittals need different reviewers:

‍

• The architect reviews submittals related to building envelope, finishes, doors and hardware, and overall design coordination.
• The structural engineer reviews structural steel, connections, foundation details, and any submittal that affects the load path.
• The mechanical, electrical, and plumbing engineers review their respective trades, including equipment, distribution, and control submittals.
• Specialty consultants (acoustics, code, envelope, commissioning) review submittals that fall within their scope.

‍

The submittal coordinator's job is to route each submittal to the right reviewers, in the right order, with enough time for a detailed review.

‍

Comment Resolution

‍

When a reviewer returns a submittal with comments, those comments need to be resolved before the submittal moves forward. The contractor addresses each comment, revises the documents, and resubmits with a clear response to each item. Skipping this step is how submittals end up approved with unresolved issues that surface during installation.

‍

Logging Reviewer Decisions

‍

Every decision needs to be logged for audit purposes. Who reviewed what, when, what action they took, and what comments they made. This audit trail matters for compliance, for inspections, and for the inevitable moment years later when someone asks why a specific assembly was built the way it was.

‍

Action Submittals, Approval, and Resubmission

‍

Not every submittal carries the same urgency. The action submittals classification helps the team focus on what matters most.

‍

Classifying Action Submittals

‍

• Critical path submittals. These drive the project schedule. Structural steel, curtain wall, long lead equipment, and any item where fabrication time is significant. These get prioritized in review.
• Standard action submittals. Most product data and shop drawings fall here. They need timely review, but they're not driving the critical path.
• Informational submittals. These don't require approval, just acknowledgment. Examples include warranty certificates, manufacturer letters, and certain test reports.

‍

Addressing Reviewer Comments

‍

When a submittal comes back with comments, the contractor's response should address each comment directly. A vague response like noted is not a response. The reviewer needs to see what was changed, what was clarified, and what justification supports any deviation from the original comment.

‍

Resubmittal Limits and Escalation

‍

Most contracts allow two or three rounds of resubmittal before the issue gets escalated. If a submittal comes back rejected for the third time, something larger is going on. The escalation path should send the issue to the PM and the design team lead for a working session to resolve the underlying disagreement rather than another round of paperwork.

‍

Construction Process Timeline and Milestones

‍

The submittal process doesn't exist in a vacuum. It runs alongside the construction process, and the milestones need to line up.

‍

Preconstruction Deliverables

‍

• Build the submittal register from the project specifications.
• Assign responsibility for each submittal to the appropriate subcontractor or supplier.
• Set required submission dates working backward from procurement and installation milestones.
• Establish reviewer assignments and required review periods.

‍

Procurement and Fabrication Milestones

‍

Long lead items drive the procurement schedule. Structural steel, custom equipment, curtain wall, switchgear, and other items with multi week or multi month fabrication lead times need submittal approvals well in advance of the procurement need date.

‍

The general rule: working backward from when material needs to arrive on site, account for fabrication time, then add the submittal review and approval window, then add buffer. If any of those numbers slip, the schedule slips with them.

‍

Installation Readiness Checkpoints

‍

Before each major installation phase begins, the team should confirm that all required submittals for that phase are approved and any required mock ups are complete. Walking into a phase with open submittals is how projects get stuck mid install.

‍

Product Samples, Mock Ups, and Quality Assurance

‍

Quality assurance through the submittal process happens in two ways: documentation review and physical verification.

‍

Documentation Review

‍

Product data, shop drawings, and certifications get reviewed against the project specifications and the contract documents. The detailed review verifies that the proposed materials and methods meet the required standards, not just that they look similar to what was specified.

‍

Physical Verification

‍

Samples and mock ups give the design team a chance to verify what the documentation describes. A product sample shows the actual color, finish, and texture. A mock up shows the assembly in real conditions. Both protect the project against installations that meet the spec on paper but miss the design intent in practice.

‍

Documenting Test Results

‍

Mock up test results, factory test reports, and field testing data all need to be documented as part of the submittal record. When something gets disputed later, the test documentation settles the question. When everything moves smoothly, the documentation supports closeout and warranty.

‍

Automated Workflows and Real Time Collaboration

‍

This is where digital platforms change the game. Manual submittal management through email and spreadsheets works on small projects. On anything with real complexity, automated workflows are the difference between submittal management and submittal chaos.

‍

Configuring Automated Workflows

‍

A modern submittal platform lets you configure workflows that route submittals to the right reviewers automatically, based on the spec section or submittal type. When a structural steel submittal comes in, it goes to the structural engineer. When an electrical equipment submittal comes in, it goes to the electrical engineer. No manual routing, no missed reviewers.

‍

Parallel vs Sequential Review

‍

Different submittals need different review patterns. Parallel review sends a submittal to all reviewers simultaneously and advances on the first response, which works for time sensitive items or where multiple reviewers provide redundant oversight. Sequential review routes through reviewers in a defined order, which works when one discipline's response needs to inform the next.

‍

Within sequential review, a Requires All setting holds advancement until every reviewer at each step responds. This is useful when you need documented input from multiple disciplines on the same step, such as structural, MEP, and envelope all reviewing a complex assembly.

‍

Real Time Collaboration on Documents

‍

Real time collaboration means multiple reviewers can see the same submittal, leave comments, and respond to each other without emailing PDFs back and forth. When the structural engineer flags an issue and the architect needs to weigh in, both happen in the same place at the same time. The result is faster communication and significantly reduce review cycles.

‍

Automated Reminders

‍

Automated reminders catch overdue reviews before they become problems. When a submittal sits with a reviewer past the agreed timeline, the platform sends a reminder. When it sits too long, the reminder escalates. This removes the burden of chasing reviewers from the submittal coordinator and reduces human error from forgotten follow ups.

‍

Integration With the Project Schedule

‍

The best workflows tie submittal status to the project schedule. When a critical path submittal is delayed, the platform should flag the schedule impact. When a submittal gets approved, the procurement team should know immediately so they can place the order.

‍

Construction Management Roles and Responsibilities

‍

Clear roles prevent the most common cause of submittal delays: nobody knows whose court the ball is in.

‍

Contractor Responsibilities

‍

• Prepare submittals that meet the spec section requirements.
• Review subcontractor submittals for completeness before forwarding to the design team.
• Maintain the submittal register and track status across every open item.
• Coordinate between subcontractors when submittals have cross trade dependencies.
• Resolve reviewer comments and resubmit corrected packages promptly.

‍

Architect and Engineer Review Roles

‍

• Conduct detailed review against the contract documents and design intent.
• Return action submittals within the agreed review period.
• Provide clear, actionable comments that the contractor can respond to.
• Escalate substitution requests or design conflicts that exceed normal review scope.

‍

Submittal Coordinator and Backup

‍

On any project of meaningful size, someone needs to own the submittal process day to day. This is the submittal coordinator, usually a project engineer. Their job is to keep the register current, route submittals, chase reviews, and surface issues before they affect the schedule. A backup coordinator should be designated for coverage during vacation or absence.

‍

Product Specifications and Compliance

‍

The submittal exists to demonstrate compliance with the project specifications. Treating it as paperwork instead of a compliance document is how projects end up with installations that don't meet the spec.

‍

Cross Referencing Product Submittals With Specifications

‍

Every product submittal should reference the specific spec section it satisfies. The reviewer's job is to verify that the proposed product meets the technical requirements in that section, not just that the product is in the same general category as what was specified. Submittals that are similar to the spec are not the same as submittals that comply with the spec.

‍

Compliance Statements for Critical Items

‍

For critical items, fire rated assemblies, code listed components, life safety equipment, the submittal should include a written compliance statement that confirms how the product meets each specified requirement. This protects the project at inspection and removes ambiguity from the review.

‍

Certificates and Test Reports

‍

Where the spec requires third party verification, the submittal package needs to include the certificate, listing, or test report. ICC ES reports, UL listings, ASTM test results, factory certifications, all need to be present and current. Submitting expired or generic documentation gets the submittal rejected.

‍

Tracking, Reporting, and Audit Trail

‍

You can't manage what you can't see. Tracking and reporting are how submittal management turns from reactive to proactive.

‍

Status Tracking for Every Submittal

‍

Every submittal needs a status at all times: drafted, submitted, under review, returned for revision, approved, or closed. The submittal register should reflect current status in real time, not at the end of the week when someone updates the spreadsheet.

‍

Weekly Submittal Progress Reports

‍

Weekly reports surface what needs attention:

‍

• Submittals overdue from the contractor.
• Submittals overdue from reviewers.
• Submittals approaching the procurement need date.
• Submittals in their second or third revision cycle.
• Critical path submittals at risk of impacting the schedule.

‍

This reporting is what lets the project team focus the next week's effort on what actually matters.

‍

Searchable Audit Trail

‍

The audit trail should make it easy to answer questions later. Who reviewed this submittal? What did they comment? What was the final approved version? When was it approved? A digital platform makes this searchable in seconds. A stack of email threads and folders makes it a week of work.

‍

How SubmittalLink Fits Into the Engineering Submittal Process

‍

SubmittalLink is a digital platform built specifically for managing construction submittals and RFIs. It's designed for local builders, mid sized contractors, and project teams who want a clean submittal workflow without enterprise pricing or enterprise complexity.

‍

Here's what it does for the engineering submittal process:

‍

• Automated log extraction. Upload your architectural spec book and SubmittalLink converts it into a structured submittal log instantly. Requirements get categorized by CSI MasterFormat or custom spec sections, so your project engineers stop typing rows into a spreadsheet for two days before mobilization.
• Configurable review workflows. Set submittal and RFI workflows as parallel or sequential at the project level. Parallel review advances on first response. Sequential review routes through reviewers in order, with an optional Requires All setting that holds advancement until every reviewer at each step responds.
• Dynamic ball in court tracking. At any moment, the platform shows who owes a response on every open submittal. No more chasing people down. The submittal register stays current automatically as work moves through review.
• Automated version controlling. Every revision is tracked with a full audit trail. Reviewers always see the latest version. The history of who reviewed what, when, and what they said is preserved for the project record.
• Automated email notifications. When a submittal is created, updated, or needs action, the platform sends emails automatically. Your team stops manually CC'ing people and remembering to follow up.
• Closeout, stamping, and reporting. At project closeout, you can generate stamped final submittals, produce a complete submittal log for the owner, and pull reporting on review cycle times, late submittals, and reviewer performance.
• Mobile access from the job site. Field teams can review submittals, respond to RFIs, and access the latest drawings without digging through inboxes or shared drives.

‍

‍Transparent pricing. No per user fees, no surprise add ons. Book a 15 minute walkthrough and get a real number on the same call.

‍

"We have been paying a fortune for other software but only using a small portion of it. SubmittalLink covers the fundamentals and does a better job." Stephan B., Project Manager at ACE Construction.

‍

Implementation Roadmap for Digital Submittal Workflows

‍

Switching to a digital submittal platform doesn't have to be disruptive. A phased approach reduces risk and keeps your team productive during the transition.

‍

Phase 1: Pilot on One Project

‍

Pick one active project of representative complexity. Set up the platform, upload the spec book, build the submittal register, and run the project on the new workflow for 60 to 90 days. Capture what works, what doesn't, and what the team actually uses.

‍

Phase 2: Train Users

‍

Train the people who'll use the platform daily:

‍

• Project engineers and submittal coordinators get the deepest training, since they'll own the workflow.
• Project managers learn the reporting and approval views.
• Subcontractors and design team reviewers get short, role specific onboarding that focuses on what they actually need to do.

‍

Phase 3: Phased Rollout

‍

Once the pilot has run successfully, expand to additional active projects. New projects start on the platform from day one. Existing projects migrate based on schedule and team capacity. By six months in, the platform should be standard across the company.

‍

Measuring Adoption

‍

Track the metrics that prove the platform is working:

‍

• Average submittal cycle time before and after.
• Percentage of submittals returned on first submission versus requiring revision.
• Number of submittals tracked in the platform versus outside of it.
• User satisfaction across the contractor, design team, and subs.

‍

FAQs About Engineering Submittals

‍

What is an engineering submittal?

‍

An engineering submittal is a documented submission from the contractor to the design team showing exactly what materials, equipment, and methods will be used on a construction project. The design team reviews the submittal against the contract documents and project specifications, then approves, comments, or rejects it. Approved submittals authorize the contractor to proceed with procurement and installation.

‍

How long should the submittal review process take?

‍

A typical submittal review should take 7 to 14 days. Complex submittals like curtain wall, structural steel, or custom equipment often need longer. The contract documents should specify review periods for each category, and the project schedule should account for them upfront.

‍

Who is responsible for the submittal process?

‍

The general contractor is ultimately responsible for managing the submittal process across all subcontractors and ensuring the submittal register stays current. Subcontractors and suppliers prepare their own submittals. The design team conducts the review and issues action. A submittal coordinator on the GC's side typically owns the day to day workflow.

‍

What's the difference between product data and shop drawings?

‍

Product data is the manufacturer's documentation for a specific item, including technical datasheets, performance specs, and installation instructions. Shop drawings are detailed technical drawings prepared by the contractor or fabricator showing exactly how an element will be manufactured and installed. Many spec sections require both.

‍

Can the submittal process be fully digital?

‍

Yes. Digital platforms can centralize the submittal process, route submittals through automated workflows, track status in real time, and maintain a searchable audit trail. Electronic submittals are becoming the industry standard. The exceptions are physical samples and mock ups, which still need to exist in the real world even when their documentation lives digitally.

‍

What happens when a submittal is rejected?

‍

The contractor receives the submittal back with comments explaining why it was rejected. They address each comment, revise the documentation, and resubmit. Most contracts allow two or three rounds of resubmittal. If a submittal keeps coming back rejected, the issue gets escalated to the PM and design team lead for a working session rather than another round of paperwork.

‍

How does the submittal process affect the project schedule?

‍

Significantly. Approved submittals authorize procurement and fabrication, so delayed submittals delay everything downstream. The project schedule should build in realistic review windows and include submittal approval dates as milestones, especially for long lead items where fabrication time is significant.

‍

The Bottom Line

‍

The engineering submittal process is one of the highest leverage activities on any construction project. Done well, it catches problems before they become expensive, keeps procurement and fabrication on schedule, and creates the documentation that protects the project at closeout and beyond.

‍

Done poorly, it's where projects bleed time. Shop drawings sit in inboxes. Reviews drift past their deadlines. Materials get ordered against assumptions instead of approvals. The schedule slips a week at a time until everyone wonders how the project got so far behind.

‍

The fix isn't more meetings or more emails. It's structure: a clear submittal register, defined timelines, automated workflows, real time visibility, and an audit trail that holds up. Whether you build that structure on a digital platform like SubmittalLink or on a disciplined manual process, the principles are the same.

‍

Want to see how SubmittalLink can simplify your submittal workflow? Book a 15 minute walkthrough and we'll show you how local builders and mid sized contractors are managing engineering submittals without the enterprise overhead.