Residences·Insights·Working with your architect

A practitioner's note

I have a design and an architect — where the general contractor comes in

Wojciech Tracichleba 14-minute readWorking with your architect
Illustrative photograph — I do not publish photographs of completed projects.

In brief

You have a design for a residence and an architect — which means the most important choice is behind you, and the order of things is right. With a finished design I do three things: I read it from the builder’s side, I put together a real budget, and I lay out a plan for the works. I can join at any stage, but the earlier I read the design, the more problems get solved on a drawing instead of on site. One rule stays fixed throughout: the design remains the architect’s and his team’s — every correction goes back to its authors with numbers and proposals, never behind their backs.

The right order

Seven out of ten residences I discuss with owners began in an architecture studio. First the architect, then the design, and only then the question of who will build it. That is the right order. A good architect does the one thing nobody else in this process will do: he translates the way you live into an actual house. He asks questions you would not have thought to ask, and he keeps the whole thing coherent down to the last detail. If you have an architect like that, hold on to him.

The question is what happens next with the design he handed you. And here is the one thing worth understanding before you start comparing contractors’ offers: that design answers the authorities, not the crew. The authorities ask what will stand, and where. The crew will ask entirely different things — what steel goes into this beam, at what level the penetration comes out, what to do when the ventilation duct meets the downstand. Those questions are answered by a different level of documentation. That is not a flaw in the design and not a criticism of the studio — this division of roles is written into the regulations.

What is in the design — and what the site will ask about

For several years now, a building design in Poland has consisted of three parts. Two of them — the site development design and the architectural-and-building design — go to the authorities together with the permit application. The third, the technical design, is not filed with the application: it has to be ready before the works start and available on site, and it formally shows up again only when the build is being closed out. That is where the structure with its calculations lives, and the service routes with their diameters — usually without material schedules and without specific equipment picked.

Then there is a fourth level, about which the regulations are silent for a private house: the detailed design, known internationally as construction documents. The law does not require it. The site does. Rebar drawings, steel and material schedules, specific equipment, coordinated penetrations through the structure: everything the crew will actually ask about is right there. The permit design does not contain those answers, and under the regulations it does not have to.

Two things follow from this, and at residence scale they decide the whole build.

First: you cannot get a binding price out of a permit design. You can get an order of magnitude — and an honest contractor will call it exactly that. A binding price needs the detailed level: take-offs, schedules, resolved details. A contractor who quotes a binding figure off the permit design alone is guessing — and where guessing leads at this scale, and where a price with real backing comes from, I described in the piece on the lump sum.

Second: a residence usually means eight to a dozen-plus design disciplines. Architecture, structure, plumbing and heating, pool-hall ventilation with dehumidification, building automation, pool technology, lighting, security. Each of those disciplines draws its own set, and each set is tidy on its own. The trouble starts when all those drawings have to fit into one structure, to the centimetre. With that many systems, some of them will land on each other somewhere — the question is where. And whether it comes out on paper, or only in the concrete.

Those two places are where my work begins.

Three things I do with a finished design

First thing — I read the design from the builder’s side. That is a different reading than the architectural one. A bit like a contract in your own company: the lawyer and the accountant get the same document, and each sees something different in it and worries about something different. The architect looks at the coherence of the intent. I lay the disciplines on top of each other and look for the places where they meet: a ventilation duct in the zone of a beam, an automation route clashing with the lift shaft, a plant room drawn without the equipment that has to physically fit into it — along with the service technician who will need to reach it a few years from now. I check whether the special elements — the pool, the car lift, the large-span glazing — have had their structural consequences drawn in from the first line, or whether they hang in the design as “to be worked out later.” And the entirely mundane things: whether a given detail can actually be executed in the declared technology, and which materials carry lead times measured in months.

Second thing — I put together a real budget. It is built from scope: item by item, on the documentation and the take-offs. Not from square metres — on a typical house the metre still tells you something, on a residence it misleads, because a home cinema does not get cheaper just because the house is a bit smaller. Where the design calls for a solution disproportionately expensive to execute, I change nothing on my own. I prepare alternatives with numbers and bring them back to you and to the architect. The decision belongs to the two of you — I show what each path costs and what it does to the schedule, before any of them becomes a fact.

Third thing — I lay out the plan of the works. The sequence of trades, a schedule with staged acceptance, an ordering calendar for the materials with the longest waits. That plan comes together before the contract, because only the plan shows whether the dates we discuss at the table have anything behind them.

When to bring me in

I join at any stage: at concept, with the design filed for the permit, with a complete set of construction documents. It works at any of them. The difference is what the findings of my reading cost.

The same remark carries three different prices. Take a plant room half the size it needs to be. Raised at concept stage, it costs a few of the architect’s lines. Raised after the permit — a redesign, and sometimes the formal change path, because some corrections then mean going back to the authorities. Discovered on site, it costs demolition, standstill, and decisions made under pressure, which is the worst possible setting for them. With each stage the cost jumps and the number of ways out shrinks.

So the conversation that pays off most sits in the window between the concept and filing the design for the permit. The design is already concrete enough for me to read it from the builder’s side, and still open enough that a correction costs a drawing. I will admit it plainly: I like those conversations most. A client who calls before anything is settled gives me the chance to make sure, ahead of time, that nothing catches us off guard. At the later stages that chance is simply gone.

And if your design is already filed, or you hold a final permit? That is fine too. Some of the questions have simply hardened into decisions, and we work with those differently.

You, the architect, and me

A well-run residence has three distinct roles.

You make the decisions: scope, budget, choices from the options presented — knowing the consequences up front. The architect answers for the design and its coherence and runs the author’s supervision on site; classifying departures from the approved design belongs, under Polish law, to the designer (across multiple disciplines — to the relevant discipline designer, with the lead architect coordinating). I answer for the execution: coordinating the trades and subcontractors, quality, schedule, and the working budget.

There is more behind that third sentence than meets the eye. I once tried to count how many people work — directly and indirectly — on an ordinary single-family house. I got past 250, and for a residence I do not even try. Out of that entire list, on the delivery side you talk to one person — me.

Two things in this division I treat as matters of principle.

Changes to the design go through the architect. Always. That is how the law works: substitute solutions are agreed with the designer, and it is the designer who rules whether a departure is material — a material one requires an amended building permit. And that is how healthy collaboration works — the author of the design knows the intentions that are not visible on the floor plans. A contractor who “improves” the design on his own is not being bold. He is a risk somebody will eventually pay for.

The architect’s supervision on site — and, when the question concerns a specific discipline, that discipline’s designer — I treat as part of the team. On a residence, sooner or later there will be questions the documentation does not answer unambiguously — and then the site needs someone who knows the intent behind the drawing. The architect’s visits, the log entries, the joint decisions on details raise the quality of the execution, and they take the guessing of someone else’s intentions off my shoulders.

There is also a fourth role, which I will bring up myself before you ask: the owner’s supervision inspector. That is a person on your side whose job is to check my work on your behalf. At this scale he should be on the team from day one. A contractor who winces at that is telling you something important about himself.

When the design needs corrections

I will say it outright, because this worry often hangs over the conversation: a design in which nothing needs correcting does not exist. Not because architects get things wrong more often than anyone else. Because a residence is a prototype — a dozen or more disciplines, designed by as many teams, meet inside one structure for the first time, since nobody has built this house before. There is no trial run. How many corrections I will find in your design — that I do not know. I know I will find some, because so far that has been the case every single time.

The whole difference is in the form. A remark thrown out as “this can’t be built” stops the collaboration and sours the mood for everyone. A remark in the form of “this detail in this technology will come out disproportionately expensive — I have two alternatives, both keep the effect, and the differences look like this” lets a decision be made and the building carry on. I work the second way. The architect rules on what happens to the design. You rule on what happens to the budget. I make sure both decisions are made on calculated data and at the right moment — before the concrete closes the subject.

What I don’t do with someone else’s design — the limits

I do not design. Designing is what the architect and the discipline designers do; my profession is building what they designed and working out what it really costs. I value those boundaries from both sides.

I do not change the design on my own. Not for convenience, and not because “it’s easier on site this way.” The law protects the design and its author, and I protect the process: every correction goes back to the architect.

I do not give a binding price off a permit design. I will estimate the order of magnitude and tell you what it depends on. A binding figure you will hear after the construction documents and the take-offs.

I do not promise that corrections will be free. Changes have their costs — design, material, time. What I promise is different: you will know each one before the decision, itemised, not after the fact on an invoice.

I do not compete with the architect over the vision. The house is to look the way you and your architect imagined it. My ambition ends at making it stand exactly like that — within the scope, the price and the schedule you knew before the start.

What I ask when you bring me a design

You do not need to prepare for the first conversation. But if you want to know what I will ask, the list looks like this:

  1. What stage is the documentation at — concept, design filed for the permit, final permit, technical design, construction documents?
  2. Are there ground and groundwater surveys, and was the structure designed on their basis?
  3. Are the special elements — pool, lift, large glazing — in the structure from the start, or “to be worked out later”?
  4. Which discipline designs exist, and who has been keeping them consistent so far?
  5. Will the architect run the author’s supervision on site — and is that already agreed?
  6. Are the rights to the design and the procedure for changes settled in your contract with the studio?
  7. Which materials and equipment carry long lead times — and has anyone built their calendar?

To some of these the answer is sometimes “I don’t know” — and that is fine. (I myself answer “I’ll check” when asked about current lead times for some of the equipment, because they can shift from one quarter to the next.) That is where we start: from completing the picture. The offer comes later.

Frequently asked questions

I have house plans and I’m looking for a builder — what should I prepare before the first conversation?

Whatever already exists: the documentation, even incomplete, the ground and groundwater surveys, the formal status, and a note of which disciplines have been designed. You do not need to fill the gaps before we talk — establishing what is missing is the first step of the collaboration. Answers to questions about the engagement itself — budget, regions, how the first conversation goes — are collected in the Questions section.

Can a contractor price a house off the permit design?

Estimate it — yes, and he should call it an estimate. A binding price requires construction documents and take-offs, because the permit design by its nature does not contain the details that costs are made of. Those details are simply not in it.

Can the general contractor change the architect’s design?

Not on his own. Substitute solutions are agreed with the designer, and it is the designer who rules whether a change is material — a material one requires an amended building permit. With me, every proposed correction goes back to the architect with numbers and alternatives.

My build has already started and I’m looking for a new contractor — is that possible?

Not with me. I don’t take over a build in progress — I never have, and that won’t change. I take a project on only when I can answer for the whole of it: for how the house is built and for the final result. After someone else that can’t be done honestly — some things are already closed up, some can’t be checked, and a fault no one can see today would still end up mine. There is a second reason: stepping into someone else’s situation almost always means “by yesterday,” and with me there is a wait, sometimes a long one. I won’t cut one client’s build short to rescue another — not even a more urgent or better-paid one, because rescuing another crew’s work usually costs more than doing it right from the start. If your build is only about to begin, that is a conversation I want to have.


This content is educational and describes a typical course of collaboration — it does not replace an analysis of your specific documentation, nor legal advice. Every project requires its own assessment.

If you have a design and an architect and are looking for the contractor who will join the team — the right conversation happens over an open set of drawings. Let’s talk about your project.

Back to Insights