Bluebeam and GeoCivix: where to get help

Bluebeam Revu is a separate product, made by a different company. Plan review uses it, but we don't build it and we can't fix it.

That distinction decides where you should go. Ask us about anything that crosses between GeoCivix and Bluebeam. Ask Bluebeam about Revu itself.

Ask Bluebeam

These are Revu questions. Bluebeam's own documentation is more accurate and more current than anything we could keep in step with, so we point at it rather than maintaining a copy that drifts.

If a link has moved, search support.bluebeam.com rather than assuming the answer is gone. Bluebeam reorganises its documentation periodically; the content usually survives the move.

Ask us

These involve GeoCivix, even when the error message says Bluebeam. Raise them with support.

• A document that won't save back after markup
• .bfx files that don't open, or open in the wrong thing
• The Import to Bluebeam action on a project's Documents panel
• Redlines that don't appear on the flattened set
• Anything about which documents go to Bluebeam and when

The rule of thumb: if the problem involves a file moving between GeoCivix and Bluebeam, it's ours. If it's about Revu on its own — installing it, licensing it, drawing on a PDF that's already open — it's Bluebeam's.

Tell us both halves when you report one. Your Revu version, and the GeoCivix project or permit number. Either alone usually costs a round trip.

A note on PDF/A

Documents saved as PDF/A resist annotation by design — the format exists to guarantee a file stays fixed, which is the opposite of what markup does. If a drawing can't be marked up, check the format before assuming Revu is broken. The fix is upstream, in how the file was produced.

If you're the person who supports Revu at your organisation

Two things worth doing once rather than repeatedly:

Standardise the version. Reviewers on different Revu versions produce different results, and the difference surfaces at the worst moment — when a set is due back. Agree one version and a schedule for moving.

Own the tool set. A shared markup tool set makes comments consistent between reviewers and legible to applicants. Decide who maintains it and how reviewers get updates, or it fragments quietly.

See Markup and redlines in Bluebeam for how markup fits into the review cycle.