Posting Backwards From a Birthday
A birthday card that arrives two days late is a small, specific disappointment, and it is almost always caused by the same mistake: deciding when to post rather than working out when to post.
Those sound identical. They are not. One starts from today and hopes; the other starts from the date on the calendar and works backwards, which is the only method that reliably lands.
The last safe posting day
Take the slow end of the range from the delivery estimator, never the fast end, and add 3 business days of slack — the ranges are typical, not promised.
| Where it is going | Post this far ahead | In calendar weeks | If you pay for priority |
|---|---|---|---|
| Same region (nearby towns) | 6 business days | 1.2 weeks | 5 business days |
| Neighbouring region | 7 business days | 1.4 weeks | 6 business days |
| Across the country | 9 business days | 1.8 weeks | 6 business days |
| Another country | 24 business days | 4.8 weeks | 13 business days |
So a card going across the country wants 9 business days — about 1.8 calendar weeks. One going abroad wants 24 business days, which is 4.8 weeks, or the better part of a month.
Business days are the trap
Every number the estimator gives is in business days, and a child counting on a calendar is counting calendar days. The two diverge fast: 6 business days is 8 calendar days, and 21 business days is over 4 weeks.
Roughly, multiply business days by 1.4 to get calendar days. Do that before writing anything on a calendar, and the card stops being late.
Why the slow end and not the middle
The cost of the two mistakes is not symmetrical. A card that arrives four days early sits on a shelf, which costs nothing. A card that arrives two days late is the thing the birthday is remembered for.
Planning to the slow end makes the first mistake and never the second, and the first mistake is free.
The dates that break everything
December. The whole system runs heavy from late November, and the 21-day end of the international range stops being the pessimistic case and becomes the realistic one. Post Christmas cards abroad in November.
Public holidays at either end. A letter abroad passes through two countries' holidays, and a country you have never thought about having a long weekend is a genuine and invisible delay.
The last week of a school term, if the card is going to a school rather than a house. Arriving after everyone has gone home is the same as not arriving.
Working an example
A birthday on the 20th, a friend in another country, standard mail.
Slow end: 21 business days. Slack: 3 more. Total 24 business days, which is about 34 calendar days.
Count back 34 days from the 20th and post it then — about five weeks earlier, so somewhere in the middle of the month before. Write that day on the calendar as a task, not as a vague intention for "early next month".
When you have left it too late
Three honest options, in order of preference.
Pay for speed. Priority cuts the same-country journey to 2–3 days and the international one to 6–10. This is what the extra money is for, and it buys most on the longest journeys.
Send something on the day and post the real card behind it. A message on the morning and a letter a fortnight later is two nice things instead of one late one.
Say so in the card. "I'm sorry this is late, I mis-counted the days" is charming from a child and costs nothing. Pretending otherwise is not.
The habit that removes the problem
Put the posting dates in the calendar, not the birthdays. Everybody already knows when their friends' birthdays are; nobody knows when to post, which is the piece of information that actually needs storing.
One evening a year with a calendar, a list of friends and the estimator settles every card for the next twelve months — and it is a genuinely good thing for a child to do themselves, because the arithmetic is easy and the result is visibly theirs.
Where the date is decided at the other end
A postmark is the date it entered the system; delivery is the date it lands. Only the second one is a birthday, and nobody at the far end sees the first.
Worth knowing because "I posted it in time" is true and irrelevant. If the card has to be opened on a day, the plan has to be built on the delivery date, which is why every number in this guide is the slow end plus slack rather than an average.
A calendar you build once
Sit down with a list of everyone a child writes to, their distance band from the estimator, and the dates that matter. For each one, subtract the posting lead time and write that date down.
The output is a short list — perhaps eight or ten dates across a year — of days on which something has to go in a postbox. That list is far more useful than a list of birthdays, and almost nobody keeps one.
Two refinements worth the extra minute. Put a reminder three days before each posting date, because a card has to be bought and written before it can be posted. And mark December separately, since the whole system slows and the lead times in the table stop being conservative.
Done once in an afternoon, it turns the most common small failure in a child's correspondence into something that simply does not happen any more.
The version for a child who wants to do it themselves
Three questions, in order. When does it need to arrive? How far is it going? What does the estimator say the slow end is?
Then count back that many working days on a calendar, add a few for safety, and circle the day. The whole method fits on an index card, and a child who works it out once will use it for every card they send afterwards — which is a more durable result than an adult remembering on their behalf.