Review edition · Complete text lesson. Platform screenshots are being prepared.
Suppose you could…
Check a small table before trusting the story
Calculate changes accurately and distinguish percentage change from percentage points.
Calculate changes accurately and distinguish percentage change from percentage points.
Time is a practice estimate. Pause or return whenever you need.A useful little possibility.
Your goal is a usable work artifact, not a perfect-looking AI answer. Calculate changes accurately and distinguish percentage change from percentage points.
Let’s make a start.
Use a fresh conversation in an AI tool you are permitted to use. Copy the fictional sample below, then paste the starter prompt with it. No file upload, web search or paid integration is required.
1. Work out 80/100 and 90/120 yourself.
2. Run the prompt.
3. Verify each arithmetic step with a calculator.
4. Ask the model to explain how more resolutions can coexist with a lower resolution rate.
Your sample material
Fictional training material. No real customer information needed.
Fictional service team, monthly totals: Month | Requests | Resolved | Cost April | 100 | 80 | €1,000 May | 120 | 90 | €1,200 June | 120 | 96 | unknown These are all requests in each month, not a tracked cohort. No staffing or case-complexity data is supplied.Download sample .txt ↓
Analyze this small table. Calculate monthly resolution rates, April-to-May request growth, April-to-May resolution-rate change in percentage points, and cost per request where cost is known. Show formulas. List unknowns and avoid causal claims. Do not estimate June cost.
Keep personal and confidential information out of external AI tools. Start with the sample material.
Turn a first try into your thing.
Compare the result with the checklist before opening the worked example. Identify one specific weakness and ask for a targeted revision, referring to the original sample. If all checks pass, tighten the wording without changing the facts. Save the reviewed result in your own document; do not send or publish it as part of this exercise.
Pause for the “aha.”
Fluent explanations do not validate arithmetic. Check denominators, units and missing values before deciding what a trend means.
Useful beats convincing.
Check these against your actual output. Your answers stay on this device; this is self-review, not automated grading.
Finished your first try? Reveal a worked example ↓
April resolution rate: 80/100 = 80%. May: 90/120 = 75%. June: 96/120 = 80%. Requests rose (120−100)/100 = 20% from April to May. Resolution rate fell 5 percentage points; relative rate change is −6.25%, not −5%. April and May cost per request are both €10. June cost per request is unknown. More resolved requests in May did not keep pace with higher intake. Causes cannot be established from this table, and these monthly figures do not track the same cases over time.
A new case. Your own approach.
Apply the review principles to these new facts, not the previous sample’s specific numbers or answers.
Month A: 50 requests, 40 resolved, €500. Month B: 80 requests, 56 resolved, €960. Calculate rates, rate-point change and cost/request. Self-check after trying: 80%, 70%, −10 points; €10 and €12.
One possibility leads to another.
Repeat on a small, permitted task of your own. Record what you changed and which check caught a problem. Keep using fictional inputs if workplace material is not approved for your chosen tool.
Your reusable workflow card ↓
Task: Check a small table before trusting the story Audience: [who will use this] Approved source material: [paste] Required output: Calculate changes accurately and distinguish percentage change from percentage points. Constraints and unknowns: [list] Review before use: - Resolution rates are 80%, 75% and 80%. - Request growth is 20%. - The rate decline is five percentage points. - June cost remains unknown. - No cause or cohort claim is invented.Download workflow .txt ↓
You tried something. That counts.
Keep a note of what you made or what surprised you. It stays in this browser.