Architect Says One Thing, Contractor Says Another. How to Make a Decision and Not Go Crazy?

When an architect presents a solution that the contractor calls unfeasible, and the contractor proposes a change that the architect considers destructive to the concept – the investor finds themselves in a position where no decision seems safe. This isn’t a personality conflict. It’s a clash of two logics: design and execution. Your role isn’t to referee disputes, but to understand why these logics differ and how to navigate a decision through this dynamic without losing control of the project.

Two Perspectives That Must Align

The architect thinks in terms of concept, proportion, and function. They design a solution that makes sense within the context of the entire building – its form, orientation, character. The contractor thinks in terms of material, detail, sequence of operations, and execution risk. They see what can go wrong during installation, in winter conditions, at a specific roof pitch.

Neither perspective is wrong. The problem emerges when a decision is made without considering both simultaneously. An architect may design a roof with an unusual pitch angle that perfectly complements the building’s form. The contractor may point out that at this angle, ceramic tile will require additional securing, and metal roofing will need special mounting hooks. Both pieces of information are valid. Your decision must stem from which consequence you’re prepared to accept.

Decision Framework: What Design Determines vs. What Execution Determines

Before making a decision, identify which stage you’re at and which elements can still be modified without systemic consequences:

• Construction design – establishes roof geometry, pitch, load-bearing structure. Changes at this stage require design corrections but don’t generate material losses.
• Execution design – specifies details: covering attachment method, flashing, ventilation. Changes are possible but affect the budget.
• Execution – changing the solution means rework, delays, additional costs, and often warranty loss.

If the conflict emerges during execution design – that’s a good moment. If during execution – the cost of the decision multiplies. Your task: prevent a situation where the dispute is resolved under time pressure and sunk costs.

Question Checklists: How to Extract Information That Matters

When an architect and contractor say contradictory things, it’s usually because they’re answering different questions. Your role is to ask questions that force both parties to provide specific answers within the same frame of reference.

Questions for the Architect

• Is the proposed solution the only way to achieve the intended effect, or are there alternatives with similar characteristics?
• Which technical parameters of this solution are essential to preserve the concept, and which can be flexibly adjusted?
• Does the design account for the specifics of the chosen roofing material, or does it assume a universal solution?
• What consequences will changing this element have on the overall project – will it affect only the roof, or also the façade, proportions, and interior lighting?

Questions for the Contractor

• Does the identified problem stem from technological limitations of the material, or from organizational difficulties on your end?
• What specific risk do you see in implementing this solution – is it about durability, waterproofing, installation safety, or cost?
• Is the change you’re proposing formally compliant with the design, or will it require documentation corrections?
• Is the alternative solution you’re suggesting covered by the same warranty as the designed solution?

These questions aren’t meant to determine a “winner.” They’re meant to reveal where the real problem lies and what the actual consequences of each decision are.

Decision Tree: How to Evaluate Each Path

Every decision in a dispute between architect and contractor leads to a set of consequences you can predict and evaluate before choosing. Below is a thinking framework that allows you to do this systematically.

Path A: You Execute the Project Without Changes

Consequences:

• You maintain full project coherence and compliance with documentation.
• Design warranty remains intact.
• The contractor may charge additional costs for “execution difficulty” or extend the timeline.
• Implementation risk largely falls on the contractor – but if something goes wrong, they’ll point to the design as the source of the problem.

Path B: You Implement the Change Suggested by the Contractor

Consequences:

• The project requires correction – cost, time, formalities.
• Implementation risk decreases, but responsibility for the change shifts to you.
• Possible loss of part of the architectural concept – you must assess whether the final result still meets your expectations.
• Contractor’s warranty is full, but design warranty may be limited to modified elements.

Path C: You Seek a Middle Ground Solution

Consequences:

• Requires a joint meeting between architect and contractor – which isn’t always easy to arrange.
• May lead to a compromise that satisfies neither party, but is acceptable.
• May also reveal a solution neither party saw before – especially if you bring the material manufacturer into the conversation.

Your decision shouldn’t stem from who speaks louder. It should stem from assessing which path of consequences you can manage and for which you’re willing to take responsibility.

Common Decision Traps and How to Avoid Them

When conflict arises between an architect and contractor, it’s easy to make decisions that seem rational at the moment but prove wrong over the entire construction process.

Trap 1: Deciding Under Time Pressure

The contractor says: “We need to settle this now, the crew is waiting.” This is classic execution pressure. If the decision involves a key element – roof pitch, covering type, structural detail – don’t rush it. Better to pay for crew downtime than live with the consequences of a bad decision for 30 years.

Trap 2: Choosing the “Cheaper” Solution Without Long-term Analysis

The contractor proposes a change that lowers construction costs. But does it lower operating costs? If the change involves insulation, ventilation, or airtightness – today’s savings may mean losses for decades to come. Always ask about operational consequences, not just installation ones.

Trap 3: Assuming “It’ll Work Out Somehow”

There are no postponed decisions – only decisions made by someone else. If you don’t resolve the dispute, the contractor will during execution, following their own logic. And you’ll find out when it’s too late to change.

Trap 4: Lack of Written Confirmation

Every decision changing the design or execution method must be confirmed by email or contract amendment. Without this, you lose the ability to hold anyone accountable – neither architect nor contractor. Verbal agreements don’t exist in construction.

How to Use These Tools in Practice

When conflict emerges, don’t try to “win” it. Instead:

• Organize a joint meeting – online or on-site – with the architect, contractor, and yourself. Let both parties present their arguments in your presence.
• Ask checklist questions – specific ones that demand answers in terms of consequences, not opinions.
• Request alternatives – have each party present not only their solution but also the consequences of the other party’s solution.
• Consult the material manufacturer – they often have the technical knowledge that resolves disputes (e.g., whether a particular pitch angle is acceptable for a specific covering).
• Document the decision – along with justification and confirmation of responsibility. If you decide on a change contrary to the design – have the contractor confirm they take full responsibility for the outcomes.

Investor Summary

Conflict between architect and contractor isn’t a sign of chaos – it’s a natural point where concept meets execution. Your decision doesn’t have to please both parties. It must be informed, based on understanding consequences, and confirmed in writing. The worst thing you can do is surrender control of the decision to someone else – because you’ll be living in this house, not the architect or contractor. At Rooffers, we believe that an investor who knows why they’re choosing something doesn’t need to fear any dispute. They just need to know what questions to ask and how to evaluate the answers.