A live record of the project, versioned and tied to the elements in the model. Not a binder.

The project record stays with the project, not with the person who left.

An issue closes only when the fix is proven. No proof, no close. How that works in BidLight: 1. The issue pins to the element. It lives on the beam, duct or pipe it concerns in Revit or Navisworks.

Yes. Stay in Navisworks. BidLight runs inside it, so you publish straight from the federated model and close issues there too. How it works on a real job: 1.

You do not take anyone's word that an issue is closed. In BidLight an issue can only close with proof attached: a screenshot, a tagged user, and the model commit that fixed it.

Yes. An issue on a level is pinned to the element it concerns, so you can close it against that element and the whole level moves with proof attached. A sign-off without proof is just a shrug.

Every export is versioned and compared element by element, so you see exactly what moved between the version that got signed off and the version in the model now. That is the check.

Every area has one live record, and sign-off is pinned to it. You do not dig through email or a PDF set to find out who closed what. How it works in BidLight: 1.

An issue closes only with proof. In BidLight, that means three things attached to the element: a screenshot, a tagged user, and the model commit that fixed it. No proof, no close.

The record lives in the model, not in someone's head. That is the whole point of how BidLight works. When a coordinator walks, nothing walks out with them. Here is how it holds up on a real job: 1.