Phil Higginson, ISM Consultant
phil.higginson@isminc.com
For most independent schools, July 1 marks the start of a new fiscal year. Somewhere in that same stretch of summer, the database rolls forward with it. Graduating seniors become alumni. New students become current students, and their parents become current parents. The parents whose youngest just graduated become parents of alumni. Grandparents shift categories. A few trustees roll off the board, and a new set of families arrives to take their first walk through the front door.
On the surface, that's a technology task. A batch of field updates, everyone moves on, and the office turns its attention to fall.
I'd gently push back on that framing. I've watched the same thing happen more than once. A school can update every record correctly and still lose the relationship story.
That's the part I want to talk through here. The database is not the relationship. It's the school's best attempt to see the relationship clearly. And every summer, in the space of a single rollover, a lot of what the school can see either gets preserved or quietly gets flattened.
Before the Database Changes, Capture the Year That Just Ended
Here's the first place things get lost, and it happens before a single record moves.
Most of us report giving by constituent groups, and those groups (current parents, alumni, parents of alumni, grandparents, trustees, former trustees) are exactly the categories that change during rollover. So the timing of the change matters enormously.
If a parent made a gift this past year as a current parent, you want that gift reflected that way before they become a parent of alumni. If a trustee gave while still serving, you want it captured as trustee giving before the record reclassifies them as a former trustee. The same holds for grandparents, alumni, and everyone in between. Once the database steps forward, reconstructing who someone was at the moment of the gift gets harder than it needs to be. The school ends up creating confusion for itself that a little sequencing would have prevented.
Some of the more sophisticated systems make this easier. If your database lets you date each constituency, marking when someone started and stopped being a current parent, a trustee, or a grandparent, you can recreate any prior year's picture on demand, and the rollover stops threatening your history. A lot of schools either don't have that capability or aren't using it fully. Either way the principle holds: know how your system tracks these transitions, and update those fields on purpose during rollover instead of letting the categories quietly overwrite themselves.
Clean rollover protects clean reporting. And clean reporting is how a school understands its own philanthropic community with any real accuracy.
This Should Not Be One Department’s Job
In a lot of schools, technology owns the rollover. From a systems standpoint, that's completely reasonable. From an advancement standpoint, it's not enough on its own, and the reason is worth sitting with, because it's the whole game.
No single team can see the full relationship. Each of us only holds a piece of it.
Admission knows which siblings are entering and which families are already connected. The registrar knows who left before graduation and shouldn't be treated as a clean-exit senior. Technology knows how the fields and codes are actually going to behave when they change. And development knows which of these relationships drive giving history, stewardship, and the year ahead. Put those four vantage points in the same room and the database stops being a system of record. It becomes a shared, accurate map of the community.
That collaboration is what lets you catch the things that quietly go wrong. The new parent who's already in the system as an alum. The family that already has a child enrolled. The grandparent connected to the wrong grandchild. The two records that should have been one. Small details, every one of them. And small details are precisely what make advancement work feel personal instead of generic.
New Families Deserve More Than a Contact Record
July is also the best window all year to actually get to know the families walking in.
Not in a way that oversteps. The goal was never to collect information for its own sake. The goal is to understand a community well enough to build honest relationships with it. A simple new-family mini-profile does most of that work:
Understand New Families Early
A new-family mini-profile
Parent names, including maiden names where they apply
Grandparents, and how they connect to the student and adult child
Sibling and extended-family ties already in your community
Alumni status and any prior school connection
University affiliations and professional background
Potential volunteer and philanthropic interests
None of that has to be complicated. It does have to be intentional, because the cost of skipping it is real and specific. Miss that a new parent is also an alum, or that a grandparent has a forty-year history with the school, and you can spend the first several months of the year treating a warm, known relationship like a cold one. That's not a data problem. That's a missed friendship. Good advancement work starts with seeing people clearly, and summer, before the year gets loud, is when you actually have the room to do it. It is a great deal easier to see a family clearly now than to repair a relationship you misread for a semester.
July Is Where Annual Fund Strategy Actually Begins
The annual fund may not feel urgent in July. That's exactly what makes July valuable.
Once school resumes, the pace changes fast, with events, openings, parent meetings, fall communications, and early asks all competing for the same hours. July hands you a quieter room to think in. It's the time to review giving history, relationship strength, engagement patterns, and capacity indicators, and to decide who needs a personal conversation, who belongs in a leadership strategy, which new families need early relationship-building, and which grandparents and parents of alumni deserve a real place in the year's engagement plans.
Segmentation is only ever as strong as the data underneath it. If the rollover was rushed or disconnected, the annual fund will feel it in October. You just won't know that's why.
Write the Checklist Now, and Write It Together
If I could get every school to do one concrete thing, it would be simple. Build a summer rollover checklist, and build it as a group.
Development, admission, technology, and the registrar should agree on what happens before rollover, during, and after: which reports get pulled, which constituent groups get reviewed, who owns each step, how exceptions are handled, and how family relationships get checked. Then document it as a plain procedure manual.
I know that doesn't sound exciting. But staff change, systems change, and institutional memory fades faster than any of us like to admit. A documented process is honestly one of the kindest things a school can do for its future self. It creates consistency, consistency creates confidence, and confidence frees the team to spend less time fixing preventable problems and more time on the relationships that actually move the mission.
The Larger Point
July rollover isn't really about what people are called in the database. It's about whether the school can still see the relationship clearly after the category changes.
A current parent becomes a parent of alumni, but the relationship doesn't end. A senior becomes an alum, but the family's whole history still matters. A grandparent shifts categories, a trustee rolls off the board, and in both cases the connection, and the obligation to steward it well, carry right on. Every one of those is a transition in a living relationship, not a conclusion. The database's job is to preserve that continuity, not to overwrite it. And the continuity worth keeping isn't only who gave what. It's the texture of a student's actual years: the courses and teachers, the seasons and stage productions, the awards and the clubs. Hold onto that, and you can one day speak to an alum as someone you remember rather than a name you're soliciting.
So before the school year gets fully underway, it's worth slowing down and asking one question:
Are we simply rolling records forward, or are we protecting the relationship story of our school community?
I'll be honest. Every school I talk to does this a little differently, and I keep learning from the differences. So I'd genuinely welcome your notes. How does your school handle summer rollover and new-family research? Is it one department's job, or a shared effort across advancement, admission, technology, and the registrar? What have you figured out that the rest of us haven't?
Reach out anytime. I'm always glad to compare notes, and I usually come away with more than I brought.
– Phil Higginson, phil.higginson@isminc.com
