Who Should Prepare Submittals in Construction: Estimator, PM, or Project Administrator?

Key takeaways

• The first submittal package is usually best owned by project administration or the project manager, not by the estimator as the ongoing owner.
• Estimators add the most value at turnover, where bid assumptions, exclusions, vendor quotes, and long-lead items are transferred clearly.
• Submittal problems often start when scope knowledge stays in one person's memory instead of a structured handoff.
• General contractors, trade contractors, and smaller firms need different submittal workflows because vendor control and document flow are different.
• Software helps route and track submittals, but clear ownership still has to be defined by the contractor.

The first submittal package should usually be prepared and tracked by project administration or by the project manager with project-administration support. The estimator should define the bid basis at turnover, then stay involved only for scope-sensitive questions.

Tribuild Consultancy is a multi-trade estimating, preconstruction, and project-administration company.

Submittals sit at the point where awarded scope, vendor information, review routing, and procurement timing start to move together. If that handoff is unclear, the estimator keeps getting pulled back into post-award document chasing, and the project team loses a clean owner.

Project administration or the project manager should usually own the first package

A practical default is simple: the estimator explains what was sold, the project manager sets priorities, and project administration assembles and tracks the package.

That setup keeps submittals with the people managing schedule, buyout direction, vendor follow-up, and document control. It also uses the estimator where the estimator adds the most value, which is at the turnover point and when a package raises a bid-basis question.

A clear ownership split looks like this:

• Estimator: transfers scope assumptions, exclusions, alternates, addenda, and quote basis.
• Project manager: sets submission sequence, long-lead priorities, and vendor direction.
• Project administrator or submittal coordinator: builds the log, requests documents, assembles the package, routes it, and tracks status.

When the estimator becomes the long-term owner, routine follow-up can start competing with active bidding. When the project team owns the live workflow, estimating stays tied to scope and risk instead of repetitive document handling.

The estimator should hand off a submittal-start package before stepping back

The estimator should not hand over only plans and specifications. The project team needs a short, organized record of what the estimate actually carried.

A useful handoff typically includes:

• awarded scope summary by trade or bid package
• proposal qualifications and exclusions
• addenda included in the bid
• approved equal or basis-of-design notes, if they affected pricing
• alternates that were accepted, rejected, or left open
• vendor quotes used in the estimate
• long-lead items flagged during bidding
• required samples, mockups, certifications, or delegated-item notes identified during review
• open RFIs or clarifications that could affect product selection

This handoff does not need to be long. It needs to be structured. A short turnover note with organized backup is usually enough to keep the post-award team from reverse-engineering the estimate.

Documents are prepared within the contractor's established review and approval workflow.

General contractors, trade contractors, and small firms need different ownership models

The right setup depends on who controls vendors, how formal the document system is, and how much of the awarded scope lives in one person's head.

General contractors usually need PM-led ownership with administrative support

For a general contractor, the first submittal package is often the start of a project-wide process, not just one product submission. The project team has to build the log, assign responsibility across trades, monitor review durations, and connect approvals to procurement timing.

A workable GC model is:

• estimator supports turnover and identifies scope-sensitive items
• project manager sets priority packages and escalation points
• project engineer or project administrator manages the live submittal workflow

Trade contractors often need stronger estimator involvement at the start

For a trade contractor, the estimator may hold the key details on the quoted manufacturer, substitution basis, exclusions, and scope assumptions used to win the work. That makes first-package involvement more important.

A workable trade-contractor model is:

• estimator prepares turnover notes and checks the first package for scope alignment
• project manager confirms field sequence and procurement timing
• project administration or a coordinator handles vendor collection, formatting, tracking, and follow-up

That is especially useful when submittal release is tied closely to purchase orders, fabrication, or material lead times.

Small firms can separate tasks even when one person holds multiple roles

Smaller contractors often have one person estimating, buying out work, and managing paperwork. The answer is still to separate the tasks, even if the title stays the same.

The tasks are:

• confirm what was sold
• decide what needs to move first
• collect, route, and track the package

If those steps are not separated, the first package often slows down because the job knowledge is informal rather than documented.

Software supports the process, but it does not decide ownership

Software can improve routing, visibility, revision tracking, and status follow-up. It does not decide who should prepare the first package.

A strong workflow uses software to support the handoff:

• seed the submittal log from award-turnover notes
• connect vendor records to package responsibilities
• flag long-lead items early
• track first submissions and resubmittals separately
• keep estimator comments tied to scope decisions

If a system routes documents well but does not carry bid assumptions into post-award work, ownership tends to drift back to the estimator. If the handoff is clear, software helps the project team keep control without losing the bid basis.

A simple post-award policy works better than role-by-role debate

The cleanest policy is this: estimators inform the first package, and project teams own the live workflow.

A practical version of that policy looks like this:

• estimator attends turnover and provides a submittal-start handoff
• project manager identifies first-priority packages and long-lead exposure
• project administration assembles and tracks the package
• estimator reviews scope-critical questions, substitutions, or bid-basis conflicts
• later packages stay with the project team unless a specific scope issue requires estimating input

That approach protects bid capacity and keeps submittals connected to procurement, schedule, and document control. If you want to review one estimator handoff or submittal workflow, Tribuild can discuss the process with your team.

Sources

• https://tribuildconsultancy.com