ChatGPT Space for SRE: keep an incident handoff current

An incident handoff has a difficult job: it must shorten the story without changing it. The incoming engineer needs to know which symptoms remain, what the team has already tried, and why the next check matters. A summary that turns an uncertain diagnosis into a settled explanation can send the next shift back through work the previous one already did.

ChatGPT Space offers a place to develop that shared account. It brings editable pages, files and collaboration into ChatGPT, so people can revise the same document alongside the assistant. The interesting SRE use comes after the first summary: a responder adds evidence, another questions a conclusion, and the handoff changes without becoming another disconnected answer in a chat. OpenAI calls the product ChatGPT Space; individual spaces group pages around a topic or team. The official overview describes that relationship.

Consider a hypothetical incident involving a queue-backed order service. Alerts report rising processing delays after a deployment. The team rolls back, but the queue continues growing. One engineer investigates worker capacity while another checks whether a dependency is slowing jobs. The incoming shift will need both lines of inquiry, including the fact that the rollback has happened without yet establishing recovery. All incident details below are synthetic; this is a proposed workflow using documented features, not a tested deployment or a report of a real outage.

Give the incident a page people can return to

Start with a page titled “Order processing delay: investigation and handoff.” Add the alert export, deployment timeline and relevant runbook reference, with the time window each covers. Keep the current account near the top; longer evidence notes can sit below it or in child pages. This gives the incoming engineer a short route into the investigation without discarding its supporting material.

Space supports creating a page from notes, files or an existing conversation. Related pages can sit inside a space, although one incident does not need a large hierarchy. In an account with Space enabled, choose New page, add the material and open ChatGPT alongside it. The getting-started guide explains the controls. Connected apps can provide additional sources, but access depends on the account and workspace settings; the initial exercise can use approved, sanitized files instead.

In our example, the alert export establishes that processing delays increased. The deployment timeline establishes when the rollout and rollback occurred. Neither establishes why the queue is still growing. Keeping that unresolved relationship visible gives the next engineer a useful question rather than an explanation they must first unpick.

A suitable initial request is: “Draft a handoff from the material on this page. Separate observed symptoms, completed actions, working hypotheses and unanswered questions. Keep the source references and their time windows. The rollback is complete, but recovery has not been established. Do not invent an investigation result where none is supplied.”

The distinction between a completed action and a verified result is what makes the request useful. A tidy timeline can accurately report that the team rolled back while still leaving the recovery question open. The same distinction belongs in the post-incident review, where readers need to understand both what people decided and what the evidence available at the time supported.

Revise the claim when new evidence arrives

Suppose the dependency investigator adds a finding at 09:30: response times for the payment dependency remained within their normal range during the sampled 09:10–09:25 interval. That narrows one investigation, but it does not explain the remaining backlog or establish that every dependency is healthy. The service, interval and observation all need to survive the revision.

An engineer can add that finding directly, then ask ChatGPT to update the affected paragraph while leaving the rest of the record alone. Pages support direct editing, selected-text changes and comments, along with child pages and reusable prompt blocks. These features make a narrow correction possible without requesting an entirely new incident report each time. See working with pages for the editing mechanisms.

The revised handoff should now explain what the payment check covered and why worker capacity remains under investigation. If the assistant writes “Dependencies ruled out,” the correction is specific: the supplied observation covers one dependency and one interval. Preserving the observation’s scope lets the next engineer decide whether another dependency check would add anything.

A new finding changes part of the handoff

Read diagram description

A responder supplies the observation that payment response times were normal during 09:10–09:25. ChatGPT proposes a scoped page revision. An engineer checks the source and accepts or corrects the wording. The handoff records the completed rollback, the limited payment check and the unresolved worker-capacity investigation. A separate current service check is required before recovery can be declared.

When the shift changes, the worker-capacity investigation can remain an open task assigned to the receiving engineer, with its next check described beside it. Later, if that investigation reveals a runbook gap, the page can carry a proposed follow-up and a link to the maintained procedure. Until the runbook owner accepts and incorporates the change, the suggestion should not read as the procedure already in force. The SRE runbook guide explains what the responder needs from that authoritative procedure.

This collaboration also has a cost. Someone must review generated changes against their sources and keep the current account coherent. If responders maintain the same narrative in an incident platform and Space, the extra copy may create more reconciliation work than it saves. Decide which record owns the incident’s current status, and use the other as supporting material rather than allowing both to appear authoritative.

Sharing the page also shares its contents

A handoff helps only if the incoming engineer can open it. Space offers view, comment and edit access where available, with permissions inherited from a shared space or parent page. Sharing the top-level space can therefore expose more material than sharing the incident page alone. Removing a direct invitation does not remove access someone still inherits elsewhere. The collaboration guide explains these distinctions and the account-dependent sharing controls.

The evidence needs a separate check. Linked source files retain their original permissions, so a colleague may be able to read the handoff but not open its supporting export. Conversely, copying private source content into the page makes it visible to that page’s readers. Uploads follow the page’s permissions. Sharing does not expose private chats or saved memory, but private details included in the document become part of the shared material. These behaviors are documented in the Space administration guide.

For the trial, use synthetic or approved, sanitized exports and invite only the intended readers. Have the incoming engineer open both the handoff and a source it cites. This checks whether the document can perform its actual job, rather than merely whether its author can see everything.

A shared page does not keep itself current

ChatGPT or a dot can help revise a page through the adjacent conversation, an inline request or a comment mention, depending on access. A comment addressed to a person and a request addressed to an agent have different consequences, so check the intended recipient. The agents guide describes these routes and recommends reviewing the resulting changes.

None of that establishes a continuous feed from the order service. The documented workflow can use supplied files and connected sources; it does not establish that this incident page is subscribed to alerts or observing the current queue. A new note at 09:30 can still describe evidence whose collection ended at 09:25. The edit time and observation time answer different questions.

OpenAI also states that Keep Updated is unavailable at launch. Recurring work must be set up separately in chat, then checked through its saved schedule and an actual run. Writing “refresh every five minutes” into a page is not evidence that anything has been scheduled. This limitation is stated in the same agents guide.

In the hypothetical handoff, label the evidence interval and the latest reviewed update. When the incoming responder needs to decide whether recovery has occurred now, they must inspect current service evidence. The page explains the investigation so far; a polished paragraph cannot supply a missing observation. That is the point at which the responder moves from reviewing the shared account to checking the live service.

Choose it for the shared work it makes easier

The surrounding ChatGPT names describe different jobs. A Project groups related chats, files, instructions and sources so separate conversations can work from shared context. A Page is the editable document, and a space groups related pages and collaborators. Sites creates hosted websites and applications, a different commitment from maintaining an incident handoff. The official Projects and Sites guides explain those roles. A team can need more than one, but the document workflow alone does not require building an application.

For an SRE team, a useful trial is small: take a sanitized historical incident, prepare its handoff in Space, and ask an engineer who did not write it to identify the remaining uncertainty and the next useful check. Observe where they must leave the page, which references they cannot open and which generated statements require correction. Include that review effort when deciding whether the workflow saves work.

If the page makes the transition easier, it has earned a place in the response process. If it mainly duplicates a well-maintained incident record, another document may be the wrong addition. The useful outcome is that the next engineer can continue the investigation with less reconstruction while still understanding exactly what the evidence has and has not established.