Run Your Workday by Voice With ChatGPT (Chat, Work & Codex)

Open the ChatGPT desktop app and create a private project for this workflow. In the demo, the project is called University Demo. Keep the project as the working space for drafts, prompts, and review history.

Start a new voice chat before you send your first message. This gives you a live conversation where you can interrupt, ask follow-ups, and change direction while work continues. You can also keep talking while ChatGPT works in the background and come back to check progress.

Pro tip: Start a new voice chat before sending the first message. If you begin in another mode, the microphone works as dictation instead of a live voice conversation.

Think of the workflow as three separate jobs:

• Source: the approved folder, document, analytics view, or meeting note ChatGPT may read.
• Storage: the shared Google Drive folder where the approved deliverable will live.
• Handoff: the test Slack, Teams, or Gmail destination where a teammate will receive the link.

Use the + control to add a missing connection, then check what each connection can actually do. A source that can be read is not automatically approved for writing files or sending messages.

For a safe first run, use fictional or demo data and a test destination. Tell ChatGPT the exact scope before it starts:

Work in the private project "University Demo."

Read only these approved demo sources:
- the connected Google Drive folder "Demo Guide Context"
- the fictional meeting note "Weekly Content Review - demo notes"

First, list the sources you can access and summarize the workday context in three bullets. If either source is missing, stop and ask me. Do not search other files, chats, accounts, or connected services.

Do not create files, send messages, save to Drive, or change anything external yet.

Once the scope is correct, scaffold the project for repeatable work:

Scaffold this private project for a simple draft-to-review-to-final reporting flow.

Keep working drafts in Markdown, make the review gate explicit, and document the approved sources, the shared Drive destination, and the draft-only messaging rule. Do not create files, save to Drive, or send messages until I approve the next step.

Use Voice to ask for a short plan from the approved context. The goal is to make the next deliverable obvious before you ask ChatGPT to create anything.

Using only the approved demo sources, give me a concise plan for today.

Return:
1. the three highest-priority actions in order
2. the one decision that needs human approval
3. the first private-project deliverable to make for [TEAMMATE_NAME]
4. the external action you will wait to take until I approve it

Keep this to the demo context. Do not use traffic, newsletter conversion, revenue, customer, or other sensitive metrics.

If the plan points to a report, confirm its purpose, audience, source, required fields, and review gate in one sentence. That small pause keeps the tool from turning an ambiguous request into an external action.

Now ask ChatGPT to create the working file in the private project. Markdown is a good intermediate format because you can scan the structure and ask for precise edits before creating a polished PDF.

Create `top-guides-video-engagement-brief.md` in this private project for [TEAMMATE_NAME].

The file must contain only a Markdown title and one table with exactly these columns:
- Guide title
- Video start rate
- Video completion rate

Use only the approved fictional demo values from the sources. If a value is missing, use `[demo value]` instead of guessing.

Do not include traffic, newsletter conversion, revenue, audience, customer, or any other metric. Do not save to Google Drive or send a message yet.

The Markdown file is the automatic output of this request. You do not need to ask ChatGPT to create a separate “draft artifact” after it finishes. Read the file, then refine it by voice:

Read `top-guides-video-engagement-brief.md` and tighten it for a teammate who needs a fast review.

Keep only the title and the exact three table columns: guide title, video start rate, and video completion rate. Preserve only approved fictional demo values, remove every other field or explanation, and show me the final Markdown for approval.

Do not make external changes.

Approve the exact Markdown before you export it. If the source data is incomplete, keep [demo value] rather than letting the tool fill the gap with a guess.

Pro tip: Refine the Markdown before making the PDF. It is easier to catch extra fields or a wrong table structure in plain text than in a finished document.

When the Markdown is correct, approve the external save explicitly. Ask ChatGPT to create one PDF and save an exact copy to the shared Drive folder:

The final brief is approved.

Convert `top-guides-video-engagement-brief.md` to one PDF and save an exact copy to `[DEMO_SHARED_DRIVE_FOLDER]` in the connected shared Google Drive.

Create no other files, overwrite nothing, and return the Drive link when the save is complete. Keep the private project as the working space and the Drive copy as the durable shared record.

Use the returned link to prepare the teammate handoff. Keep the message short and free of metric values:

Using only the approved demo meeting-note context, prepare one concise message to [TEAMMATE_NAME] for [DEMO_SLACK_CHANNEL] or [DEMO_GMAIL_THREAD].

Include:
- the Google Drive link to the approved brief
- that the brief contains the three agreed fields only
- the next review choice this helps [TEAMMATE_NAME] make

Do not include any metric values and do not contact anyone else. Show me the exact message for approval before it is sent.

Review the message in Slack, Teams, or Gmail and send it yourself. The durable pattern is simple: the private project holds the work in progress, Drive holds the approved record, and the message carries the record to the person who needs to act on it.

Pro tip: Make messaging draft-only by default. Review the populated message in the destination app and click Send yourself so a mistaken thread or extra detail does not go to the team.