Article
September 9, 2026
Before the first meeting: A morning brief for government chiefs of staff
# Government
# Productivity
How to use scheduled tasks in ChatGPT to build a repeatable briefing routine—with staff review built in.
Laura Keenan
A chief of staff’s morning can begin with three versions of the agenda, an overnight email that changes the conversation, and a decision the leader needs to make before the first meeting.
The preparation is familiar: gather the context, reconcile the updates, and identify what deserves the leader’s attention. Repeating that work every morning makes it a useful place to try scheduled tasks in ChatGPT.
OpenAI’s scheduled-tasks walkthrough demonstrates preparing meeting briefs from connected calendar events and emails, refining the result, and scheduling it to run again. For a government chief of staff, the application is straightforward: a first draft of the morning packet, ready for staff review.
Start with one leader and one useful brief
Choose a bounded pilot: one calendar, a defined set of related correspondence, and a brief your leader can scan quickly. Decide what a useful result must contain before scheduling anything.
A practical structure is:
Today’s priorities: The issues most likely to need the leader’s attention.
Meeting preparation: Purpose, relevant context, and any documented decision requested.
Open commitments: Follow-ups, owners, and deadlines supported by the records.
Gaps to resolve: Missing information or conflicting updates that staff should check.
Use an agency-approved environment and only information permitted there. Confirm that scheduled tasks and the required connections are available in your workspace; this example does not establish availability in any particular government deployment. You can practice the drafting step with fictional materials if live connections are unavailable.
Prompt 1: Build the first morning brief
Replace the bracketed text with your approved sources and local time zone.
Prepare a draft morning brief for the chief of staff supporting [office or leader]. Use [approved calendar] for today’s meetings in [time zone] and [approved email source] for relevant correspondence from the past seven days.Begin with up to three priorities, explaining why each needs attention today. Then summarize each meeting: time, purpose, relevant background, documented decisions requested, and open commitments with their recorded owners and deadlines.Link factual statements to the supporting events or messages. Distinguish documented facts from your inferences. Do not infer attendance from an invitation or invent a position, owner, deadline, or decision. Flag conflicting records and missing information. Identify any source you could not access and include the preparation timestamp.Keep the main brief under 600 words. Return it for my review without sending messages or changing records.
Read the first result against the original sources. Does it capture the decision behind the meeting? Does it distinguish a proposed deadline from an agreed one? A polished summary still needs those checks.
Prompt 2: Make the brief useful for decisions
Revise this brief for a leader with five minutes to prepare. Put documented decisions needed today first, followed by unresolved dependencies and significant changes. Move routine background below the main brief.For each decision, state what is being asked, the documented deadline, and what information is still missing. If the sources do not establish that a decision is needed, say so. Preserve source links and uncertainty. List up to three questions I should resolve with staff before sharing the packet.
The review step: verify the sources, resolve gaps, and add the judgment only your office can provide.
Prompt 3: Schedule the version you have reviewed
Once the format is useful, add the schedule in the same conversation. The walkthrough explains how to inspect results, edit instructions, or pause a task in the Scheduled tab. See the setup steps .
Run this morning-brief task every weekday at 7:00 a.m. America/New_York. Use that day’s calendar and the latest relevant correspondence from the approved sources specified above. Keep the structure, word limit, source links, and review boundaries we established.Include the preparation timestamp and clearly identify any unavailable sources or incomplete coverage. If there are no meetings, say so. Return each draft for my review without sending messages or changing records.
Check the next scheduled run. For tasks that depend on local files or locally saved skills, OpenAI’s walkthrough instructs users to keep the computer on and the desktop app running.
When the agenda changes, ask what changed
A morning brief is a snapshot. Before a consequential meeting, request a fresh check:
Compare the morning brief above with the latest accessible records for [meeting]. Show only changes to the time, agenda, documented decisions, and open commitments. Link each change to its source and distinguish confirmed changes from proposals. Flag unresolved conflicts. Do not update the calendar or contact participants.
Keep the chief of staff in the review loop
The value of this routine is having more preparation in hand when the day begins. Staff still need to judge what matters, check sensitive context, and decide what reaches the leader.
Try it for one week. Track preparation time, corrections required, and whether the brief surfaces the right decisions. Refine the instructions based on those results before expanding to another recurring product.
Start with tomorrow’s first meeting. Build a brief worth reading. Then make that preparation repeatable.
Images are AI-generated editorial illustrations, not product screenshots or depictions of an actual government office.
Dive in
Related
Resource
Unlocking ChatGPT for Government: A Prompt-Pack IT Staff
By David Sperry • Jul 19th, 2025 • Views 249
Video
Getting Started with ChatGPT Enterprise for Government Employees
By David Sperry • Jul 19th, 2025 • Views 155
Resource
Unlocking ChatGPT for Government: A Prompt-Pack for Analysts & Program Staff
By David Sperry • Jul 19th, 2025 • Views 260
Resource
Unlocking ChatGPT for Government: A Prompt-Pack IT Staff
By David Sperry • Jul 19th, 2025 • Views 249
Resource
Unlocking ChatGPT for Government: A Prompt-Pack for Analysts & Program Staff
By David Sperry • Jul 19th, 2025 • Views 260
Video
Getting Started with ChatGPT Enterprise for Government Employees
By David Sperry • Jul 19th, 2025 • Views 155