Shelter software for intake to adoption, not five spreadsheets.

Animal shelter management software keeps one record per animal from the day it arrives to the day it leaves, and every step in between. Intake details, medical history, foster placements, volunteer work, adoption applications, and the final outcome all sit on that one record, so staff, fosters, and volunteers work from the same current information instead of rebuilding it from paper files, spreadsheets, and inboxes.

Shelter software follows an animal from intake to adoption: who arrived, what care they need, where they are fostered, who applied to adopt them, and how the placement turned out. Kennel software follows a paid stay: a booking, a kennel, daily care sheets, and checkout. The two overlap on animal records and vaccination checks, but boarding software does not cover adoption, and shelter software does not cover boarding. If your operation boards pets for paying customers, that is a kennel workflow, and it belongs on a kennel system.

One record covers the intake source and reason, identification and microchip details, safety and behavior notes, medical history and due dates, foster placements, adoption applications and decisions, the outcome, and any return, linked back to the same animal. A return is not a new stranger: it reopens the same history, including what the adopter learned, so the next placement starts from what is already known.

Each foster home has a visible profile: what species and sizes they can take, how many animals they already hold, what capacity is left, and when a check-in is due. A placement records the animal, the home, the start date, supplies given, and the next check-in, so a coordinator can see who is available without calling around or reading a group chat. When a foster placement ends, the animal's record keeps the full placement history.

Medical notes, vaccinations, treatments, vet visits, and medication schedules sit on the animal's record in date order, with the next due date visible to the whole team. One shelter-wide view shows what is overdue and what falls due soon, so a vaccination or a medication round does not depend on one person remembering it. Records entered by a foster or a vet visit are added to the same record, not kept in a separate file.

Applications arrive in one queue against the animal they concern, with the questions you set, reference and landlord checks tracked on the application itself, and the decision recorded with who made it. Approved adopters move to contract and fee handling, and follow-up check-ins are scheduled after placement, so a missed follow-up is visible instead of forgotten. If an animal returns, the return reason and the new notes go on the same record.

Volunteers see open shifts, claim the ones they can cover, and log their hours themselves, with training and role limits deciding who can take which shift. Coordinators see coverage gaps before a shift starts instead of discovering them by text message, and hours are counted from the logged record, which is the number a grant report can defend. Fosters get their own limited view: only their animals, their check-ins, and their appointments.

Reports come from the same records staff already keep: intakes and outcomes over a date range, length of stay per animal, foster placements and capacity, volunteer hours, adoption follow-ups completed, and returns. Because the numbers are drawn from the working record rather than rebuilt in a spreadsheet at report time, the board and the funder see the same figures the team works from day to day.

Buy an existing shelter product when it handles your intake, medical, foster, volunteer, and adoption work with reasonable setup and its pricing makes sense. That is the right answer for most standard shelters and foster-based rescues. Own software when your workflow breaks the template: a multi-site or multi-partner operation, a transfer network with its own rules, reporting your funders require in a shape no product produces, or connections to your other systems that no product covers cleanly. If your intake rules are still changing every week, settle them first.

Moving your data over is part of the scope, not an afterthought. Paper intake forms and spreadsheet columns are mapped onto the new record field by field, and anything that does not fit cleanly is flagged for a human decision before it is moved, not silently dropped. The old files stay readable until the team has checked the new record against real animals, and the handover notes record exactly what was moved and what was left behind.

It can connect where the listing site or payment tool offers a working connection and your team owns the account and the mapping. A common pattern is one adoptable-animal record feeding your public listings, so marking an animal adopted updates the listing instead of leaving a stale page up. A connection is only promised after it is checked against the real service, including what happens when the connection fails or a listing is edited by hand.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how deep the intake-to-adoption workflow goes, how many kinds of users it serves, what it needs to connect to, whether data needs moving over, whether phones or tablets are involved, and the condition of existing records. The agreed phase is priced in writing before it starts.

Timing depends on scope: a bounded audit or a single workflow, such as intake plus foster tracking, is a smaller engagement, while a full intake-to-adoption system with several system connections, data to move over, and mobile use for fosters and volunteers takes longer. The schedule is set once the first workflow and what 'done' looks like are clear.

You own the code built for you and control where it lives, the cloud accounts, the data, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: a real intake, a real foster placement, a real adoption decision. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your shelter.