A delayed submittal is rarely delayed because no one opened the file. More often, it is held between parties that have different responsibilities: the contractor has reviewed it, the architect needs design confirmation, the engineer must verify technical requirements, and the owner may require visibility or a separate acceptance. Understanding who approves submittals begins with separating these roles clearly.

On a well-controlled project, submittal approval is not a single signature or an informal email response. It is a documented workflow that confirms the proposed material, product, fabrication detail, shop drawing, or method meets the contract requirements before work proceeds. The exact approval authority depends on the contract, delivery method, project specifications, and public-agency requirements. However, the underlying control principle remains consistent: each reviewer should approve only the matters within their assigned authority.

Who Approves Submittals in Construction?

In most design-bid-build projects, the architect or engineer of record is the party that reviews and approves, approves as noted, rejects, or returns submittals for revision. Their review focuses on conformance with the design intent and contract documents. This does not transfer responsibility for dimensions, quantities, fabrication methods, means and methods, site conditions, or construction safety from the contractor to the design professional.

Before the submittal reaches the design team, the general contractor should perform an internal review. The contractor’s review confirms that the submission is complete, coordinated with related trades, and consistent with the work being proposed. Many specifications require a contractor stamp or certification before a submittal can be formally transmitted. Without that step, the design reviewer may receive incomplete documents, conflicting information, or products that do not fit the construction sequence.

The owner typically does not approve routine technical submittals directly, although the owner may have approval rights for significant finishes, major equipment, samples, mockups, substitutions, or products with operational implications. Public owners may also require review by a project manager, works supervisor, asset operator, safety representative, or designated government authority. In these cases, the contract should state whether the owner’s action is approval, acceptance, comment, acknowledgment, or a condition for release.

A consultant may review specialized packages such as geotechnical works, fire protection, façade systems, rail systems, traffic control, electrical protection, environmental measures, or commissioning documents. The consultant’s role must be recorded precisely. A technical recommendation is not automatically final approval unless the contract delegates that authority.

Review Authority Is Not the Same as Responsibility

The word “approved” can create unnecessary risk when a project team uses it loosely. Design professionals generally approve a submittal for limited conformance with the contract documents. They do not certify that every field measurement is correct or that the contractor’s chosen construction process is safe and workable.

For that reason, a clear workflow should show the review status and any limits attached to it. “Approved as noted” may permit procurement or fabrication only after the contractor incorporates stated comments. “Revise and resubmit” means the submission is not ready for release. “No exceptions taken” may be used in some organizations, but it should still be tied to a defined review scope. A verbal instruction, screenshot, or untracked email should not be treated as authorization to proceed.

The contractor remains responsible for coordinating the approved item with the actual site conditions, adjacent work, applicable codes, and supplier information. If a shop drawing conflicts with the contract documents, the contractor should identify the discrepancy through the formal process rather than assume that a review stamp silently changes the contract.

The Typical Submittal Approval Sequence

A controlled sequence prevents reviewers from working on the wrong version and helps project teams understand where responsibility sits. The process normally begins when a subcontractor or supplier prepares the required documents. The general contractor reviews the package, confirms completeness, and sends it to the designated design reviewer.

The architect, engineer, or specialist consultant then reviews the submission within the agreed review period. Their comments are consolidated and returned through the document control system. If revisions are required, the contractor or supplier prepares a new version, responds to each comment where appropriate, and resubmits it. The cycle continues until the package receives an acceptable disposition.

Once approved, the system should issue a controlled record showing the approved revision, date, reviewer, status, comments, and any attachments. The site team must be able to identify that revision quickly. An outdated approved drawing can be as damaging as an unapproved drawing when crews, inspectors, and fabricators are working from different information.

For high-risk items, approval may include additional hold points. A structural steel package may require coordination with connection design and fabrication release. A concrete mix design may require trial data and field verification. A material sample may require physical acceptance before procurement. These are not administrative details. They determine whether the approval supports safe, compliant construction.

When the Owner or Authority Has Final Approval

Some projects require an additional approval layer beyond the architect or engineer of record. This is common when the item affects operations, maintenance, aesthetics, environmental compliance, security, statutory approvals, or public safety. For example, an owner may reserve final selection of interior finishes, while an operations team may accept equipment that must integrate with an existing facility.

Government and infrastructure projects may also require approvals from agencies with jurisdiction. Permitting authorities, utility owners, transportation departments, fire authorities, or environmental regulators may review specific packages. Their approval is separate from the design team’s review and should not be assumed to replace it.

The practical question is not simply, “Has this submittal been approved?” It is, “Has every required party completed the action assigned to them, and is the current revision released for the next project activity?” A digital workflow should make that answer visible without searching through email chains or paper transmittals.

Setting Approval Roles Before Submittals Start

The strongest submittal process is established before the first shop drawing is issued. The project team should create a submittal register that identifies each required package, responsible contractor, reviewer, target submission date, required review duration, and dependency on procurement or site work. Approval roles should be linked to the contract and specifications, not assigned casually after a delay occurs.

A responsibility matrix is especially useful where several consultants, owner representatives, and contractors participate. It should identify who prepares, checks, reviews, recommends, approves, returns, and distributes each type of submittal. This is particularly valuable for delegated design, BIM coordination, design-build work, and multi-discipline infrastructure packages, where authority may not follow a simple architect-contractor pattern.

The workflow should also include escalation rules. If a reviewer is overdue, the system should notify the responsible party and record the delay. If a reviewer rejects an item due to missing information, the contractor should receive a defined reason rather than a vague status. If a change affects cost or time, it should be routed into the change management process instead of being buried in a submittal comment.

Why Digital Document Control Matters

Submittal approval produces a critical project record. It establishes what was submitted, who reviewed it, what comments were issued, which revision was accepted, and whether the field received the correct release. Paper folders and uncontrolled email threads make that evidence difficult to retrieve, especially during inspections, disputes, handover, or future maintenance.

A digital works supervision and document management platform can route submittals by discipline and authority, apply status controls, preserve reviewer comments, maintain revision history, and provide real-time dashboards for overdue items. It can also connect approved records with site inspections, BIM models, quality records, and final asset documentation. This gives project managers a dependable view of approval readiness without replacing the professional judgment required from engineers and supervisors.

For complex projects, systems such as InnoShare DWSS 2.0 support structured, auditable workflows that reflect the project’s actual review hierarchy. The value is not merely faster circulation. It is the ability to prove that the correct person reviewed the correct revision at the correct time, with a clear record of any conditions attached to the approval.

Common Approval Failures to Avoid

Submittal controls often fail when teams treat all review comments as equal. A contractor coordination comment, an architect’s design comment, an owner’s preference, and a regulatory condition may each require different follow-up actions. Recording the comment source and required disposition prevents a minor observation from blocking procurement or a mandatory condition from being overlooked.

Another frequent failure is releasing work based on a preliminary status. “Reviewed,” “for information,” or “pending owner selection” may sound positive, but none necessarily authorizes fabrication or installation. Field teams need a simple, controlled indication of whether the item is approved for procurement, approved for construction, or still on hold.

Finally, approval workflows fail when they are disconnected from the submittal schedule. Long-lead equipment, fabricated components, and regulated materials need early visibility. A complete register and automated aging report allow the team to address bottlenecks before they become site delays.

The party who approves a submittal is defined by the contract, but the project team is responsible for making that authority visible, traceable, and usable. When approval roles, revision control, and release status are managed in one disciplined process, the site can act with confidence rather than assumption.