Core Module ยท MVP
Procurement & Materials

Automated lead-time monitoring that tells you exactly when to order every material โ€” before it becomes a crisis. Every item is tied to the construction schedule, so BuildOS knows how much time you have before a late order delays your project.

The Procurement Problem

Windows for a custom home can take 12 weeks to arrive. Engineered lumber can take 4โ€“6 weeks. HVAC equipment can take 8 weeks. Ordering too late causes schedule delays that cascade through dozens of downstream tasks. Ordering too early ties up cash and creates storage problems.

Most GCs manage this mentally โ€” an experienced superintendent "just knows" when to order windows. The problem is that this knowledge lives in one person's head, doesn't scale across multiple projects, and fails when that person is unavailable. BuildOS externalizes this knowledge into a systematic, date-driven monitoring process.

How the Must-Order Date Works

For every material item in a project, BuildOS calculates a Must-Order Date โ€” the last possible day the order can be placed and still arrive before the task that needs it is scheduled to start.

Must-Order Date Formula
Task Early Start Date
โˆ’
Supplier Lead Time (days)
โˆ’
Weather Buffer (days)
=
Must-Order Date
The weather buffer adds extra days for supply chain disruptions caused by weather โ€” especially relevant for exterior materials in winter markets. The task early start date comes directly from the CPM schedule, so the must-order date automatically adjusts when the schedule shifts.

Example: Windows on a Spring Project

Windows are needed for WBS 13.2 (Window Installation), scheduled to start April 15. The supplier's lead time is 84 days (12 weeks). The weather buffer is 7 days. BuildOS calculates:

April 15 โˆ’ 84 days โˆ’ 7 days = January 14 โ€” Must-Order Date

BuildOS will alert Sarah on January 1st (14 days before the deadline) with a WARNING status, and again on January 11th (3 days before) with a CRITICAL status.

Status Lifecycle

Every procurement item moves through four statuses as time passes and actions are taken:

โœ…
OK
Must-order date is >14 days away. No action needed.
โ†’
โš ๏ธ
WARNING
Must-order date is within 14 days. Sarah should prepare the order.
โ†’
๐Ÿšจ
CRITICAL
Must-order date is within 3 days or passed. Order now or face schedule delay.
โ†’
๐Ÿ“ฆ
ORDERED
Order has been placed. Item is off the action list.

What Each Item Tracks

Every procurement item in a project contains:

FieldDescription
WBS CodeWhich construction phase this material belongs to (e.g., 13.2)
Item DescriptionWhat the material is (e.g., "Andersen 400 Series Windows โ€” all units")
Lead Time DaysHow many calendar days the supplier needs from order to delivery
Weather Buffer DaysAdditional buffer for supply chain weather disruptions
Need-By DateThe task's early start date from the schedule โ€” when the material must be on-site
Must-Order DateCalculated: Need-By minus Lead Time minus Weather Buffer
StatusOK / WARNING / CRITICAL / ORDERED
SupplierVendor name and contact (optional, for quick reference)

How Items Are Created

When a project is initialized from a permit, BuildOS automatically populates the procurement tracker from the WBS template โ€” the standard set of materials associated with a residential build. This gives every project a complete procurement list from day one, with lead times pre-set based on typical supplier windows.

Sarah and admins can also:

Connection to the Notification Feed

The Procurement Agent checks every item daily and generates feed cards when items cross status thresholds:

TransitionFeed Card PriorityCard Content
OK โ†’ WARNING Urgent "Order [item] for [project] by [date] โ€” 14 days remaining"
WARNING โ†’ CRITICAL Critical "ACTION REQUIRED: Order [item] for [project] โ€” deadline in 3 days or less"
CRITICAL (Tribunal) Critical "Tribunal recommends: Approve [item] order for $[amount]" โ€” with Approve / Dismiss actions

Tribunal Integration for Procurement Decisions

For CRITICAL-status items where the must-order date has been crossed or is imminent, the Tribunal ConsensusEngine is invoked. The Tribunal evaluates whether a purchase should be approved and generates a recommendation card for Tom or Sarah. See AI Agents for full detail on how the Tribunal works.

๐ŸŽฏ
Target outcome: With the Procurement Agent and Tribunal running, 80% of routine procurement decisions should be surfaced and resolved before a project is ever affected by a late material delivery โ€” with zero manual tracking required from Sarah or Mike.

Long-Lead Items

Certain materials require especially long lead times and need to be ordered well before construction even begins. BuildOS flags these as long-lead items and surfaces them during the initial schedule setup:

Item TypeTypical Lead Time
Custom windows and doors10โ€“16 weeks
Engineered lumber packages4โ€“8 weeks
HVAC equipment (custom tonnage)6โ€“10 weeks
Custom cabinetry8โ€“14 weeks
Specialty roofing systems4โ€“8 weeks
Elevator / lift equipment12โ€“20 weeks

For long-lead items, the Must-Order Date may fall before the permit issuance date โ€” meaning the order needs to be placed even before construction officially begins. BuildOS surfaces these immediately when a project is initialized, so Sarah can place them without waiting for the schedule to "feel urgent."