Two ways to count in Revu

The Count tool

The Count measurement is a click-per-device markup. Pick the tool, set a subject such as "Smoke detector", and click each symbol on the sheet; Revu keeps the running total and lists every count in the Markups List, where you can total by subject and export to CSV. It is exact, because you are the one deciding what each symbol is. It is also the slow way: every device is a click, every type is a pass over the sheet, and a dense sheet is a few hundred clicks.

VisualSearch

VisualSearch looks for other places on the sheet that look like a region you draw a box around. The usual routine:

  1. Open the Search panel and switch it to Visual.
  2. Draw a tight box around one instance of the symbol, say a smoke detector hexagon, with as little of the surrounding linework and text as you can manage.
  3. Choose the current page or the whole document, set the sensitivity, and search.
  4. Go through the results. Untick the false hits (text, similar symbols, pieces of the legend) and tick the ones you want.
  5. Apply a Count measurement to the ticked results, so they become count markups with a subject and show up in the Markups List like hand-placed counts.
  6. Repeat for the next symbol, and the next sheet if you searched page by page.

On a clean set with a few device types this is quick and the markups are yours to keep. The problems start when the set is large or the symbols vary.

When it stops working

None of this is a fault in Revu. It is a markup tool with a search feature, and it is very good at the first half of the job: giving you a marked sheet you can stand behind. The second half, reading the attributes and tallying by sheet, it leaves to you.

Doing the whole sweep at once

Fire Alarm Takeoff was built for the second half. You upload the set, point at the legend sheet, tick the plan sheets, and it reads every device on each sheet with its candela, mounting, weatherproof and duct attributes, then gives back:

Addenda are a re-run of the changed sheets, at one page each. A page is one sheet counted; the pricing page has the packs.

AI-generated count. Verify before bidding. The reading is done by software, including an AI model, and it can miss a device or misread a tag. The marked PDF exists so you can check it the way you would check your own VisualSearch results: sheet by sheet, against the original. The results page tells you where to look first.

A sensible way to combine the two

  1. Run the set through Fire Alarm Takeoff. Two pages are free on a new account, so the first try costs nothing.
  2. Open the marked PDF beside the original in Revu. Walk the sheet; look at the "Check these" items first.
  3. Fix what you disagree with on your own copy, the way you already mark up a set.
  4. Take the counts from the grid, with your corrections, into the estimate.

The fire alarm takeoff guide covers what the count has to contain, and the attributes guide explains why the tags beside each symbol matter as much as the symbol.