A birthday & fiesta gift calendar for family back home

The problem is never the caring. It’s the calendar. From abroad, dates arrive faster than the box does, and a remembered occasion that ships too late turns into an apology. The fix is not a better memory; it is a structure: list the recurring occasions once, convert each into a ship-by date, and work backwards. This page is that structure, not a list of dates. The dates are the family’s, and town fiestas in particular are not a thing this page can state for you.

Two kinds of occasion, two different moves

The reason a single planner works for events as different as a fiesta and a graduation is that they split cleanly into two types, and each type has exactly one move. Mixing the two (treating a fixed date as if it needed recalculating, or treating a count-back date as if the occasion date were the deadline) is where the calendar quietly fails.

Fixed dates — set once. A town fiesta and a wedding anniversary fall on the same date every year. The work is one-time: write the family’s actual date down once and it never needs deciding again; only the ship-by offset is reapplied annually. The fiesta date is specifically the family’s town’s: patron-saint fiestas differ town to town and barangay to barangay, so there is no national date to fill in here, only theirs. The value of the “fixed” group is precisely that, once captured, it stops being something to remember at all.

Count-back dates — convert each time. Birthdays and graduations are known well in advance, but the date itself is not the useful number. The ship-by date is, and it is the occasion minus transit minus buffer. The trap is that the occasion date feels like the deadline, so the box gets sent toward it rather than ahead of it, and arrives after. That subtraction is the same one the Christmas-timeline page sets out in full, and it applies to every count-back occasion. Graduations simply sit further out and can be planned a whole term ahead.

The per-recipient drift the calendar fixes

There is a second failure the structure quietly solves: with several recipients and several occasions a year, the same person can be sent the same thing twice while another is missed entirely, because each box is decided in isolation without a view of the year. A per-recipient line (what went to whom, when) turns “what should I send” from a memory test into a glance, and is the part of the structure that most repays writing down. The occasions are the calendar; the per-recipient history is what keeps the calendar from repeating itself.

Why no dates are filled in

A planner that pre-filled fiesta dates would be wrong for almost everyone using it, because there is no single fiesta date to fill. It is local by design, and asserting one would be inventing data the page cannot have. The same restraint covers transit: the ship-by column says “count back using the courier’s estimate” rather than a number, because that number is the courier’s to quote and shifts seasonally, and is owned by a single source-of-truth page rather than re-stated here. The structure is asserted; the dates and the transit are not, because asserting either would be claiming to know what the page does not.

How to read this

This is a framework to fill, not a calendar of asserted dates: no fiesta or occasion date is stated, because those are the family’s and town-variable, and the back-calculation is cross-linked to a single source of truth rather than duplicated. The page is seasonal-recurring and re-checked yearly. The whole method is three habits: capture the fixed dates once, convert every count-back occasion into a ship-by date ahead of time, and keep a per-recipient line so the year does not repeat itself.

The ship-by math lives on the Christmas box timeline; this applies it across the year. For what goes in each box, see what to send your parents and pasalubong that survives the box.