Day 12: Check Data and Choose a Chart with ChatGPT

One small win today
Check the total of 66 requests and the units against the four original counts.
Let’s try itListen with Cue
Cue guides you through the whole lesson. Listen straight through, or choose a chapter. Pause whenever you want to try something.
Complete podcast · 8 min 29 sec · AI-generated character voice
Jump to a chapter
Day 12: Check Data and Choose a Chart with ChatGPT audio transcript
Welcome
Cue: Hi, I’m Cue. Welcome to the Day 12 lesson: Check Data and Choose a Chart with ChatGPT. I’ll guide you through the whole lesson. Pause whenever you want to try something. Chapter links and the full transcript are available alongside the player, so you can return to the part you need.
Your one useful idea
Cue: Here’s the one idea to keep in your pocket today. Verify the input values, units, calculation, and interpretation. For this lesson, the four mock counts total 66.
Why this helps
Cue: Let’s connect this to a real working day. Prism says: A small table can reveal more than a long paragraph. Practise asking a question you can check, using data that fits in a compact example.
Before you begin
Cue: A quick check before we get our draft-making shoes on. Files, screenshots, and spreadsheets may contain hidden or sensitive information. Use the inline sample today. An assistant can also misread units or calculate incorrectly.
Try it together
Cue: Ready to make a little progress? Here’s the quick route and the full practice. You can pause after the steps and work in your own time. Quick version: Add the four counts yourself, then check the assistant’s table and units against your total. About 10 minutes is enough. Step 1. Paste the mock weekly counts. Step 2. Ask for a table, total, and one simple visual suggestion. Step 3. Calculate the total yourself and compare it with the answer. Practice material or example: Mock requests completed per week: Week 1 = 12, Week 2 = 18, Week 3 = 15, Week 4 = 21. These are counts, not hours. The checked total is 66.
Simple and Expanded prompts
Cue: Time to frame the request. Both prompt versions are in this lesson. You only need to try one. I’ll read both versions so you can hear the difference. Pause and copy the exact text from the lesson if you’re practising. Here’s the Simple prompt. Make a four-row table from these mock completed-request counts: 12, 18, 15, 21 for Weeks 1 to 4. Show the total and calculation, then suggest one readable chart. Describe the change without claiming a cause or predicting next week. Here’s the complete Expanded prompt. Make a four-row table from these mock completed-request counts: 12, 18, 15, 21 for Weeks 1 to 4. Show the total and calculation, then suggest one readable chart. Describe the change without claiming a cause or predicting next week. Label the values completed requests, not hours or percentages. Show 12 + 18 + 15 + 21 = 66. Recommend a simple column chart with Weeks 1 to 4 on the horizontal axis and completed requests on the vertical axis. Distinguish a change in counts from its cause. Pick the version that fits your task. One useful prompt is enough. Give it a try when you’re ready.
A worked example
Cue: Let’s open a little window onto one possible result. This example is written for the course. Your assistant’s answer can look different. One possible result: Total: 66 completed requests. Week 4 has 9 more completed requests than Week 1. A four-column chart would show the weekly counts without suggesting why they changed. Why it works: The calculation is checkable, the units are preserved, and the description does not claim a trend will continue. Prism says: What are these numbers measuring? Folio says: Completed requests. Check 12 + 18 + 15 + 21 = 66, then describe the counts without inventing a cause. Watch for: "AI increased productivity by 75%" invents both a cause and a productivity measure.
Spot the Wobble
Cue: Tiny detective break! Let’s spot the wobble. Draft to check: Weekly counts: 12, 18, 15, 21. Draft total: 68. Question: What total should Folio put in the table? A: 68, because the assistant already calculated it. B: 66, after checking 12 + 18 + 15 + 21. What do you think?
*A short thinking pause. Pause the player for as long as you need.*
Cue: Here’s Prism’s check. The answer is B Why: The checked total is 66 completed requests. Week 4 exceeds Week 1 by 9. Neither figure tells us why the counts changed. A wobble is a clue, not a disaster. That little check is how a draft gets stronger.
Keep something useful
Cue: Let’s give your useful work a home. Save table, visual recommendation, and source-data check note for the full practice, or just keep your checked quick result. Keep the input beside it and note one thing you checked.
Review and save
Cue: Time for the satisfying bit: checking what you made. The quick finish counts. You don’t have to do every extra. Is the total 66, are the units counts, and does the answer avoid inventing a cause? Quick finish: Check the total of 66 requests and the units against the four original counts. You can stop here. Done when: Full practice: Your table contains all four counts, a checked total of 66, and a chart suggestion with correct labels. You can stop here. Extra practice, only if useful: If an approved file tool is available, try the same sample as a CSV. Do not connect an app just for this exercise.
Your optional official video
Cue: If you’d like to see the tool in action, there’s an optional official video embedded in this lesson. We’ll explain what to notice. You can watch later. Folio says: Notice that the business question comes before the chart. What does your small table actually let you say? Watch: Use ChatGPT Work to build dashboards from a business question (official OpenAI YouTube channel, published September 18, 2026, verified October 2, 2026). Keep it small: About 0 minutes and 42 seconds. This edited demo uses synthetic data and a connected business setup. You only need today’s small table and a careful check of the numbers. Watching is optional.
Questions you might be wondering
Cue: Two questions you might be wondering about. Let’s clear them up. What should I check in an AI-generated data summary? Verify the input values, units, calculation, and interpretation. For this lesson, the four mock counts total 66. Does an upward pattern explain its cause? No. The weekly counts describe a change but provide no evidence of why it happened or what will happen next.
Quick quiz: question 1
Cue: Question 1 of our three little checks. What is the checked total of 12, 18, 15, and 21 completed requests? Option A. 56 requests. Option B. 66 requests. Option C. 76 requests. Want a hint? Add all four weekly counts, not just the first three. Pause to choose. Keep listening when you’re ready for the answer.
*A short thinking pause. Pause the player for as long as you need.*
Cue: The answer is B. 66 requests. Twelve plus eighteen plus fifteen plus twenty-one equals 66 requests.
Cue: If you spotted it, lovely work! If you picked another answer, you’ve found something useful to practise. There’s no score to chase.
Quick quiz: question 2
Cue: Question 2 of our three little checks. Which label matches the sample data? Option A. Hours saved per week. Option B. Average response time in minutes. Option C. Requests completed per week. Want a hint? Check the original units before choosing a chart label. Pause to choose. Keep listening when you’re ready for the answer.
*A short thinking pause. Pause the player for as long as you need.*
Cue: The answer is C. Requests completed per week. The inputs are counts of completed requests, not time measurements. Another little check in your toolkit. You’re building a habit one answer at a time.
Quick quiz: question 3
Cue: Question 3 of our three little checks. Week 4 has the highest count. What can you conclude from these counts alone? Option A. Week 4 recorded 21 requests, but the cause is not established. Option B. The new form caused every increase. Option C. Everyone became more productive because of AI. Want a hint? A pattern in counts does not tell you what caused it. Pause to choose. Keep listening when you’re ready for the answer.
*A short thinking pause. Pause the player for as long as you need.*
Cue: The answer is A. Week 4 recorded 21 requests, but the cause is not established. You can describe the observed values without inventing an explanation. Three checks, one stronger understanding. The online quiz lets you try again until each answer clicks.
Your next small step
Cue: Before you leave, keep the original input beside your checked result. Your judgment is the part no assistant can replace. You made room for one useful step today. That counts. Day 13 is ready whenever you are. Cue asks, Folio makes, Prism checks. See you for your next small win!
See today’s example with your practice partners

Key Takeaway
Verify the input values, units, calculation, and interpretation. For this lesson, the four mock counts total 66.
Why It Matters
Prism: A small table can reveal more than a long paragraph. Practise asking a question you can check, using data that fits on the page.
Know Before You Try
Files, screenshots, and spreadsheets may contain hidden or sensitive information. Use the inline sample today. An assistant can also misread units or calculate incorrectly.

Try It
Quick version: Add the four counts yourself, then check the assistant’s table and units against your total. About 10 minutes is enough.
- Paste the mock weekly counts.
- Ask for a table, total, and one simple visual suggestion.
- Calculate the total yourself and compare it with the answer.
Practice material or example: Mock requests completed per week: Week 1 = 12, Week 2 = 18, Week 3 = 15, Week 4 = 21. These are counts, not hours. The checked total is 66.

Prompt
Primary Prompt
Pick one to try. Simple gets you moving. Expanded adds structure. Both include the practice inputs.
Make a four-row table from these mock completed-request counts: 12, 18, 15, 21 for Weeks 1 to 4. Show the total and calculation, then suggest one readable chart. Describe the change without claiming a cause or predicting next week.Make a four-row table from these mock completed-request counts: 12, 18, 15, 21 for Weeks 1 to 4. Show the total and calculation, then suggest one readable chart. Describe the change without claiming a cause or predicting next week.
Label the values completed requests, not hours or percentages. Show 12 + 18 + 15 + 21 = 66. Recommend a simple column chart with Weeks 1 to 4 on the horizontal axis and completed requests on the vertical axis. Distinguish a change in counts from its cause.Worked Example
: see a result and what to check
One possible result: Total: 66 completed requests. Week 4 has 9 more completed requests than Week 1. A four-column chart would show the weekly counts without suggesting why they changed.
Why it works: The calculation is checkable, the units are preserved, and the description does not claim a trend will continue.
Watch for: "AI increased productivity by 75%" invents both a cause and a productivity measure.

Spot the Wobble
Draft to check: Weekly counts: 12, 18, 15, 21. Draft total: 68.
What total should Folio put in the table?
Reveal Prism’s check
B is the better choice. The checked total is 66 completed requests. Week 4 exceeds Week 1 by 9. Neither figure tells us why the counts changed.
Spotted it? Nice checking. Missed it? Now you know what to look for.
Make Something Useful
Save table, visual recommendation, and source-data check note for the full practice, or just keep your checked quick result. Keep the input beside it and note one thing you checked.

Review and Save
Is the total 66, are the units counts, and does the answer avoid inventing a cause?
Quick finish: Check the total of 66 requests and the units against the four original counts. You can stop here.
Done when: Full practice: Your table contains all four counts, a checked total of 66, and a chart suggestion with correct labels. You can stop here.
Want one more little stretch?
If an approved file tool is available, try the same sample as a CSV. Do not connect an app just for this exercise.

Watch with Folio
Folio: Notice that the business question comes before the chart. What does your small table actually let you say?
Watch: Use ChatGPT Work to build dashboards from a business question (official OpenAI YouTube channel, published September 18, 2026, verified October 2, 2026).
Show video player: Use ChatGPT Work to build dashboards from a business question
Keep it small: About 0:42. This edited demo uses synthetic data and a connected business setup. You only need today’s small table and a careful check of the numbers. Watching is optional.
FAQ
What should I check in an AI-generated data summary?
Verify the input values, units, calculation, and interpretation. For this lesson, the four mock counts total 66.
Does an upward pattern explain its cause?
No. The weekly counts describe a change but provide no evidence of why it happened or what will happen next.

Three little checks
“Let’s see what stuck! Pick an answer and I’ll help you check it. You can try again as often as you like.”
Question 1 of 3
Lovely work. Three checks complete!
You’ve practiced the key ideas and checked the reasons. Keep that curiosity for the next day.

A small win worth keeping
Checked and saved? You can call it a day. Come back when you’re ready.
Progress is saved in this browser when available.
Stored on this device. No account or cross-device sync.
Course position: Day 12 of 30 · ChatGPT module
Continue: Day 13: Build a Realistic Weekly Work Plan
Sources and review date
Product features and interfaces can change. OpenAI ChatGPT Learn is the reference for current details. Course content reviewed October 2, 2026.