Skip to main content

πŸ”„ Sync β€” Multi-Trade Coordinator

The exclusions don’t cancel. They stack β€” onto your number.
Sync reads Divisions 08, 26, and 27-28 against each other and returns every component of every electrified opening β€” claimed, contested, or claimed by no section β€” with the section number behind every claim.
Send the spec set from a bid you already closed.

The Problem

You’ve read the hardware schedule. Forty electrified openings. The door sub’s quote excludes power and line voltage. The electrical sub excludes the door pathway. The security integrator excludes the electric hardware. Each exclusion is rational. Together they leave a hole, and the hole is standing on your number with nobody behind it to back-charge.

You sent the RFI. It came back coordinate in the field β€” which assigns nothing, closes the question, and starts the clock on a change order argued after award, when every party who excluded the scope excluded it correctly.

You know the manual fix: read all three divisions against each other before the bid goes out. You also know the truth about the bid window β€” that read does not fit inside it, so it gets skipped, and the skip is invisible until the wall is closed.

And you’ve been here before: right in writing, and paid anyway.

The Stakes

The first disputed opening sets the precedent that governs every remaining opening on the job. Absorb the first unclaimed power supply into general conditions, and the next thirteen are yours by precedent. A component priced at zero at bid comes back at field-discovery rates with change-order markup after the frames are grouted β€” and by then the only argument left is with parties who each said no in writing before you did.

Who it helps

GC preconstruction estimators whose number absorbs the union of everyone else’s exclusions β€” the component in nobody’s quote and nobody’s exclusion surfaces after award, and there is nobody behind the line to back-charge.
Post-award project engineers who asked who provides and got a part number back β€” the RFI shows closed, the assignment was never made, and masonry closes Friday.
Security and low-voltage integrators who mobilize last and discover on site what everyone upstream assumed β€” drywall days away, no conduit, no back box, and the front doors missing from the schedule entirely.
Door and hardware subcontractors whose Division 08 sets get read after award to say they own electrification they never priced β€” bid the set exactly and get blamed for the surplus, exclude it and get back-charged for the gap.
MEP coordinators who can build the matrix cell but cannot fill it β€” walking into Thursday’s meeting with the electrified-opening rows blank in exactly the cells that matter.

How It Works

  1. 01
    Send the three divisions, the door or hardware schedule, and the addenda β€” the set you already have.
  2. 02
    The read comes back inside your bid window: every component of every electrified opening, marked and cited.
  3. 03
    Check it. Pick any finding, open your own book to the cited section, and confirm it in thirty seconds. Then price it, exclude it, or send the drafted RFI.
β€œNeither section claims it β€” and that is the finding, not a technicality. Nobody carries the circuit. What you do with that is yours; what you now have is the citation.”
Sync

What it does

Sync is a pricing input, not a coordination platform. It reads the specification set you already hold β€” no data entry, no model, no design-team buy-in β€” and returns:

01

The components claimed by no section.

Named, with the three sections that each fail to claim them. This is the finding that exists nowhere else β€” not in your exclusions stack, not in your RFI log, not in any highlight pass.
02

The contested components.

Both citations side by side, with the deferral chain traced to where it closes β€” or the statement that it closes on nobody.
03

The assignments that cannot physically work.

Two correctly assigned components that cannot connect β€” the device’s draw against the transfer path’s rating, checked from manufacturer data, provable before award.
04

The count mismatches.

A per-door specification against a consolidation plan, both numbers cited, flagged before either one is bid.
05

The RFIs, drafted.

Built to force a named party instead of a part number, with a response window and the line that non-response constitutes acceptance.

The Promise

What Sync promises: a component-level furnish-and-install reading of every electrified opening in the set, with the governing section cited for every claim and every unclaimed component named, delivered inside your bid window. It will not invent a section number. Where the documents don’t support an answer, it says so instead of producing one β€” a missing addendum stops every component it could touch, by rule.

What closing the gap looks like: fourteen power transfers at the stair and corridor openings, install claimed by no section, in no subcontractor’s quote β€” found before submission, priced as a visible line. After award, that same list is a change order argued against three subs who each correctly excluded it, with the first resolution governing the other thirteen.

The condition for success: you bring the current set β€” all three divisions, the schedule, every addendum issued. A read against a superseded set produces a wrong answer confidently, which is why the read states the set it ran on and stops where the set stops.

Objections

β€œWe already have exclusions and scope sheets.”

Exclusions tell you what each subcontractor is not doing. Nothing in that stack tells you the interface between three subcontractors is unowned β€” when the door sub excludes power, the electrical sub excludes the door pathway, and the integrator excludes the electric hardware, the exclusions do not cancel. They stack, and your number absorbs the union. The test is the closed-bid run: if it names a component in no quote and no exclusion, the gap is real on your own paper.

β€œI don’t have time for another step during a bid.”

There is no data entry β€” the read runs against the set you already have. The honest comparison is not Sync versus nothing. It is Sync versus the manual three-division read that does not fit in the bid window, which is why it gets skipped.

β€œWe already have an RFI process.”

Your log cannot distinguish a late answer from a complete answer that assigns nothing. You ask who provides the power supply and get back a manufacturer part number β€” process complete, question unanswered, trade unassigned. Sync drafts the question that forces a named party, and flags the response that answers with a product.

β€œThat’s a coordination problem β€” we have tools for that.”

Those tools resolve geometry. None of them can tell you, before Thursday, that a power transfer appears in Division 08’s hardware set and in no Division 26 assignment β€” the objects don’t collide, because one of them was never assigned to anyone. Sync doesn’t touch drawings, models, or clash detection. It is a pricing input, and it engages before award, in the phase you own.
The next set you price will carry this gap or it won’t β€” and right now you can’t tell which.

Send the spec set from a closed job. The read either names the component that appeared in no quote and no exclusion, or it documents that it found nothing. Both are answers, and it costs you one spec set to get one.

Every solution in this market operates downstream of an assignment that was never made.