LO
Architect — tasks, one by one
The unit of analysis is the task, not the job title. Each one below carries its direction, whether the judgement rests on evidence or on platform inference, the reasoning, and what it does not establish.
Every task on this page#
Renderings and presentation images
Automating✓ Evidence-backedProducing the images that sell the scheme to a client or a planning committee.
Image generation from a massing model or a sketch is now fast and convincing, and practices that outsourced rendering are bringing it in-house as a prompt. This was a specialist sub-trade with its own studios, and it is the part of the architectural world under the most direct pressure.
This was a specialist sub-trade with its own studios and its own people. Practices absorbing it in-house is good for practices and terminal for visualisers.
Construction documentation
Being augmented✓ Evidence-backedThe drawings and specifications a contractor builds from — hundreds of sheets, coordinated with engineers.
Building-information tools already generate much of the documentation from the model, and code-checking and clash detection are automating further. What remains is the judgement in detailing — how this junction actually keeps water out — and the professional liability for the drawings, which stays with the signing architect.
Documentation is where most of a practice's billable hours sit and where most architects spend their careers. Compressing it changes the economics of running a practice long before it changes who signs the drawings.
Understanding the brief and finding the idea
Still human-led≈ Platform inferenceWorking out what the client actually needs, what the site allows, and the organising idea that makes it a building rather than a diagram.
Generative tools produce many plausible massings quickly, which is useful for exploring options. Choosing between them requires knowing the client, the neighbours, the planning officer and the budget — context that is not in the prompt — and the responsibility for the choice is the architect's. Having options was never the scarce thing; knowing which one is right was.
Concept work is what architects want to do and a small share of what they are paid for. Protection here does not fund a practice.
Approvals and coordinating the team
Still human-led✓ Evidence-backedPlanning permission, building control, and keeping structural, mechanical and cost consultants pointing the same way.
Approvals are negotiations with authorities and communities, and coordination is a people-management task under commercial pressure. Code-checking tools assist the compliance part; the persuasion and the accountability do not automate, and they are a large share of a project architect's time.
Negotiating with authorities is protected by how authorities work, which is a rule set, not a law of nature. Digital planning submission regimes are already narrowing what has to be argued in person.
Site inspection and construction-phase decisions
Still human-led≈ Platform inferenceWalking the site, answering the contractor's questions, deciding what to do when the ground is not what the survey said.
Construction is physical, local and full of exceptions, and the decisions taken on site carry liability. Drones and scanning improve the record of what is there; deciding what to do about it remains the architect's, on the day, in the mud.
Site work is a phase, not a job, and on many projects it is contracted out to a different role entirely. Being safe on site says little about the studio jobs that make up the profession.