Documentation

Requirements

• Revit: 2024, 2025, 2026 or 2027. One installer covers every version present on the machine.
• Windows: 10 or 11, 64-bit.
• Runtime: [.NET 8 desktop runtime: bundled or required — confirm].
• Network: none needed to run. See Licence & offline use.
• Disk: the local cache is roughly [N] MB per open model; it is rebuilt on demand and safe to delete.
• Model size: the published measurements were taken on a medium commercial model (136 doors, 195 sheets, 193 warnings). The grid is designed to stay responsive at 100,000-plus rows by filtering rows rather than re-rendering, but that is a design target; no large or federated model has been benchmarked yet, and no figure is claimed for one.

Install & uninstall

Interactive

1. Close Revit.
2. Run IQTools-1.0.0.msi. The default scope is per-machine (all users, administrator rights). Choose per-user on a machine where you cannot elevate.
3. Start Revit. IQ Tools is on the ribbon under [TAB NAME].

Silent, for deployment tools

msiexec /i IQTools-1.0.0.msi /qn            &:: per-machine, default
msiexec /i IQTools-1.0.0.msi /qn [PER-USER PROPERTY]   &:: per-user

The installer is signed by [SIGNING IDENTITY]. If SmartScreen shows a reputation warning on an early build, the signature is still the thing to check: right-click the MSI → Properties → Digital Signatures.

Uninstall

Windows Settings → Apps → IQ Tools → Uninstall, or msiexec /x with the same MSI. The add-in manifest, the ribbon entry and the per-project caches are removed. Your models are untouched: IQ Tools only ever wrote what you approved in a Sync Review, and that is ordinary Revit data.

If two copies load. A stale per-user install alongside a per-machine one makes Revit load the add-in twice. Uninstall both and reinstall once. The ribbon showing two IQ Tools panels is the symptom.

The Sync Review model

IQ Tools never writes to the model as you type. This is not Revit's Synchronize with Central: an IQ Tools sync writes to your local model as one transaction, and you synchronize with central as usual afterwards. It follows four stations:

1. Read. The model is read out-of-process over a local named pipe. Reads never modify the document.
2. Cache. What was read lives in a local SQLite file. The grid, filters, grouping, censuses and exports all run against that cache, which is why they answer in milliseconds.
3. Stage. An edit in the grid or the inspector is held in the cache and shown as pending. Revit has not changed.
4. Sync Review. Sync shows you the exact batch: every element, every parameter, old value and new value. Approve it and the batch lands in Revit as one transaction. A cell Revit refuses is reported against that cell with the reason, and the rest of the batch still lands.

This is deliberate friction. The time study prices it at roughly 6–11 hours a year. It is what lets you catch a bad bulk edit before it touches 136 doors.

Worksharing

• Before writing, each element in the batch is checked against Revit's live checkout state. An element checked out by a colleague is refused with their name against that row ("Checked out by …"); pinned and deleted elements are refused with their reason. The remaining rows commit.
• Refusals are listed per row after the sync, so you can see exactly which edits did not land and why, and re-sync them once the element is released.
• IQ Tools does not borrow, check out, or relinquish elements on your behalf, and it does not call Synchronize with Central — you still SWC in Revit in the normal way. [unverified — needs runtime probe] whether a successful IQ Tools commit implicitly places the edited elements on your own worksharing checkout/ownership the way a native edit would.

Undo

• A sync is one Revit transaction, so one Ctrl+Z in Revit reverses the whole batch. The one exception: if Revit rejects a grouped-element edit at commit time, the batch is split and the retried rows land as their own transactions, which adds an undo step for those rows only.
• Every sync is recorded: which elements and parameters were written, the old and new values, who committed it and when. The history is kept with the project cache and can be exported from [SYNC HISTORY LOCATION / EXPORT ACTION], so a director's question after a bad batch, "what changed, and who approved it", has an answer.

Read-only cells

• Any cell that cannot be edited is greyed, and double-clicking it states why: a computed value, a workset checkout, or a restriction Revit imposes. Type parameters ARE editable — one edit is written to the type and applies to every instance of it, which the confirmation dialog states before you commit. On Revit 2026, parameters that Autodesk made read-only on a sheet show as read-only for that reason.

What it will not do

• Edit geometry, place elements, or compose views. Geometry is Revit's job.
• List elements from linked Revit models in the grid. The grid shows the open model only — see Does it work across linked models? below.
• Write to the model while a Sync Review is open somewhere else. One batch at a time.
• Discard staged edits on a licence event. An expired licence degrades to read-only and lets you commit or export what you have staged.

Does it work across linked models?

Today, no: the grid lists elements of the open model only. Elements inside linked Revit models are not listed, filtered, or editable in the grid — open the linked model directly in Revit (or as its own host model in IQ Tools) to work with its data.

[ROADMAP OR PERMANENT — owner to state]

Where native Revit closes the gap

Several workflows on this site are honestly priced against a native baseline that a newer Revit release, or a different native path, narrows. This table collects those admissions in one place.

Where your data lives

• Model data is cached in a local SQLite file per project under [CACHE PATH]. It is never uploaded. It is safe to delete; the next open rebuilds it.
• Logs are written to [LOG PATH]. They contain element IDs, parameter names and timings, not model geometry. Support will ask for them.
• Crash reporting and usage telemetry are opt-in. Nothing is collected unless you turn it on. If you opt in, a crash report carries the stack trace, the IQ Tools and Revit versions and the operating system version, never model data; usage telemetry carries feature counts, never model data. The switch is at [SETTINGS LOCATION]. See Privacy.
• Licence checks send the licence key, a machine identifier and the product version to [LICENCE SERVICE HOST]. Nothing about your models is included.

Licence, Revit versions & offline use

Two ways to buy

• Individual seats by card, monthly or annual. A seat is bound to one Windows user on one machine and can be moved from your account page without contacting support, so it survives a laptop replacement.
• Multi-seat firm plans on invoice or purchase order, with seats added, removed and reassigned by your BIM manager from one account. Seats are named: one person, one machine. Your BIM manager reassigns a seat to someone else from the account page as people move between projects. A shared floating pool for occasional users is planned, but is not available today.

Every Revit version is included

• Every seat runs on Revit 2024, 2025, 2026 and 2027. When Autodesk ships a new release it is added to the subscription; there is no separate upgrade to buy. Target availability after each Revit release: [N weeks].
• One installer carries every supported Revit version and installs for all of them by default, so a supported Revit version installed after IQ Tools finds the add-in already in place. The wizard (or the silent ADDLOCAL switch) lets IT limit the install to chosen versions. A Revit release newer than the installer needs the next IQ Tools release, which the subscription includes.

Offline, VDI and networks

• The licence revalidates online periodically and tolerates 14 days without a connection, so a firewalled BIM workstation keeps working.
• If a check is blocked — a proxy, a firewall rule, or an outage at either end — the seat keeps working. After 14 days IQ Tools starts telling you plainly that it has not been able to verify the licence and what to allowlist, but it does not take the tool away. A licence that has genuinely expired or been cancelled is a different case and takes effect immediately.
• A re-imaged workstation is normally recognised as the same machine, so the seat carries over with no action. If it is not — a new laptop, a replaced motherboard — release the old machine from your account page and activate the new one; no support ticket needed. Non-persistent VDI pools (Citrix, AVD and similar) are not supported today, because every session looks like a new machine. Pooled licensing for non-persistent environments is planned.
• One outbound HTTPS connection on port 443 to licence.[DOMAIN]. That is the only thing to allowlist. The system proxy is honoured, including an authenticated corporate proxy using your Windows credentials. Nothing listens for inbound connections, and no certificate pinning is used, so a TLS-inspecting proxy will not break it.
• Trial: 14 days, full product, no card. When it ends the grid stays readable and exportable; editing and Sync need a seat.

Deployment brief for IT

• What it is: a Revit add-in (one .addin manifest per Revit version) plus a separate desktop process that runs beside Revit. The two talk over a local named pipe on the same machine. No service is installed, and nothing listens on the network.
• Scope: per-machine by default (add-ins under %ProgramData%\Autodesk\Revit\Addins\<year>\, application under [PER-MACHINE PATH]). A per-user, no-admin variant installs under %LOCALAPPDATA%\Programs\IQTools\ with per-user add-ins. The two scopes are mutually exclusive on one host; the installer refuses the second and names the first.
• Silent install: msiexec /i IQTools-1.0.0.msi /qn, with ADDLOCAL to choose Revit versions. Signed by [SIGNING IDENTITY].
• Data: a per-project SQLite cache and a log file, both local (paths above). No model data leaves the machine. Crash reporting and telemetry are opt-in and off by default.
• Network: none needed to run. The only outbound call is the periodic licence check to [LICENCE SERVICE HOST]: [PORT / PROTOCOL / PROXY BEHAVIOUR / FAIL-OPEN POLICY — decisions pending, see above].
• Uninstall: standard Windows uninstall or msiexec /x; removes the add-in manifests, the application and the per-project caches. Models are untouched.
• Revit versions: 2024, 2025 and 2026 today; 2027 is added in the launch build. [Confirm 2027 is in the shipping installer before launch.]

Changelog