Revit forgets. Lens doesn’t — it gives the model a flight recorder that captures who changed what on every sync, and answers the questions that used to end in a shrug.
You synchronise, the file moves on, and the story of how it got that way is gone. Every “who did this?” becomes archaeology.
Lens has two halves. The recording side runs itself — three layers of memory that fill up as the team works. The answer side is where you go when a question lands on your desk.
Tap Input or Output to isolate a half — the other collapses.
Turn Record on once and every synchronisation writes the net story of what changed. Add a team folder and everyone’s story merges. Switch on the journal and even your own session gets a timeline.
The first synchronisation takes a baseline photograph of the model. From then on, each sync compares against it and records the net result — created, modified, deleted — with the parameter, the old value, the new value and the author Revit’s worksharing reports. No forms to fill: if the team syncs, the history writes itself.
Point Lens at a shared folder — a network drive or a synced cloud folder — and every collaborator’s records merge into one team timeline, deduplicated and clock-proof across time zones. The path is saved inside the model itself, so teammates inherit it the moment they open the file. Nobody configures anything twice.
Every collaborator’s Lens publishes its own changes here and reads the others’. The path is stored in the model — teammates inherit it automatically. Leave empty to stop sharing.
Turn on Chronicle and Lens reads this session's Revit journal into a live timeline of the commands you have run — real time, real name, colour-coded. A strip of health chips distils the same journal: warnings raised, dialogs answered, and how long ago you last synced. It is yours only, never shared.
Everything below reads from the recording above. Same panel, zero extra setup.
Search the history, click an element, audit the deletions, watch the live feed — or hand the whole week to someone as a single file.
History groups every sync by author, newest first, and the search box speaks your language: an element id, a user, a category, a parameter, a date. Excel-style filters narrow by user, category, action or date range — and every row carries the old and the new value, so the answer comes with receipts.
Switch the scope to Element and the panel dedicates itself to your selection. A row of chips answers the first question — is this element healthy? — pulling Revit's own warnings, Canon's standards violations and its worksharing state into one place. Below them sit the sections that explain each chip: Overview, Warnings, Canon rules, and every parameter tagged with where it comes from. One tap on ✨ Explain has your connected AI read the lot back in plain language.
Every deletion is logged with what it was, when it went and where it stood — room, level, host — even though Revit itself no longer remembers the element. One click plants a red ghost at its last-known position so you can stand exactly where it used to be. And because Revit never says who deleted, Lens says so honestly instead of guessing.
Live Activity polls the central model and shows who has what open for editing, what they released, what changed hands — with the active users pinned on top. It is the difference between “is anyone touching Level 2?” and a phone call.
Export builds a self-contained HTML dashboard — charts, people, hotspots, deletions, the full inventory — plus an AI-written executive summary for the humans who won’t read charts. No install, no viewer, works offline. The dashboard below is a real one: scroll it.
This is an actual HTML report Lens exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Lens starts recording from your first sync — try it on your own project. Full trial, no card.