Skip to content
Book a demoStart your free trial
Registrar how-to

Clearing a registration backlog: a plan for registrars and boards

The short answer

A registration backlog clears when the registrar and the board treat it as a project rather than a personal failing: count and sort everything that is waiting, tell members the real position, work through it in a set order of priority, and fix the cause so the queue does not refill. The board's job is to give the registrar a plan, a deadline it can meet and help with clear limits.

Dusty Mumphrey
Founder, Breed Ledger. Senior engineer. Active multi-species breeder.

Published 7 min read

Illustration of a tall, leaning in-tray stack of registration applications on the left, a green arrow, and a short neat out-tray stack on the right topped by an approved certificate with a green check mark.

This plan is for the registrar, secretary and board of a breed club, society or registry, of any species, whose registrations, transfers or corrections are waiting longer than members expect. By the end you will have a way to size the backlog, a message for members, an order of work, a policy for temporary proof, and the changes that stop it coming back.

How do you find out how big the backlog really is?

Count every item that is waiting, by type and by age, before deciding anything else. A backlog that has not been counted always feels larger, or smaller, than it is.

  1. Gather every inbox. Post, email, the registry's online form, messages sent to officers' personal accounts, and anything handed over at a show.
  2. Log each item once. One line per application: date received, member, type, and what is missing.
  3. Sort by type. New registrations, transfers of ownership, corrections, and queries.
  4. Sort by age. Under a month, one to three months, over three months.
  5. Mark incomplete items. Missing fees, signatures, parentage details or photos.

For the fictional Copperleaf Gecko Society, the count might show that most of the queue is hatchlings from a few busy clutches, with a smaller group of transfers for geckos already sold. That changes the plan: the transfers are urgent, and the hatchling registrations can be batched.

Tip

Keep the log in a place at least two officers can open. The backlog should not depend on one person's inbox.

What should the board tell members while the backlog clears?

Tell members the truth, in one public message, with a date for the next update. Silence produces more emails and calls, and each one takes time away from clearing the queue.

Registries that have faced this have said so plainly. The North American Working Australian Kelpie Registry told members that some submissions had been delayed for several months, and that post was the most dependable way to reach it [1]. The American Morgan Horse Association published its current processing time of three to six weeks during a software change [2].

A good update covers:

  1. What is happening. A backlog exists, and roughly how large it is.
  2. Why. In one sentence, without blaming a volunteer.
  3. What members should do. Usually: do not resubmit, and check that the application is complete.
  4. What comes first. The order of priority the board has agreed.
  5. How to reach the registry. The one channel that is being watched.
  6. When the next update comes. A date, and keep it.

Which registrations should the registrar handle first?

Handle the items that block someone else first, then the oldest, then batch the simple ones. A clear order also gives the registrar a fair answer when a member asks why theirs is not done.

  1. Transfers tied to a sale. A new owner is waiting for papers, and a buyer's complaint reaches the board fastest.
  2. Items that block other work. A parent that must be registered before its offspring can be.
  3. The oldest complete applications. Fairness by date received.
  4. Simple registrations in batches. For Copperleaf, hatchlings from the same clutch can be checked and registered together.
  5. Incomplete items. Send one message listing everything missing, then move on.
  6. Disputed or complex cases. Parentage questions or corrections that need a board decision go to a separate list, reviewed at a set time.

Should the club issue temporary proof of registration?

It can, if the club's rules allow it and the board writes a short policy first. Temporary proof helps a member who needs to show that an application is pending, for example to complete a sale, but it carries risk if it looks like the real thing.

A temporary proof policy should cover:

  1. Who can issue it. The registrar, or a named deputy.
  2. When. Only for complete applications with the fee paid.
  3. What it says. That the application is pending, the date received, and that it is not a registration certificate.
  4. How long it lasts. An expiry date, after which only the certificate counts.
  5. What happens if the application fails. The temporary proof is void, and the member is told in writing.
Warning

Temporary proof must never look like a certificate. Use a different title, layout and wording, so nobody can pass it off as a completed registration.

How does the board stop the backlog coming back?

Find the cause and change it. Clearing the queue without fixing the cause only resets the clock.

Common causes include:

  1. One person does everything. When the registrar is ill, busy or stepping down, the queue stops.
  2. Seasonal peaks. Registrations arrive together after the breeding or hatching season.
  3. Unclear rules. Members send incomplete applications because the requirements are hard to find.
  4. A system change. The American Brahman Breeders Association reported unexpected delays in its 2018 move to a new system, which left an unforeseen backlog [3].

Fixes the board can adopt:

  1. Train a second person. No registry should depend on one volunteer. The Hebridean Sheep Society's job description already asks its Registration Secretary to keep notes on where all society data held as Registration Secretary is kept, and to give them to two other trustees [4].
  2. Publish a checklist for a complete application. Fewer incomplete forms means fewer round trips.
  3. Plan for the peak. Add help before the busy season, not after.
  4. Review the queue at every board meeting. A count by type and age, read into the minutes, makes a growing backlog visible early.
  5. Plan any system change around the queue. Clear or freeze the backlog before switching, and never switch during the peak.

If the board is weighing new software for the registry's records, the registries page describes what Breed Ledger offers registries.

Key takeaways

  • Count and sort the backlog by type and age before making any promise to members.
  • One honest public update, with a date for the next one, saves more time than it costs.
  • Work in a fixed order: sale transfers and blocking items first, then the oldest, then batches.
  • Temporary proof needs a written policy and must never look like a certificate.
  • Fix the cause, whether one person, a seasonal peak, unclear rules or a system change.

Frequently asked questions

What causes a registration backlog in a breed club?

Common causes include a single volunteer doing all the work, a seasonal peak, unclear application rules, and a change of system. The American Brahman Breeders Association, for example, reported a backlog after its 2018 move to a new system [3].

Should the registrar work through the backlog in date order?

Mostly, but not strictly. Transfers tied to a sale and items that block other registrations should go first, then the oldest complete applications.

Is it safe to issue temporary proof of registration?

It is lower risk when a written policy limits who issues it, sets an expiry date and makes it look nothing like a certificate. Without a policy, it can be mistaken for the real thing.

How often should the board check on the registration queue?

At every board meeting. A count of waiting items by type and age, recorded in the minutes, shows a backlog forming before members notice it.

Sources

  1. North American Working Australian Kelpie Registry, "Registration Information" (undated), https://kelpiesinc.com/wp/registration-information/ (external site), checked 2026-11-03.
  2. American Morgan Horse Association, "AMHA Participates in Software Training; Delays Expected" (26 April 2017), https://morganhorse.com/media-events/news/detail/10204 (external site), checked 2026-11-03.
  3. The Brahman Journal, "ABBA Registry Update" (28 June 2018), https://brahmanjournal.com/cattle/abba-registry-update (external site), checked 2026-11-03.
  4. Hebridean Sheep Society, "Registration Secretary Job Description" (approved by Trustees, February 2016), https://Hebrideansheep.org.uk/Documents/Registration%20Secretary%20Job%20Description.pdf (external site), checked 2026-11-03.
Share this articleLinkedIn (external site)Email

About the author

Dusty Mumphrey

Written by

Dusty Mumphrey

Founder, Breed Ledger. Senior engineer. Active multi-species breeder.

Dusty builds Breed Ledger and breeds more than one species himself. He writes about why club records matter and what he is building next.

About Breed Ledger

Registries

See how Breed Ledger works for registries.

Registrations, certificates and records, run from one place.