My European Client Said Week 32. I Showed Up 6 Days Late.

The email from my client was polite. Suspiciously polite. "Hope your travel went smoothly — we've been looking forward to getting started. Looking forward to seeing you tomorrow!"

I was sitting in an airport lounge in Chicago, about to board a flight to Munich. Tomorrow was August 4, 2025 — a Monday. Week 32, just like we'd agreed.

Or so I thought.

I landed in Munich the next morning, checked into the hotel, put on my best business-casual outfit, and showed up at the client's office at 10am. The receptionist looked at her calendar, then at me, then back at her calendar. "Herr Chen? The kickoff was last Monday. They've been working for a week already."

Last Monday? Last Monday was... July 28. That's Week 31.

No. As it turns out, in Germany, under ISO 8601, August 4, 2025 is Week 32. But July 28, 2025 is also Week 32 — if you're using the US system where Week 1 starts on January 1.

I had just traveled 4,400 miles to arrive 6 days late to my own project kickoff.

Two countries, two "Week 32s"

Here's exactly what happened. My client and I had been emailing back and forth about scheduling. We agreed on "Week 32" as the kickoff date. Simple, right? A week number is a week number.

I opened my calendar, found Week 32 — which to me meant counting from January 1 as Week 1, the standard I'd always used — and saw it started on Sunday, August 3. So I booked a flight arriving Monday morning, August 4. First meeting at 10am. Everything lined up.

My client, using the ISO 8601 standard that's standard across Europe, had a completely different mapping. Under ISO 8601, Week 32 of 2025 started on Monday, July 28 and ended on Sunday, August 3. They had been in the office all week waiting for me while I was still in Chicago, thinking I had another week.

We weren't just off by a day or two. We were off by six entire days. Two different weeks, two different start dates, two different sets of people wondering where the other was.

The exact mechanics of the gap

I want to explain precisely how this happened, because if you've never dealt with international scheduling before, the mechanics are not obvious.

In the US system, Week 1 is the week that contains January 1. It doesn't matter what day of the week January 1 falls on — that week is Week 1. Period. So if January 1 is a Thursday, Week 1 runs from Sunday, December 29 (of the previous year!) through Saturday, January 4. The first Sunday-to-Saturday span that contains January 1.

Under ISO 8601, Week 1 is the week that contains the first Thursday of the year. This rule exists to make sure that Week 1 always has at least 4 days in the new year. If January 1 falls on a Friday, Saturday, or Sunday, it's still considered part of the last week of the previous year.

Here's the real kicker: in 2025, January 1 was a Wednesday. Under the US system, Week 1 started on Sunday, December 29, 2024 and ended on Saturday, January 4, 2025. Under ISO 8601, Week 1 started on Monday, December 30, 2024 and ended on Sunday, January 5, 2025.

That one-day difference in Week 1 cascaded through the entire year. By Week 32 in August, the US and ISO weeks were offset by nearly a full week. Same number. Different days.

The conversation I had to have

I'll never forget walking into that project room. Everyone was already there. Whiteboards covered in diagrams. A sprint board with tasks already assigned. Coffee cups from the previous week's sessions still on the side table.

I had to explain — in front of the client's entire project team — that I had shown up a week late because I used a different definition of "week" than they did.

They were gracious about it. Germans are practical people. The project lead — a guy named Marcus — actually laughed when I explained what happened. "Ah, the American week system. We have this problem with our US suppliers all the time. You are not the first."

Somehow that made me feel worse. This was a known problem. It had happened before. To other people. And I had walked right into it like it was a brand new discovery.

We recovered the project timeline. We extended the engagement by a week to make up for the lost time. But here's the part that still stings: when it came time to renew the contract six months later, the client mentioned "some initial coordination challenges" in their feedback. They renewed anyway, but I know that "coordination challenges" was a polite way of saying "you showed up a week late to your own kickoff because you didn't understand international standards."

What I do now before every international project

After that experience, I built a small pre-flight checklist for any project that involves people in other countries:

1. Never assume "week number" means the same thing to everyone. If a client says "Week 32," I immediately ask: "Which calendar system are you using? ISO 8601 or US standard?" If they look confused, that's actually a good sign — it means I need to get specific.

2. Always confirm the actual calendar dates. Now I reply with something like: "Just to confirm — Week 32 on my calendar maps to August 4-10. Is that the week you have in mind?" It takes 15 seconds and has saved me at least three times since.

3. Use a tool to cross-check. I keep weeknumber.cc bookmarked. Before I send any project schedule, I plug the dates in and check them against both ISO and US standards. If they don't match, I flag it immediately.

4. Include both the week number AND the date range in every project doc. Instead of writing "Sprint 3: Week 32-33," I now write "Sprint 3: Week 32-33 (ISO: Aug 4-17, 2025)." It's redundant for people who share my week system, but it's a lifesaver for everyone else.

The thing that bothers me most about this whole experience is how preventable it was. This isn't some obscure edge case. The gap between ISO and US week numbers exists every single year. Billions of dollars of international business happen every day, and somewhere in a conference room right now, two people are looking at "Week 32" on a slide and picturing two completely different weeks. I used to be one of them.