Procurement Tracker (engine)
Extract procurement items from a schedule of values, bill of materials, or procurement log. Every extracted row becomes a live entry in the Procurement Tracker workspace with vendor, PO, ETA, and budget burn.
What it does
Procurement Tracker (engine) reads a procurement source document — SOV, BOM, bid leveling export, or existing procurement log — and extracts each item as a structured record: description, qty, unit, assigned vendor (if known), PO number (if issued), committed amount, actual ETA, and current status. Output imports to the Procurement Tracker workspace, where you manage items through delivery.
What to upload
- Schedule of values
- Bill of materials
- Bid Leveling export (chain from Bid Leveling — data carries forward)
- Existing procurement log
Step by step
Open the engine
Sidebar → Engines → Procurement Tracker.
Upload source
SOV, BOM, log, or chain from Bid Leveling.
Run
20–40 seconds.
Review + assign
Each row as editable. Link items to vendors if not already assigned.
Import to tracker
Merges by description + qty if items already exist.
Understanding the results
Description, qty, unit, vendor, PO, committed amount, ETA, status.
Separate section for items without a vendor. Assign from the Vendor Database before importing to tracker.
Total committed, uncommitted, over/under budget.
Every control, explained
Run analysisOne run.
Assign vendorPick from vendor database or create new.
Link to submittalCross-reference a procurement item to its submittal tracker entry.
Import to Procurement TrackerPush to tracker.
Export PDFProcurement log report.
Export XLSXRaw table.
Chains
Chains into
Chained from
Exports
- PDF — procurement log.
- XLSX — raw table.
- CSV — flat list.
Troubleshooting
SOV line "Electrical package" is too coarse to track separately from "Switchgear" — provide a more granular source, or edit rows before import.