Most building projects are not run by one team. An owner hires an architect to produce drawings, a separate studio to produce renderings for the fundraising campaign, a general contractor to bid and build from the drawings, and sometimes a fourth consultant to handle permitting or a specialty scope like acoustics or kitchen design. Each of these firms is good at its own job. None of them is responsible for the seams between the others, and it is in those seams that most of the expensive surprises on a construction project actually happen.
We have sat in enough project meetings to know what those seams look like from the inside. A rendering used in a donor presentation does not match the floor plan that was revised two weeks later. A submittal gets approved through an email thread the architect of record never sees. A change gets agreed to verbally on site and never makes it back into the drawings, so the next subcontractor builds to the old version. None of these are dramatic failures on their own. They are small, and that is exactly why they are dangerous. They accumulate quietly until a change order or a missed deadline forces everyone to figure out, after the fact, who knew what and when.
The Gap Nobody Is Paid to Close
This is not a new problem, and it is getting more attention as projects get more complex. AIA’s contracts and practice management partner Part3 recently published a analysis of construction administration risk that describes exactly this pattern. Construction communication now spans email, shared drives, contractor platforms, and on-site conversations, and critical information routinely gets duplicated in one place and lost in another. A submittal reviewed in email but never logged centrally. An RFI answered on site but never documented. Different teams working, without realizing it, from different versions of the same drawing set.
What stood out to us in that analysis is the observation that most construction administration risk does not come from one major issue. It builds gradually, through a string of small undocumented gaps between what the contract intended, what got communicated, and what actually got built. Every one of those gaps has an owner in theory. In practice, when three or four separate firms are each managing their own slice of a project, nobody feels responsible for the connective tissue between them, because it was never anyone’s job description to begin with.
None of this is abstract for the owner footing the bill. When a dispute over a change order lands on a project with several disconnected consultants, the first several weeks are often spent simply reconstructing who said what to whom, because no single party held the whole record. That reconstruction work is billable, slow, and adversarial by nature, since each firm is understandably protecting its own position rather than solving the owner’s problem. An owner who just wants their building finished on schedule ends up paying, in time and in legal fees, for a coordination failure that had nothing to do with the quality of any individual firm’s work.
Why We Keep Design and Visualization Under One Roof
This is a large part of why we built UNITE the way we did. Rather than treating architectural design and 3D visualization as two separate services that happen to serve the same client, we run them as one team working from the same model, the same file, and the same understanding of where a project actually stands. When a donor asks to see a proposed fellowship hall from a different angle, or a planning commissioner wants to understand how a building will read from the street, the people producing that image are the same people who drew the plan it is based on. There is no handoff, no separate vendor’s queue to wait in, and no risk that the picture a donor falls in love with quietly diverges from what gets built.
We have written before about why the rendering comes before the fundraiser, and the integration point matters just as much as the timing. A rendering that comes from a disconnected studio is only as current as the last file it was handed. A rendering that comes from the same team holding the drawings is current by definition, because updating one updates the other. That difference sounds small until a design changes twice during a capital campaign, which happens on nearly every project we have worked on.
What This Looks Like on an Actual Project
Consider a church expansion where the building committee, midway through design, decides the fellowship hall needs a different configuration to support a growing children’s ministry. Under a fragmented team, that request goes to the architect, who revises the plan on their own schedule, and then eventually gets forwarded to whichever rendering studio handled the original visuals, who revise the image on their own separate schedule, weeks later, using whatever version of the plan they were last sent. Under our structure, the same conversation results in an updated model and an updated set of drawings within days, because both come out of the same working file rather than two disconnected ones.
The same dynamic shows up outside of church work. A hospitality owner preparing to present a renovation to a planning and zoning board, or a franchise operator rolling out a prototype design across several sites, faces the identical problem if the visuals used in that presentation come from a different firm than the one managing the construction drawings. A P&Z board that approves a rendering it later learns does not match the permitted plans will remember that the next time the owner comes back for an approval. A franchise operator who needs a prototype tweaked for a tight urban lot cannot afford the multi week lag of routing that change through two disconnected firms before the next site’s drawings are due. In both cases, the coordination gap costs real time and real credibility, not just a slightly awkward meeting.
This is the same logic behind what we described in what a 3D model catches that the blueprints never will. A coordinated model surfaces problems, a mechanical duct running through a beam, a door that will not clear a corridor, before they reach the job site. That coordination only works if the model and the drawings are the same living document rather than two separate deliverables produced by two separate firms on two separate timelines. The moment you introduce a handoff between disconnected teams, you reintroduce the exact lag and version drift that the AIA analysis flags as a primary source of construction risk.
A business owner planning their first significant construction project usually feels this gap the hardest, because they have no prior experience telling them which questions to ask before they sign three separate contracts instead of one. They are often told, correctly, that separate firms will each bring specialized expertise, but nobody tells them who is supposed to notice when those specialties stop lining up with each other. By the time a mismatch surfaces, usually in the form of a bid that comes in high or a permit reviewer flagging a discrepancy, the owner is the one left explaining to their lender or their board why the numbers moved. A single team accountable for the whole picture does not eliminate every surprise a construction project can produce, but it does mean there is always one place to go for an answer, and one party who cannot point to someone else’s file as the source of the problem.
One Team From First Sketch to Final Walkthrough
The same principle carries into construction administration, long after the renderings have done their job of raising money or winning approval. The firm reviewing submittals and answering RFIs during construction is the same firm that programmed the building, drew it, and modeled it, which means there is no institutional knowledge lost in a handoff partway through the project. When a contractor asks why a detail was drawn a certain way, the person answering was in the room when that decision was made, not reading a file left behind by someone else.
Twenty five years and more than a thousand church projects have taught us where these gaps most often open up, and the pattern is consistent. It is almost never the architecture itself that causes budget overruns and schedule slips. It is the space between disciplines, between design intent and construction reality, between the version everyone thinks they are working from and the version that actually exists. Closing that space is not a service we bolt on. It is the reason we structured the firm the way we did.
If your project currently has a different firm handling your drawings, your renderings, and your fundraising visuals, it is worth asking a plain question: who is actually responsible for making sure those three things agree with each other next month, and the month after that. We built UNITE so that the answer is always the same team, working from the same information, from the first conversation about your site through the final walkthrough of your building. If you are weighing how to structure your project team, or wondering whether the gaps between your current consultants are costing you more than you realize, we would welcome the chance to talk through what you are planning.
