Build this pathway in your community
Traps to Laps was not designed perfectly on day one. It started with four kittens, a spreadsheet, and a gap nobody else was filling, and it changed as the work taught the team what was missing. Everything below is what we would tell a community starting now.
For the working detail underneath this plan — setup requirements, volunteer role descriptions, and the measures a chapter dashboard should track — see the chapter tools reference.
A phased plan for starting a local chapter
Phases 1 through 3 belong in place before a single kitten enters the program. Phases 4 through 6 build while the first cases move through the pathway.
- 1
Phase 1 · Before any animal enters
Define the program and its limits
- Write down the service area, the animals you will accept, and the animals you will not.
- Define alternative disposition pathways up front — TNR, return to owner, barn placement, partner referral — so a case that doesn't fit still has somewhere to go.
- Name a Program Director and at least one person who shares administrative ownership.
- Decide the local nonprofit, insurance, liability, and volunteer structure before operating.
- 2
Phase 2 · Before any animal enters
Secure medical and sterilization capacity
- Identify a competent Medical Lead, or a clearly defined escalation resource who answers when a Field Tech calls.
- Confirm reliable spay/neuter access and its realistic monthly volume.
- Arrange referral for care beyond field scope — emergencies, surgery, chronic conditions.
- Adopt standardized protocols for vaccination, deworming and parasite care, and wellness monitoring.
- 3
Phase 3 · Before any animal enters
Stand up the shared records system
- Choose one shared platform the whole team can reach — not a private spreadsheet on one person's computer.
- Create the core record types below and the fields each one needs.
- Set who can see and edit what before the first record exists.
- Train every Field Tech to enter and maintain their own records from day one.
- 4
Phase 4 · First few months
Build field capacity through apprenticeship
- Train Field Techs on competency, not hours — each skill is signed off when demonstrated.
- Give every tech an explicit safety stop: any tech may pause a task and escalate without penalty.
- Pair new techs with experienced ones on real cases before they carry cases alone.
- Equip each tech with a supply kit and a restock process.
- 5
Phase 5 · First few months
Secure downstream placement before intake grows
- Commit at least one adoption partner in writing before your first litter is ready.
- Establish the transfer standard: what medical, age, weight, and socialization state a partner expects.
- Build supported foster capacity — finders and community members fostering with a system around them.
- Set up a TNR or return pathway for cats who stay feral or aren't adoption candidates.
- 6
Phase 6 · Ongoing
Take the first cases, then measure and adjust
- Start deliberately small — a handful of cases you can fully document.
- Review dispositions monthly across the whole pathway, not just intake counts.
- Assess the environment around each case and address upstream sources through TNR.
- Delegate administration as volume grows, before the Director becomes the bottleneck.
The shared records system
Traps to Laps began on a private spreadsheet, and that single decision cost the program more rework than anything else. Information that lives with one person stops the work when that person is unavailable, and it can't follow an animal to a vet or an adoption partner.
The requirement is not a specific product. It is that information moves with the animal and can be reached by the appropriate team members. Set this up in Phase 3, before the first record exists.
What the system has to hold
Litter and animal record
One record per animal, linked to its litter and finder: intake date and location, estimated age, weight history, current caregiver, and current status in the pathway.
Medical Log
Every vaccination, deworming, treatment, weight check, and escalation, with the date and the person who performed it. This is the record that travels with the animal to a partner.
Field Tech assessment
The recurring check each tech submits per kitten — body condition, eyes, ears, coat, appetite, elimination, socialization progress, and concerns needing escalation.
Intake and eligibility record
The finder's report, the environmental assessment, the eligibility decision, and the disposition pathway chosen — including cases routed to TNR, RTO, or a partner instead of intake.
Supply and kit tracking
What each Field Tech has, what they used, and what they need restocked, so medical supplies never run out mid-case.
Partner and outcome tracking
Transfers, adoptions, TNR, RTO, and barn placements by partner, so the program can see which relationships are actually moving animals to outcomes.
Access rules to set first
- Field Techs can create and update records for the animals they carry.
- The Medical Lead can see and annotate every medical record.
- The Program Director and admin team can see everything and manage accounts.
- Access is granted to named, approved people — not shared logins or open sign-up.
- Finder and foster contact details are visible only to the people who need them.
Practices that keep it usable
- Every field visit gets an entry the same day, from a phone, in the field.
- Forms are short enough that a tired volunteer finishes them.
- One vocabulary for statuses so reports across the pathway actually add up.
- An animal's full medical history exports as one document for a vet or partner.
- A monthly review of dispositions by partner, so gaps surface early.
Start with the infrastructure, not the first litter.
The model is written to be adapted. Adoption partnerships, assessment protocols, and field support should be part of the infrastructure from the beginning rather than something a program figures out once kittens are ready.
- Assessment criteria and standardized care protocols
- Field Tech visit and support structure
- Foster agreement expectations and alternative pathways
- Adoption partner coordination
What a community needs before taking its first litter
A startup checklist — in place before accepting a first case:
- A defined intake and eligibility process, including alternative disposition pathways for animals that don't fit.
- Supported foster capacity — community members and finders willing to foster with a system around them.
- At least one trained Field Tech or equivalent field-support role.
- A competent Medical Lead, or a clearly defined medical escalation resource.
- Standardized care protocols and records.
- A shared information system the appropriate team members can actually reach.
- Reliable access to spay/neuter.
- Reliable access or referral arrangements for veterinary care beyond the program's field scope.
- At least one committed downstream adoption partner.
- A TNR (trap-neuter-return) or return pathway for cats who remain feral or aren't adoption candidates.
- A plan for administrative ownership and delegation, so the Program Director isn't the only operational hub.
Everything else — which software, the exact organizational structure, the funding mix, staffing — can be built locally, as long as these hold. Each community must also determine the appropriate nonprofit, insurance, liability, volunteer, and legal structure for its local program before operating. Additional Traps to Laps guidance in that area is still under development.
Measure the whole pathway
Intake volume is the easiest number to count and the least useful one on its own. Traps to Laps tracks disposition across the whole pathway:
- Kittens and cats currently in the program
- Animals transferred or “graduated” to partners
- Animals ultimately adopted
- Cats TNR'd (trap-neuter-return)
- Animals returned to owner, or RTO
- Animals placed through barn programs
Results are also tracked partner by partner through a Partner Pivot report. Success is not how many kittens entered the program — it's whether each one reached an appropriate outcome.
What we learned by building it
The current model was not designed perfectly on day one. It evolved through field use, and that evolution is part of the lesson.
- Start with a shared information platform instead of a private spreadsheet.
- Train Field Techs to enter and maintain their own information from the beginning.
- Build an admin team early — ideally the Program Director has one or two people helping build administrative structure.
- If a full admin team isn't possible yet, delegate intentionally rather than letting all administration accumulate with the founder.
- Establish a competent Medical Lead.
- Establish veterinary and adoption relationships before intake volume grows.
- Expect processes to change as the program learns.
Administration is the bottleneck, not the field work
Traps to Laps' current primary constraint on growth is administrative capacity and Program Director bandwidth. Funding is always a concern, but it isn't what limits the program today.
At its current volume, the program needs roles such as a Foster Coordinator, a Field Tech Coordinator, and additional medical support. A field model can work well and still stall if every decision, record, relationship, and coordination task flows through one person. Plan for administrative delegation before volume demands it.
Keep the name, adapt the operations
Communities using the model are strongly encouraged to retain the Traps to Laps name, paired with their region or city — for example Traps to Laps – [Region or City] — so programs can share a recognizable identity while adapting operations to local resources. This is a strong recommendation from the program's founder, not a franchise, license, or formal trademark agreement.
What has to stay the same, and what doesn't
Non-negotiable
- Upstream shelter diversion
- Defined intake, eligibility, and disposition processes
- Supported community and finder fostering
- Competent Field Tech support
- Standardized protocols and records
- Baseline medical care: vaccination, deworming and parasite care, wellness monitoring, sterilization
- A guaranteed escalation and referral pathway for medical care beyond field scope
- Genuine socialization for adoption candidates
- An appropriate return or TNR pathway for feral animals
- Committed downstream adoption capacity
- Assessment of the broader environment when relevant, including unmanaged community cats and chances to prevent future litters
- Shared information that moves with the animal and can be reached by the appropriate team members
Locally adaptable
- The exact software platform
- The exact administrative structure
- Specific veterinary providers
- Specific adoption partners
- How supplies are distributed
- Funding mix
- Geography and service area
- Staffing configuration
- Transportation structure
- Specific local organizational relationships
"I have the basic foundation set up — I'd love to help another community start this."