🗓️ September 2025 Challenge - Data in Disguise!

Hi everyone!

Welcome to the September Monthly Challenge: Data in Disguise! This month is all about showcasing how you use markups as more than just visuals.

Markups may look simple at first glance, but often they carry a lot more information. From measurements and quantities to statuses, costs, and notes. Markups can be packed with valuable data that drives your projects forward.

Do your markups track more than just visuals like quantities, costs, or statuses? Share how you make them smarter, more informative, and more powerful!

📝 How to Participate

🤝 Share an example of a markup that does more than meets the eye. Post a screenshot or description of your markup and explain how it supports your workflow.

💬 Discuss how others are using markups. You might uncover a new trick to put to work in your own projects.

🏅 Rewards

All participants will earn a unique challenge badge and points to level up in the community!

📚 Resources

https://www.youtube.com/%40BluebeamInc/videos

How to Use Markups in Bluebeam Revu

Working with Markup Tools

The Markups List and Markup Data

Find more posts tagged with

Revu

Markups

Community Activity

Comments

Vince French

So, I'll go back to my trusty old Brickwork and Scaffolding take-off for this one.
The green front door is the markup to look in this example.

It is an area markup which is actually pretty useless to a bricklayer initially but then when combined with Excel it isn't.
However, first the information that it contains in the Bluebeam Markup List.
As well as the area, we also have a width and a height, which are from the standard columns, and are very useful to us.

We also have a label which clarifies identifies at a glance what the markup is.
The Layer is used in a Parent and Child configuration in order to be able to turn on and off markups as the drawing becomes rather too busy at times.

The Space allocates which housetype the markup belongs to.

Then we have the Custom Columns.
Work Details allocates the markup to a certain work section - in this case External Walls. Other work sections include External Features, Party Walls, Garden Walls, Scaffolding, etc..
Lift allocates the markup to a Brickwork Lift. In this case it is the Ground Floor which covers both the 1st and 2nd Lifts.

Power is used to determine whether the measure is to be used in Power Query in Excel. Most measures are used but things like a template for the scaffold lifts aren't. So, this is just a double check for after the csv has been exported.
Then back to the Width and Height details. These are then combined with information in an Excel table: -

With the width measurement, we can use this length to produce a lintel schedule (rounded up to the actual correct length inc the bearing at each end, the cavity tray above the door inc the number of weep vents, the amount of any bed reinforcement that is necessary, etc..

With the height, we can work out what cavity closer is required, the total length of any reveal blocks and insulated dpc's, etc..
Then of course, we know there is one of these markups so we can the add the number of dummy frames or profiles that are required.
In summary, one markup which is generally produced with a single click of a button (placing it in a cut out) can produce a whole heap of usable information.

Hope this helps to give some others a few ideas for their workflows!

Doug McLean

The big trick to getting more out of a markup is adding one or more Custom Columns to them.
In our workflows we happen to have 44 Custom Columns that we can use to add information to any markup. In addition to this we use the Space, Subject, Label, columns from the stock columns. (Along with the measurement columns of course). The data for these columns comes directly out of our Estimating Software. In essence, we use Revu as an extension of our Estimating Software.

I work in Architectural Millwork, which has very specific requirements that can only be achieved by using Custom Columns.

A Typical toolchest for us looks like this. The Subject is set to the type of Millwork that it is, and then the Label is set to the a specific product within that type. I.e. a STR-POST LAM is a straight diewall that we would build and then apply either a laminate or veneer to after it was built. A CRV-UNFINISHED would be a Curved diewall that is left RAW for a filed applied finish.

When we place a Diewall markup, we use an Area tool and then assign a specific depth to it. A diewall typically can be anywhere from 5" deep to well over 16".
We also have some of our 44 Custom columns specifically devoted to options for Diewalls.

By setting these, we will eventually tell our Estimating software (and our Drafting team) what all has been allowed for. Does this Diewall have a finished end? A Top Cap? Will it have removable panels? Note that not all of these will apply to a Diewall. Also note that some tools have some of these custom columns pre-defined so that we don't have to fill in every column with every markup. We also have a standard colour pallet that we use, and the tools are built using that pallet. We also have a list of Custom Columns where we as Estimators, can apply some additional time if we feel that the item is not standard. This gives us some flexibility and allows us to use our expertise right in the markup stage.

After we do a Markup Summary Export, the whole thing gets cleaned and prepped for import into our Estimating Software via Power Query and a couple of Excel Macros.

We go from this:

to this:

in a matter of seconds.
From there its just a simple import into the Estimating Software and we're off.
(If you caught my XCON 2022 presentation, this workflow is what I presented)

Custom columns offer you that chance to bring in so much more than just the Length, Width, Height, and Depth. Used effectively, they can generate so much data right at the beginning of the process. They are what make Revu such a powerhouse.

Want to learn some more cool tricks on what you can do with your Markups and with Power Query? Catch my Unbound 2025 presentation on Supercharging your Revu Markups with Power Query in Excel.

Doug McLean

I also have a way where I can extract two different things from the same mark up.

For that though, you'll have to come to Unbound. 😁

Vince French

Using the height and width as well as an area by any chance @Doug McLean ?

Doug McLean

MAYYYYYBE!!!

Vince French

Looking forward to seeing your presentation a

Peter Martin

With the Status column in the Markups List, you can create a custom State Model for quality control or reviews. Defining states for typical QC issue statuses and assigning them a color based on the state allows users to track the state of an issue without having to dive into the Markups List while looking over a drawing.

For example, open the Markups List and click on the Manage Status button on the Status column heading. Create a new Model with the "Add…" button called QAQC then create the associated states using the other "Add…" button for a traditional QC workflow: Issue, In Progress, Solved, and Accepted or Closed. Assign the traffic signal colors to the states - Red for Issue, Yellow (or orange for better visibility on white backgrounds) for In Progress, and Green for Solved. I applied Grey for Closed. In the Default dropdown, select "Issue" for a new markup's default state.

With the Markups List open, use the Cloud+ tool to highlight an issue that needs to be addressed and type a comment that provides clarity and context. Once the markup is complete, you'll notice the Status column populate with "Issue".

You can double-click on the Status field in the Markups List or right-click the markup itself and use the context menu to select Set Status. Choose In Progress and watch Bluebeam apply the yellow/orange color to the markup. Choose Solved and watch the magic happen again with the new color, green.

This is a simple way to communicate with color and only takes a minute - literally - to setup.

Doug McLean

You know, another great way to embed data in a markup is to use Spaces.

Used in the right way, Spaces allow you to create an 'assembly' if you will.
So now you've taken your one markup and made it part of a bigger unit by not really doing anything.

Have some more fun, tie it back to a room with another markup tool.

I'll be talking about all this in the next CANBUG meeting after Unbound.

__________
Community Champion.