ChatGPT Space lets people and AI agents co-edit the same project page. A PM should decide who owns that record first

ChatGPT Space is a shared workspace where a team, ChatGPT, and OpenAI's agents edit the same documents, called Pages. For a GC's project team, the value is one place for meeting notes, open-item lists, and look-aheads. The risk is that an agent's edits become part of a record nobody formally approved.

What did OpenAI launch?

At its DevDay on September 29, 2026, OpenAI introduced Space, per VentureBeat and other trade coverage. Reported details:

• Pages: interactive documents that can hold charts, images, checklists, and dashboards.
• Shared editing: several people can edit one Page at once, each using their own ChatGPT against it.
• Agents as participants: Codex and OpenAI's always-on "dot" agents can contribute alongside people.
• Integrations: automated meeting summaries and native Slack and Microsoft Teams connections.
• Availability: Pro, Business, and Enterprise plans on desktop and web. Mobile can read and share but not yet create or edit.

We found no pricing for Space beyond the plan tiers, and no construction-specific features. Everything below is our read of how a project team could use it, not something OpenAI claims.

Where would a GC project team actually use it?

Three candidates, from lowest to highest risk:

1. Weekly OAC and subcontractor meeting notes. A Page that an agent drafts from the meeting summary and the PM edits is a reasonable starting point.
2. Three-week look-ahead and open-items list. Super, PE, and PM can edit the same Page, and an agent can flag items with no owner or date.
3. Draft scope letters and RFI responses. Useful for drafting. Risky if the Page is what gets sent.

We previously covered what always-on agents mean for PM follow-up. Space is where those agents would write their output.

What's the catch for a PM?

Authorship gets blurry. If an agent and three people edit one Page, the question "who wrote this and who approved it" needs an answer before a dispute, not after. Confirm what version history and attribution Space keeps. The launch coverage we read does not say.

Drafts can drift into the record. A Page with a clean look can pass for an official document. Label draft Pages as drafts, and keep RFIs, submittals, and change orders in the platform your contract names.

Access is per-team, not per-project-party. Owners, architects, and subs each have their own tenant and contract terms. Don't put another party's pricing or backcharge detail on a Page without checking who can see it.

Data terms matter. Before project files go in, read the plan's data-retention and training terms, and check them against your owner's confidentiality clause.

Should a mid-size GC adopt it now?

Run a contained pilot. Pick one job, use Space only for the weekly meeting notes and the look-ahead, and keep every contractual document where it lives today. After four weeks, check three things: did an agent change anything a person didn't catch, could you reconstruct who changed what, and did the team actually stop re-typing notes.

If the answer to the first is yes or the second is no, stop. If Space doesn't remove duplicate entry, it's one more place to look.

Construction AI Brief publishes three times a week. Subscribe at constructionaibrief.com and forward this to the PM who owns your meeting minutes.