Why I Built a Logic Engine for "The Second Sunday in May"

If you’ve ever looked at a standard custody order, you know they weren't written by software engineers. They are written in a strange, legacy dialect of English that sounds like a logic puzzle.

"The Father shall have the child on Father’s Day, defined as the third Sunday in June, from 9:00 AM until 8:00 PM. In even-numbered years, the Mother shall have Thanksgiving from Wednesday at school dismissal until the following Sunday at 6:00 PM..."

As a developer, when I see "the third Sunday of [Month]" or "even-numbered years," my brain immediately starts mapping out Cron jobs and modulo operators. But for a parent trying to plan a family reunion three years out, these rules are a source of constant friction and potential conflict.

The Complexity of the "Nth-Weekday"

Automating a standard calendar is easy. Recurring every Monday? Simple. But co-parenting schedules are rarely that linear. Holidays often follow the "Nth-Weekday" rule (like Memorial Day or Mother's Day) or a "Closest to X" rule.

When I sat down to build the holiday rotation logic for CustodyTrac.com, I realized that hard-coding these holidays wasn't enough. Every family has unique traditions—maybe it’s a specific "Lake Weekend" that always happens on the second weekend of August.

The challenge wasn't just calculating the date for the current year; it was building an engine that could project these rules into the future indefinitely. By treating holiday rotations as a set of logical parameters rather than static entries, we can eliminate the "Who has the kids this year?" text message that so often leads to an argument.

Handling the "Alternating" Logic

The second hurdle is the alternating year toggle. Most courts default to a "Parent A gets Even, Parent B gets Odd" split for major holidays like Thanksgiving or Spring Break.

From a data perspective, this requires a robust way to handle overrides. A holiday schedule should sit as a layer above the regular recurring custody cycle. If it’s my weekend, but it’s the "Mother’s Year" for Labor Day, the system has to intelligently "punch a hole" in the regular schedule and prioritize the holiday rule without breaking the rest of the year’s flow.

Here is a simplified look at how we might think about calculating that "Nth" day programmatically:

// A simple helper to find the Nth occurrence of a weekday in a month
function getNthWeekday(year, month, dayOfWeek, n) {
    let date = new Date(year, month, 1);
    let count = 0;

    while (date.getMonth() === month) {
        if (date.getDay() === dayOfWeek) {
            count++;
            if (count === n) {
                return new Date(date);
            }
        }
        date.setDate(date.getDate() + 1);
    }
    return null; // For those rare "5th" Sundays
}

// Usage: Father's Day (3rd Sunday of June)
const fathersDay2024 = getNthWeekday(2024, 5, 0, 3);

Moving Toward "Set It and Forget It"

The goal of automating these rules is to reduce the "mental load" of co-parenting. When the calendar is the single source of truth—calculating alternating years and specific weekday rules automatically—there is no room for interpretation or "forgetting."

I built CustodyTrac.com to solve this specifically for parents who are tired of manual spreadsheets and expensive, clunky software. By providing a holiday rotation engine that handles the logic of alternating years and nth-weekday rules, we take the math out of the equation. This allows parents to focus on the transition itself, rather than the debate over whose turn it is.

We decided to make this entire platform free forever. We believe that the tools needed to keep the peace and stay organized for your children shouldn't be hidden behind a subscription paywall.

Try it free → https://custodytrac.com

How do you handle complex date logic in your own projects? Does the "Nth-weekday" rule pop up in your industry, or is it mostly a scheduling headache? I'd love to hear how others tackle these calendar edge cases.