Back to the Lab The Lab · Your first job

The Payroll Sheet

Twenty-four camp counselors get paid Monday, if the payroll sheet reaches the payroll service by 4:00. It's 3:15, the bookkeeper is on a plane, and the sheet has mistakes in it. Find the ones that matter.

  • About 15 minutes
  • No sign-up

Friday, 3:15 pm

  1. It's Friday, July 24, and you're 17. This is your fourth week as the summer office helper at Fernbrook Day Camp in Pittsburgh. The camp's 24 counselors are 16 to 19, and most of them are your friends. You just got back to the office from setting up chairs for the show.
  2. Avery Chen, the bookkeeper, built this week's payroll sheet this morning and then left for the airport. Jules Marino, the director, is running the end-of-session show until 4:30 and can't step away. There's nobody to ask.
  3. Ledgerline Payroll needs the sheet by 4:00 to pay the counselors on Monday. When you upload it, the camp moves the sheet's Total into the payroll account, which is empty until then.
  4. Before pickup, somebody always comes to the front desk.
  5. Avery left a note.
From
Avery Chen
Sent
Friday, 11:40 am
Subject
Payroll for this week

Hi! I ran out of time before my flight, so this week's payroll is yours to send. A few things:

  • Hours come from the time clock report, last Friday through Thursday. Today's hours go on next week's sheet. I pasted them in this morning.
  • Three new counselors started Monday: Marley, Devon and Ellis (Ellis was a counselor here two summers ago). I added them at the bottom.
  • Deductions, money taken out of someone's pay, are in my log, in the Payroll folder.
  • Fernbrook pays one and a half times the rate for hours over 40 in a week. A couple of people went over, so I had the sheet's AI helper add overtime. It looked right to me.
  • Jules usually looks it over before it goes in, but Jules has the show. Ledgerline has a "Check file" button.
  • Bailey asked for a copy of a June pay stub. That can wait until I'm back.
  • Pay is private, even from friends.
  • I set up the transfer, so when you upload, the Total moves to the payroll account on its own. It moves exactly the Total, so it can never take more than we meant to send. Upload by 4:00!

Thanks!
Avery

The sheet, as Avery left it

ID (A)Name (B)Rate (C)Hours (D)Regular (E)Overtime (F)Deduction (G)Pay (H)
21203Ari Abrams14.5038551.000.000.00551.00
31187Bailey Brennan14.5040580.000.000.00580.00
41311Cameron Castillo13.5036486.000.000.00486.00
51094Dakota Dunn16.0046736.00144.000.00880.00
61256Emerson Feld14.5000.000.000.000.00
7417Finley Garza14.5039565.500.000.00565.50
81342Harper Ito13.5035472.500.000.00472.50
91119Hayden Kowalski16.0040640.000.000.00640.00
101278Kai Mbeki14.5037536.500.000.00536.50
111305Logan Novak13.5032432.000.000.00432.00
121150Noa Pereira14.5040580.000.000.00580.00
131226Parker Quist14.5034493.000.000.00493.00
141269Quinn Ramos13.5040540.000.000.00540.00
151133Reese Santos14.5036522.000.000.00522.00
161290Riley Shah14.5031449.500.000.00449.50
171172Rowan Uribe14.5044638.0087.000.00725.00
181215Sage Vance13.5036486.000.000.00486.00
191248Sam Bauer14.5040580.000.000.00580.00
201361Sam Okoye13.5033445.500.000.00445.50
2192Skyler Tan13.5030405.000.000.00405.00
221199Taylor Webb18.0040720.000.00-120.00840.00
231401Marley Fox13.5024324.000.0015.00309.00
241402Devon Ward13.5028378.000.0015.00363.00
251403Ellis Grant14.5030435.000.0015.00420.00
26Total11,209.50

The formulas, copied down each column: Regular is =C2*D2. Overtime is =IF(D2>40,(D2-40)*C2*1.5,0). Pay is =E2+F2-G2. The Total, in H26, is =SUM(H2:H22).

The time clock report

Hours worked last Friday through Thursday, by ID. Total: 836 hours.

  • 1203 Ari Abrams: 38
  • 1187 Bailey Brennan: 40
  • 1311 Cameron Castillo: 36
  • 1094 Dakota Dunn: 46
  • 1256 Emerson Feld: 0
  • 0417 Finley Garza: 39
  • 1342 Harper Ito: 35
  • 1119 Hayden Kowalski: 40
  • 1278 Kai Mbeki: 37
  • 1305 Logan Novak: 32
  • 1150 Noa Pereira: 40
  • 1226 Parker Quist: 38
  • 1269 Quinn Ramos: 34
  • 1133 Reese Santos: 40
  • 1290 Riley Shah: 36
  • 1172 Rowan Uribe: 44
  • 1215 Sage Vance: 36
  • 1248 Sam Bauer: 40
  • 1361 Sam Okoye: 33
  • 0092 Skyler Tan: 30
  • 1199 Taylor Webb: 40
  • 1401 Marley Fox: 24
  • 1402 Devon Ward: 28
  • 1403 Ellis Grant: 30

Avery's deductions log

  • Taylor Webb: $120.00, paying back an advance (pay the camp gave early) from last month.
  • Marley Fox, Devon Ward and Ellis Grant: $15.00 each for a staff T-shirt.
  • Total: $165.00.

What the checks would have shown

  • Adding up the Pay column yourself: $12,301.50. The Total cell says $11,209.50.
  • The sheet's hours against the time clock: 829 hours on the sheet, 836 on the time clock.
  • Deductions against Avery's log: -$75.00 on the sheet, $165.00 in the log.
  • A made-up week, 45 hours at $15.00: $712.50 by hand. The sheet's formulas give $787.50.
  • Ledgerline's "Check file": two rows don't match any employee, IDs 417 and 92. Ledgerline adds up the Pay column itself, $12,301.50, and it doesn't match the file's Total.
  • The sheet's AI helper: "The Total in H26 adds rows 2 to 22, so rows 23 to 25 are left out. Rows 19 and 20 may be the same person entered twice: both are Sam, both started this summer, and neither went over 40 hours. If so, clear row 20. The overtime formula in column F is correct."

What was wrong

The Total stopped at row 22

Avery added the three new counselors at the bottom, rows 23 to 25, but the Total still added H2 to H22. It was $1,092 less than the Pay column. Ledgerline holds the whole payroll when the account can't cover it, so if you uploaded it like that, the whole payroll was held until Wednesday. Adding up the Pay column yourself took a minute and showed two different numbers. Ledgerline's "Check file" showed it too.

Four rows of hours were pasted one row off

Rows 13 to 15 each had the hours of the person below, and row 16 still had last week's 31. The total hours came out 7 short of the time clock, which is how a three-minute check found it. Pasting the hours in again, matching each ID, fixed all four. You didn't need to find the four rows first.

A minus sign

Taylor Webb was paying back a $120 advance, pay the camp had given early. Typed as -120, the deduction added $120 instead of taking it away, a $240 mistake. The Deductions column didn't match Avery's log.

Two IDs lost their zeros

Finley Garza's ID is 0417 and Skyler Tan's is 0092. When the IDs were brought into the sheet, the spreadsheet treated them as numbers and dropped the zeros. Ledgerline matches people by ID, so neither would have been paid. Its own "Check file" button said so.

Overtime was paid twice

The AI helper added an Overtime column that was right: hours over 40, at one and a half times the rate. But Regular pay still paid the rate for every hour, so hours over 40 were paid once there and again in Overtime. The sheet paid Dakota $96 too much and Rowan $58. A made-up week you can work out in your head, 45 hours at $15, showed it. If you asked the AI helper, it said the overtime formula was correct, and it was. The mistake was in the column it didn't change. Setting every Overtime cell to 0 instead stopped the double pay, but then hours over 40 got no extra half.

Right, even though they looked odd

Emerson Feld's 0 hours (on vacation all week). The two Sams, Sam Bauer and Sam Okoye, who are different people. Taylor Webb's $18.00 rate (the head counselor). If you cleared the "duplicate" Sam's row because the AI helper suggested it, Sam Okoye wasn't paid.

The checks that worked

  • Totals against something outside the sheet. The time clock and Avery's log each took a few minutes and showed that something was wrong, and in which column.
  • A test you can do in your head. One made-up week caught the overtime mistake that reading the numbers could miss.
  • The payroll service's own check. It knew who the employees were, which the sheet didn't, and it added up the file itself.
  • Adding a column yourself. A minute, and it caught the biggest mistake of the day.

Checking every row by hand would have taken 48 minutes, longer than the time you had, before you fixed anything. The quick checks didn't fix anything either. They told you where to look.

Keep these

Four questions before a spreadsheet goes out

  1. Does every total add up, and does it match something outside the sheet? Add up the column yourself, then compare it with a time clock, a log, a bank statement or last week's number.
  2. Did you test the formulas with a case you can do in your head? One made-up row is enough to catch a formula that's wrong for everyone. Test in a copy, or delete the test row before the file goes out.
  3. Did anything get pasted or brought in? If it doesn't match where it came from, paste it again from the source instead of hunting row by row. Then look for zeros that vanished and entries that turned into dates.
  4. Who else looked at it? A second person often catches mistakes the person who built it missed.

You'll never have time to check every cell. A total that doesn't match tells you where to look.

What's true outside the game

  • News from this September. On September 1, 2026, British Columbia's government said spreadsheet errors had overstated its expected natural gas royalties (the money gas companies pay the province for the gas they take) by about 1.46 billion Canadian dollars over five years. The biggest error treated Canadian dollars as if they were US dollars. First Nations, Indigenous communities in Canada, had raised questions about the numbers in a letter in July. The minister called it a human error, and the Premier, the head of the province's government, asked the auditor general, the official who checks the government's books, to review it.
  • A payroll upload went wrong this March. In March 2026, a field left blank on a spreadsheet uploaded to the City of Austin's payroll system overpaid 675 city employees about $1.4 million in all.
  • A total that stopped short. A famous 2010 economics paper by Carmen Reinhart and Kenneth Rogoff, used in arguments about government debt, averaged a range of spreadsheet rows that left out five countries. In 2013 Thomas Herndon, a graduate student, and two professors at the University of Massachusetts found it while checking the paper's numbers. The authors admitted the spreadsheet error and stood by their main conclusion. It was one of three problems the critics raised.
  • Pasted out of line. In 2003 the Canadian power company TransAlta lost about 24 million US dollars when bids it sent for US contracts that protect against the cost of crowded power lines didn't line up with the right prices after a spreadsheet paste. Its chief executive called it "a simple clerical error," a paperwork slip.
  • A minus sign. In 1994 Fidelity's Magellan fund, a big pool of investors' money, told investors to expect a year-end payout of $4.32 for every share they owned. A tax accountant had left the minus sign off a $1.3 billion loss in a spreadsheet, turning it into a gain. The estimate was off by $2.6 billion, and the payout never came.
  • Hidden data that wasn't gone. In 2023 the Police Service of Northern Ireland answered a public records request with a spreadsheet that had a hidden tab listing all 9,483 officers and staff. The UK's data regulator fined it £750,000. In 2008, a junior lawyer reformatting a spreadsheet to make a PDF made its hidden rows visible again. That added 179 contracts the bank Barclays never meant to buy to its deal for parts of Lehman Brothers, a bank that had just failed.
  • Data cut off. In early October 2020, England found that 15,841 positive COVID cases from the previous eight days had been left out of the daily figures. Public Health England said the files had gone over a maximum size. Reports said they were loaded into an old Excel format that stops at 65,536 rows.
  • Software that changes what you typed. A 2016 study of 18 leading journals about genes found that about one in five papers that came with gene lists in Excel had gene names turned into dates or numbers. The committee that names human genes renamed some of them in 2019 and explained why in 2020: SEPT1 became SEPTIN1 and MARCH1 became MARCHF1, so Excel would stop turning them into dates. Excel also drops leading zeros, like the ones in 0417; since 2023, newer versions of Excel let users turn some of these changes off.
  • A formula wrong from the start. In 2012 JPMorgan's London office lost about $6.2 billion on trades. Its new risk model, a spreadsheet that estimated how much the trades could lose, was filled in by hand, and one step divided by a sum where it should have divided by an average. The bank's own review said that probably made the risk look smaller than it was. It wasn't the only cause: a US Senate report blamed bank officials who ignored the growing risk.
  • Spreadsheet mistakes are common. In five careful checks (audits) from 1995 to 2000, collected by the researcher Raymond Panko, 91% of 55 spreadsheets had at least one serious error. That's a small sample, and Panko thinks the audits missed errors too. In 14 lab studies, people working alone got about 4% of cells wrong. In one of Panko's experiments, people checking a spreadsheet alone caught 63% of the planted errors, and teams of three caught 83%.
  • AI in spreadsheets: check its work. Microsoft, Google, OpenAI and Anthropic all offer AI that works inside spreadsheets, and their own pages say not to take its work on trust. Microsoft says to review and verify anything Copilot creates before you rely on it. Google says its Gemini features in Sheets may suggest inaccurate information. OpenAI says AI can make mistakes, so verify important numbers. Anthropic says to always review Claude for Excel's changes before you finalize your work. In a public test of realistic business spreadsheet work, researchers tried eight leading AI models in March 2026, and the best one got about 35% of the tasks right. On a smaller set of 30 tasks they also tried four AI spreadsheet tools, Kimi Sheet, GLM in Excel, ChatGPT for Excel and Claude for Excel, and the tools did no better. Microsoft's and Google's own tools weren't in that test. Two other companies later posted scores of about half on the test's public scoreboard.

Now do it for real

  1. Watch a spreadsheet change your data. In LibreOffice Calc, which is free and needs no account, type a short list: an ID that starts with zeros (0417), a gene-style code (MARCH1, which Excel turns into a date; see what yours does), a 17-digit number, and a column of hours where you type one of them with an apostrophe first ('38), which stores it as text. Before you press Enter on each, write down what you expect to see. Then add up the hours with =SUM() and see whether the one stored as text counted. Then add the same cells with plus signs (like =B2+B3+B4) and compare. If the apostrophe shows in the cell, the cell is already set to Text, so type 38 again without the apostrophe; it's still stored as text.
  2. Plant three, swap, catch. Make a small sheet of made-up pay for ten people with a total at the bottom. Plant three mistakes from this lesson. Swap with a friend, set a timer for ten minutes, and use only the quick checks: totals against a list, one test case, a row count.
  3. At your next job, ask one question: "When a spreadsheet goes out, who checks it, and what do they check it against?"

You will have seen a spreadsheet change your data with your own eyes, and caught a friend's mistakes on a clock. Time: 40 minutes. You need: LibreOffice, or any spreadsheet you're allowed to use, and a friend. No AI account.

Sources

Last checked November 11, 2026. Fernbrook Day Camp, Ledgerline Payroll, every counselor and everyone else in the story are made up, and so is every number in the sheet. Ledgerline's rule about holding a short payroll, the parent at 3:30 and how long each check takes are made up too, and taxes are left out of the math to keep it short. The sheet's AI helper and everything it says are made up too; it isn't any real company's product. Four of the mistakes are modeled on the real cases above; the fifth, the AI's overtime column, on what the AI companies themselves warn about. Torah Tech wrote this lesson with the help of Claude, an AI made by Anthropic. Any mistakes are ours.

Back to the Lab

The Opportunity Year · Tel Aviv, Israel

Learn like this for a year

Torah Tech is a beit midrash in Tel Aviv built for personal and professional growth: Torah learning at the center of every day, and internships at Israeli startups. It is the year a future Jewish leader realizes who he can become, and chooses to become it.