ExAC Podcast | Examitect

A signed construction contract is an agreement between its parties, so a design change needs the proper authorisation. We look at the architect's role in proposing and documenting adjustments without assuming authority to rewrite that agreement. The episode closes project management by returning to the tools, communication, and clear responsibilities that keep a project moving deliberately.

An addendum belongs to the bidding stage, while changes after signing need the appropriate construction-phase process. We separate those terms and compare them with change orders, directives, and site instructions. Knowing the timing helps you name the right document before considering what it needs to say or who has the authority to issue it.

Bonds and surety documents appear at different points in selecting and appointing a contractor. We revisit the bid bond, prequalification, and consent of surety, then look at who receives the protection. The discussion helps separate a document supplied for the owner's benefit from one that the contractor or architect would call on for themselves.

Contractual relationships and coordination lines are not always the same thing. We compare construction management as agent with design-build, looking at who contracts with whom and when the price and scope become clearer. The episode connects those relationships to the relevant CCDC documents, helping make sense of diagrams that can otherwise look deceptively similar.

Knowing the price early can be reassuring for the owner, but someone has to carry the uncertainty behind it. We look at delivery methods through that tension and the point when a contractor is asked to commit. The discussion connects cost certainty, risk, and timing, giving another way to understand why different clients choose different arrangements.

Quality assurance sets up the process; quality control checks the result. We explore that distinction through familiar office procedures, including how drawings are prepared and issued. The episode also considers how a small practice can begin putting useful checks in place without building a system that is too cumbersome for the work it does.

A team needs clear work, clear objectives, and a way to keep everyone informed. We explore assignments, follow-up, measurable goals, milestones, and communication protocols, including checking that the message was received and understood. The discussion brings leadership back to everyday habits that help people stay aligned as the project becomes more complicated.

An architecture practice is also a business, and a business plan needs to explain the case for it. We look at the company's position, goals, and the information that helps someone understand what it is trying to achieve. The discussion connects a clear proposal to the practical need to win support and revisit the plan as the practice changes.

Management plans can be useful without becoming long reports. We look at setting out how quality will be checked and how the client will be involved, including reviews, decisions, and changes. The episode uses everyday office work to show how a short, clear plan can make expectations easier to discuss and follow.

An organisation chart shows the relationships behind a project, while the budget shows what it takes to support the work. We look at responsibility and coordination across parties, including those without a direct contract. We then build the budget picture from labour, overhead, other costs, contingency, and profit, connecting people and money to the work plan.

A schedule needs to show how tasks depend on one another, not just when you hope they will happen. We look at task links, slack, and the critical path through a project. A construction sequence helps explain why saving time on one activity may move the finish date while speeding up another may leave it unchanged.

A work plan turns the next phase into activities that can be assigned and followed. We introduce the work breakdown structure and show how large packages are divided into smaller tasks. Breaking the work down makes gaps easier to see and gives the team something clearer to manage than a broad promise to finish the phase.

A project manager keeps work moving through people, resources, and decisions. We look at assigning tasks, following up, solving problems, assessing risk, and keeping information moving in both directions. The discussion shows why the role needs more than technical knowledge and why a useful response may involve changing the plan or the resources behind it.

Project management is a discipline with tools that apply well beyond construction. We introduce the idea of a project as a unique piece of work with a beginning and an end, then consider the manager's role in bringing it to completion. The episode sets up the people, time, money, and risk questions explored through the topic.

The language used during construction carries meaning from the contracts, legislation, and local requirements. We look at certificates, occupancy-related documents, and terms that can be interpreted too casually. The episode closes the site topic by connecting an understanding of each document's purpose to the need to use its defined language accurately.

Some work can only be reviewed properly before the next layer covers it. We look at meetings, specialist inspections, and the timing of general reviews as construction progresses. The discussion connects attendance and coordination to a simple practical problem: once an assembly is closed up, the opportunity to see what is inside may be gone.

A useful site visit needs careful records and the right preparation. We discuss notes, reports, filing, safety equipment, and coordination with the owner and contractor. The long view matters here: a problem may only appear years later, when a clear record of what was observed and communicated becomes essential to understanding what happened.

On site, the architect brings the documents together with the work in front of them. We look at walking the construction, attending meetings, interpreting the contract information, and resolving questions through the proper channels. The episode also recognises how field and office work overlap when notes and reports can be prepared during the visit itself.

Closing a project still calls for careful review and reporting. We look at the final general review report, outstanding matters, and the final certificate, connecting them to the records kept throughout construction. The episode closes the office-side topic by bringing the paperwork back to its purpose: giving the parties a clear account of the completed work.

Handover brings together the systems, records, and instructions the owner needs to use the building. We look at commissioning, record drawings, warranties, declarations, and the closeout package, while distinguishing the architect's review role from the specialists' work. The discussion shows why completing construction and delivering a usable record are related but separate tasks.