Explore every episode of the podcast 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.

Substantial performance is about readiness for the intended use as well as the work completed. We explore the safety, usability, and legal considerations discussed in the episode, then connect certification to its date and the consequences that follow. The focus is on understanding the milestone clearly before treating it as another item on the closeout checklist.

The word 'review' matters when a shop drawing comes back from the architect. We look at the contractor's role before submission, the review responses, and the risks of changing or completing the design information supplied by others. Keeping the contract requirements and the purpose of the submission in view helps prevent an ordinary review from taking on unintended responsibilities.

Once values have been assigned to the work, payment review turns to how much has actually been completed. We look at checking quantities and progress, coordinating the consultants' reviews, and bringing the findings into a certificate. The episode connects the office calculation to what can be supported by the work observed on site.

A payment application needs a clear breakdown of the work and the documents that support it. We introduce the schedule of values, the monthly cycle, declarations, and holdback as parts of that process. The discussion also returns to the start of the project, when checking the proposed values helps make later payment reviews more meaningful.

A change can affect time, money, or both, and the right document depends on how it is authorised. We compare change orders and change directives, following the communication between contractor, architect, and owner. The episode helps explain the difference between agreeing on the adjustment first and directing work while the consequences are still being established.

Before construction begins, several protections and responsibilities need to be confirmed. We look at bonds, insurance, workers' compensation documentation, and safety and emergency arrangements. Renovation work adds another layer to the discussion, where an occupied or partly accessible property can make the boundaries around the site and stored materials less straightforward.

The first construction meeting sets habits the team will use for the rest of the job. We look at meeting frequency, communication routes, schedules, recurring submissions, and the documents that need early attention. A checklist becomes a practical tool for covering the whole project, including the less visible requirements that are easy to overlook.

Responsibility for carrying out the work needs to stay clear during construction. We explore the contractor's control of site activities alongside the architect's responsibility for the design and interpretation of the documents. Project milestones also enter the discussion, helping explain why the timing of a decision can affect which obligations are in play.

The owner and contractor each need to do their part for administration to work. We look at timely decisions, responses, construction obligations, testing, and the information the architect depends on. The discussion also considers the limits of the architect's authority, where knowing who is responsible can be as important as recognising that something needs attention.

The architect's construction-phase work stretches from early schedules to the final closeout documents. We look at shop drawings, submittals, field-review follow-up, progress reporting, and the flow of information through the office. The episode also begins separating activities that sound similar but carry different responsibilities, helping establish what the architect has been engaged to do.

Construction administration gives the architect's office a steady flow of information to receive, check, and issue. We introduce the work through samples, documents, questions, payments, changes, and closeout. This opening sets the tone for the topic, where clear records and careful communication support decisions that may matter long after construction is complete.

A closing deadline and a letter of acceptance can have consequences beyond routine correspondence. We discuss late bids, modifications made before closing, and the role of the acceptance letter. The topic closes with a practical writing habit: make every notice and letter clear, factual, and understandable to someone who may later need to review the decision.

Bid documents need a clear structure, and changes need a reliable way to reach everyone. We look at the organisation of specifications and the role of addenda in updating the package. Written changes, numbering, dates, distribution, and acknowledgments all help keep bidders working from the same information as the process moves toward a contract.

Bid, performance, and labour and material payment bonds cover different stages and concerns. We follow each through the bidding and construction process, separating the commitment to enter the contract from completing the work and paying those who contributed. The episode helps you identify which protection a scenario is asking about before choosing the document.

Construction asks an owner to commit to work that has not yet been completed, which makes financial security part of the conversation. We introduce surety in that context, alongside the guidance for calling and receiving bids. The discussion also looks at the steps that help establish whether a bidder can provide the required bonds.

Evaluating bids starts with checking what was actually submitted. We look at completeness, prices in words and figures, addenda acknowledgments, dates, subcontractor information, and references. The episode also separates the architect's technical review and recommendation from the owner's decision to award, keeping the findings factual and tied to the stated requirements.

The invitation to bid is only the beginning of the package. We look at closing details, document access, security, the proposed contract, instructions, forms, drawings, specifications, addenda, and evaluation criteria. Bringing those pieces together helps explain how the documents give bidders a common basis for preparing their offers and showing they can carry the required obligations.

A competitive bid process creates expectations about fairness before the construction contract is signed. We introduce the legal issues discussed in the episode and the importance of applying the stated requirements consistently. Clear deadlines, disclosed criteria, and equal information become practical ways to support a process that bidders and the owner can rely on.

A bid package needs to give contractors enough common information to price the work. We look at distributing the contract documents, how contractors build up prices from their subtrades, and the difference between open and invited bidding. Prequalification also enters the discussion as a way of deciding who is eligible to take part.

Construction contracts also need to address the protection of people, property, and the finished work. We explore insurance, workers' compensation, warranties, and the conditions around taking over the project. The discussion then returns to supplementary conditions and the wider team, where each party needs to understand the protection required for its role.

Money and changes can put pressure on a project, and the contract sets out ways to handle them. We look at financial information, changes in the work, default notices, and dispute-resolution provisions. The episode connects the available processes to the need for careful administration before a disagreement grows into a more formal dispute.

The general conditions provide the working machinery of the construction contract. We look at the consultant's authority, defective work, shop drawings, and the role of supplementary conditions in making changes. Cash allowances and contingency allowances offer a useful comparison between money expected to be spent and a reserve whose use remains uncertain.

CCDC 2 becomes easier to read when you know what each part contains. We open the agreement and definitions, looking at parties, dates, contract documents, price, and payment terms. The episode also flags the distinction between a change order and a change directive, where a precise definition matters during construction administration.

Before comparing contract forms, it helps to understand what a contract is meant to establish. We introduce the basic ideas discussed in the episode and the role of standard templates, then revisit the major pricing families. Stipulated price, cost plus, and unit price offer different answers to when the final cost becomes known.

Large projects can bring together public-private partnerships or integrated project delivery arrangements. We introduce the roles and commitments within those models, then consider collaboration and the treatment of uncertainty. The examples show how the way a project is organised can influence the handling of risk, responsibilities, and decisions across a much wider team.

A bridging consultant helps define what an owner is buying in a design-build arrangement. We look at outline and performance requirements, then turn to the wider role of a turnkey developer. Land, approvals, and financing enter the picture, showing how responsibility, potential reward, and risk can expand beyond the design and construction contract.

Choosing a delivery method starts with understanding the client. We work through contrasting examples of a time-driven business and an owner with in-house expertise and a firm budget. Comparing what each needs makes the advantages, disadvantages, and relationships of the methods more useful than simply memorising their names.

Design-build puts design and construction under one entity, changing the owner's point of contact and the architect's working position. We explore the appeal of a combined service, potential schedule benefits, and the effect of setting costs early. The discussion keeps professional responsibility in view while examining what the arrangement means for design control.

A construction manager can also take on the responsibility to build. We follow that arrangement from early advice through pricing and the move into construction, then look at the consequences for risk and cost. The episode helps separate this role from the advisory models and explains why the choice needs to suit the owner and project.

A construction manager brought in early can help with cost, schedule, and constructibility before work begins. We compare the advisor and agent roles, looking at how authority and contractual relationships change between them. The distinction matters when deciding who can act for the owner and how early construction expertise will influence the design.