Home / Guides / Chronicle
QA / QC panelChronicle ★ Flagship

Every Revit session leaves a story. Chronicle reads it back.

Revit writes a journal of everything that happens in a session — every command, every sync, every crash — in a script only Autodesk support can read. Chronicle turns it into plain language: pick any session, or several, and read the whole story on a filterable timeline, then export a post-mortem anyone can open. And while you work, it quietly records what changes on every sync, so “who deleted this?” finally has an answer.

Revit 2024–2027Read-only — never touches the modelWorks with no model openSelf-contained HTML post-mortem
Why Chronicle exists

The evidence was always on disk. Nobody could read it.

Every session, Revit writes journal.NNNN.txt — the full record of the day, in a replay script meant for a machine. When a model crashes or a wall vanishes, the answer is in that file; the file might as well be encrypted.

Revit on its own
  • “Jrn.Command "Ribbon", "… ID_FILE_SAVE_TO_CENTRAL"” — thousands of lines like this per session.
  • “Who deleted it?” and “did they sync before the crash?” are guesses.
  • The crash post-mortem is a phone call and a shrug.
The same journal, through Chronicle
  • Every action in plain language, on a timeline you can search and filter.
  • Every sync, the gaps between them, and honest risk flags — “Went 3h 40m without synchronising.”
  • One self-contained HTML file anyone can open — no Revit needed.
A session post-mortem, start to finish

From cryptic journal to a story you can hand over.

Chronicle is read-only end to end — it reads files Revit already wrote, and records to its own local store. It never touches the model.

Open it

Every session you ever ran, already listed.

Click Chronicle — no model needed. It scans every installed Revit version's Journals folder in the background, with a real progress readout, and lists the sessions grouped by project, model or user. Each row is named by the model, never the journal number; it carries a verdict dot — green clean, amber worth a look, red no clean exit — plus the user, date, duration and action count. Tick one session or five: the whole week of a model, or one user's day across models, merges into a single story.

New to Revit: your Revit history as a browsable list — months back, across versions.
Chronicle — SessionsBIMIO
Sessions
84 session(s) across 6 project(s). Tick the ones to show in Chronicle's Journals card.
Select allGroup by: Project ▾
Snowdon Towers — Sample Architecture · 3 session(s) · 2 models
Snowdon Towers — Sample Architecture
fmartinez · Mon 06 Jul 2026 · 08:47 · 7h 32m · R2025 · journal.0412
4890 actions
Snowdon Towers — Sample Architecture
fmartinez · Fri 03 Jul 2026 · 09:05 · 6h 04m · R2025 · journal.0409
3112 actions
No model opened
fmartinez · Thu 02 Jul 2026 · 18:21 · 12m · R2025 · journal.0408
36 actions
2 session(s) selectedCloseShow in Chronicle
Read it

A timeline in plain language — with a verdict on top.

“Synchronised with central.” “Loaded family Door-Handle-Lever.” “Error reported — 1 error(s), 2 warning(s).” Every action lands on the timeline, colour-coded by category, newest first, searchable. Escape-key and zoom churn is classed as noise and hidden by default — one tick brings it back. Above it, the verdict: how often the session synchronised and the longest gap, warnings and errors, and whether the journal ends with a clean close. The flags are honest sentences — “Last sync was 52m before the session ended — unsaved work may be at risk.”

New to Revit: a session you can interrogate — instead of a log you scroll past.
ChronicleBIMIO
!
Snowdon Towers — Sample Architecture
Snowdon Towers · Central · fmartinez · Revit 2025
Duration7h 32m
Actions8002
SharingCentral
Syncs9
Longest gap3h 40m
Warnings14
Errors1
Search actions…
All categories ▾All sessions ▾Noise
16:12:04ErrorError reported — 1 error(s), 2 warning(s)
15:58:41WorksharingSynchronised with central
15:31:09CreateWall: Architectural
14:47:52FileLoaded family Door-Handle-LeverSnowdon Towers — Sample Arc… · 06 Jul 08:47
12:07:18WorksharingSynchronised with central
6000 of 8002 action(s) · noise hiddenExport HTML…Copy
Meanwhile, it records

Chronicle is the suite's recorder.

While you work, Chronicle captures what every sync changed — created, modified, deleted — clustered per sync and per user, so a sync three people fed shows three correctly attributed bands. Select an element and its history follows; the Deleted card names the deleter when the record knows, and says “Unknown” when it honestly doesn't. Two switches — Live Activity and History — sit right on the cards, mirrored live with the Lens panel.

New to Revit: “who changed what, sync by sync” as a record — not a memory.
Chronicle — Snowdon TowersBIMIO
Search activity — user, category, name…
Refresh
Following selection · Doors · Single-Flush 1200 × 2100 #187245
Live Activity12 eventsON
M. Weaver — editing 36 elements ▸ · 2m ago
J. Ortiz — synced · 214 elements · 8m ago
HistoryProject · Whole projectON
created214
modified1032
deleted57
syncs38
Sync · M. Weaver — 214 changes · 2h ago
Fire Rating → 60 · 18 Doors
M. Weaver — created Single-Flush 1200 × 2100
M. Weaver — deleted 3 Doors
What changed

Paint the difference into the view.

Compare against the last sync, this session — or any sync the record holds. Chronicle totals created, modified and deleted, lists the most-changed categories each with a one-click Select, and paints the model: created green, modified amber, everything untouched ghosted. Toggles isolate each group while the paint is on, and clearing it puts the view back exactly as it was.

New to Revit: “what moved since Thursday?” answered in the view itself.
Chronicle — Snowdon TowersBIMIO
Search activity — user, category, name…
Refresh
What changed
Last syncThis sessionSync…
created38
modified121
deleted6
Doors · 42 — Select
Walls · 31 — Select
Ducts · 18 — Select
Paint in view ↗ created green · modified amber · untouched ghosted
Hand it over

A post-mortem anyone can open.

One click exports the combined timeline as a single HTML file — no install, no internet, works offline. Session status, duration, syncs, warnings and errors up top; a written summary; the sync-cadence strip; the full filterable timeline and the most-used commands. Mail it to whoever asked “what happened on Thursday?” — they need a browser, not Revit. The report below is a real one.

Snowdon Towers — Sample Architecture-chronicle.html
9 syncs
!Ended without a clean exit — a crash, or the session is still open.
Went 3h 40m without synchronising.
4890 actions on the timeline · noise separated
See the real output

This is an actual HTML report Chronicle exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.

Open full report

Stop guessing what happened.

Chronicle ships on the QA / QC panel of the BIMIO tab. Open any session — even from months ago — read it in plain language, and export the post-mortem. Read-only, always. Revit 2024–2027, full trial, no card.

← PreviousAssay