The job had a banded color — one course of one-band split-face running through the wall every few feet. Clean detail. The kind of thing the architect specs because it looks sharp from the parking lot.
There's no corner block for it. Not in the library, not anywhere. So I built one — modeled the unit in the masonry estimating software, defined the dimensions, then placed it. Every corner of every banded course. By hand.
I spent more time making the corner block and placing them than the mason would spend laying the whole course.
The software already drew the corner
The software knew the wall had corners. It rendered them. I could see them on the screen — two walls meeting at 90 degrees, the bond stepping through. The geometry was right there on the monitor.
So why doesn't the software put the special unit at the corner? It already knows the corner exists. It drew the corner. The pixels are on the screen.
A corner block is the same block as a stretcher, just turned. Same dimensions, same color, same finish. The software has all of it — the bond, the dimensions, the location. Nothing is missing. It's just not connected.
It can see the corner. It drew the corner. It should know to count the corner.
Corners carry a premium
This isn't a small problem. Corner units cost more — sometimes 20 percent more than the equivalent stretcher, more for specialty colors and finishes. They're a separate SKU on the supplier's invoice. Palletized separately. Priced separately. Ordered separately.
When the software misses one, the takeoff comes back short on corners and long on stretchers. The order goes in short. The crew shows up, lays the run, and gets to the corner with the wrong unit on the pallet. That's not a rounding error. That's the project pausing for a delivery you should have ordered with the original release.
And then there's the odd course
Here's the part nobody talks about: half-high courses.
When the wall height isn't modular to 8 inches, you've got a half-high course at the top or bottom. That course needs its own corner unit — a half-high corner, often a totally different SKU than the standard corner. Easy to forget. Easier still when the software doesn't prompt for it.
I've had takeoffs come back from the spreadsheet check with three or four missed corner courses. Every one was an odd course where I'd placed the standard corners and forgotten the half-high. The software didn't catch it because the software wasn't looking. It just drew the rectangle and stopped.
What automatic corner detection looks like
The Masonry Modeler does this because it has to.
When you draw a wall and the wall meets another wall, the engine treats the intersection as a corner. Not a guess — geometry. The corner unit gets placed automatically. The bond runs through it. Every course gets the corner it needs — full, half-high, bond beam, lintel-bearing — because every course is generated by the same engine that drew the wall.
If you've defined a custom unit — a banded color, a one-band split-face, a 12-inch matching face shell — you mark it as corner-capable once. After that, every wall that uses that color gets the corner from your library. You stop placing. You start drawing.
That's the whole shift. The software can see the wall. The software should know what the wall is.
The wall shouldn't take longer to count than to build
I built this because I was tired of spending Friday afternoons modeling corner blocks for the third banded color of the year. The corner shouldn't take longer in the software than it does on the wall. The takeoff shouldn't take longer than the bid is worth.
A masonry estimating tool that draws the corner and doesn't count the corner is doing half the job. The half that doesn't matter.
Join the waitlist →