# The Friday spreadsheet — bild

> Ninety minutes of senior attention, every week, reconciling three systems that don’t talk to each other. Field note 001 from bild.

Markdown rendering of https://bild.systems/thinking/the-friday-spreadsheet — the HTML version is canonical. Contact: humans@bild.systems

Note 001

# The Friday spreadsheet

Ninety minutes of senior attention, every week, reconciling three systems that don’t talk to each other.

Every Friday afternoon, the same spreadsheet. Export the invoices, check them against the project system, chase the two that don’t match, paste the totals into a third tool that doesn’t talk to the first two. Ninety minutes, most weeks, done by the most senior person in the room because the stakes were too high to hand it to anyone else. That was us, before bild existed. It’s the note everything else here grows out of.

## What is the Friday spreadsheet?

It’s the recurring job where a person supervises data moving between systems that don’t talk to each other: exporting from one, checking against a second, typing totals into a third. Ours was invoicing. Yours might be month-end, timesheets, a stock reconciliation or a compliance register. The name changes; the shape is the same, and it almost always lands on someone senior.

## Why does it land on the most senior person?

Because the stakes are real and the checks need judgment. A wrong total goes to a client or the bank, so nobody wants to hand it to the newest person, and the senior person tells themselves it only takes an hour. It never shows up on a roadmap. It just quietly takes the hours they were hired to think with, week after week.

## Why isn’t it just fixed with an integration?

Often part of it is. The platforms’ own connectors move approved records from one system to another. What they don’t do is the work before that: matching, checking, chasing the two lines that don’t agree, and deciding what to do about them. That’s the part the person was actually doing, and it’s the part that stays manual when a connector is switched on.

## What did the fix look like?

Small, specific and boring. An agent exports, matches and drafts the reconciliation, and a person looks at the two lines that don’t line up and decides. The checking still happens. The typing stopped. It wasn’t a platform and it wasn’t a transformation programme; it was the same Friday job with the machine work taken out of it.

## How do you know which work is a Friday spreadsheet?

Three tells. It’s repetitive but too important to drop. It moves the same information between systems by hand. And when you ask who does it, the answer is someone whose time costs more than the task. If all three are true, it’s a candidate, and the two-week audit is where we find out whether it’s worth automating.

## What stays with the person?

The decision. Which of the two mismatched invoices is right, whether a variance is a problem or a rounding difference, when to call the supplier. Everything up to that point can be drafted; the judgment stays where it was, with a record of what was drafted and what was decided.

Our own operations went quiet after that. Not dramatic, quiet. The reconciliation happened before anyone opened the file, and the senior people got their Fridays back. Then clients started asking what we’d done.

Yours has a different name and lives in a different folder. But it’s the same work.

All field notes

Start with the work that keeps getting in the way.