There is a technique I call the "living brief", and ChatGPT Pages is the first tool that makes it practical. You put the rules for maintaining a document inside the document itself, so ChatGPT updates it the same way every time instead of rewriting it from scratch. Most people who open Pages this week will use it as a fancier chat export. That misses the point.
OpenAI launched Pages at DevDay on 29 September 2026, alongside ChatGPT Space. A page is a shared document that you, your teammates and ChatGPT can all edit. The interesting part is not the editor. It is the set of blocks that let you store instructions, reusable prompts and source references right on the page. This guide shows you how to combine them into a brief that stays accurate for weeks, not hours.
What are ChatGPT Pages?
ChatGPT Pages are editable documents inside ChatGPT Space that people and ChatGPT work on together. You can write, research, add tables and charts, generate images and comment on a page. They launched on 29 September 2026 for Pro, Business and Enterprise plans, on the desktop app and the web.
According to OpenAI's DevDay 2026 recap, anything you can do in a chat you can also do on a page. You create a page in a conversation, then invite your team to edit and leave feedback. Several people can edit at once, and each of them works with their own ChatGPT alongside the page.
Pages live in Space, the new team area that replaces the old Library. Projects stay separate. On mobile you can currently find, read and share pages, but creating and editing is desktop and web only for now. Collaborative slides are promised "in the coming weeks", and they will sit in the same Space.
One practical note for Hong Kong readers: OpenAI still does not list Hong Kong as a supported region for direct ChatGPT sign-ups, so check with your IT team whether your company workspace actually has Pages switched on before you plan a workflow around it.
Which Pages features matter most for a team brief?
Four block types do most of the work. Agent Instructions tell ChatGPT how to maintain the page. Prompt blocks store requests readers can run with one click. File, page and chat mentions link sources without copying them. Ask for change edits only the text you select, so the rest of the page stays untouched.
You open all of these by typing / on a page. OpenAI's Pages documentation lists the full insert menu. These are the ones worth learning first:
- Agent Instructions: a block of guidance for agents working on the page. This is where your maintenance rules go.
- Prompt: a saved request that any reader can run as a chat with "Chat about this". Perfect for "what changed?" or "what is still open?"
- Files, Pages and Chats (via @): references to source material that keep the evidence one click away without pasting it into the page.
- Generate: drafts new content in place. OpenAI's own example tells ChatGPT to leave unconfirmed dates as open questions, which is a good habit to copy.
- Visualize: builds a small interactive calculator or diagram, such as a budget estimator readers can adjust.
- Subpages: keep the overview short and push research or meeting notes one level down.
The habit that changes everything is selecting text and using Ask for change instead of asking for a whole-page rewrite. Whole-page rewrites are where AI documents quietly lose details.
How do you build a living brief in ChatGPT Pages?
Build it in four layers. Start with an Agent Instructions block that sets the maintenance rules. Add a short status section and a decision table with owners. Link every source with an @ mention. Finish with two or three Prompt blocks readers can run. The rules travel with the page, so every edit follows them.
Step 1: Create the page from the conversation that already has the context. If you have been planning a campaign or a project in a chat, ask ChatGPT to turn it into a page rather than starting blank. Use this prompt:
Try this prompt (create the page):
Create a page called "[Project name] brief" from this conversation.
Structure it as: 1) Status in three bullet points, 2) Decisions table with columns Decision, Owner, Date confirmed, Source, 3) Open questions, 4) Change log.
Only include facts stated in this conversation or in files I attached. If a date, budget or owner was discussed but not confirmed, put it under Open questions and mark it [OPEN].
Keep the whole page under 400 words.
Step 2: Add the maintenance rules as an Agent Instructions block. Type /, choose Agent Instructions, and paste the rules below. This is the core of the technique. Without it, every future "update this page" request is a fresh interpretation.
Try this Agent Instructions block:
When you update this page:
1. Change only the sections affected by the new information. Never rewrite the whole page.
2. Every new fact needs a source: an @ mention of a file, chat or page, or the name of the person who confirmed it.
3. Anything unconfirmed goes under Open questions with [OPEN]. Do not guess dates, prices or owners.
4. When an [OPEN] item is confirmed, move it into the Decisions table and delete the [OPEN] line.
5. Add one line to the Change log for every update: date, what changed, source.
6. Keep Status to three bullet points. If something new matters more, replace the least important bullet.
Step 3: Mention your sources instead of pasting them. Type @ and pick the brief from the client, the kickoff chat or the budget sheet. Mentions keep the source close to the claim, and they make rule 2 above easy for ChatGPT to follow.
Step 4: Add Prompt blocks for your readers. Your manager does not want to read the whole page. Give them a button. Two that work well: "Summarise what changed on this page since last Monday, using the Change log only" and "List every [OPEN] item, who should answer it, and what is blocked until they do."
What does a living brief look like in a real workflow?
A typical example is a marketer running a product launch with an agency and two internal teams. The page holds status, decisions and open questions. After each meeting or email, one person pastes the new information and asks ChatGPT to update the page under its rules. Everyone reads the same current version.
Here is how a week runs for that marketer, call her Mandy. On Monday she pastes the agency's revised timeline into the chat beside the page and asks for an update. ChatGPT moves the confirmed shoot date out of Open questions, adds the agency email as the source, and writes one Change log line. Nothing else on the page moves.
On Wednesday her boss opens the page on his laptop, runs the "what is still open?" Prompt block, and sees three [OPEN] items with suggested owners. He answers one in a comment and tags ChatGPT. On Friday Mandy uses Ask for change on the Status section only: "Rewrite these three bullets for the sales team, keep the dates and numbers exactly as written."
The weekly refresh prompt she reuses is simple:
Try this prompt (weekly refresh):
Update this page using the Agent Instructions on it and the new information below.
Before you change anything, list the edits you plan to make and the source for each one. Wait for me to reply "go" before applying them.
New information:
[paste meeting notes, emails or the updated file name]
The "list first, then wait" step costs ten seconds and catches most mistakes before they reach the shared page. If you have read our guide to output contracts for consistent AI results, this is the same idea applied to a document instead of a single answer.
What are the common mistakes and limits with ChatGPT Pages?
The biggest risks are sharing and drift. Anything ChatGPT writes on a shared page is visible to everyone with access, including details it pulls from your personal memory. Whole-page rewrites silently drop facts. Pages also inherit access from their Space or parent page, so a private-looking subpage may not be private.
- Memory leaks onto the page. The Paluch DevDay review points out that personal details ChatGPT remembers about you can end up in shared content. Add "Do not use my personal memory on this page" to the Agent Instructions if that matters.
- Prompt injection. OpenAI warns that pages, files and tool results can contain hidden instructions. Be careful when you mention files from outside your company, such as supplier documents.
- Inherited access. A subpage takes the access of its parent or Space. Check who can see a page before you paste salary numbers or client contracts into it.
- Blocking sharing is not revoking it. If an admin turns sharing off later, existing access stays in place. Decide the sharing rules on day one.
- Mobile is read-only for now. Your team can read and share on phones, but edits and Prompt blocks you create need the desktop app or the web.
- Plan limits. Pages need Pro, Business or Enterprise. Plus users will not see it, so a mixed team may not all be able to edit.
Pages is also brand new. The features above reflect OpenAI's documentation in early October 2026, and details like automations and slides are still rolling out. Treat this as version one and keep a copy of anything critical elsewhere.
How can you try the living brief technique in 20 minutes?
Pick one real project you are already tracking in chat or email. Create a page from that conversation, add the six-line Agent Instructions block, mention two sources, and add one reader Prompt block. Then feed it one new update and check that only the affected section changed.
Here is the 20-minute drill:
- Minutes 0 to 5: open the chat with the most context about your project and run the "create the page" prompt above.
- Minutes 5 to 10: add the Agent Instructions block and @ mention the two most important source files or chats.
- Minutes 10 to 15: add one Prompt block for your manager, such as "List every [OPEN] item and who should answer it."
- Minutes 15 to 20: paste one new email or note and run the weekly refresh prompt. Compare the before and after. If anything outside the affected section changed, tighten rule 1.
If your team also works in Claude, the same rules-on-the-document approach works in Claude Docs inside the merged Cowork interface. The tool changes; the technique does not.
The real shift with Pages is that the document finally remembers how it should be maintained. Write the rules once, let ChatGPT follow them, and spend your time on the decisions instead of the formatting. We understand AI. We understand you better. With UD by your side, AI doesn't feel cold.
Reviewed by the UD AI team. Feature details reflect ChatGPT Pages as documented by OpenAI in early October 2026. Sources: OpenAI: DevDay 2026 recap, ChatGPT Learn: Work with pages, Szymon Paluch: ChatGPT Space, Pages and plugins.
Turn your AI documents into a real team workflow
A living brief is one piece of a bigger system. UD's AI Employee Hub shows the ready-made AI skills and roles you can plug into your team, and if you want help connecting them to the way your team works, we'll walk you through every step, from tool setup to workflow design and rollout.
