Let ChatGPT help you keep track of work

Outcome

See your commitments, upcoming reviews, unanswered requests, and project risks in one place. A Chief of Staff workflow can help you prepare a brief from sources you approve and see which decisions need your attention. When specifically authorized, it may prepare one bounded internal next step.

The system is useful because it reduces context switching and makes obligations explicit. It does not impersonate you, set priorities without guidance, or treat every unread item as important. You retain authority over commitments, communication, and tradeoffs.

This is a practical operating pattern, not a claim that every account includes a ready-made Chief of Staff product. Chapter 6 explains four distinct roles: Detect, Incubate, Collaborate, and Reflect.

When to use it

Use a personal Chief of Staff loop when work spans multiple projects, meetings generate follow-ups, messages contain obligations, or important tasks are being crowded out by reactive work.

Start with a narrow daily or weekly brief. Add meeting preparation, follow-up review, and checks for unanswered requests only after you trust the sources and classifications. Avoid broad monitoring if the input systems contain highly sensitive material or if organizational policy does not permit access.

For a single quiet project, a simple task registry may be enough.

Operating pattern

Define the loop around five questions:

1. What changed in the approved sources?
2. What requires my decision, response, or review?
3. What commitments have I made, and by when?
4. Which upcoming moments need preparation?
5. What one bounded internal action can reduce risk now?

Create one source map and one bounded cadence for the Chief of Staff workflow. Keep each workstream's files and execution in its existing project. For each item, preserve the source link, owner, date, confidence, and reason it matters. Distinguish commitments from suggestions and explicit deadlines from inferred urgency.

Produce a ranked brief with three lanes: act, review, and watch. Allow one reversible internal preparation step only when the action is explicitly in scope, for example drafting an agenda or assembling approved source material. End with separate counts or descriptions for work detected, work actually advanced, decisions needed, blockers, and no-change findings.

One weekly home-base task and one weekday controller are a useful configuration when scheduling is supported and the user approves it. They are not automatic product entitlements. Keep requests open until the actual owner or source confirms completion.

Regularly reflect on false positives, missed items, and abandoned categories.

Copyable implementation

# Personal Chief of Staff scan

Approved sources: [calendar, project registry, selected messages, notes]
Existing workstream owners: [the approved project or task registry]
Time window: [current and look-ahead periods]
Priority rules: [commitments, decisions, deadlines, strategic importance]
Excluded content: [private or irrelevant categories]

Return:
1. ACT — explicit commitments or time-bound decisions
2. REVIEW — drafts, risks, and ambiguous items needing judgment
3. WATCH — upcoming items with no current action
4. NO CHANGE — sources checked with nothing material found

For every item include source, owner, date, confidence, and next action.
Report detected items separately from actions actually completed.
Advance at most one explicitly authorized, reversible internal step.
Do not send, schedule, publish, accept, decline, purchase, change access,
or delete anything.

Use a stable format so each run can be compared with the last.

Example

For example, a design leader has three upcoming reviews, a project registry, and a selected set of messages. The morning scan finds one explicit promise to share a draft by Wednesday, one meeting whose pre-read has changed, and six unread messages with no request.

The brief places the promised draft in ACT, the changed pre-read in REVIEW, and ignores unread count as a priority signal. ChatGPT Work assembles the approved sources for the draft and creates a private outline. It does not send the document or modify the calendar.

The next scan reports that the draft is awaiting review and that no new commitments were found.

Approval boundary

The loop may inspect only configured sources and prepare internal artifacts within its permission scope. It must not infer consent from urgency, calendar proximity, or a previous similar action.

Require explicit approval before sending or replying, scheduling or rescheduling, accepting or declining invitations, publishing, changing project ownership, granting access, purchasing, or deleting. Sensitive sources may require additional policy and consent checks.

Connecting accounts, installing integrations, configuring permissions, and activating recurring scans are separate administrative actions. A copied prompt alone does not establish them.

Validation

Review a sample of included and excluded items:

• Each item traces to a current source.
• Commitments are explicit or clearly labeled as inferred.
• Deadlines preserve timezone and source wording.
• Rankings follow the stated rules rather than unread volume.
• The brief avoids duplicating already completed asks.
• Existing work stays open until completion is independently verified.
• The internal action is bounded, reversible, and useful.
• Detected, blocked, review-ready, and actually advanced work stay distinct.
• No-change runs name the sources and window checked.
• Outbound and consequential actions remain pending approval.

Track false positives and missed commitments over several cycles before expanding the scope.

Failure modes

The system can become an anxiety engine if it converts every message into work. Unread does not mean urgent, mention does not mean ownership, and a meeting does not always require preparation.

Other failures include scanning everything without consent, inventing deadlines, repeatedly surfacing stale items, drafting duplicate replies after an answer already exists, and silently changing priorities. A beautiful daily brief can still be wrong if sources are stale.

Avoid “helpful” unbounded follow-ups. When nothing material changed, return a no-change receipt. When priority rules conflict, ask for a decision rather than resolving organizational tradeoffs from weak signals.