Product · risk operating system

Turn construction signals into early warnings.

SlabSignal connects site captures, schedules, budgets, change orders, supplier updates, and field reports to help teams see what is slipping, why it matters, and what to do next.

Risk signal pipelineLive
01
Field evidence
Captures, walks, notes
02
Progress comparison
Plan vs actual
03
Risk prediction
Ranked, explained
04
Recovery plan
Actions for review
05
Evidence pack
Owner / lender brief
The SlabSignal system

From signal to recovery, one rail.

Five disciplined layers turn raw site reality into reviewed recovery actions. Risk intelligence flags the signal; the project team owns the call.

  1. 01LAYER
    Observe
    Data in
    Site photos, drone flights, 360 walks, field notes.
    Analysis
    Localize captures to WBS zones; tag visible work in place.
    Output
    Captured progress, by activity, with source frames linked.
    Decision
    Trust the lookahead — or not.
  2. 02LAYER
    Compare
    Data in
    Schedule (P6 / MSP / Asta), budget, contractor reports.
    Analysis
    Reconcile actual vs plan at the activity and package level.
    Output
    Drift map: where reality is ahead, on, or behind plan.
    Decision
    Where to focus this week's recovery attention.
  3. 03LAYER
    Predict
    Data in
    Drift, predecessors, weather, supplier feeds, change orders.
    Analysis
    Forecast slip and exposure on the critical path.
    Output
    Ranked risk list with confidence and affected milestones.
    Decision
    Which risks justify a recovery action now.
  4. 04LAYER
    Recover
    Data in
    Risk list, crew availability, sequence constraints, scope.
    Analysis
    Generate recovery options with float, effort, and trade-offs.
    Output
    Suggested actions with owner, due date, and impact.
    Decision
    Which action the project team approves.
  5. 05LAYER
    Report
    Data in
    Approved actions, evidence, status changes from the week.
    Analysis
    Compose the brief with linked evidence and owners.
    Output
    Weekly risk and recovery brief for owner / lender / board.
    Decision
    Defensible answer to 'what changed and why'.
Core product modules

Seven modules. One project view.

Every module reads from systems your project already runs on, and contributes evidence to the same risk feed.

Module · 01

Site Progress Intelligence

What is actually built, by activity.

  1. 1Ingest site photos, drone captures, 360 walks, and field notes.
  2. 2Locate captures against the WBS and the planned sequence.
  3. 3Compare visible work in place to schedule and milestones.
  4. 4Surface visible progress drift with source frames attached.
Reads from
DroneDeployOpenSpaceField photosDaily reports
You receive
Progress score per activity, with linked evidence frames.

Human in the loop · Flagged for human review before status changes are applied.

Module · 02

Delay Predictor

Which milestones are slipping, and by how much.

  1. 1Identify slipping tasks from observed progress and predecessors.
  2. 2Roll slip forward through the critical path.
  3. 3Estimate delay probability and impact on key milestones.
  4. 4Recommend recovery actions tied to the slipping activities.
Reads from
Primavera P6 (.XER upload)CSV fallback
You receive
Forecast slip per milestone with the activities driving it.

Human in the loop · Recovery actions are suggestions for planner approval.

Module · 03

Cost Risk Radar

Where cost is drifting before close-out.

  1. 1Track committed cost, change orders, and contingency draw.
  2. 2Watch package-level pressure against approved budget.
  3. 3Surface cost exposure with the lines and POs driving it.
  4. 4Connect cost risk to related schedule and scope signals.
Reads from
Yardi Elevate (REST API)Procore commitmentsCSV fallback
You receive
Ranked exposure by cost code with the cause behind each.

Human in the loop · Cost changes are reviewed by commercial before posting.

Module · 04

Change Order Analyzer

Plain-language impact on scope, cost, and float.

  1. 1Parse directives, RFIs, and change orders.
  2. 2Identify scope, cost, schedule, trade, and approval impact.
  3. 3Estimate dispute risk and missing approvals.
  4. 4Summarize impact in plain language, ready to edit.
Reads from
Autodesk Build (webhook)Procore submittalsCSV fallback
You receive
Editable impact brief mapped to activities and packages.

Human in the loop · Output is a draft for the PM and commercial team.

Module · 05

Supplier Risk Monitor

Long-lead exposure, before it becomes a delay.

  1. 1Monitor delivery confirmations, lead times, and shipping events.
  2. 2Track procurement gaps and supplier notes.
  3. 3Flag material risk against the install date.
  4. 4Connect supplier risk to the milestones it affects.
Reads from
EDI ASN feedsCarrier APIsProcurement log
You receive
Per-package supplier status with affected install windows.

Human in the loop · Slips trigger a notification — they do not auto-replan.

Module · 06

Safety Signal Detector

Decision support for the safety lead — not an authority.

  1. 1Surface visible site-risk signals in captures and observations.
  2. 2Cluster near misses by zone and activity.
  3. 3Attach confidence and the source frame for every flag.
  4. 4Route every signal to a named human reviewer.
Reads from
Field observation logToolbox topicsSite captures
You receive
Signals queue for the safety lead, with review status.

Human in the loop · SlabSignal is decision support. The safety lead is always the final authority on stop-work and corrective action.

Module · 07

Weekly Recovery Plan

The brief, with evidence and owners attached.

  1. 1Generate the weekly risk summary across all modules.
  2. 2List top recovery actions with impact and effort.
  3. 3Assign owners and target dates for each action.
  4. 4Connect every action to the evidence behind it.
Reads from
All modules aboveApproved actions from last week
You receive
Reviewable brief for owner, lender, and board distribution.

Human in the loop · Brief is held for human approval before it is sent.

Evidence-first intelligence

Every warning should show its evidence.

Risk without evidence is just an opinion. Every flag in SlabSignal lands with the source, the affected activity, and the recommended next step — ready for a human to review.

Risk record · anatomy

What lands on a reviewer's screen

Reviewable
Field
Field capture
Drone, 360 walk, photo
Field
Schedule dependency
Activity + predecessor
Field
Affected milestone
Critical path link
Field
Cost item
Budget line, PO, CO
Field
Supplier update
ASN, carrier event
Field
Change order
Directive, RFI, CO
Field
Confidence level
Model + rules
Field
Recommended action
Owner, effort, impact
Field
Human review status
Pending / approved
How SlabSignal is different

Construction tools report what happened. SlabSignal shows what is drifting.

Existing tools each cover one side of the project. SlabSignal connects them and turns the gap into a ranked, reviewable risk feed.

CapabilityField reportingSchedule toolsDocument storageGeneric dashboardsSlabSignal
Captures site reality
Drone, 360, photo, field notes — tied to activities.
SupportedNot coveredPartialNot coveredSupported
Compares plan vs actual
At the activity / package level, not just summary roll-ups.
Not coveredPartialNot coveredPartialSupported
Predicts what is drifting
Forward-looking risk on milestones and exposure.
Not coveredNot coveredNot coveredNot coveredSupported
Proposes recovery actions
With owner, effort, and impact attached.
Not coveredNot coveredNot coveredNot coveredSupported
Every flag carries evidence
Source capture, activity, cost, supplier, CO.
PartialNot coveredPartialNot coveredSupported
Human-reviewed by default
Risk intelligence suggests; the project team approves.
Not coveredNot coveredNot coveredNot coveredSupported
Generic categories — no individual products are named.
Security & trust

Verified controls behind every SlabSignal signal.

Certification scope, encryption, retention, access, identity, residency, and incident response — stated exactly as audited.

SOC 2 Type 2

SOC 2 Type 2 certified October 2025. Scope includes AWS Virginia region infrastructure and the SlabSignal core application.

Encryption

Data is encrypted at rest with AES-256 via AWS KMS and in transit with TLS 1.3.

Retention

Project artifacts are retained for 7 years. System logs are retained for 30 days.

Access control

RBAC tiers: System Admin, Organization Admin, Project Admin, Read-Only User.

Identity

MFA is enforced through Okta or Azure AD SSO.

Residency

Data residency is US-only in AWS us-east-1.

Incident response

Incident response targets: 4-hour initial response for P1 critical bugs; 24-hour SLA for P2/P3.

Automatic — SlabSignal
  • Signal generation
  • Data cross-referencing
  • Alert notification
Human decision required
  • Risk level determination
  • Recovery action approval
  • Financial impact sign-off

SlabSignal generates signals, cross-references data, and sends alerts. Risk level determination, recovery action approval, and financial impact sign-off remain human decisions.

From signal to recovery

Start with one project. See what is drifting.

Connect the schedule, a capture source, and the cost feed. SlabSignal ranks the first risks within a day.