From plans
to materials.

Review documents, track purchases, and build takeoffs — all from one place.

127
Docs Processed
24
Pending Review
295
Active Projects
59
Training Samples
Projects
View all projects
Donner Fields
41 invoices · $296,663 billed
$11,794 open 1 mismatch 11 partial 29 matched
Sunnydale
33 invoices · $57,785 billed
$42,201 open 24 partial 9 matched
NCC Operations
22 invoices · $19,415 billed
$273 open 18 partial 4 matched
Midway Village Phase 2
1 invoices · $9,166 billed
1 matched
How Documents Connect to Purchases
Document Pipeline
📁
Source
Dropbox or Email
→
📥
Intake
intake_queue
→
⚙️
Docflow
OCR + extraction
→
🔍
Review
Verify fields
→
✅
Approved
Linked to Purchase
→
⚖
Reconcile
Match across docs
Vendor vs. Supplier (the lumber supply chain)
NCC
Nobles Construction
Issues PO, pays the vendor.
→
Vendor (dealer)
Idaho Pacific / White Cap
The company NCC pays. Their name goes on the Purchase record.
→
Supplier (mill)
Hampton / AFP / Simpson
Physically ships goods. Name appears on BOL as shipper.
→
Job Site
Donner Fields
Where materials are delivered. BOL ship-to address.
BOL ≠ Invoice. BOLs are delivery documents (no prices). Invoices are billing documents (has prices). Different vendor names between BOL and PO is normal — the supplier shipped it, the vendor sold it.
Operating Model

Every document moves through one auditable lifecycle.

PlanSight should preserve the original OCR and document evidence, normalize deterministic data where possible, capture human corrections separately, and only let approved processing values feed reconciliation, exports, FileMaker, billing, and analytics.

Core Principle
Original value, normalized value, corrected value, and approved processing value are separate layers. Nothing important gets overwritten.
01
Intake
Email, upload, watched folders, scanner/OCR, FileMaker links, or manual drop create a durable intake record.
02
Preflight
Confirm readable file, managed copy, page count, OCR/artifacts, source health, and basic metadata.
03
Identity
Capture document type, vendor, project, PO, invoice, BOL, quote, order confirmation, date, and total.
04
Duplicate Gate
Check file hash plus important document numbers. Exact repeats are voided and hidden from the default queue.
05
Intake Review
Approve, deny, relabel, link, or hold the document while seeing the original preview and key numbers.
06
Extract
Use structured data and embedded text first, OCR second, and model fallback only where deterministic methods fail.
07
Normalize
Map projects, vendors, MIDs, HIDs, SKUs, materials, treatments, and descriptions to professional canonical values.
08
Review + Correct
Use one workstation to edit fields and line items beside the source document, evidence, OCR text, and correction history.
09
Compare + Process
Compare related docs, approve processing, reconcile the chain, export, analyze, and feed corrections back into rules.

Validation gates before processing

Duplicate identity Hash and document numbers must not already be processed.
Required fields Project, vendor, document type, date, and key document numbers must be known or explicitly waived.
Line identity MID/HID/material should resolve through FileMaker, hardware matrix, lumber matrix, aliases, or flagged derivation.
Source evidence Original document, OCR text, and bbox/page evidence should stay reachable from every corrected value.
Cross-doc match Quote, PO, order confirmation, BOL, invoice, statement, and billing quantities/prices must reconcile or show open deltas.
Override discipline Any manual override requires reviewer, timestamp, reason, and downstream impact.

Document states

pending_intake intake_error denied duplicate_voided approved_for_extraction extracted needs_review reviewed approved_for_processing linked reconciled exported archived
Intake Decision
Approve, deny, classify, label document numbers, and remove duplicates before extraction.
Field Correction
Compare original OCR, normalized values, corrected values, confidence, and source evidence.
Line-Item Correction
Open the bottom sheet, split the source document, zoom selected rows, and preserve original pulls.
Document Compare
Review quote vs PO, PO vs BOL, BOL vs invoice, invoice vs statement, and billing deltas.
Approval
Promote only validated and corrected values into downstream processing and analytics.
Evidence + Audit
Trace every processed value back to source file, OCR text, bbox/page, reviewer, and correction reason.
Design decision: Inbox, Compare, and Review should converge into one workstation cockpit. The UI can expose modes, but the underlying lifecycle, correction ledger, duplicate policy, validation gates, and approved analytics layer should remain unified.