Book a model check →
For BIM & VDC

You own
the model.
You own
the issues.

Forefront IO does not federate, clash, or close. It proposes candidate conditions from trade-language checks. Your review queue gets install reality, not only geometry conflicts.

Book a model check → See the check ↓
Operating boundary
Runs on
The federated model you provide
Applies
A pack you switched on
Returns
A candidate, with a measurement
Stops at
Your reviewer
Writes out
Only after accept
Candidate, not verdict.
01 — Where it sits

A trade pass underneath.
Not a second coordination tool.

01 / 05

Federated BIM

The file you already run.

02 / 05

Trade check

Field language, mapped to elements in that file.

03 / 05

Configured requirement

Project spec or a sourced rule you turned on.

04 / 05

Candidate

Measured condition, or insufficient data.

05 / 05

Your review

Accept, reject, or leave it off the log.

After clash grouping, or beside it. Before trade sign-off. Into the meeting. Not instead of the meeting.
02 — The four results

Four states.
No silent skips.

The language model stops at intent. The model and the requirement do the check.
01 / 04

Candidate

Element, requirement, measurement.

02 / 04

Accepted

Reviewer sends it to the tracker.

03 / 04

Rejected

Not an issue. Stays off the log.

04 / 04

Insufficient data

The model cannot answer. Shown. Not guessed.

LANGUAGE MODEL → INTENT   /   MODEL + REQUIREMENT → CHECK   /   REVIEWER → DECISION
03 — The boundary

Why this is
not a bypass.

01
Checks run only on the federated model you provide.
02
Rule packs are configured. There is no hidden brain.
03
You choose the trades and the packs.
04
Write-back is off until a designated reviewer accepts.
05
Bad models produce insufficient data. That is coordination work made visible, not a software failure.
You still own
Forefront IO does not
Federation
Federate
Clash detection
Replace clash
Model authorship
Author the model
Issue close-out
Close the issue
04 — Tracker

Your tracker
stays the tracker.

Accepted items are meant to land in the workflow you already run. Connectors get named when they are live. Not before.

01
Issue / BCF path
02
CDE remains source of truth
03
No silent publish
Full-scale review
Full-scale review is available when spatial judgement matters. The headset is the surface. The product is the check.
Model check

Bring the person
who owns the file.

One trade sentence. One configured requirement. One candidate — including a reject or an insufficient-data state if that is what the model returns.

Book a
model check →
Forefront IO surfaces candidate model conditions for qualified human review. Candidate conditions are not code rulings, engineering determinations, or automatic issue approvals.