How to Manage Authority Design Submissions

An authority rejection rarely starts with one missing note on a drawing. More often, it begins when structural assumptions, MEP loads, fire strategy, utility constraints, and drawing revisions stop telling the same story. To manage authority design submissions effectively, project teams need a controlled technical process that makes compliance visible, coordinates every discipline, and preserves a defensible record of decisions.

For developers, contractors, and asset owners, this is not an administrative exercise. Authority approval affects procurement, site mobilization, utility connections, construction sequencing, and final occupancy. A package that is technically adequate but poorly coordinated can still lose critical weeks in review cycles. The objective is not simply to submit documents. It is to submit evidence that an approving engineer can review, verify, and accept without having to reconstruct the design intent.

Start with the authority pathway, not the drawing deadline

The submission program should be established during design planning, before detailed production begins. Each authority has its own required stages, forms, discipline interfaces, review periods, and conditions for resubmission. Dubai Municipality, RTA, civil defense, utility providers, airport authorities, and local municipalities may each require a different sequence of approvals. The same applies to permitting agencies in international markets.

Create a submission register that identifies the approving body, package title, applicable project stage, required deliverables, responsible discipline, planned issue date, review status, and closeout owner. It should also identify dependencies. A drainage layout may depend on approved road levels. A fire pump room layout may depend on electrical load confirmation and civil defense criteria. A bridge substructure package may depend on geotechnical parameters, hydraulic clearance, and highway authority design criteria.

The register is most useful when it is treated as a live engineering control document rather than a project management tracker. Every date should connect to a technical readiness condition. If a package has unresolved load paths, incomplete utility data, or an unapproved design basis, it is not ready because the drawing set happens to be complete.

Define a code and design basis that can be checked

Approving authorities need to understand what rules govern the design and how those rules have been applied. A clear design basis report should state the project location, design life, occupancy or asset classification, environmental exposure, loading criteria, material specifications, analysis method, and governing codes.

For structural packages, this may include ACI or Eurocode concrete design, AISC or Eurocode steel design, AASHTO requirements for bridges, wind and seismic parameters, geotechnical design values, durability provisions, and fire resistance criteria. For MEP packages, it should define electrical demand assumptions, short-circuit levels, HVAC external conditions, ventilation rates, plumbing demand, drainage criteria, fire water storage, pump duties, and life safety interfaces.

Do not rely on a code reference in general notes alone. The submission should demonstrate application. If a retaining wall is designed for surcharge loading, identify the adopted surcharge and the source of the value. If a steel connection is governed by moment, shear, axial force, and constructability constraints, show the design actions and connection checks. If a smoke control strategy relies on pressure differentials or extraction rates, identify the design scenario and acceptance criteria.

A reviewing engineer should be able to trace a critical result from the authority requirement, through the design assumption, to the calculation and drawing detail. That traceability is what makes a decision defensible to any authority.

How to manage authority design submissions across disciplines

Multidisciplinary coordination is the point at which many submissions fail. Structural, architectural, civil, electrical, mechanical, plumbing, fire protection, and specialist systems may each be correct in isolation while the combined package remains unbuildable or noncompliant.

Coordination should begin with controlled base information. Establish the approved grid, levels, site benchmark, plot boundary, road alignment, utility corridors, architectural model version, and design model coordinates. A minor discrepancy in levels can become a major issue where road drainage, basement ramps, external works, and building thresholds meet.

The design team should then review interfaces that carry approval risk. Typical examples include slab openings and MEP penetrations, fire-rated shafts, equipment maintenance clearances, transformer and generator ventilation, fire truck access, pump room drainage, bridge utility crossings, gantry foundation locations, and utility conflicts with culverts or retaining walls.

A federated BIM model can make these risks visible, but clash detection alone is not enough. Not every geometric clash matters, and not every authority issue appears as a clash. The coordination review must test compliance intent: Does the fire access route remain usable after final landscaping? Does the electrical room maintain required clearance after structural thickening? Can a proposed drainage route achieve the required invert level without conflicting with foundations?

For remote BIM delivery, define the model exchange protocol at the outset. This includes model origin, file naming, revision status, level of development, IFC exchange requirements where applicable, and responsibility for closing coordination comments. A model with unclear authorship or uncontrolled revisions creates approval exposure even when the geometry is accurate.

Issue one coordinated package, with a clear hierarchy of documents

An authority submission should read as one package, not as a collection of discipline outputs. The cover letter, document index, drawing register, reports, calculations, models, specifications, and forms must use consistent project information and revision references.

Establish a document hierarchy before issue. The approved design basis and authority conditions should govern calculations. Calculations should govern drawing dimensions and reinforcement or equipment schedules. Drawings should govern construction intent. Where a discrepancy exists, it must be resolved before submission, not left for the reviewer to identify.

For contractor drawing offices, this control is equally important in shop drawing submissions. A reinforcement drawing must align with the latest structural design drawings, architectural openings, embedded items, bar marks, construction joints, and bar bending schedule. A steel fabrication package must align with member releases, connection forces, bolt grades, weld requirements, erection sequence assumptions, and interface tolerances. Producing drawings on the client’s title block is straightforward. Maintaining revision integrity across the complete package is the real technical responsibility.

Use an internal pre-submission check that separates design verification from document verification. Design verification confirms that the calculations, load cases, analysis model, and detailing assumptions are correct. Document verification confirms that sheets are signed where required, references are current, submissions contain all mandatory forms, and revisions are clearly clouded or otherwise identified according to authority procedure.

Treat review comments as engineering actions

Authority comments should not be distributed as an unstructured email chain. Log each comment with its source, discipline, technical issue, required action, response owner, target close date, and evidence of closure. The response should be concise but specific.

A weak response states, “Noted and revised.” A controlled response identifies the change: “Foundation schedule revised to reflect the geotechnical allowable bearing pressure of 250 kPa. Footing sizes and punching shear checks updated in calculation package revision C, sheets S-421 to S-426.” This allows the reviewer to confirm closure quickly and reduces repeat comments.

Some comments require a design change with consequences beyond the marked drawing. Increasing a water tank capacity changes dead load, support reactions, electrical demand, pump duty, and possibly room dimensions. Relocating a utility corridor may affect pavement build-up, drainage crossings, and access chamber locations. The comment log should trigger an impact assessment whenever a change crosses discipline boundaries.

Where an authority comment is ambiguous or appears inconsistent with the stated code, seek clarification early. Do not build a large resubmission around an assumed interpretation. A short technical meeting, supported by marked-up drawings and a focused code reference, can protect weeks of redesign.

Protect approval after the stamp

Approval does not freeze every design decision permanently. Value engineering, site conditions, material substitutions, utility revisions, and construction sequencing often introduce changes after approval. The risk is that the site proceeds using a revision that no longer matches the approved package.

Maintain an approval matrix that distinguishes approved-for-permit documents, approved-for-construction documents, shop drawings, temporary works, and field change notices. Any change affecting code compliance, structural capacity, egress, fire protection, utility connection, or public safety should be assessed for resubmission before it reaches site.

This is especially critical for existing assets. Strengthening works, load rating decisions, and rehabilitation details may rely on inspection findings, material test results, reinforcement scanning, monitoring data, or assumptions about concealed conditions. If site evidence changes the engineering basis, the authority record may need to change with it.

The most reliable submission process gives reviewers less to infer and project teams less to recover later. Build the evidence trail early, control every interface, and answer each comment with proof. Approval then becomes a managed engineering outcome, not a late-stage gamble.