Most small churches do not have a records problem. They have a records opinion, held loosely by whoever has been around the longest, and never written down. Someone remembers that giving records should be kept “a while.” Someone else is fairly sure background checks get shredded eventually. The filing cabinet in the closet holds minutes back to a year nobody can name, because throwing them out felt like a decision no one wanted to make alone.
A retention schedule fixes this not by making the church more careful, but by making the decision once instead of every time. It is one page: a list of record types, how long each is kept, and where. Write it in an afternoon, and the filing cabinet stops being a monument to indecision and starts being a system someone can actually run.
Start with the records you already have, not the ideal list
It is tempting to open a browser tab, find a denominational retention guideline, and copy it wholesale. Resist that until you have looked at what is actually in your office. Open the filing cabinet, the closet, the shared drive folder nobody has cleaned out. Make a plain list: giving records, meeting minutes, background-check results, pastoral care notes, personnel files, insurance policies, building records, old bulletins. Your schedule only needs rows for categories you actually hold. A generic template with nineteen rows, four of which apply to you, is a worse starting point than your own eight.
Assign each category a plain reason, not a guess
Every row on the schedule should answer “why this long” in one clause, because a number with no reason attached gets argued with later, and a number with a reason attached does not. Giving records are commonly kept seven years because that lines up with how long the IRS can look back at a donor's return. Background-check results often follow a state-specific window tied to when a volunteer's status was last reviewed. Meeting minutes are frequently kept permanently, because they are the institutional memory of decisions the church made and may need to point back to. None of these are universal — check what applies where you are — but each should have a reason a volunteer could repeat back to you, not just a number someone remembered from a conference.
If you genuinely do not know the right number for a category, write “confirm with counsel” in that row rather than guessing and moving on. A schedule with one honest gap is more trustworthy than one that fills every row with confidence it has not earned.
Separate what is sensitive from what is merely old
Not every record on the schedule needs the same handling once its time is up. A stack of old bulletins can go in the recycling bin. A background-check result or a pastoral care file cannot — those need to be shredded, or deleted in a way that does not leave a copy sitting in a downloads folder. Mark these categories on the schedule itself, in a column or a note, so the person doing the clearing-out does not have to guess which pile is which. Pastoral care records deserve the strictest handling of all: they carry details a person shared in confidence, and the schedule should say plainly who is allowed to see them while they exist and who destroys them when the time comes.
Write the schedule as one page, not a policy manual
The number one reason retention schedules get written and then ignored is length. A twelve-page policy with definitions, exceptions, and a preamble reads like something to file away and never open again — which is exactly what happens to it. A single page with a short table does the opposite: it can be taped inside the filing cabinet, handed to a new volunteer in thirty seconds, and actually consulted the next time someone wonders whether to keep a box or toss it. If your first draft runs past one page, the fix is usually to cut explanation, not rows. State the rule. Save the reasoning for a conversation, not the document.
Build in a yearly review, not a one-time project
A schedule written once and never revisited will eventually be wrong — a new state law changes a window, the church starts holding a record type it never had before, or someone realizes a seven-year rule should have been ten. Pick a month, tax season is a natural one since giving records are already on everyone's mind for year-end giving statements, and put a fifteen-minute review on the calendar. The review is not a rewrite. It is a read-through, a check of anything that changed, and a note of anything new. This is the same instinct behind keeping a light weekly rhythm for admin work generally: small, regular attention beats a once-a-decade overhaul every time.
Apply the schedule to what is already piled up
Once the schedule exists, the backlog stops being a scary undifferentiated mass and becomes a sorting job with a clear answer for each pile. This is close cousin work to a database cleanup — both are about applying a rule you have already decided on to a mess you inherited, rather than deciding case by case as you go. Go category by category. A box of minutes from 2011 is easy once the schedule says minutes are kept permanently: it goes in the permanent archive, not the shredder, and not a maybe pile. A box of unlabeled giving envelopes from nine years back is equally easy once the schedule says seven years: it goes.
The point of doing this pass is not to end up with an empty closet. It is to end up with a closet where every remaining box is there because a written rule says so, not because someone was afraid to decide. Giving records are the category people hesitate over most, since they touch money and trust at once; if you want the fuller case for handling them with care rather than suspicion, tracking giving that respects the giver is worth reading alongside this one.
Let the software carry what it can, and no more
A retention schedule is a decision about paper, boxes, and files as much as it is about anything digital, and no piece of software makes that decision for you. What a system like SundayBridge can do is keep the records it holds organized enough that applying your schedule is a quick check rather than an excavation — giving history attached to a person rather than scattered across spreadsheets, year-end statements generated and ready to print instead of assembled by hand every January, pastoral care cases kept in one place with the history that matters. The schedule still has to be yours: what to keep, for how long, and who is allowed to see it. The software's job is only to make sure that once you have decided, finding the record to act on is not the hard part.
Keep it short, keep it visible, keep it honest
The best test of a retention schedule is whether a volunteer who has never seen it before could open the document, find the row for “background checks” or “giving records,” and know what to do without asking anyone. That is a low bar on purpose. A schedule nobody can read under pressure is a schedule nobody follows under pressure, and the whole point was to stop relying on someone remembering the right answer. Write it plain, post it where the filing happens, and revisit it once a year. That is the entire job.