Last reviewed . Revu’s panels move between versions. If a step here no longer matches what is on your screen, tell us and we will fix it.
The short version
Decide which systems you carry and who owns the rough-in. Read the legend and the risers first. Count each device type as its own count, and count data by port. Tag counts by floor and room. Trace cable along the real pathway to the right closet, then add the drop, the rise and the service loops. Split rough-in, devices and head-end, and check it all against the schedules and the AV equipment list.
The search-and-check technique for counting is in How to count symbols on a drawing, and the power side of the same ceiling is in How to do an electrical takeoff in Bluebeam Revu.
Low-voltage and AV takeoff, in order
Settle which systems are yours, and who does the rough-in
Low voltage is not one scope. Structured cabling, access control, video surveillance, fire alarm and audio-visual can each be its own bid package, its own spec section in Division 27 or 28, and its own sub. Read the spec and any responsibility matrix before you open a plan sheet, and write down which systems you are carrying.
Then find out who owns the rough-in. Back boxes, conduit stubs to the ceiling and sleeves through walls are often the electrical contractor’s work, carried under Division 26, with the low-voltage contractor pulling and terminating cable. Sometimes it is the other way round. Either answer is fine. Not knowing is how a bid ends up carrying the same back box twice, or not at all.
Fire alarm deserves its own line here. On some jobs it is a separate design-build package with its own drawings issued later. If it is in your scope, take it off as its own system. If it is not, leave it alone even when the devices are drawn on your sheets.
Read the legend and the riser diagrams before you count
The legend is where a triangle with a 2 next to it becomes a two-port data outlet and a triangle with a W becomes a wireless access point. Symbol sets vary by engineer and sometimes by sheet, so read the legend on every T, TY or LV series sheet you are using, not just the first one.
The riser diagrams tell you what the plans cannot: how many IDFs there are, which floors each one serves, the backbone between the MDF and every IDF, and where the head-end gear sits for each system. Keep the riser open beside the plan for the whole takeoff. It is the sheet that turns a pile of device counts into a system you can price.
Count devices one system at a time, and count ports, not plates
Build a Count tool for each device type in your Tool Chest, with the system in the subject: "DATA, 2-port outlet", "ACS, card reader", "CCTV, fixed dome", "AV, ceiling speaker". Box one clean instance, run Visual Search across the sheet or the set, turn the results into counts, then move to the next type. A search that mixes a single-port and a two-port outlet gives you a number you cannot cable.
For structured cabling the unit that matters is the port, because every port is its own cable back to the closet. A two-port outlet is one plate, one back box and two cables. Record both: the device count for the box and the plate, the port count for the cable and the terminations.
Then pan the sheet for what the search missed. Rotated symbols, symbols under a tag and symbols on a hatched wall are the ones that go quiet. The generic technique for that check is in How to count symbols on a drawing.
| System | What to count | What to measure | Check against |
|---|---|---|---|
| Data and telecom | Outlets by port count, wireless access points, IDF and MDF racks | Horizontal cable per port, backbone between closets, cable tray | Riser diagram, device schedule per IDF |
| Access control | Card readers, door contacts, request-to-exit devices, panels | Cable from each door to its panel | Door hardware schedule |
| Video surveillance | Cameras by type, recorder, mounts | Cable from each camera to its closet | Camera schedule, riser |
| Fire alarm, if in scope | Initiating devices, notification devices, modules, panels | Circuit cable and conduit, per the fire alarm drawings | Fire alarm riser and device matrix |
| Audio-visual | Displays, speakers, microphones, touch panels, floor boxes, wall plates | Cable from each device to its rack or room equipment | AV equipment list and room-type sheets |
Tag every count by floor and by room as you go
Low-voltage quantities get asked for in more ways than most trades: by system, by floor, by IDF, by room for the AV rooms, by phase for a fit-out. If the counts only carry a type, every one of those questions means counting again.
Revu’s Spaces tag a markup with the space it sits in, and the Space column in the Markups list lets you sort and filter by it. Draw spaces for the floors, the IDF zones and the AV rooms, and add a Custom Column for system so the list can be filtered any way somebody asks. Put each system on its own layer too, so you can switch one off and see the others clearly.
Measure cable as a route, then add the drop, the rise and the slack
A cable runs from the device to its closet along the pathway, not in a straight line. Use Polylength to trace the route the cable really takes: down the corridor in the cable tray or along the J-hook path, then across to the device. Measure to the IDF that the riser says serves that area, not to the nearest closet on the sheet.
The plan length is not the cable length. Every run also climbs from the device box up to the ceiling pathway, drops at the closet down to the rack, and leaves a service loop at one or both ends. Keep those as separate allowances, written into a Custom Column or a note your shop agrees on, not buried in the traced length where nobody can check them later.
On a large floor, a common approach is to trace a fair sample of runs per IDF zone, nearest, farthest and a spread in between, take the average with the allowances added, and multiply by the port count for that zone. Whatever method you use, check the longest run against the channel limit in the cabling standard the spec calls out. A run that comes close is a sign the device belongs to a different closet.
Keep rough-in, devices and head-end as three different lists
Rough-in is the back box, the mud ring, the conduit stub to the ceiling, the sleeve through the wall and the firestop at a rated wall. Devices are what the end user touches: outlets, readers, cameras, speakers, displays, touch panels. Head-end is the gear in the room: racks, patch panels, the access control panel, the recorder, the fire alarm control panel, the AV processor and amplifiers.
They are priced differently, often installed by different people, and sometimes some of them are owner furnished. One device count can drive all three, so measure once and split the result into three named quantities rather than three separate takeoffs that drift apart.
Floor boxes and AV wall plates need extra care. A floor box in a conference room can carry power and data and AV connections in one device, and it usually needs a coring or a sleeve through the slab. Decide which scope owns each part of it, and write that into the name of the count.
Reconcile against the schedules and the AV equipment list
Most low-voltage sets carry something to check against: a door hardware schedule that says which doors get a reader, a camera schedule, a device schedule per IDF, and on AV jobs an equipment list or a room-type sheet that says what goes in each conference room. A count that has never been held against one of those is a guess.
When the plan and the schedule disagree, that is the finding. A door shown with a reader on the plan and no electrified hardware on the schedule, or an AV room type with a mic count the plan does not show, is an RFI. Export the Markups list to CSV or Excel, set it beside the schedule, and work the differences line by line.
Counting plates and cabling plates
Cable follows ports, not outlets. A floor of two-port outlets cabled by plate count carries half the cable it needs.
Taking the plan length as the cable length
The drop from the ceiling, the rise at the closet and the service loops are real cable on every run. Leave them out and every run is short by the same amount.
Measuring to the nearest closet instead of the right one
The riser says which IDF serves which area. A run measured to the closest room on the sheet can be the wrong closet entirely.
Carrying rough-in that belongs to the electrician
Back boxes and conduit stubs are often in Division 26. Price them twice and the bid is high; assume the other trade has them when it does not and it is low.
Mixing systems in one count
A data outlet and an AV wall plate can look alike at plan scale. One count holding both cannot be priced or cabled.
Counting fire alarm devices that are not in your package
Fire alarm is drawn on many low-voltage sheets and bid as a separate package on many jobs. Read the scope before you count it.
Never checking the AV equipment list
AV rooms are specified by room type and equipment list as often as by symbols. The plan alone undercounts the gear in the rack.
Questions people ask
Do I count data outlets or data ports for a cabling takeoff?
Both, for different things. The outlet count prices the back box, the plate and the rough-in. The port count prices the cable and the terminations, because every port is its own cable back to the closet. A two-port outlet is one plate and two cables.
How do I get from a traced cable route to a cable quantity?
Trace the route the cable really takes with Polylength, along the tray or J-hook path to the closet the riser assigns. Then add the vertical drop at the device, the rise at the closet and the service loops, as allowances you can see and change rather than numbers folded into the trace. On a big floor, average a sample of runs per closet and multiply by the port count.
Who carries back boxes and conduit stubs for low-voltage devices?
It depends on the job. Often the electrical contractor carries them under Division 26 and the low-voltage contractor pulls and terminates cable, but some specs put the rough-in in Division 27 or 28. Check the responsibility matrix or the spec before you price it, and name the count by which scope owns it.
What should an AV takeoff check against besides the floor plan?
The AV equipment list and any room-type sheets. AV rooms are often specified as a type, with the displays, microphones, speakers, processors and control panels listed once for every room of that type. The plan shows where the devices go; the list shows what is in the rack.
How do I keep low-voltage quantities separate by floor and by system in Revu?
Name each count with its system, draw Spaces for the floors and closet zones so every markup is tagged with where it sits, add a Custom Column for system, and put each system on its own layer. The Markups list can then be filtered or exported to CSV by any of them.
The faster way through it
Or ask for the count out loud
“Count the two-port data outlets and the card readers on T-201.” Our AI model reads the sheet, works out which symbols the scope covers, and drives the Bluebeam Revu you already have open to place the counts. They land in your Markups list as native, editable markups, named by system the way you asked for them. It asks before it writes.