Evos

Submittals & RFIs · Concrete & masonry

No pour delayed by a pending submittal.

Mix designs, rebar shop drawings, and embeds have to clear the engineer before the field can place. One submittal stuck in review three weeks stops a pour cold.

The reality

A delayed pour is usually a delayed approval.

The PM logs a mix design submittal, emails it to the EOR, and forgets it until the field calls asking why they can't pour, then discovers the engineer returned it revise-and-resubmit two weeks ago and no one routed the markup back.

The operator logs each mix design, shop drawing, and embed submittal, routes it to the EOR, tracks the response clock, escalates anything aging past the pour date, and issues the approved set to the field with the RFI log current.

How the operator runs submittals & RFIs

The outcome

−40% open submittals at any point in schedule

No pours delayed by pending submittal approvals.

  • Revise-and-resubmit caught before it stops a pour
  • Every submittal tracked against the date it's needed in the field
  • The RFI log current enough to trust

Common questions

Submittals & RFIs

What does the Submittals & RFIs operator do?
The operator logs each mix design, shop drawing, and embed submittal, routes it to the EOR, tracks the response clock, escalates anything aging past the pour date, and issues the approved set to the field with the RFI log current.
What impact does the Submittals & RFIs operator have?
−40% open submittals at any point in schedule. No pours delayed by pending submittal approvals.
How does the Submittals & RFIs operator work?
Registers each mix design, shop drawing, and embed submittal and routes it to the engineer of record. Watches each submittal against the pour date and escalates anything aging toward a field hold. Records the engineer's stamp, routes revise-and-resubmit markups, and releases the approved set to the crew.

More operators in Concrete & masonry

See the full catalogue →

The operations workforce you don’t have to hire.