Yes. Every export BidLight publishes from Revit or Navisworks is versioned, and each new version is diffed against the last element by element.

Your sub never has to leave Navisworks. BidLight runs inside it, so he publishes straight from the federated model and works his issues right there. Here is the loop: 1.

An issue pins to the element it concerns inside the model, not to a PDF or a chat thread. Click it and you land on the exact duct, pipe or beam that caused the problem. Here is the flow: 1.

The 6am digest is your daily list of what you own. It goes to every owner on the project with their issues in it. Not the whole team's pile. Yours. Each issue is pinned to the element it concerns.

No. Closing an issue in BidLight needs a person and a model commit, so your MEP sub will log in. That is the point of it. Here is what closing looks like.

Every morning at 6am, everyone who owns an issue gets a short digest of what they own.

It came back because it was never really closed. Someone marked it done, but nothing tied that closure to the model.

Handover falls apart when the project history lives in one person's head, a Teams thread and a folder of PDFs.

Yes. The project view shows who is behind while there is still schedule to recover. You do not wait for the GC coordination meeting to find out an issue has been sitting open for weeks.

Hand over the login, not a folder of files. BidLight keeps one live record of the project inside Revit and Navisworks, so the history stays with the model, not with whoever ran the last meeting.