Why a Written Service Agreement Protects Both Client and Architect

A written agreement can feel overly formal at the beginning of a friendly project. The client is excited. The architect is eager to help. Everyone believes the important details can be settled as the work proceeds. Then the first revision arrives, the budget changes, a consultant is needed, or someone remembers the conversation differently.

That is not always bad faith. Human memory is simply an unreliable project-management system. arrangement.

A contract is a shared map

The best service agreements do more than protect the architect's fee. They tell both parties what journey they have agreed to take. What is the project? What services are included? What will be delivered? Who makes decisions? How are consultants appointed? What information must the client provide? How will changes affect time and compensation? How can either party pause or end the engagement?

Republic Act No. 9266 expressly recognizes a written service agreement in architectural practice. That legal requirement matters, but the practical reason is even easier to understand: a building project contains too many decisions to rely on goodwill alone.

Clarity is not hostility

Some clients hesitate because contracts look one-sided or are written in intimidating language. That is a fair concern. An architect should be willing to walk through the agreement in plain language, identify negotiable terms, and explain why particular protections are present. A client should have time to read, ask questions, and seek independent advice when the commitment is significant.

The goal is informed consent, not a hurried signature.

At a minimum, the agreement should define the scope and exclusions, deliverables, programme, fee and payment schedule, reimbursable expenses, client responsibilities, consultant arrangements, review and approval points, additional services, change procedures, ownership and permitted use of documents, suspension or termination, dispute process, and the limits of any stated duty.

Changes are where weak agreements usually fail

Design changes are normal. What creates conflict is an unrecorded change whose effect is discovered too late. A useful agreement establishes how changes are requested, evaluated, approved, documented, and paid for. It also distinguishes a correction from a client-directed revision, a regulatory requirement, a consultant change, or new work caused by previously unknown conditions.

Written records do not need to make the relationship cold. A short confirmation after a meeting can preserve a warm working relationship by preventing a future argument about what was decided.

A contract cannot replace competence or trust

No document can rescue a project from poor judgment, chronic indecision, inadequate coordination, or dishonest conduct. The agreement creates a framework. The people still have to communicate, keep records, meet their obligations, and address problems early.

Nor does a breach automatically produce a quick remedy. Rights and remedies depend on the wording of the agreement, the facts, the evidence, and applicable law. When a dispute becomes serious, the parties may need qualified legal advice.

Before work begins, both client and architect should be able to answer a simple question: if we disagree six months from now, where will we look to understand what we promised each other? If the answer is only memory, the project is already carrying avoidable risk.

Read other articles:

• The Project Planning Workshop
• Five most essential things to know before deciding to design and build
• Best Way to have Better Control and Fast-Tract Your Project
• How Much Does Hiring an Architect Cost
• The Architect's Basic Design Service
• 7 reasons why Architects are seen as expensive and an unnecessary cost in building projects
• How to create a Design Brief for your architect
• Philippine architecture practice and P.R.C.'s position with Civil Engineers' encroachment in the architecture profession
• Architects and Architecture: Myths vs Reality

What the Architect's Regular Design Service Actually Includes

Many clients first meet an architect by asking for plans. That shorthand is understandable, but incomplete. The plans are the visible result of a longer process in which needs are translated into decisions, tested against a site and budget, coordinated with specialists, and documented for approval and construction.

The exact service varies. What follows is a practical map, not a substitute for the written agreement.

1. Understanding the project

Before designing, the architect should help clarify what the owner is trying to achieve. This may include the brief, site conditions, users, space requirements, budget, programme, regulatory constraints, risks, and information still needed. Surveys, geotechnical work, title review, environmental studies, or specialist advice may be separate appointments.

A useful first output is not always a drawing. Sometimes it is a decision that the proposed project, budget, or site needs to be reconsidered.

2. Schematic design

The architect develops and compares broad design ideas. Plans, diagrams, massing studies, and preliminary images help the owner understand organization, character, movement, climate response, and major tradeoffs. At this stage, decisions are still relatively flexible, but every option should be tested against the agreed brief.

3. Design development

The selected concept is developed in greater detail. Dimensions, materials, structural ideas, building systems, envelope, accessibility, and regulatory matters are coordinated with the appropriate consultants. Cost information should be reviewed at agreed points, recognizing that an estimate is not the same as a contractor's final price.

4. Contract and permit documents

The architect and consultants prepare the drawings, specifications, schedules, and other documents required by the appointment. Different authorities and procurement methods require different information. A permit set may not contain every detail needed for competitive pricing or high-quality construction, so the intended use of each document set should be clear.

5. Procurement assistance

When included, the architect may help prepare bid information, respond to questions, compare submissions, identify qualifications or exclusions, and advise the owner. The owner makes the commercial decision. A low bid should be examined for scope gaps, unrealistic allowances, and the contractor's capacity to perform.

6. Construction-stage service

The architect's role during construction depends heavily on the contract. It may include periodic site observation, review of submittals, responses to design questions, evaluation of proposed changes, assessment of payment applications, records of instructions, and reporting to the owner.

These services do not automatically make the architect the contractor or the continuous site supervisor. The contractor generally remains responsible for construction means and methods, sequencing, temporary works, site safety, labour, workmanship, and compliance with the construction contract. If the architect accepts a distinct construction-supervision, project-management, or contracting role, it must be lawfully defined and compensated.

7. Completion and closeout

Near completion, the architect may inspect or observe the work for stated purposes, identify incomplete or nonconforming items, review closeout documents, and advise on completion under the contract. No brief visit can discover every concealed defect. Warranties, tests, commissioning, as-built information, and post-occupancy review should be explicitly assigned.

The architect's regular design service is valuable because it connects decisions across the life of a project. Its limits are equally important. A professional relationship becomes stronger when the client knows not only what the architect will do, but also what the architect has not been appointed to do.

Read other articles:

• The Project Planning Workshop
• Five most essential things to know before deciding to design and build
• Best Way to have Better Control and Fast-Tract Your Project
• How Much Does Hiring an Architect Cost
• Why contracts are essential when engaging in services
• 7 reasons why Architects are seen as expensive and an unnecessary cost in building projects
• How to create a Design Brief for your architect
• Philippine architecture practice and P.R.C.'s position with Civil Engineers' encroachment in the architecture profession
• Architects and Architecture: Myths vs Reality

Why Architectural Services Can Seem Expensive, and What Clients Are Actually Paying For

People often ask why they should pay an architect before a single hollow block is laid. I understand the hesitation. A drawing can look deceptively simple, while construction is visible, noisy, and obviously expensive. The architect's work often happens quietly: clarifying the brief, testing options, coordinating specialists, anticipating conflicts, documenting decisions, and helping the owner understand what each choice may cost.

That difference in visibility creates a problem. Clients can easily count bags of cement or truckloads of gravel. It is harder to count the value of a bad decision that never had to be built.

The fee pays for decisions before they become expensive

A building project is a chain of decisions. How should the site be used? Which rooms genuinely matter? Where will heat, glare, rain, noise, and privacy become problems? Can the proposed structure and building systems work together? Is the design consistent enough for contractors to price and construct? Each unresolved question can return later as a variation, delay, compromise, or dispute.

Architectural work is not simply the production of attractive images. It includes inquiry, analysis, design development, documentation, coordination, and communication. The exact scope varies, and it should be stated in a written service agreement. A modest house may not need the same service package as a commercial building, but both benefit from knowing who is responsible for what.

Cheap design is not always inexpensive construction

A low initial quotation may be legitimate. It may reflect a narrower scope, a young practice, efficient systems, or a simple project. It may also omit services the owner assumes are included. The only sensible response is to compare like with like.

Ask whether the proposal includes site analysis, design options, consultant coordination, permit documents, specifications, cost checks, bidding assistance, site visits, contract administration, revisions, and record documents. Ask what is excluded. Ask how changes will be handled. A fee is difficult to judge until the service behind it is visible.

The same caution applies to offers of a free design tied to construction. Free may simply mean that the design cost is recovered somewhere else. That does not automatically make the arrangement improper, but the owner should know how the provider is compensated, whose interests the provider represents, how prices are checked, and who carries responsibility for design and construction decisions.

Architecture is not a contest against engineers or builders

Buildings require collaboration. Architects, engineers, contractors, suppliers, craftspeople, and public officials perform different but connected roles. The public is not helped when one profession explains its value by insulting another. The better question is whether each person is qualified, properly appointed, accountable for a defined scope, and working from coordinated information.

A good architect should not ask for blind trust. The architect should make the process legible. What are we deciding today? What evidence supports this option? What uncertainty remains? What will a change do to cost, time, performance, and character? Those questions build credibility more effectively than professional titles alone.

How should a client judge value?

Before choosing any proposal, ask for a clear scope, deliverables, exclusions, schedule, fee basis, payment stages, and change procedure. Review relevant experience and speak with previous clients when possible. Most importantly, test whether the professional listens well and can explain complex matters without hiding behind jargon.

An architect's fee is not automatically cheap or expensive. It is reasonable only in relation to the work, responsibility, competence, and value required by the project. The purpose of professional service is not to make construction costly. It is to help an owner spend a much larger construction budget with clearer intent and fewer avoidable surprises. 

Read other articles:

• The Project Planning Workshop
• Five most essential things to know before deciding to design and build
• Best Way to have Better Control and Fast-Tract Your Project
• How Much Does Hiring an Architect Cost
• Why contracts are essential when engaging in services
• The Architect's Basic Design Service
• How to create a Design Brief for your architect
• Philippine architecture practice and P.R.C.'s position with Civil Engineers' encroachment in the architecture profession
• Architects and Architecture: Myths vs Reality