AI for Architects and Interior Designers: Who Does What on a Joint Job

Yes, if the two firms agree three things first: one shared brief that both work from, a named owner for each task, and rules for client data and image sources. As a starting split, the architect owns anything that affects built form, drawings and consultants, while the interior designer owns finishes, furniture, lighting and mood boards.

Tools matter less than handoffs. Most joint-job trouble comes from two firms each using AI on the same brief and producing two versions of the truth: a concept image that implies a window the architect never drew, or a finishes schedule that disagrees with the room data sheet. A shared record with one owner per output prevents more of that than any choice of tool.

Follow me on Instagram@sagnikteaches

A starting split of tasks between the two firms

Treat this as a first draft to argue over at the kick-off meeting. The lead column assumes the architect is lead consultant and holds the client relationship; swap it if the designer leads.

Connect on LinkedInSagnik Bhattacharya

Two principles sit behind the table. First, AI never owns an output; a person in one of the two firms does, and the last column names the record that proves it. Second, anything that changes the building, a structural opening, a ceiling height or a stair, belongs to the architect, whatever tool a mood board came from. Where a task has two leads, as with schedules, each firm owns its half and the reconciliation is a named job rather than something that happens on goodwill.

Subscribe on YouTube@sagnikteaches

The shared brief: one document both firms work from

Everything else on a joint job hangs off one brief. It has a version number and a date, it lives in one place both firms can open, and each firm replies "confirmed" when a new version is issued. AI earns its keep by turning the messy output of a client meeting into the same four headings every time, so nobody has to reread forty lines of notes to find what was decided. If the client's answers come in as a questionnaire, summarising it into a brief is the same step done once at the start.

Summarise these meeting notes for a joint architect and interior designer project. Use four headings: Decided (with date and who agreed), Open questions (with who must answer and by when), Client preferences (likes and dislikes), Constraints (budget range, programme, items to keep). Draw only on the notes. Do not resolve open questions or add suggestions. Mark anything unclear as "unclear".

An illustrative extract of the result, after the person who ran the meeting has corrected it:

SHARED BRIEF v3 (issued after meeting 3)
DECIDED
- Rear extension agreed at 14 ft deep (architect; client confirmed at meeting 2)
- Kitchen island stays; sink moves to the window wall (designer and client, meeting 3)
OPEN
- Hall floor: oak or stone? Client to decide by meeting 4; designer to bring two samples
- Rooflight over the dining area? Architect to price; client waiting
PREFERENCES
- Likes: warm timber, soft lighting, plants. Dislikes: gloss finishes, open shelving
CONSTRAINTS
- Interiors budget range agreed in writing; kitchen delivery needed before week 14

The "Decided" list matters most, because it is the record people reach for in a dispute. Keep the rule that only a person adds to it, and only after both firms have heard the client say it. A second job for the AI is comparing version 2 with version 3 and listing what changed, so the confirming reply is a read of five lines instead of a hunt through the whole document. The comparison is a draft too: the person confirming still opens the brief.

Mood boards and concept images need a label and a checker

A mood board is for feeling, and a concept image is for imagining. Neither is a design. AI makes both so convincing that clients start treating them as promises, so every image that leaves either firm should carry the same line: "Concept only. Not to scale. Not a design commitment." The architect then reviews anything that shows built form, and the designer reviews anything that shows furniture or finishes against the schedule. Five questions to ask before an image goes to the client:

Keep a source log so you can show where any image came from. Filled in, it looks like this:

A common way this goes wrong: a designer's concept image of the dining space shows a full-height glazed wall, and the architect's plan has a window and a structural column in that position. The client falls in love with the image and assumes it is in the design. The architect spends a week explaining why it is not, and the relationship takes a knock that the label and a ten-minute architect review would have avoided. If an image shows something you cannot yet build, say so on the image: "Glazing indicative, subject to structural design." For more on getting the images themselves right, mood boards and presentations for interior designers covers the designer's side.

Schedules: let AI find the mismatches and people resolve them

The architect's room data sheet and the designer's finishes and fittings schedule overlap in more places than anyone plans for: ceiling heights (which decide pendant drops and curtain tracks), floor build-up against floor finish (which decides threshold levels), door types against hardware and finishes, socket counts against the furniture layout, and light points against fixtures. A tool is good at comparing two lists of facts and bad at knowing which list is right, so use it for the first and keep the second for people. Paste both schedules as text. The details of building each sheet are in room data sheets from a client brief and building and checking an FF&E schedule.

Below are two schedules pasted as text. Schedule A is the architect's room data sheet. Schedule B is the interior designer's finishes and fittings schedule. Compare them room by room on ceiling height, floor finish, door type, socket count and light points. List every mismatch as: room, item, value in A, value in B. Do not decide which is right. If a room or item appears in only one schedule, list it as "missing from A" or "missing from B". Do not guess missing values.

SCHEDULE A
Kitchen/Diner | ceiling 9 ft 0 in | floor engineered oak 14 mm | door D1 glazed | sockets 12 | lights 8
Hall | ceiling 8 ft 6 in | floor oak 14 mm | door D2 solid | sockets 3 | lights 4
Utility | ceiling 8 ft 6 in | floor porcelain 10 mm | door D3 solid | sockets 6 | lights 2

SCHEDULE B
Kitchen/Diner | ceiling 9 ft 0 in | floor engineered oak 20 mm | door D1 glazed | sockets 14 | lights 8
Hall | ceiling 8 ft 6 in | floor stone 20 mm | door D2 solid | sockets 3 | lights 5
Utility | ceiling 8 ft 6 in | floor porcelain 10 mm | door D3 solid | sockets 6 | lights 2
Boot room | ceiling 8 ft 6 in | floor porcelain 10 mm | door D4 solid | sockets 4 | lights 2

An illustrative reply lists five mismatches: Kitchen/Diner floor 14 mm against 20 mm, Kitchen/Diner sockets 12 against 14, Hall floor oak against stone, Hall lights 4 against 5, and Boot room missing from A. The people then take over:

On the full 14-room set the same check listed 11 mismatches across 70 compared cells (14 rooms by 5 columns). Four were out-of-date entries, three were real decisions waiting on the client, two came from different room names for the same space ("Kitchen/Diner" and "Kitchen"), and two needed the architect's input, a heavy stone floor on a timber structure and a pendant drop below the ceiling void. Agree one room list before you start, because room names are the commonest cause of false mismatches. The money argument is simple: a hall floor specified wrongly across an illustrative 190 sq ft at $9 a sq ft is $1,710 of material, and caught at schedule stage it costs one message. Caught on site, it costs a re-order and a delay.

Client updates in one voice

Clients on a joint job get confused fastest when two firms write to them. Pick one sender, normally the lead, and have the other firm add its items to a shared update log by the day before. The AI drafts from the log, both firms read the draft, and the sender approves it. Use the same three headings every time so the client learns where to look.

Draft a client update of about 150 words from the log entries below. Use three headings: Decided this week, Waiting on, Coming up. Use plain words. Only include dates that appear in the log. Do not promise delivery or completion dates; where the log gives a supplier estimate, call it an estimate.

LOG
Kitchen units ordered Monday; supplier estimate week 6 from order.
Hall floor: client decision outstanding.
Structural engineer visits Thursday.
Lighting plan v2 sent to client.

The risk is the sentence that turns an estimate into a promise. Compare a typical first draft with the version a person should send:

In the third row the edit explains why the decision matters, which is more persuasive than urging. Meeting minutes feed the same log, and recording, summarising and issuing minutes the same day shows the routine. Refer to the firms by role in client emails, "the architect" and "the designer", so each update reads as one project team.

Who owns what the tools produce

Ownership has three layers, and a joint job needs all three settled. The first is between the two firms, which only your own agreement can cover. The second is between each firm and the tool vendor. The third is what happens if an image turns out to resemble someone else's work.

• Between the firms. Say in writing, even in an exchange of emails, who owns which outputs (images, schedules, summaries), how each firm may reuse them in a portfolio or on a website, and what happens to shared files when the job ends. A tool's terms say nothing about any of this.
• Between you and the tool. Terms differ, so they should influence which account makes the images. OpenAI's terms say that, as between you and OpenAI, you own the output and OpenAI assigns you its rights in it, and they add that output may not be unique and other users may receive similar output. Midjourney's terms say you own your assets to the fullest extent the law allows, with exceptions, one of which is that a company or an employee of a company with more than $1,000,000 a year in revenue must be on a Pro or Mega plan to own them. Midjourney also takes a broad licence to use what is made, and content is public by default; only its Stealth feature on Pro or Mega plans, on a best-efforts basis, avoids publishing, which matters when an image shows a client's home.
• If someone claims a resemblance. Do not assume the vendor stands behind you. As of October 2026, OpenAI's output indemnity names API and Enterprise customers and not ChatGPT Business, and Adobe's commercial-safety claim covers its own Firefly models rather than partner models in the app, with its IP indemnity limited to eligible enterprise customers.

Whether a purely machine-generated image can be protected by copyright varies by place and is still developing, so do not promise a client exclusivity in an AI image, and ask a qualified adviser what a given image means for your portfolio. Third-party material needs its own care. Use manufacturers' photos only as their terms allow, keep credits, and never prompt with a living designer's name to reproduce their scheme. Copyright and client data risks of AI in architecture practices goes further on the practice-side risks.

Client data and copyright checks before anything is shared

Decide, before the first file moves, what each firm may put into an AI tool at all.

The account matters as much as the table, because both big vendors draw the line by plan. OpenAI's pages say ChatGPT Business, Enterprise and its API are not used for training by default, and Anthropic makes the same promise for its commercial products. On ChatGPT Free, Plus and Pro, though, model improvement is on by default; you switch it off under Settings, then Data controls, with the toggle called "Improve the model for everyone". Use a business account for anything about a client, and keep personal accounts away from project work. Whether you can share an AI Project with people outside your own organisation depends on the plan, so the dependable route between two firms is plain, dated documents shared the way you already share everything else: the brief, the logs and the schedules. At the end of the job, remove the other firm's access and archive what you need to keep.

A joint job over 20 weeks, with the hours and the costs

A four-person architecture practice, acting as lead, and a solo interior designer take on a rear extension and a refit of 14 rooms for a couple. The project runs 20 weeks. They adopt three routines from this tutorial: a shared brief, updated six times; a schedule cross-check three times; and a weekly client update. The figures are illustrative; replace them with your own log.

That is 13 hours saved. At a blended $60 an hour it is worth $780. The cost is the extra seats: one more on the practice's existing team plan and, because ChatGPT Business and Claude Team both start at two seats, two for the solo designer. Three seats at $25 a month billed monthly for five months come to $375, leaving a net of $405. It is a modest figure, and it is not the reason to do this. The reasons are the 11 mismatches caught before anything was ordered, and the absence of two competing versions of the truth. One wrongly specified hall floor, at the $1,710 worked out earlier, is bigger than the entire net saving.

What stays with a person on both sides is the same in every project of this kind: the client conversation about taste and money, sign-off on drawings and specifications, any judgement about safety, accessibility or the fire performance of finishes and furniture, coordination with consultants and the decisions recorded in the brief. The AI drafts, compares and sorts. It never signs, and it never decides.

A kick-off checklist for the two firms

Run through this at the first meeting, and record the answers at the top of the shared brief:

1. Which firm is lead, and who sends client updates?
2. Who owns each output in the table at the top of this tutorial?
3. Which accounts will be used, and are they all business accounts?
4. What is the label on concept images, and who reviews images that show built form?
5. Where is the source log kept, and who fills it in?
6. Is there one agreed room list for both schedules?
7. What may and may not go into an AI tool, using the data table above?
8. Who may reuse which images and documents afterwards, and in what form?

Eight answers on one page cost an hour at the start and save arguments later. A written AI policy for your own practice sits one level above this agreement, and each firm should have one before the job starts.

Joint projects and AI: questions between two firms

Should both firms use the same AI tool?

Not necessarily, but they should share one brief and one set of rules. Each firm can use its own business account, as long as both work from the same dated brief, log decisions in the same place and agree what may be shared. Mixing tools is fine; mixing versions of the truth is what causes trouble.

Who owns an AI-generated concept image on a joint job?

The collaboration agreement should say, because a tool's terms only cover the user's relationship with the vendor. The terms I read assign output to the user, with conditions such as plan requirements for larger companies. Agree who may reuse images in portfolios and in what form, and ask a qualified adviser about copyright in machine-generated work.

Can we put the client's photos into an AI tool?

Only in a business account, and only if the client has agreed. Interior photos show private details such as family pictures, documents and security equipment. Crop what you can, tell the client which tools you use, and delete uploads from the project when it ends. Check contract terms for any limit on sharing.

What if the other firm will not use AI?

Then keep AI inside your own boundary: your notes, your drafts, your schedules. Ask only that shared documents are accurate and dated, and do not feed their drawings or schedules into a tool unless the contract and the client allow it. Handoffs still work when they are plain, dated documents.

Further reads

• Midjourney for Architects: Concept Images for Client Meetings — Concept images for client meetings, from the architect's side.
• Best AI for Interior Design Mockups: Client-Ready Images for a Studio — Client-ready mockup images for a design studio.
• Best AI for Architecture and Interior Design: Concept Image Tools by Cost — Concept image tools for both professions, compared by cost.
• Interior Design Project Timeline: Draft Phases and Lead Times With AI — Draft project phases and lead times with AI help.
• AI for Freelance Designers: Faster Concepts Without Rights Issues — Faster concepts without rights problems.
• AI Policy for Architects: A Ready-to-Use Checklist and Clauses — A ready-to-use AI policy checklist for a practice.
• AI for Architecture: Keep a Drawing Issue Register and Transmittal Log — Keep a drawing issue register and transmittal log.
• AI Marketing Tools for an Interior Design Business: Houzz and Pinterest — A three-hour monthly routine for interior designers: one project card and photo set become fresh Houzz, Pinterest and Google profile content.
• Interior Design Proposal Template: Scope, Fees and Phases With ChatGPT — What goes into an interior design proposal, with a worked two-room example and ChatGPT prompts for scope, phases, fees and exclusions that you then check.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI terms of use and business data pages, Midjourney terms of service, and Anthropic commercial privacy page, all read in November 2026; Adobe Firefly points rest on notes checked in October 2026.