Engineering & Quality

Submittals

Submission to consultant review to approval or rejection, with resubmission handled automatically.

Overview

Material and technical review cycles

Submittals covers material and technical submissions, prequalification and method statements. The workflow runs from submission through consultant review to approval or rejection, with approval codes recorded against each item.

Status tracking and resubmission workflows are automated, so a Code C does not have to be chased manually and the next cycle starts with the right references already attached.

Submittals are the most common source of programme slippage that nobody planned for. A façade package with two hundred submissions and a fortnight of review time each will quietly consume months, and the delay is only visible once it has already happened. Making the queue and its ageing visible to every party changes behaviour on both sides.

  • Material & technical
  • Prequalification
  • Method statements
  • Resubmission workflow
Material & technicalPrequalificationMethod statementsResubmission workflow
Submittals
SubmittalsMaterial and technical review cycles

How it works

The review cycle

Submitted with the right attachments

Guided submission means the required documents are present first time, which removes a common cause of rejection.

Routed to the reviewer

The submittal reaches the right consultant with the specification reference attached.

Coded and returned

Approval codes are recorded against the item, with comments held on the record.

Resubmitted with history intact

A rejected submittal returns as the next cycle of the same item, not as an unrelated new submission.

Why it matters

On a live project

Review cycles keep moving

Items sitting with a reviewer are visible to everyone, which shortens the queue considerably.

Resubmission is structured

A rejected submittal comes back with its history intact rather than as a fresh submission.

Subcontractors submit correctly

Guided submission means the required attachments are there the first time.

Use cases

Where teams feel the difference

Long-lead procurement

Approval delays on long-lead items are visible while there is still time to expedite.

Consultant performance

Turnaround times by reviewer are a matter of record, which makes the conversation about them straightforward.

Subcontractor management

Package submittal status is visible to the subcontractor, so chasing is replaced by looking.

Questions

Frequently asked about Submittals

Yes. Codes A/B/C/D or your own scheme are configured during onboarding to match your contract and consultant.

Reviewers who only respond to submittals can be given limited-access accounts rather than full user licences.

Yes. Elapsed time is tracked against the contractual review period and overdue items are surfaced.

Yes, both run through the same structured workflow as material and technical submittals.

See Submittals on your project

Take the next step and empower your projects with Fortis Sync.