CSV Dates Day and Month Swapped? The Corridor Chairs

2026-10-30

You are sitting on a child-sized plastic chair outside Room 4B. It is 17:20 on a Tuesday. Parents' evening is running ten minutes late, and the corridor smells of floor polish and wet coats.

Your phone buzzes. It's a client, and it's polite, which is worse.

"Hi Priya, quick question on the hours summary. It shows work on 3 November. We were closed that day. Could you check?"

You open your own report on the tiny screen. You stare at it. The dates look fine. Then you scroll and find a line for 11 March. You were on holiday on 3 November, and you know you didn't work in March at all that week.

Then it clicks, slowly and unpleasantly. 03/11 was read as 11 March, and 11/03 as 3 November. Day and month have been swapped.

The knot you know

The export came out of your time tracker as a CSV. Your laptop is set to one date habit. The tracker had another. Somewhere between the download and the spreadsheet, the dates that could be read both ways got read the wrong way. The ones like 25/11, which can only be one thing, came through fine.

That's the cruel part. Half the file looks right.

The monthly totals were built on those dates. So some hours landed in the wrong month, a few sit on days that never happened, and your tidy pivot table is quietly wrong.

You already sent that report. Yesterday. With a little "all good on my side!" at the bottom.

It's a small embarrassment, and it's very specific. It isn't a disaster. It's the feeling of being a professional who doesn't quite trust her own numbers.

What it quietly costs

You think about what happens next, because you can't help it.

Tonight you will open the file again and try to fix it by hand. You'll sort by date, squint at rows, and compare against your calendar. You'll change a few, then wonder whether you changed the right ones.

Tomorrow you'll write an apology email that sounds calm and sure of itself. You'll rewrite it twice, because you don't want to sound careless, and you are not careless. You just got handed a file that looked right.

And then, next month, the same export will arrive, and you'll have to remember what went wrong. You will remember only that it's something to do with dates.

The real cost isn't the hour of fixing. It's the small, steady doubt: can I put my name under this?

The door opens

"Priya? We're ready for you."

You put the phone away. You spend six good minutes talking about reading levels and a friendship that's going fine. You walk back out into the corridor lighter than you walked in, because a teacher just said something kind about your child, and for six minutes nothing else existed.

On the bus home you do something different. You don't open the spreadsheet. You think about what you actually want.

You don't want to become a person who understands date formats. You don't want a weekend course on regional settings. You want to drop in the file and have the dates come out as real dates. You want to see, in plain words, what changed. And you want the original left alone, so that if something looks odd you can go back.

That's all. It's a small wish. But it's the difference between "I think this is right" and "I checked, and here's the list."

A different Tuesday

Picture the same week, with that wish granted.

The export lands in your downloads folder. You run it through a cleaning step you set up once. It takes a moment. It gives you a tidy file and a short report: these rows were fixed, these were already fine, these two look odd, please check them yourself.

You glance at the two odd ones. You know straight away that one is a typo and one is a genuine Sunday. You sort it out in half a minute.

The report goes to the client with correct dates. Nobody writes back. Nobody asks about the 3rd of November. Your inbox stays gloriously dull.

And you are in the corridor of Room 4B, or the supermarket queue, or wherever your Tuesday takes you, without a small cold feeling in your stomach.

If this sounds like your file

A swapped date is a very ordinary problem. It happens when a tool, a laptop and a country disagree about what 03/11 means. It says nothing about how careful you are.

If you work with CSV or Excel exports often and want to stop fixing them by hand, there's a small Python toolkit built for exactly this kind of chore. It cleans dates, duplicates, phone numbers and encoding, and it can split, merge and validate files too. It has a dry-run mode, so you can see what would change before anything does, and it writes a change report afterwards. It does not replace your own judgement on the odd rows, but it gives you a clear list to judge from.

You can look at it here: Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python). If it doesn't help, there is a 30-day money-back promise, no questions asked.

For tonight, maybe just go home, put the kettle on, and fix the file once, calmly. The 3rd of November was a good day off.

An illustrative story, written with AI assistance.