PUSHT · Submittals, RFIs, transmittals — end to end
Submit. Track. Approve.
Transmit. Close out.
The construction document lifecycle, automated. PUSHT reads your proposal, designs the submittal packages, drafts the vendor and engineering RFIs, sends every issue with live delivery tracking, and lines up the transmittal when approvals close. One tool. One log. One source of truth for your PMs and field leadership.
All Div 20-28
CSI sections covered
PDF · DOCX · MSG · QB
Intake formats
Live webhooks
Delivery tracking
Days · timer · alert
Per-package SLA
What PUSHT does
One workflow, end to end — not a tool you bolt onto your existing stack of seven.
PUSHT covers every stage of the construction document lifecycle — reading the proposal, designing the submittal packages, issuing vendor and engineering RFIs, tracking every delivery, managing approvals, and compiling the transmittal at close-out. One product. One audit trail. Same place every PM on your team works.
01
Intake
02
Design
03
Issue
04
Track
05
Approve
06
Transmit
01 · Intake
A proposal, an email, a QuickBase record — same intake.
Drop in a proposal PDF, paste scope-of-work text, or pull straight from a QuickBase record by ID. PUSHT lifts the structured job — project, customer, site, archetype, scope summary, equipment list — and you start with a job already populated. No re-typing.
- PDF, DOCX, MSG, and pasted-text intake at /admin/new
- QuickBase ingest reads proposal record by rid in one call
- Archetype validated against your closed-set vocabulary
- Equipment list extracted verbatim — no invented manufacturers
02 · Design
Submittal packages, designed from the scope.
The package-designer agent reads the intake plus the closest matching past jobs from your archive, and proposes the submittal packages this new job needs — with the right CSI section, the right equipment items, and a one-line rationale you can sanity-check.
- CSI MasterFormat sections picked from explicit equipment rules
- Anti-over-segmentation guardrails for small-job shapes
- In-house trades absorbed, not split out as fake packages
- Plain-English rationale for every package on the list
Packaged Rooftop Unit Replacement
BAS / DDC Controls
HVAC Piping Insulation
03 · Issue
RFIs and vendor asks, drafted and routed automatically.
For each item missing a manufacturer or capacity, PUSHT auto-drafts the vendor ask or engineering RFI, groups them by recipient, and lines up the send. You review, pick the recipient, hit issue. Every send is logged and trackable.
- Vendor and engineering asks classified at the item level
- Asks grouped per recipient — one email per vendor, not twenty
- Recipient picker so you can override the auto-routed contact
- Every issue logged with template, content, and timestamp
Recommend a Distech model for (qty 4) BAS controller sized for 80 points each. Capacity is fixed; we need the matching model number for the submittal cutsheet.
Manufacturer/model recommendation for (qty 2) sensor (capacity 0-10 in. wc). The proposal did not name a basis-of-design product; please confirm an acceptable manufacturer.
04 · Track
Delivery proofs, SLA timers, and approvals in one view.
Resend webhooks land delivery + bounce + spam-complaint events back into the artifact view in real time. Per-package SLA timers tick once an issue goes out. Approvals close packages cleanly, and the transmittal is one click away.
- Live delivery / bounced / delayed / complained badges on every send
- SLA timer per package — alerts when a recipient is overdue
- One-click resend if a delivery bounced or got marked spam
- Transmittal package compiled when approvals close the job
BAS controller submittal — 4 items
Sensor BoD confirmation needed
RTU model selection — 15-ton
Damper actuator cutsheet
Also included
Everything else the submittal workflow needs, in one place.
QuickBase ingest
Pull a proposal record by rid — structured job in one call.
Drag-drop intake
PDF / DOCX / MSG dropped at /admin/new — text extracted in-browser.
Auto-package designer
Reads intake + past comparables, proposes the submittal package list.
Auto-RFI classifier
Missing model number? Missing capacity? Vendor + engineering asks drafted automatically.
Issue everything in one click
Composite action sends every drafted ask at once; one log row per recipient.
Live Resend webhook tracking
Delivered / bounced / complained / delayed — surfaced inline on every send.
Per-package SLA + alerts
Timer starts on issue; warning when the recipient blows through their window.
Transmittal & close-out
Approved package rolls into the transmittal cleanly — no last-minute scramble.
The shift
Your PMs are spending half their bid weeks chasing submittal status by phone.
That is time not spent coordinating the field, not spent on the next job, not spent on the schedule. PUSHT gives that time back.
The old way
- Submittal packages built by hand in Word
- Vendor and engineer asks emailed one-off
- No record of who got what, when
- "Did you get my RFI?" calls on bid day
- Approvals lost in inbox threads
- Transmittals re-typed from scratch
With PUSHT
- Packages designed from the scope in seconds
- Vendor + engineering asks grouped and auto-sent
- Every send logged with delivery proof
- Live delivery + bounce badges on every artifact
- Approvals close packages directly
- Transmittal compiled when the job closes
Early access · limited availability
Run the whole submittal lifecycle
from one place.
Your competitors are still chasing submittal status by phone. Get on early and see what running the construction document lifecycle end-to-end feels like.