Merged Cells and Blank Rows Before the Deadline? The 8:15 Train

2026-10-13

The train is already moving when you open the laptop.

You balance it on your knees, a coffee wedged between your elbow and the window. The file arrived at 7:50 from a client's accounts person, with one line: "Here's everything, need the summary by 10."

You open it. Your stomach drops a little.

The headers are merged across three columns. Some rows are blank for no reason you can see. A title sits in the middle of the sheet, as if someone wanted it to look nice for a print-out in 2014. Half the dates are text. Somewhere around row 212 there's a block that just... repeats.

You have about eighty minutes. The train has about forty of them.

The kind of mess nobody warns you about

Nobody puts this in the project brief. The brief said "summarise the data." It didn't say "first rescue the data from the person who made it pretty."

So you do what everyone does. You click a merged cell and unmerge it. Now there's a hole where the value used to be. You click the next one. And the next. You delete a blank row, then another, then you scroll and find twenty more.

It feels productive. It isn't, quite. Every fix reveals the next problem, and a quiet voice starts up behind your eyes: what if I delete something that mattered?

That's the worry nobody says out loud. Not that the file is ugly, but that you'll tidy it wrongly, hand over a summary built on a shifted column, and the client will notice in the meeting. Or worse, they won't notice, and it'll surface three weeks later.

The train stops. People get on with wet umbrellas. You're still on row 90, and your shoulders have crept up toward your ears.

What it quietly costs

It's never just this one morning.

It's the Sunday you spent "just quickly" fixing an export before a Monday call. It's the evening that disappeared into find-and-replace. It's the slightly sheepish email asking if the client could send it again as a plain table this time, if possible, which feels like asking someone to apologise for their own spreadsheet.

And underneath, a small, stubborn feeling: a real professional would have a way to deal with this. Not a heroic scramble on a Tuesday train, but a quiet, boring, reliable way.

You don't need to be a data person to feel that. You only need to be someone who gets files from other people.

The moment it clicks

You make the deadline, barely. At 9:52 you send a summary you're about 90 percent sure of, and you spend the meeting watching every slide for the number that might be off.

Afterwards, walking back along a grey street, you do something unusual. You don't just exhale and move on. You ask a different question.

Why am I cleaning this by hand at all?

The mess is always the same kind of mess. Merged headers. Blank rows. Dates that are really text. Duplicates. Phone numbers in five formats. It has a pattern, and patterns are exactly what a computer is patient about and you are not, at 8:15 on a train.

The shift isn't about learning something clever. It's about deciding that this chore doesn't have to be done with your own two hands and your own nerves, every single time.

A different Tuesday

Picture the same email, the same 7:50, the same "need it by 10."

This time you're at the kitchen table, tea still warm. You open the attachment, take one look, and feel... almost nothing. A small ah, that kind of file. You hand it to a routine you trust and let it run.

Before anything is actually changed, you see what would change. A short list: these rows were blank, these headers were merged, these dates were read as text. Nothing is overwritten, nothing is a surprise. You skim it, nod, and let it go ahead.

Ten minutes later you have a clean table. You build the summary from it. You send it at 8:40, and you're not rehearsing your defence in your head.

The rest of the morning is yours. You answer two emails you'd been avoiding. You go for a walk before the next call, because you can.

That's all it is. Not a transformation. Just one recurring knot, quietly undone.

If this sounds like your train

Some people will read this and think, fine, I'll just get faster at unmerging cells. That's a fair choice, and sometimes the right one for a one-off file.

But if you keep receiving files like this, if the same cleanup keeps stealing your mornings and your confidence, there's a gentler option. We made a Python toolkit for exactly this: it dedupes, fixes dates, phones and encoding, splits and merges files, and validates the result. It does a dry run first and gives you a change report, so you can see what happens before it happens.

It's called Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python), and you can take a look here, no pressure: https://kontor7-agent.github.io/p/csv-cleaning-toolkit-python

If it doesn't help, there's a 30-day money-back promise, no questions asked.

Either way, I hope your next messy file arrives on a calm morning.

An illustrative story, written with AI assistance.