Day two of three. Two rungs of the ladder. A number you can stand behind, and something to put beside it.
Yesterday you spent an afternoon making a file you can trust. That was real work and it was worth it. This morning I gave you one number out of a clean file, and not one of you could tell me whether it was good news.
Yesterday I told you a model holds a limited amount of text in view at once. That limit has a name: the context window.
| Copilot Chat Track B | Copilot in Excel Track A | Claude | |
|---|---|---|---|
| Where it sits | Your account and its security boundary | Inside the workbook | A separate browser session |
| Best at | Files and Microsoft tools | Building what you saw at nine o’clock yesterday | Long reasoning, cleaning logic, explanations |
| Long pasted data | Weaker | Reads the file, not a paste | Handles more, more reliably |
| Needs a license | No | Yes, and not everyone has it | Depends on your account |
The file is work-orders-full.xlsx. Attach it, do not paste it. For most of you this is the first time you have attached a file rather than pasted one.
Yesterday your prompt had a part that asked the tool to state its row count. Which part number?
Six profile questions, answered once, about the dataset as a whole. This is a different question, and it changes from question to question.
CloseDate is filled in eighty-six percent of rows. Every other column in this file is one hundred percent.
Two rules, and they hold all day: the check goes in your workbook before you open the file, and every answer arrives with the row count the tool reports.
Four minutes. Then three of you read your answer out.
| Site | Average days to close |
|---|---|
| Ahmadi Refinery | 3.17 |
| Burgan Gathering Center | 3.30 |
| Sabriyah Station | 3.38 |
| Mina Al-Zour Terminal | 3.42 |
| Wafra Station | 3.42 |
| North Field Booster | 3.70 |
Site · RaisedDate · CloseDate.You have had that check in your hand since half past ten. It takes ninety seconds. Every one of you agreed it was obvious.
Nothing went wrong with the tool. Every number in that first table is arithmetically correct. It answered the question it was asked, using the rows it could use, and said nothing about the rest.
Same tool. Same file. Same question. The job is to make the trap show itself before it catches you.
What is the average time to close a work order, by site? Time to close means the days between RaisedDate and CloseDate. Before you answer: - report how many work orders have no CloseDate - report that count by site, as a percentage of each site's rows Then give me two tables: Table A: the average using only work orders that have a CloseDate. Table B: the average counting work orders with no CloseDate as still open, measured from RaisedDate to the latest date in the file. Tell me which sites change rank between the two tables.
That number is now trustworthy. It is still not useful, and the next twenty-five minutes are about why.
This morning I gave you one number and asked whether it was good. Here is what you asked me for, in your own words, at ten past nine.
Take any number from the Work Order Set that you can defend. Then produce four versions, one for each comparison. All four will be true.
The work order costing forty times the next highest. Hands up who wrote: yes, delete it.
WO-2087 is also one of the twenty duplicate IDs, and the two rows carrying it are different work orders. Removing duplicates by ID could have deleted it without anybody choosing to.Everything today lands on this one object. Grounding, the row count, the comparison, the outlier.
Wisdom, which sounds grand and is not. It is one practical question. You have a finding on that card, and it is a good one, tomorrow somebody has to understand it without you standing next to them.