ChatGPT Space for architects: shared project briefs

01

What is ChatGPT Space?

OpenAI's update for the week of 28 September–2 October 2026 highlights Space as a place to develop and share work with ChatGPT. Pages can be drafted or revised with an agent, edited directly, and shared with collaborators where the feature is available.

For an architecture team, a useful first experiment is the project brief that keeps changing during early design. The studio example here is archiPrompt's proposed workflow: bring the current brief, the evidence behind it, and the unresolved questions into a document the team can review together.

• Source: September 28–October 2, 2026: work together in ChatGPT Space

02

Build a brief with visible decisions

A Page is a document you and ChatGPT can edit together. A space groups related pages around a team or topic. Pages can also have child pages. Space includes other saved work, such as files, spreadsheets, presentations, and images, depending on the capabilities available to your account.

Start with a root Page named for the project and design stage. Give the team a short current brief, then add related pages only when a topic needs its own discussion. The structure below is a suggested studio layout; keep it small enough that everyone can find the current decision.

• — Project brief: purpose, users, scope, and the current revision date
• — Agreed decisions: decision, approver, date, and supporting source
• — Open questions: owner, next action, and target response date
• — References: named documents, revision identifiers, and source links
• — Design review notes: proposed changes awaiting a decision

• Source: ChatGPT Space: Pages, files, and connected sources

03

Try one focused revision

Suppose the client has confirmed the number of homes but is still reviewing the ground-floor community room. An AI revision should carry that distinction into the brief. Give the agent the dated meeting record and identify the exact section to update.

In the conversation beside the Page, paste the prompt below. You can also ask an agent inline with @ChatGPT or @dot where those controls are available. Explicitly say whether you want discussion in chat or an edit to the Page, then inspect the resulting text.

Update only the Project requirements and Open questions sections of this Page using [meeting record and date]. Preserve the approved scope, confirmed unit count, and existing decision references. Treat the community-room proposal as awaiting client approval unless the source explicitly confirms it. Add a source reference for each changed requirement. Keep missing information visible as an open question. Do not invent dimensions, budgets, approvals, or dates. After editing, list the changes and the decisions the project lead still needs to make.

• Source: Work with agents in Space

04

Share with the people who need to contribute

Space's sharing controls offer view, comment, and edit access according to the available recipient and workspace options. Access can also be inherited from a parent Page or shared space. Check the saved permissions and confirm that a collaborator can open the work with the intended role.

For this pilot, give the project team edit access where they maintain the brief, and use comment access for review where it is offered. Keep proposed changes clearly identified until the person responsible for the brief accepts them. Agree on who will edit each section during the first design review.

• Source: Collaborate in Space: roles and inherited access

05

Check what the shared Page reveals

Linked source files retain their original permissions. Material copied or summarized into a Page is visible to people who can access that Page. A colleague may therefore read a summary without being able to open its underlying source. Sharing a Page also does not share your private chats or saved memory.

Before inviting a consultant, check the actual text, attachments, and inherited access. A client-only budget note copied into the brief deserves the same audience check as the source document. Give the brief enough evidence to be useful while keeping internal discussion in the appropriate location.

• Source: ChatGPT Space: Pages, files, and connected sources
• Source: Collaborate in Space: roles and inherited access

06

Confirm updates before calling the brief current

A shared Page does not establish an automatic updating process. OpenAI's current agent guide says Keep Updated is unavailable at launch. For recurring work, request it in chat, inspect the saved schedule, and verify an actual run and Page update. Writing a cadence into the brief alone does not schedule the work.

A first studio review can be manual: compare the Page with the latest client notes, approve changes, and record the review date. Measure whether teammates can identify the current requirements and outstanding decisions faster than they could before. Resolve conflicting source revisions before adding more automation.

• Source: Work with agents in Space

07

Reuse the structure in your next brief

After the pilot, keep the headings and review method that helped the team. Add a short handoff note explaining which sources govern the brief and who approves revisions. A repeatable structure is most valuable when new team members can understand it without reading every earlier conversation.

The related Project Lessons Learned Brief is an archiPrompt Template bundle for closeout interviews and action registers. The Precedent Research Brief is a Prompt system for comparative research with citations and project-transfer notes. Their output structures can inform Page content; assess each listing's setup and compatibility separately.