CSV Full of Trailing Spaces and Mixed Dates? The Lunch Break Fix

2026-10-14

12:35, and the Sandwich Is Still in Its Wrapper

The export finished downloading at 12:20. You opened it expecting a quick look. Fifteen minutes later, the sandwich is still in its paper, and you are zooming into column D.

One row says 03/04/2026. The next says 2026-04-03. Another says 3 Apr. Somewhere further down, someone typed "April 3rd" into a field that was never meant to hold words.

Is 03/04 the third of April, or the fourth of March? You honestly don't know. The system that made this file doesn't seem to know either.

Let's call you Mara. You look after the operations side of a small online shop, and the report is due to your boss at two. It's the sort of job that was supposed to take ten minutes.

The Space You Can't See

Then the lookup fails. A customer named "Jonas Keller" is definitely in the list. You can see him. But the sheet insists he isn't there.

You click into the cell and press the End key. The cursor jumps one character past the final letter. There is a space there. A trailing space, invisible, patient, and completely ruinous.

You fix that one. Then you wonder how many others there are. You scroll. Four hundred rows. Maybe six hundred. You can't tell, because the problem is made of nothing.

So you start doing what everyone does. Click, delete, click, delete. Then a find-and-replace that fixes some of it and quietly breaks something else. Then a column of helper formulas, then a second column to clean the first one, then a third to check the second.

The sandwich stays wrapped.

What It Quietly Costs

Nobody puts this on a timesheet. It doesn't look like work. It looks like a person muttering at a spreadsheet.

But it costs something. It costs the lunch break, and the calm you wanted for the afternoon. It costs a small, nagging doubt: did I fix everything, or only everything I noticed?

That doubt is the worst part. You hand the report over at 1:55 and say "should be fine." Then you spend the meeting watching the screen, waiting for someone to ask why two customers appear twice.

And there's a quieter feeling underneath it. It's the sense that a competent person shouldn't be doing this by hand. That there must be a better way, and that everyone else must already know it.

They mostly don't. Plenty of capable people are fixing the same dates, row by row, right now.

The Colleague Who Wasn't Even Trying

The next week, a developer friend stops by your desk. Call him Tobias. He sees the familiar mess on your screen: the half-selected column, the three helper columns, the look on your face.

"Is that the same export?" he asks.

It is.

He doesn't lecture you. He doesn't say "you should learn Python." He just says that cleaning a file like this is a solved problem. It doesn't need to be done by eye, and it doesn't need to be redone every month. A small, careful routine can handle it and tell you exactly what it changed.

That last part is what stays with you. Tell you exactly what it changed. Not "trust me, it's fine," but a list you can read.

A Different Kind of Monday

Picture the next export. It arrives on Monday morning, around nine, with your coffee still too hot to drink.

You drop the file in. You look at what would change before anything is touched. The spaces, the dates that all agree now, the two duplicate customers that were hiding in plain sight. A short report, written in plain words.

You check it. It makes sense. You accept it.

Then you close the file, and the coffee is a good temperature.

Nothing dramatic happened. That's the point. The knot that used to tighten at the sight of an export just isn't there. You eat lunch somewhere with a window, and the afternoon belongs to the work you actually wanted to do.

If This Sounds Like Your Lunch Break

Maybe you're not in an online shop. Maybe you're a freelancer with a client's messy file, or a bookkeeper's helper, or the one person who "is good with spreadsheets" and therefore gets everything. The scene changes, but the feeling is the same.

We made a small toolkit for exactly this. It's called Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python). It tidies dates, phone numbers, encoding and duplicates, can split and merge files, and checks the result. It runs a dry run first and gives you a change report, so you can see what it did instead of hoping.

If you recognise yourself in Mara's 12:35, you can take a look here. There's a 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

An illustrative story, written with AI assistance.