Architecture in Motion: Managing Time from Brief to Handover
Updated: Oct 4
Architecture is often described through space: the rooms we create, the buildings we occupy, and the environments we shape. But there is another dimension that quietly controls almost every project—time.
A building does not appear overnight. From the first conversation with a client to the final handover, an architectural project moves through a sequence of decisions, approvals, revisions, procurement, construction and inspections.
Understanding this timeline is not only the architect's responsibility. Clients who understand time can make better decisions, control costs and avoid unnecessary delays.
Architecture Is a Process, Not an Event
One of the biggest misconceptions about architecture is that the final drawings are the project.
They are not.
The drawings are one part of a much larger process.
A typical project may involve:
Brief → Concept Design → Design Development → Documentation → Approvals → Tender/Procurement → Construction → Inspections → Handover
Each stage depends on the one before it.
If the client changes the number of bedrooms after the construction drawings have been completed, for example, the change may affect the floor plan, elevations, structural information, electrical layouts, plumbing, quantities and potentially the approval process. A decision that takes five minutes to make can sometimes create days or weeks of additional work.
This is why time in architecture is closely connected to decision-making.
The Cost of a Late Decision
Time and money are closely related in construction.
Early design changes are generally easier to accommodate because relatively little work has been completed. As the project progresses, however, the cost of changing a decision increases.
Consider a simple example.
A client decides during concept design that they want a larger kitchen. The architect can adjust the layout relatively easily.
The same decision made after construction has started could potentially involve:
Revising approved drawings
Re-coordinating consultants
Changing quantities
Ordering different materials
Delaying contractors
Increasing labour costs
Applying for amendments where required
The lesson is simple:
The earlier a decision is made, the more flexibility the project usually has.
This does not mean clients should rush decisions. It means that projects benefit from having a clear process for making, recording and approving decisions.
Why Architects Keep Asking for Information
Clients sometimes wonder why architects ask for seemingly small pieces of information.
What type of kitchen do you want?
Where should the television go?
Do you want a bath or shower?
Which floor finish do you prefer?
Where should the air-conditioning units be positioned?
These questions are not simply about aesthetics.
They are coordination questions.
A single decision can affect several drawings and disciplines. The architect has to translate the client's requirements into information that can be understood by consultants, contractors, suppliers and authorities.
The better the information is coordinated, the less likely the project is to experience unnecessary rework.
The Importance of a Project Programme
Every serious architectural project should have some form of project programme.
A programme identifies what needs to happen, when it needs to happen and who is responsible for it.
For a residential project, this could look something like:
Stage | Typical Responsibility |
Project Brief | Client + Architect |
Concept Design | Architect + Client |
Design Development | Architect + Client |
Technical Documentation | Architect + Consultants |
Municipal Submission | Architect |
Approval Process | Municipality / Relevant Authority |
Contractor Appointment | Client |
Construction | Contractor |
Inspections | Architect / Consultants |
Practical Completion | Project Team |
Handover | Client + Project Team |
The exact duration will vary considerably depending on the size, complexity, location and approval requirements of the project.
The important point is that the programme creates expectations.
Without one, clients may assume that everything is happening simultaneously. In reality, many activities depend on information or decisions being completed first.
Time Is Also a Design Constraint
Architects are accustomed to thinking about constraints.
A site has boundaries.
A budget has a limit.
A building has structural requirements.
Planning regulations impose restrictions.
But time is also a constraint.
A client who needs to occupy a building by a specific date has a different project strategy from a client who is willing to wait for a highly customised design.
For example, if a project needs to be completed within a tight timeframe, the team may need to consider:
Simpler construction methods
Readily available materials
Early procurement
Faster approval strategies
Reduced design changes
Clear decision deadlines
Early appointment of consultants and contractors
Time should therefore be considered during design—not after design.
The Client Is Part of the Project Team
Good project management is not something the architect does to the client.
It is something the project team does with the client.
Clients have important responsibilities, including:
Providing information on time
Reviewing drawings
Giving clear feedback
Approving decisions
Confirming budgets
Selecting finishes
Making payments according to the agreed terms
Communicating changes through the agreed process
This is particularly important because architectural projects often involve many moving parts.
The architect may be waiting for the client.
The engineer may be waiting for the architect.
The contractor may be waiting for drawings.
The supplier may be waiting for specifications.
A single delay can move through the entire chain.
Don't Run Your Project on WhatsApp Alone
WhatsApp is extremely useful for communication, but it is not necessarily a project-management system.
A project can quickly become difficult to track when important decisions are buried between:
"Morning."
"Can we move this window?"
"Yes, that's fine."
"Actually, can we make the kitchen bigger?"
"What about the tiles?"
Six months later, nobody remembers exactly when a decision was made, who approved it or which drawing incorporated it.
A better approach is to use dedicated project-management tools where decisions, tasks, files, deadlines and responsibilities can be recorded.
This does not mean communication has to become complicated.
It means important information should be organised so that everyone can find it when they need it. At TectArch, we make it a priority to hold at least one client meeting each week throughout the active design stages of a project. These meetings provide an opportunity to review the client’s requirements, discuss design decisions, and evaluate the project through drawings, floor plans, and 3D perspectives. All key decisions and agreed changes are recorded in meeting minutes, creating a clear record that helps keep the client, architect, and wider project team aligned.
Project Management Tools Clients Can Use
Clients do not need to become professional project managers to benefit from project-management software.
Here are several useful categories of tools to consider:
1. Trello
Trello is useful for clients who want a simple visual overview of their project.
You can create columns such as:
To Do → In Progress → Awaiting Client → Approved → Complete
This is particularly useful for tracking decisions and outstanding tasks.
2. Asana
Asana is useful for more structured projects where there are many tasks, deadlines and responsibilities.
A client can use it to see:
What needs to be done
Who is responsible
When it is due
What is overdue
What has been completed
3. ClickUp
ClickUp combines tasks, documents, deadlines and project information into one platform.
It can be particularly useful for clients managing larger developments or working with several consultants and contractors.
4. Microsoft Planner
Microsoft Planner is a practical option for clients already using Microsoft 365.
It provides a relatively straightforward way to organise tasks and responsibilities without introducing an entirely separate ecosystem.
A well-organised document system can save enormous amounts of time.
The Best Tool Is the One Everyone Uses
Technology will not solve poor communication.
A beautifully configured project-management platform is useless if nobody updates it.
The objective should therefore not be to introduce as many tools as possible.
Instead, establish one clear source of truth for the project.
Use messaging applications for quick communication.
Use email for formal communication where appropriate.
Use cloud storage for documents.
Use project-management software for tasks, deadlines and responsibilities.
Most importantly, establish a simple rule:
If a decision affects the project, record it.
Because architecture is ultimately about more than designing buildings.
It is about coordinating people, information, money, materials and—perhaps most importantly—time.
The better a project manages time, the more opportunity the design team has to focus on what matters most:
creating a building that works.
Starting a project and want it to run on time?
TectArch Architects is an award-winning, PrArch-led practice based in Johannesburg. We run every project with a clear programme, weekly client meetings and recorded decisions, from brief to handover.
Book a Site Assessment to plan your project properly from day one.
Written by Mfanelo Hlophe, TectArch Architects.
Comments