OUR EDITORIAL PROCESS
Built by people who’ve done the work
Built is Bluebeam’s blog for the people who design, manage, and put up the built world. Every story we publish is written, edited, and fact-checked by humans who know construction — and reviewed by someone who would have to defend it on a jobsite.
WHY WE BOTHER SAYING THIS OUT LOUD
Construction has a content problem
At Built, we publish because someone with real field or product knowledge decided it was worth your time. Search results for most construction topics are crowded with keyword-driven articles that don’t reflect how the work really gets done. This page lays out exactly how a piece gets from the idea stage to published. If you’re going to trust what we say, you should know how we got there.
HOW A STORY GETS MADE
Five steps from idea to publish
Every post on Built — whether it’s a 2,000-word guide on quantity takeoffs or a field story from a superintendent — runs the same gauntlet. The order matters. The people matter more.
01
We start with a real problem, not a keyword
Topics come from the field and the work — questions estimators really ask, workflows that ultimately break, debates AEC pros are having. A human editor decides what’s worth writing and why. If a topic only exists because a keyword tool flagged it, it doesn’t make the list.
02
A human who knows the subject writes it
Drafts come from people with the standing to write them: AEC journalists, Bluebeam staff and executives, and, sometimes, practitioners who’ve carried the work — estimators, PMs, supers, architects. When we use AI in the drafting process, it’s a research assistant and a first-draft sparring partner, never the author. A named human owns every word and opinion in the piece. If we can’t put a credible name on it, we don’t run it.
03
We check it against reality
This is the part most construction content skips. Before anything publishes, an editor verifies the claims — stats traced to their original source (not a blog that cited a blog that cited a blog), product details checked against current documentation, workflows pressure-tested against how the work is done on site. Numbers without a traceable primary source get cut. “Everybody knows” is not a source.
04
Someone who’d have to defend it reviews it
This is the part most construction content skips. Before anything publishes, an editor verifies the claims — stats traced to their original source (not a blog that cited a blog that cited a blog), product details checked against current documentation, workflows pressure-tested against how the work is done on site. Numbers without a traceable primary source get cut. “Everybody knows” is not a source.05
An editor makes the final call
AI doesn’t get the last word. A human editor reviews the final piece — for accuracy, voice, clarity, whether it earns the reader’s time — and decides whether it publishes. The division is simple: humans own what we say and why; tools only help with the plumbing (research, drafts, SEO checks, structured data). The judgment stays with people.THE EDITORIAL FILTER
What doesn’t make it onto Built
Editorial work is about saying no. Here’s what gets cut before it ever reaches you:
- Stats we can’t trace to an original, credible, non-aggregated source — government data, peer-reviewed research, primary industry reports.
- Claims that sound right in a marketing deck but fall apart on a jobsite.
- AI-generated drafts that no human is willing to put their name on.
- Vendor talking points dressed up as objective advice — including our own. If a piece only works as a Bluebeam ad, it doesn’t belong on the blog.
- Topics that exist only because a keyword tool said the volume was high. Demand isn’t the same as value.
- “Thought leadership” with no thought and no leadership.
OUR LINE ON AI
Humans own the content. Tools handle the plumbing.
We’re a construction technology company. We’re not going to pretend we don’t use modern tools — that would be dishonest, and you’d see through it. We do use AI in our process: to research, to surface gaps, to draft early passes, to catch typos. Ultimately though, it’s person who decides what’s worth writing. A person writes it or owns it. Someone with field credibility reviews and approves it. The expertise, the judgment, and the accountability are ours — names attached, defensible on a jobsite.
WHAT WE COMMIT TO
Our editorial principles
Field credibility over polish
If it reads clean but rings false to someone who does the work, it doesn’t run. The jobsite is the final fact-checker.Traceable sources, always
If it reads clean but rings false to someone who does the work, it doesn’t run. The jobsite is the final fact-checker.
Humans hold the pen and the final call
AI helps. Humans decide. No piece publishes without a named editor’s explicit sign-off — regardless of what any tool suggests.
Honest about our own product
Built is the Bluebeam blog, and we won’t insult you by hiding it. But editorial advice and sales are kept structurally separate. When we recommend an approach, it’s because it truly works.
We fix our mistakes in the open
When we get something wrong, or when the ground shifts under a claim, we correct it and say so. Accuracy beats looking infallible.
Named authors, real expertise
Every piece carries a real byline from someone with the standing to write it. No house pseudonyms. No anonymous content-farm filler.CORRECTIONS & UPDATES
Spot something wrong? Tell us.
If you find an error, contact us. Whether it’s an outdated stat, or a claim that doesn’t hold up, we review everything and fix what needs fixing. All content is reviewed and refreshed on a regular cycle so it doesn’t go stale.
WHY YOU CAN TRUST US
The range of AEC voices behind Built
Built draws on a wide cross-section of the people who actually design, build, and maintain the built world — welders, electricians, and specialty trades; structural and MEP engineers; architects and project managers; owners and developers; estimators and superintendents; and industry veterans who’ve spent careers watching how this work gets done and where it goes wrong. Some write for us. Some sit on the field-review side, pressure-testing claims before anything gets published. Some are Bluebeam product and field experts whose day jobs put them in front of contractors every week. The point is that no single perspective owns this blog. Every piece is shaped by people who’ve carried the work in some form — and who’d have to answer for it on a jobsite.THE PEOPLE BEHIND IT
Real names, real standing
Built is produced by Bluebeam’s editorial team alongside named contributors. Editorial decisions are made by real people.
Questions about how we work, or a story you think we should tell? Reach the team here.
