BUILDIT CONSULTANT PATHWAY

Architect

Understand how the Architect thinks, how the consulting team really works, what information should arrive, where the hidden tensions sit and how to get coordinated decisions without trying to do the Architect’s job.

Primary lens: consultant interface literacy · Manage the interface, not the personality · Technical package scoping is handled through your procurement systems and company scope documents.

CHAPTER 1UNDERSTAND THEM

Know their role, pressures and place within the team.

01The role in plain EnglishThey turn the project’s brief and design intent into a coordinated architectural outcome›

The Architect is the principal author and custodian of the architectural outcome. They translate the client’s brief, approvals and design intent into spatial layouts, material choices, details and coordinated information that the wider team can develop, price, approve and build.

Their value

Holding the whole architectural outcome together across aesthetics, function, compliance, user experience and multiple consultant inputs.

Your interface

Turning that intent into sequenced, procured and constructed work while protecting cost, programme, access, safety and buildability.

02Why the project needs themThe Architect gives coherence to decisions that would otherwise fragment by discipline›

Converts the client’s ambitions, functional needs and planning commitments into an integrated design.

Provides a common architectural frame for structure, services, façade, fire, access, acoustics, interiors and landscape.

Protects the qualities and obligations that can be lost when cost, time and trade packages pull in different directions.

Explains how individual decisions affect the whole building rather than one isolated detail.

Maintains continuity as the project moves from concept and approval into documentation, procurement and construction.

03When they matterTheir influence changes, but it never disappears›

Concept and DABrief, planning strategy, massing, spatial organisation and the promises made to gain approval.

PD and DDMajor systems, room layouts, materials, details and cross-consultant interfaces become real.

IFC and procurementInformation must be stable enough to price, coordinate, release and fabricate.

ConstructionRFIs, samples, shop drawings, substitutions, site conditions and departures from intent.

CompletionDefect closure, approved changes, handover information and confirmation of the built outcome.

Critical lessonAn early architectural assumption can stay dormant until a late trade, compliance or access decision exposes it.

04What they own and do not ownResponsibility is not the same as coordination›

Typically controls

Architectural layouts, spatial intent, finishes, doors, partitions, reflected ceiling intent, visual junctions, architectural details and coordination of the overall design response.

Does not automatically control

Structural calculations, building services performance, fire engineering, façade engineering, certification, specialist trade design, temporary works or the builder’s construction methodology.

The trap: the Architect may coordinate an interface without accepting another party’s design responsibility. Equally, another consultant’s approval does not automatically close the architectural outcome.

05What good looks likeA good Architect makes the whole team more effective›

Understands the brief, current commercial deal and non-negotiable design obligations.

Produces information matched to the project stage and is candid about what remains unresolved.

Coordinates actively with other consultants rather than simply collecting their drawings.

Listens to construction, access, sequencing and procurement constraints without surrendering professional judgment.

Explains the reason for a decision and its downstream interfaces.

Distinguishes preference from compliance, client requirement and core design intent.

Responds with clear authority, records changes and closes the loop.

Works constructively with the actual people in the project team, including builders and specialist trades.

06Dependencies and pressuresTheir answer is shaped by people, history and obligations you may not see›

Client and briefBudget, brand, functionality, approval commitments and long-held expectations.

Other consultantsStructure, services, façade, fire, access, acoustics, landscape, interiors and specialist design.

Authorities and certifiersPlanning, building approval and evidence requirements.

Builder and tradesBuildability, sequence, access, temporary works, product availability, tolerances and fabrication.

Professional dutyLiability, competence, records, design integrity and reluctance to approve outside their authority.

Project historyEarlier client discussions, DA compromises, design narratives and decisions that may pre-date the builder.

CHAPTER 2WORKING WITH THEM

Understand how the consulting team actually works.

07The real consulting teamDrawings are the visible output; coordination happens between people›

Consultants rarely solve a live interface alone. They test positions with each other, protect discipline boundaries, seek client direction, reconcile compliance advice and negotiate who will change. Much of this happens in short calls and side conversations before a formal answer appears.

Encourage direct coordination

Let the right technical people talk early. It is faster and often produces a better integrated answer than routing every detail through a meeting chain.

Control the outcome

Material decisions, departures, cost or programme effects and changed documents must return to the project record with an owner and authority.

08Existing working relationshipsWho has worked together before can matter more than the company logos›

A solid consulting team often has trusted working relationships behind the scenes. People understand each other’s standards, response styles, risk appetite and decision pathways. That familiarity can make coordination faster and more honest.

What to test

Ask about the named individuals, their recent comparable projects together, who actually coordinates, availability, continuity and how disagreements were resolved.

What to watch

Familiarity can also produce groupthink, complacency, undocumented decisions, cliques or historical loyalty to a client position that no longer reflects the current deal.

09Engagement gaps that affect deliveryNot a package scope: the interface conditions that make good performance possible›

Unclear current client, reporting line and authority after novation or delivery-model change.

No common record of the final deal, approved design intent, departures and retained client obligations.

Unclear deliverable maturity, review cycles, response times and required issue dates.

Other consultant and specialist-trade scopes are not visible enough to identify interface ownership.

Site access, meetings, workshops, inspections and hold-point attendance are not realistically allowed for.

Change, substitution, shop drawing, sample and variation pathways are vague.

The personnel promised at engagement are not the people doing the work.

Fee pressure discourages coordination exactly when the team needs it most.

BUILDIT focus: recognise these conditions and manage the interface. Detailed technical package scopes remain in your procurement platform and company scope documents.

10When to involve themGive them the right issue before options close›

Call now

Irreversible work, safety, compliance, fabrication, a concealed interface or a decision actively blocking site.

Workshop early

Dense interfaces, substitutions, methodology-dependent design, samples, mock-ups or competing consultant positions.

Formalise

Conflicting information, a departure, changed obligation, cost or time consequence, or a decision requiring authority.

Builder-managed

Pure sequencing or methodology that does not alter permanent design, performance criteria or another party’s assumptions.

Give them: exact location, marked-up current information, the project constraint, affected interfaces, options already tested, the decision required and a genuine need date tied to procurement or construction.

11Top 20 construction questionsThe recurring questions builders need the Architect to close›

What is the controlling dimension?

What is the finished level, fall or threshold?

Where exactly does this wall, door or opening go?

Which drawing, schedule, model or detail governs?

These documents conflict. What is the authorised resolution?

What finish is required and where does it stop?

What happens at this junction?

What is the ceiling, bulkhead or set-out level?

How is this element meant to terminate?

What door, frame, glazing or hardware is required?

Is the opening, clearance or access zone acceptable?

How is waterproofing continuous through this interface?

Can this move to resolve buildability or coordination?

Does this shop drawing preserve design intent?

Is this proposed product, sample or substitution acceptable?

How does this coordinate with structure, services and façade?

Does the change affect fire, acoustic, access or planning?

Who owns the permanent design at this interface?

What information is still needed before you can decide?

What is the final decision, who authorised it and when will revised information issue?

12Do not ask this. Ask this.Better framing produces faster, more useful answers›

WEAK“Your drawings do not work. Send a detail ASAP.”

BETTER“At grid C4, A-402 rev 6 conflicts with S-215 rev 3. The façade support is released Friday. Please confirm the required permanent outcome, affected disciplines and governing detail by Wednesday 2 pm.”

WEAK“Can we use this cheaper product?”

BETTER“Proposed substitute attached. Please review the listed appearance, compliance, warranty, interface, maintenance and lead-time differences and confirm who else must accept it.”

13Interpret the response“Reviewed” is not the same as a coordinated, authorised decision›

Check authority: is the person entitled to make the decision, or only providing discipline comment?

Check completeness: did the response close the actual question or redirect it elsewhere?

Check qualification: note “subject to”, “design intent only”, “no objection”, exclusions and missing approvals.

Check interfaces: which other consultants, certifiers, client representatives or trades must respond?

Check implementation: identify changed drawings, schedules, models, procurement packages and site work.

Check status: distinguish advice, acceptance, instruction, approved change and formal issue.

14What slows them downThe visible delay may be a symptom of a different unresolved problem›

Missing inputSurvey, structural response, services layout, product data, client direction or trade methodology.

No authorityThe person answering cannot commit the client, company or another discipline.

Liability exposureThe requested answer extends scope, accepts unknown design or creates a professional risk.

Commercial disputeA technical question is actually masking a variation, redesign or unpaid service.

Conflicting positionsConsultants disagree and no design leader or client decision has closed the issue.

Poor requestNo exact location, outdated information, invented urgency, hidden constraint or no real need date.

Management response: diagnose the blockage, supply what is missing, identify who can decide and escalate the consequence—not the personality.

CHAPTER 3DELIVERABLES AND COMMON ISSUES

Know what to expect and recognise when information is breaking down.

15Typical outputsUnderstand the evidence without turning BUILDIT into a package scope›

Design narrativeBrief response, design intent, planning commitments and principles that explain the “why”.

Drawings and modelPlans, elevations, sections, reflected ceilings, details and coordinated geometry.

SchedulesRooms, finishes, doors, hardware, glazing, fixtures and other selections.

SpecificationMaterials, workmanship, products, performance and quality requirements.

ReviewsRFI responses, shop drawing comments, samples, mock-ups, substitutions and site observations.

Controlled issuesRegisters, transmittals, revision records, approved changes and completion information.

The question is not “does a document exist?” Ask whether the current, coordinated and authorised information is mature enough for the decision, procurement or work about to occur.

16PD, DD, IFC and issue statusA stage label is not proof of design maturity›

Progressed Design / PD

The design is being developed. Major choices may be established, but interfaces, selections and details can still be open.

Detailed Design / DD

The design should be substantially resolved and coordinated, but confirm the project’s defined deliverables and outstanding decisions.

Issued for Construction / IFC

The issue should be authorised for construction within its stated purpose and limitations. It does not cure conflicts or missing inputs.

Other statuses

Tender, pricing, coordination, review, preliminary, superseded and as-built each carry different permissions. Read the status and transmittal.

Test maturity directly: what is resolved, what is excluded, what approvals remain, which interfaces are coordinated and what may safely be procured or built?

17Critical informationWhat the builder needs to see before work becomes irreversible›

Controlling dimensions, grids, RLs, datums, falls, thresholds and tolerances.

Complete plans, sections and elevations through difficult or changing conditions.

Project-specific junctions, terminations, penetrations, movement and waterproofing continuity.

Coordinated interfaces with structure, services, façade, fire, access, acoustics, landscape and interiors.

Finish extents, room data, doors, glazing, hardware, fixtures, joinery and ceiling zones.

Products, systems, performance criteria, samples, mock-ups and acceptance requirements.

Clear delegated-design boundaries, retained design obligations and consultant review points.

Current revision, document status, change description and approval authority.

18Drawing and revision disciplineIf the change is hard to find, it is not being managed›

A proper issue makes the change visible and traceable. The project team should not have to compare entire drawing sets by eye to discover what moved.

Use the agreed revision procedure, with changed areas clearly clouded or marked in red where required.

State meaningful revision descriptions—not only “updated” or “coordination changes”.

Issue a drawing register or transmittal identifying new, revised, unchanged and superseded documents.

Provide an issue summary that explains the material changes and affected packages.

Align drawing, schedule, specification and model revisions so the set does not contain competing answers.

Withdraw superseded information from live work areas and notify procurement, trades and consultants of the effect.

Record who authorised the change and whether it affects cost, programme, compliance or prior approvals.

19Common missing or unclear informationThe gaps that force site teams to infer the design›

GeometryDimensions, RLs, datums, slopes, openings, ceiling zones and set-out priorities.

JunctionsSections through edges, transitions, terminations, penetrations and changes in substrate.

Wet interfacesFalls, upturns, thresholds, drains, overflows and membrane continuity.

SelectionsFinish extents, door/hardware sets, glazing, fixtures, joinery and approved samples.

CoordinationStructure, services, fire, façade, access and acoustic requirements not reconciled.

AuthorityProvisional notes, undefined status, unanswered departures and no clear governing document.

20Common performance issuesThe twenty builder gripes that surface most often›

These are recurring builder-side complaints, not claims about every Architect. Use them as early-warning prompts and convert each one into a maturity check, interface owner, hold point or decision date.

Design ambition is not reconciled with budget

Bespoke or award-facing outcomes are defended without transparent cost, programme and lifecycle trade-offs.

PD, DD and IFC labels overstate maturity

Major selections, interfaces and approvals remain open despite the issue status.

There are not enough plans, sections or elevations

The hard conditions are left for the site team to infer.

RLs, dimensions and datums are incomplete

Set-out, falls, thresholds and ceiling zones cannot be relied upon.

Generic details replace actual details

Standard details ignore the project’s substrate, exposure, geometry and adjoining systems.

Critical waterproofing details are unresolved

Terminations, upturns, penetrations, falls, thresholds and façade/roof interfaces remain incomplete.

Unresolved design is pushed into D&C

The builder or trade is expected to invent the solution without a complete performance brief or acceptance path.

Discipline interfaces are not coordinated

Architectural intent collides with structure, services, façade, fire, access or acoustics.

Drawings, schedules, specifications and models conflict

The project receives different answers with no clear hierarchy or resolution.

Revision procedure is weak

Changes are not clouded or marked, revision descriptions are vague, and no reliable issue summary accompanies the set.

Design changes arrive after release

Procurement, fabrication or installed work moves before the full consequence is recognised.

Schedules and selections remain incomplete

Doors, hardware, finishes, fixtures, joinery and glazing are still provisional when orders are due.

RFI responses do not close the question

The answer refers elsewhere or restates intent without a buildable, authorised decision.

Decisions are slow or authority is unclear

Site-critical responses wait on internal review, the client or another discipline without a clear escalation path.

Buildability and sequence are overlooked

The finished detail ignores access, temporary works, installation order and realistic trade sequence.

Tolerances and real substrates are ignored

There is no room for movement, membranes, packers, fixings, drainage or site variation.

Shop drawings become the design process

Fabrication information exposes unresolved decisions and no party closes the integrated interface.

Products are selected without delivery reality

Lead time, availability, test evidence, warranty, maintenance and replacement are checked too late.

Compliance is verified too late

Fire, access, acoustic, energy, planning or certification advice forces late redesign.

Site observation and close-out are too light

Concealed work, departures, defects and as-built changes are not reviewed or consolidated in time.

The practical lesson: this list is not ammunition against the Architect. It is a checklist for creating the conditions in which the team can perform.

CHAPTER 4MANAGE THEM EFFECTIVELY

Manage the interface, not the personality.

21Behind-the-scenes pinch pointsThe twenty tensions hidden behind a simple request for information›

The answer is rarely controlled by one consultant

A simple detail may require structure, services, façade, fire, access and client input.

The person answering may lack authority

They can advise, but cannot commit the client, company or another discipline.

Quiet coordination happens before the response

Consultants often test positions privately before recording a formal answer.

Existing relationships affect performance

Trust can accelerate coordination; history and alliances can also distort it.

Consultants may privately disagree

The apparent delay can be an unresolved design-leadership issue.

One discipline avoids undermining another

A consultant may qualify their answer rather than openly contradict a peer.

The issue exposes a scope gap

No one clearly owns the missing design or coordination task.

The answer creates liability

Approval may accept risk beyond the consultant’s information, authority or engagement.

The Architect carries historical client expectations

Years of concept and DA conversations may still shape their instinctive response.

Professional obligations remain

Commercial pressure does not remove duties around competence, compliance and records.

Builder urgency meets consultant review processes

A genuine site need still requires sufficient information and internal checking.

A required input is missing

The Architect may be waiting on survey, engineering, product, client or trade information.

The real issue may be commercial

Redesign, unpaid work or changed scope appears as a technical delay.

Senior knowledge is not reaching the delivery team

The people doing the work may not know the assumptions held by project leaders.

The consultant may miss the construction consequence

A small drawing change may affect access, sequence, trades, fabrication and rework.

The builder may miss the design consequence

A practical change may affect planning, fire, access, aesthetics or client obligations.

A substitution is not just a product swap

It can alter tests, warranties, appearance, interfaces, maintenance and approvals.

Informal coordination is productive but risky

A useful side conversation becomes dangerous if the project record never catches up.

One acceptance is mistaken for complete approval

Architect review does not automatically close every discipline, authority or client requirement.

Methodology and permanent design are blurred

Unresolved design can be pushed to the builder under the label of construction methodology.

22Allegiance, authority and historyThe Architect may be working for today’s client while carrying yesterday’s project›

By the time the builder arrives, the Architect may have years of history with the developer, end client, authorities and original brief. Under novation or a changed procurement model, the formal reporting line may move to the builder, but relationships, design narratives and earlier promises do not vanish overnight.

The tension

They may be unsure whether a request changes the agreed design, conflicts with the original client’s expectation, falls outside current scope or asks them to approve a commercial compromise.

The control

Reset the project together: current client and authority, final contract deal, DA commitments, design intent, departures, retained obligations, consultant scopes, approval routes and decision records.

Do not demand loyalty. Create clarity about who instructs, who approves, which obligations survive and what the current deal actually requires.

23Outcome versus methodologyThe most contested boundary in the Architect–builder relationship›

The Architect controls the required outcome. The builder controls sequencing, temporary works, access and construction methodology. The boundary is regularly blurred and fought over.

Architect position

“The permanent performance and design intent are shown. How you safely sequence, access and construct it is the builder’s responsibility.”

Builder position

“The documented outcome cannot be built without additional permanent design. Unresolved interfaces are being pushed into D&C smarts.”

Methodology can affect permanent design through propping, pour sequence, façade installation, waterproofing continuity, tolerances, penetrations, access and trade order. The right question is: has the Architect adequately defined the required permanent outcome and constraints, or is the builder being asked to complete unresolved design under a methodology label?

Separate permanent works, temporary works, delegated design and pure construction methodology.

Identify methodology-dependent permanent interfaces and the design assumptions they rely upon.

Name the responsible designer, consultant reviewers, acceptance criteria, approval authority and hold points.

Record how the proposed method changes loads, geometry, tolerances, performance, access or finished appearance.

24Quality, cost and programmeMake the trade-off explicit before each party defends only its own pressure›

Design qualityWhat experience, function, appearance or long-term value is the Architect protecting?

ComplianceWhich requirements are non-negotiable and who confirms them?

CostIs the impact capital cost, downstream work, lifecycle cost or commercial risk?

ProgrammeWhat decision, release, fabrication, approval or site activity is affected and when?

BuildabilityWhat access, sequence, temporary works, tolerances and trade constraints apply?

Client valueIs the item a contractual obligation, critical intent, preference or opportunity for change?

25Information, decisions and changeConvert coordination into a controlled project outcome›

Use one current source of issued information, with clear status and superseded-document control.

Maintain a live interface and decision register: issue, location, owner, contributors, required date, status and affected packages.

Record the reason for material decisions, not only the selected option.

Translate meeting, phone and site outcomes into the formal record promptly.

For each change, identify design, compliance, cost, programme, procurement, fabrication and installed-work consequences.

Require updated drawings, schedules, specifications and models where the decision changes the work.

Do not treat a marked-up screenshot, email opinion or shop-drawing comment as an IFC update unless the agreed process says it is.

26RFIs, VE and substitutionsAsk for a decision with evidence, not a reaction to price pressure›

A strong RFI

Exact location, current documents, conflict or missing information, why it matters, affected packages, options considered, decision required and a genuine need date.

A strong VE proposal

Baseline and alternative, real saving, programme effect, performance comparison, appearance, interfaces, test evidence, warranty, maintenance and approvals required.

Substitution discipline: acceptance by the Architect may address architectural intent only. Close every affected consultant, certifier, authority, client and warranty pathway before release.

27Chain of consequenceFollow a “minor” decision through every downstream package›

Moving one doorway can look architectural and local. It is neither.

Door move→Wall set-out→Structure→Services→Fire/access→Joinery→Floor finish→Hardware order→Rework and delay

Management habit: ask who designed it, who depends on it, what is already released, what approvals are touched, what records must change and who confirms final closure.

28Warning signsSignals an experienced project team notices early›

The Architect and builder describe different versions of the final deal.

Consultant scopes and cross-discipline dependencies are not visible to the delivery team.

PD, DD or IFC labels are used without an outstanding-decisions list.

Repeated responses refer elsewhere without closing the interface.

Changes are hard to find because revisions are not marked or summarised.

Procurement is progressing while selections and governing information still move.

Shop drawings are the first place unresolved design is discovered.

Consultants coordinate privately, but the controlled project record never catches up.

One consultant’s “no objection” is treated as total approval.

A permanent-design gap is repeatedly dismissed as builder methodology.

Site-critical decisions depend on someone who rarely attends or lacks authority.

The team argues about blame before it maps the consequence and decision path.

29Management playbookCreate the conditions for a coordinated team to perform›

Reset: confirm the current client, reporting line, authority, final deal, DA commitments, design intent and known departures.

Map: show responsibilities, consultant dependencies, delegated design, methodology boundaries, review points and decision owners.

Plan: align design maturity gates, issue dates, procurement releases, workshops, samples, mock-ups, hold points and site access.

Frame: bring marked-up current information, the real constraint, options, affected interfaces and an honest required-by date.

Connect: get the actual technical people working together early, especially where there are proven relationships.

Record: capture material informal coordination as an authorised decision and update every affected document.

Test: follow cost, programme, compliance, procurement, fabrication, warranty, operation and downstream package consequences.

Escalate: escalate by material consequence, missing authority or failed decision path—not frustration or personality.

Close: confirm the decision has reached the drawings, trades, site, approvals, quality records and as-built information.

Backbone: understand them, work with the real team, recognise deliverable failure early, then manage the interface so the right person can make and record the right decision.

CHAPTER 5PROVE YOU GET IT

Apply the judgment in realistic project situations.

30Interface assessmentArchitect Consultant Interface Assessment›

This tests whether you can work intelligently with the Architect and consulting team in live construction. It does not test whether you can perform the Architect’s professional design role.

20 questions · 8 to 10 minutes

What is the Architect’s central role at the consultant interface?

Control every consultant’s technical design.Hold the architectural outcome together across the brief, approvals, design intent and consultant inputs.Determine the builder’s sequence and temporary works.Approve all trade design without qualification.

Which is the best evidence of a strong Architect consultant?

The largest brand and most awards.The lowest fee and shortest drawing programme.Clear stage-appropriate information, active coordination, constructive judgment and reliable closure.A promise to accept every builder proposal.

Why do existing consultant relationships matter?

They can improve trust and coordination, but still require checks against groupthink and undocumented decisions.They mean formal records are unnecessary.They allow the builder to ignore consultant scope gaps.They guarantee every consultant will agree.

A response is delayed because the Architect is speaking privately with two consultants. What is the best interpretation?

They are deliberately avoiding the builder.The interface may require cross-discipline coordination before an authorised answer can issue.The other consultants now own the architectural decision.Verbal agreement is automatically sufficient for construction.

Which is the clearest sign of an engagement/interface gap rather than a purely technical problem?

A project-specific detail requires engineering input.No one can identify who owns the missing design, who may instruct it or how the extra service is authorised.A sample needs client review.A drawing uses a standard scale.

When should the Architect be involved in a methodology proposal?

Never; methodology is always isolated from design.Only after the method is implemented.When the method could alter permanent performance, geometry, interfaces, tolerances or finished intent.For every routine site sequence, regardless of consequence.

Which request is most likely to produce a useful Architect response?

“Urgent. Confirm immediately.”“This is wrong. Please fix.”“At this exact location, these current documents conflict; this release is affected; please confirm the governing outcome by this genuine date.”“Please review the attached project.”

The Architect marks a shop drawing “reviewed—design intent only”. What should the builder do?

Treat it as complete approval by every discipline.Ignore the qualification because the Architect is design lead.Clarify what was reviewed and close the remaining design, compliance, coordination and authority pathways.Release fabrication without checking the response.

A package is labelled IFC, but key selections and interfaces remain unresolved. What is the correct response?

Assume the label overrides the gaps.Test actual maturity, identify exclusions and outstanding decisions, and limit release to what is genuinely authorised.Issue every trade package and manage the changes later.Rename it DD without telling the team.

A revised drawing set arrives with no clouds, red mark-ups or issue summary. What is the main risk?

The drawings may print in the wrong colour.The team cannot efficiently identify, assess and distribute the changed work.The revision number becomes legally invalid.Only the Architect is affected.

Drawings, schedules and specifications conflict. What should happen first?

Let each trade choose the cheapest interpretation.Assume the drawing always governs.Identify the exact conflict, contractual hierarchy if applicable, decision authority and affected packages, then obtain a controlled resolution.Wait until installation exposes the issue.

After novation, the Architect keeps referring to an earlier client preference that is not in the current deal. What is the best response?

Accuse them of disloyalty.Ignore all project history.Reconcile the current contract, DA commitments, design intent, departures and authority, then record the controlling position.Accept the preference as a variation without review.

Who controls the permanent architectural outcome and who controls construction methodology?

The builder controls both.The Architect controls both.The Architect controls the required outcome; the builder controls sequence, temporary works, access and methodology, subject to their effect on permanent design.The trade contractor controls both once shop drawings start.

The Architect says an issue is “builder methodology”; the builder says permanent design is missing. What is the key test?

Who has the stronger personality.Whether the required permanent outcome and constraints are adequately defined, or unresolved design is being shifted under a methodology label.Whether the trade can produce a sketch quickly.Whether the Architect attended the last meeting.

Two consultants privately disagree and neither will issue a final position. What should the builder manage?

Choose the response that suits the programme.The interface owner, missing decision authority, required inputs, consequence and escalation path.Separate email chains so neither consultant sees the other’s view.Only the consultant personalities.

A cheaper façade product appears visually similar. What makes the proposal credible?

The supplier says it is equivalent.A full comparison of performance, compliance, appearance, interfaces, testing, warranty, lead time, maintenance and approvals.The cost saving alone.Architect acceptance without any other consultant review.

An urgent RFI cannot be answered because structural information is missing. What is the best next move?

Repeat the same RFI in capital letters.Escalate the Architect personally.Bring the structural owner into the interface, identify the missing input and authority, and tie closure to the real consequence date.Let the site supervisor infer the answer.

A useful consultant workshop produces a verbal solution. What must happen next?

Nothing; all attendees heard it.The material decision, authority, consequences and affected documents must enter the controlled project record.Only the Architect’s personal notes need updating.Wait until handover to record it.

What is the best basis for escalating an Architect interface issue?

The consultant has been difficult before.The response is inconvenient to the builder.A material consequence, missing authority or a decision path that has failed despite clear inputs and dates.Every answer that takes longer than one day.

What is the central BUILDIT lesson for managing the Architect?

Learn enough technical design to replace them.Manage the interface, not the personality: clarify roles, inputs, authority, consequences, decisions and records.Send more RFIs than the team can ignore.Keep consultant coordination separate from procurement and site.

Result can later feed your Consultant Interface Literacy profile.

0/20