The Floor Has Risen
A junior designer once handed me a code report that was entirely correct and completely unconsidered. I have been thinking about it ever since, because the thing that made it inadequate is the only thing we have left to sell.
August 19, 2026
4 min read
Frank Cauthen, AIA, LEED AP BD+C, DBIA
A junior designer once handed me a code report I'd asked for. Everything in it was correct. The occupancy classifications were right, the egress calculations checked out, the references were current. And I sat with it for a long moment before I could say anything.
Default type. Margins that fought the page. Tables that ran on because the data ran on. Diagrams that answered the question without considering who would read them. It was, in the most literal sense, adequate.
I understood exactly how it had happened, because I would have done the same thing at that point in my career. Nobody had ever told them this document was design. They had been taught, implicitly, that there is real work: the building, the form, the thing that gets photographed. And then there is the paperwork that surrounds it. They had prioritized correctly according to everything the profession had shown them. And they had turned it in on time, which was more than I always managed.
But somebody reads it. A plan reviewer at seven in the morning with forty submittals in the queue. A client's project manager trying to explain a constraint to a board that doesn't speak our language. A contractor pricing a condition. Every one of them is forming a judgment, and not only about the code. Every drawing that leaves the office is an argument about our judgment. When the diagram is careless, the reader quietly begins to wonder what else was.
Beauty in a technical document isn't decoration. It is the most visible evidence we have that someone was paying attention.
The floor has risen
For most of my career, making a clean document took skill. You had to know how to set type, build a hierarchy, decide what belonged in a drawing and what didn't. That skill was scarce enough that simply doing it well set you apart. Competence looked like distinction.
That era is over, and it ended faster than anyone expected. Anyone can now generate a serviceable diagram in seconds. Properly aligned, reasonably legible, technically clean. The floor has risen, and it has risen for everyone at once.
Which means adequate stopped being an achievement somewhere along the way and became the starting condition.
What's left is the part that was never really about production in the first place. Knowing which idea a diagram is supposed to carry. Knowing what to leave out, which is almost always the harder decision. Sensing when a page is balanced and when it is merely full. Understanding that hierarchy is an argument about importance, and that someone has to decide what matters before any tool can render it.
None of that can be prompted, because none of it is a formatting problem. It is judgment, and judgment is what we are actually selling.
The profession is about to discover this uncomfortably. When the mechanical part of drawing becomes free, the only thing distinguishing one firm's documents from another's is taste. And taste is the thing we have spent twenty years treating as a luxury we would get to if the schedule allowed.
It costs decisions, not hours
None of this requires more time than we have. That is the part I most want to land, because "make it beautiful" sounds like a request for hours nobody has.
It isn't. It is a request for decisions.
Choose a typeface and stay with it. Set a hierarchy and let it hold across every page. Give each diagram one idea to carry, and move the second idea to its own frame. Align things because you meant to. Delete the note that repeats the drawing. Leave white space and don't apologize for it.
These are not expensive moves. They are the difference between a document that was produced and a document that was composed. A reader feels it in about two seconds, even if they would never say so out loud.
Why it scales
I care about this more than almost anything else I try to teach, because it is the one habit that carries into everything else. Someone who won't ship an ugly code report also won't ship a sloppy detail, or a client presentation that buries the point, or a schedule nobody can read. The standard isn't really about graphics. It is about refusing to let anything leave your hands in a state you are not willing to sign.
It matters to a practice because documents are the part of our work most people actually touch. Long before a client stands in a finished terminal, they have read a hundred pages of ours. That is the building, as far as they are concerned.
And it matters to the profession, urgently, because the ground is moving. If our value was ever in producing drawings, that value is evaporating. What remains is judgment, care, and the conviction that there is no such thing as a document too small to deserve them.
There is no reason to make something that isn't beautiful. There never was. It's just that now, there's no excuse either.