Webinar

2026年8月12日

ChatGPT 102: Webinar Resource Guide

# Workplace & Business

# ChatGPT

# Use Cases

# Work

Follow along with our webinar ChatGPT 102: Scaling your best work

Diana Stegall

一部のコンテンツは元の言語で表示される場合があります。

翻訳

ChatGPT 102: Webinar Resource Guide

Follow along with our webinar ChatGPT 102: Scale Your Best Work

Use this guide to remember the core ideas from the webinar, recreate the weekly project update demo, and turn one useful result into a workflow you can repeat.

This webinar builds on ChatGPT 101. If you are new to Chat and Work, begin with the ChatGPT 101 webinar resource guide .

The webinar is designed for people using ChatGPT Enterprise. Your screen and available features may vary based on your plan, role, workspace settings, and ChatGPT surface. Your organization may also control which Plugins, apps, skills, and scheduled tasks are available.

Practice in a ChatGPT workspace approved by your organization. Before connecting a tool or adding company information, make sure you are in the correct workspace and follow your organization’s policies for confidential, personal, and proprietary information.

Quick recap: Choose Chat or Work based on the job

Use	When you need
Chat	A quick answer, help with one part of a task, or a conversation that helps you think something through
Work	ChatGPT to gather context, complete several steps, and create a substantial result you can review

The weekly project update belongs in Work. ChatGPT needs to gather information from several places, decide what matters, flag inconsistencies, and create a complete document.

Choose a task worth repeating

Not every task needs to become a workflow. Good candidates usually:

Happen regularly

Take meaningful time

Follow a process that stays fairly consistent

Produce a result a person can clearly review

The source information can change each time. The job, rules, and review criteria should stay stable enough to reuse.

The workflow to remember

Create it once. Make it better. Save what worked. Test it with fresh information. Then schedule it.

Stage	What you do
Create	Complete the real task with the right sources, tools, constraints, and output format.
Improve	Review the first draft and add the rules your team expects.
Save	Turn the tested process into a reusable skill.
Test	Run the skill in a new conversation with fresh information.
Schedule	Automate the start only after the workflow passes the fresh-input test.

Three checkpoints

Use these checks at every stage:

Checkpoint	Ask yourself
Input	Am I allowed to use these files, messages, and connected tools here?
Evidence	Can I trace important claims to the source files or messages and see where sources disagree?
Action	Will the right person review the result before it is shared or used?

Putting work on a schedule changes when it starts. It does not change who is responsible for reviewing the result.

Sample files

Download the ChatGPT 102 sample files .

The pack contains:

Cavenridge Client Portal - Project Plan.docx

Cavenridge Weekly Project Update Template.docx

Cavenridge Client Portal - Milestone Tracker - Week 1.xlsx

Cavenridge Client Portal - Milestone Tracker - Week 2.xlsx

Cavenridge Client Portal - Slack Seed Messages.md

The company, project, and data are fictional. Use the sample materials for practice, not production work.

The July 31 and August 3 dates belong to the fictional project scenario. Slack records the real time when you post a message and does not let you backdate it. For on-demand practice, post the baseline messages first, record the actual cutoff date and time, and complete the first run. Post the fresh test messages later, after the first run.

Before you begin

The webinar uses:

Google Drive to retrieve the project plan, tracker, and company template

Spreadsheets to read the newest dated tab in the tracker

Slack to retrieve current project context and deliver a private summary

Documents to create the weekly update as a Google Doc

Skills to save the tested workflow

Scheduled to run the workflow every week

The Default templates Plugin is optional. It can provide a general-purpose starting point when you do not already have an approved company template.

Your workspace determines which Plugins and actions you can use. Connecting a tool does not give ChatGPT unlimited access; it works within the permissions available to you. If your organization uses another approved file-storage or messaging system, use the equivalent tools available in your workspace.

To prepare the sample environment:

Create a Google Drive folder named Cavenridge Client Portal Launch and a subfolder named Weekly Updates.

Add the project plan, weekly update template, and Week 1 milestone workbook to the main folder.

Rename the tracker tab Week 1 - Jul 31. Keep only this tab in the tracker for the first run.

Create or reuse a private demo Slack channel named client-portal-launch. Add the baseline messages from the seed file in order. Treat each bolded fictional name and role plus the paragraph beneath it as one Slack message, and include the name and role in the message text when posting from a single demo account. Wait until every message is visible, then record the actual posting cutoff for the first prompt.

Choose a harmless private destination for the notification, such as your own Slack direct messages. Do not use a real team channel for practice.

Open Plugins, connect and authorize the required tools, and confirm that ChatGPT can reach the demo folder and private channel. Authenticate if prompted.

Demo 1: Create and improve a weekly project update in Work

What to remember

For a larger assignment, tell Work what result you need, where to find the information, which format to follow, where to put the finished artifact, and what it must not do. You do not need to prescribe every internal step.

Recreate it

Confirm that Google Drive, Spreadsheets, Slack, and Documents are available, enabled, connected, and authorized in your workspace.

Open a new Work conversation and paste:

On-demand date note: Keep the fictional week-ending date and tracker-tab name below. Replace only the two July 31 Slack cutoff dates in the second paragraph with the actual baseline posting cutoff you recorded.

Create the weekly project update for the Cavenridge Client Portal Launch for the week ending July 31.

Use the project plan and the Week 1 - Jul 31 tab in the milestone tracker. Use only messages sent on or before July 31 in the client-portal-launch Slack channel. Ignore any messages posted after July 31. Follow the Cavenridge Weekly Project Update template.

Create the update as a Google Doc in the Weekly Updates folder. Then send me a direct message in Slack with the three most important updates and a link to the document.

Only include information you can support with the project files or Slack messages. If something is missing or the sources disagree, tell me. Don’t guess. Don’t change any of the original files or share the update with anyone else.

Open the completed Google Doc and the private Slack message.

What to check

The document is in the Weekly Updates folder and follows the Cavenridge template.

It includes an executive summary, milestone progress, risks, decisions, and priorities for next week.

The overall status is Yellow. The data migration test is delayed, SSO is waiting on the vendor, and the August 24 beta date has not moved.

It includes newer Slack context: the accessibility review passed, six clients confirmed for the beta, and the custom report builder is out of the first release.

Important claims link back to their sources, and missing or contradictory information appears under sources or open questions.

The Slack message contains the three updates that most need attention and a link to the full document.

The original files are unchanged, and nothing was shared with other people.

Wording may vary. Check the facts, source support, and required sections rather than looking for an exact sentence match.

Add the rules that are not in the template

Return to the same Work conversation and paste:

Please make a few changes to the update:

Start the executive summary with anything that needs a decision or help.

Don’t use percentage-complete estimates. Use the milestone status and explain what actually happened.

Keep the Slack message to three short bullets and a link to the full document.

Whenever you use the milestone tracker, use the most recent dated tab.

What to check

Decisions and requests for help appear first in the executive summary.

Milestones use a status and an explanation, not an invented percentage complete.

The Slack message has three short bullets and a link.

The workflow now contains a rule to use the most recent dated tracker tab.

At this point, ChatGPT has the original assignment, the company template, your corrections, and a finished example that works the way the team expects.

Save the tested workflow as a skill

What to remember

A skill is a reusable set of instructions and resources that teaches ChatGPT how to do a particular kind of work. Create the result and improve it before saving the skill. This gives ChatGPT a tested process to preserve instead of an imagined one.

Recreate it

In the same Work conversation, paste:

Save this workflow as a skill called Weekly Project Update.

Answer any follow-up questions and install the skill when prompted.

Open Plugins → Skills, then open Weekly Project Update.

Review the instructions and resources ChatGPT included.

Find the fixed Slack cutoff copied from the first assignment and replace it with a rolling window that includes messages through the current run time:

Slack messages since the previous weekly update through the current run time

Save the change. If your workspace permits skill sharing, review the skill again before sharing it.

What to check

One-time facts and dates are not frozen into the reusable instructions.

The template, reporting rules, source locations, output destinations, and review expectations remain.

The skill uses the most recent dated tracker tab and includes relevant Slack messages posted since the previous update through the current run time.

Every included resource belongs in the skill and is appropriate for anyone who may receive access.

The facts should change every week. The template, reporting rules, and basic process should stay the same.

Demo 2: Test the skill with fresh information

What to remember

Do not assume a skill works because it succeeds inside the conversation where you created it. Test it in a new conversation with new information and a deliberate contradiction.

Recreate it

Open the existing milestone tracker and create a tab named Week 2 - Aug 3.

Paste the data from Cavenridge Client Portal - Milestone Tracker - Week 2.xlsx into that new tab. Do not upload the Week 2 workbook to the connected Drive folder.

After the first run, add the fresh August 3 scenario messages from Cavenridge Client Portal - Slack Seed Messages.md to the private demo channel in order. Again, include each fictional speaker’s name and role in the same message as their update when posting from one demo account. Wait until every message is visible before starting the test. Slack will use the real posting time.

Open a completely new Work conversation and paste:

Use the Weekly Project Update skill to create this week’s update for the Cavenridge Client Portal Launch using the latest information.

Open the completed update and the Slack message.

What to check

The skill uses the Week 2 - Aug 3 tracker tab and the new Slack messages.

It catches the disagreement about the security review. The tracker says it is on track, while a newer Slack message says final approval is paused because of a password-reset issue.

It says the help-content milestone has no confirmed owner instead of guessing one.

It still follows the company template and the four reporting rules you added.

The Slack notification remains short and links to the complete draft.

Spot-checking the deliberate contradiction proves that the workflow used the fresh inputs. Review the full document before anyone relies on it.

Put the workflow on a schedule

What to remember

Schedule a workflow only after it produces a good result with fresh information. The skill tells ChatGPT how to do the work. The schedule tells ChatGPT when to start.

Recreate it

Return to the Work conversation and paste:

Run the Weekly Project Update skill every Monday at 11:00 a.m.

Review the scheduling confirmation.

Open Scheduled in the ChatGPT sidebar to see the next run, change the timing or request, pause the task, or delete it.

What to check

The task runs every Monday at 11:00 a.m. in the intended time zone.

The tracker will be updated before the scheduled start time.

The workflow uses the newest tracker tab and relevant Slack messages posted since the previous update through the current run time.

The completion notice goes to the intended private Slack destination.

The result remains a draft for you to review. It is not sent directly to leadership.

The project team still owns the source information and must keep the tracker current. The scheduled workflow creates the update; it does not maintain the tracker or approve the finished document.

Two useful prompts to try

Find a recurring task

If you are not sure where to begin, ask:

Look at my recent work and suggest three recurring tasks I could turn into a reusable workflow.

Tell me why each one is a good candidate. Don’t start anything until I choose.

You do not need to automate your entire job by next Tuesday. Choose one useful task that happens regularly, takes meaningful time, follows a reasonably stable process, and gives you a clear way to review the result. Do it once, make the result better, and save what worked.

Pressure-test a workflow before scheduling it

Use a fresh set of approved inputs and ask:

Before I schedule this workflow, test it once with these fresh inputs.

Compare the result with the source materials. Tell me what changed correctly, what is missing or contradictory, which instructions did not carry over, and what a person should review before the result is shared or used.

Do not schedule anything until I confirm that the test passed.