Sub-Bid Requests and Mirror Projects

01Create a sub-bid request

From a project’s Sub-Bid Requests tab (or the project Bids tab → Request Sub Bids button), click + New Request.

1. Title. Descriptive: “Electrical Rough-In for Unit 4B,” “Plumbing rough-in,” etc.
2. Project. Required. Picks the project this scope belongs to.
3. Description / scope. What you need bid — line-item-level detail helps subs price accurately.
4. Trade Type. Electrical, Plumbing, HVAC, Mechanical, GC, etc. Drives which subs get suggested in the invite step.
5. Due Date. When you need responses back by.
6. Budget Hint ($). Optional. Helps subs gauge the ballpark; not a hard limit and not shown to them as authoritative.
7. Invite Subcontractors. Section continues below the form fields — that’s where you add emails to invite (covered in tab 02).

1 2 3 4 5 6 7

Documents (plans, specs, anything subs need to price accurately) attach below the Invite Subcontractors block.

02Invite subs

In the request detail, scroll to the Invitations section.

1. Add emails one at a time or batch-paste.
2. In-app notifications if the sub is already on Conduit.
3. Email invite if they aren’t (with a link to sign up and respond).
4. Status indicators per invite: Pending, Sent, Viewed, Responded.
5. Resend any invite that hasn’t been viewed.

Track who’s seen it and who hasn’t. No more chasing subs over text.

03The sub’s experience

When a sub accepts the invitation, this is what they see (helpful context for understanding the GC side).

1. Incoming Bid Requests card on their dashboard.
2. Open the request to see scope, due date, budget hint, and all attached documents.
3. Build their bid. Title, description, line items with pricing, proposed start/duration, deposit terms.
4. Save draft or submit immediately.

The sub can ask questions through the bid’s comment thread before submitting; the GC sees those.

04Compare submitted bids

Back on the GC side, once bids come in, click Compare Bids on the request detail. Every submitted bid becomes a column laid out apples-to-apples.

1. Trade + SBR number. Header tells you which request you’re comparing on (e.g., “Plumbing — Hartford Medical Office, SBR-2026-0004”).
2. Sub name + bid number. Each column starts with who submitted it and their internal bid number for traceability.
3. Status badge. Per-bid status — Pending review, Accepted, or Declined. Cheapest bid also gets a “Lowest” badge automatically when you have more than one.
4. TOTAL. Big number at the top of each column — Subtotal + Tax broken out underneath.
5. LINE ITEMS. Full breakdown for that bid. Compare scope across columns line by line.
6. SCHEDULE. Proposed Start, Duration, and Valid Until — the timing dimension you can’t get from price alone.

1 2 3 4 5 6

Cheapest isn’t always best. A bid that’s $500 cheaper but with a 3-week delay can cost you more than the savings — read the schedule and line items together, not just the total.

05Accept and create a mirror project

Click Accept on the winning bid. Four things happen automatically: a mirror project is created in the accepted sub’s account, the sub gets a notification confirming acceptance, the other submitted bids auto-decline with a “GC accepted another bid” reason, and the sub can immediately start working inside the shared project structure.

The screenshot below shows the mirror as the sub sees it. They get the same project skeleton you have, but their tab counts reflect only their own work.

1. Project name + address. Synced from the GC’s source project. Updates flow one-way (GC → sub).
2. Active status chip. Mirrors the GC’s status — when the GC moves the source to Completed, the mirror moves too.
3. Same tab bar. Plans, Bids, Jobs, Invoices, POs, Bills, RFIs, Submittals & Specs, Change Orders, Timesheet, Schedule. The count chips reflect only the sub’s own items.
4. Profit & Loss card. Sub’s own P&L for this engagement — their invoices vs their costs, not the GC’s.
5. Committed Cost. The sub’s POs against this project (subcontractor commitments visible from the sub’s perspective).

1 2 3 4 5

06Cross-company visibility

This is where the GC’s superpower kicks in. From your project’s RFIs, Submittals, Change Orders, and Invoices tabs, you see items from all your subs aggregated into one list.

1. One unified view per resource type. All RFIs from electrical sub, plumbing sub, HVAC sub appear together.
2. Company name labels on each item show which sub it’s from.
3. Sort + filter by sub if you want to focus on one trade at a time.
4. Subs only see their own items. Their data stays private to them; you see the aggregated view because you’re the GC source project.

This eliminates the GC’s “switching between sub accounts to see the project” problem. It’s all in one place.

That’s the sub-bid + mirror project workflow. Next: RFIs for the question-and-answer flow.