Animal Welfare Professionals

Something I keep running into as we build out our Pet Help Desk is how badly standard intake reason codes describe what actually drives surrender.

A caller says housing. We code housing. But the real chain is more like: pet rent went from $25 to $50, the security deposit was already a stretch, the apartment they could afford requires renters insurance with a breed exclusion, and the only "yes-pet" landlord they found wants a $400 nonrefundable fee they don't have. Housing is the bucket. None of those five barriers are the bucket.

Same thing on the cost-driven calls. Sara Pizano's 2026 Go-To Guide cites 77% of surrenders as cost-driven, which tracks with what we hear. But "cost" can mean a $90 vet visit they can't pay this week, a chronic med refill that ran out, a landlord pet rent they didn't budget for, or a vacuum-sealed combination of all three. If we code it as "financial," we lose the intervention point.

So we built a longer reason field on our call intake. Pet deposit help, pet fee help, pet rent help, lease violation pet, eviction threat pet, landlord dispute pet, insurance help pet, ESA question, temporary housing pet, behavior emergency, neglect report, stray found, community cat help, rehoming request, and a few more. Sixteen total right now. It is not elegant. But the field tells us where to send the family before they ever reach a shelter door.

Two things that surprised me once we started coding at this resolution.

One, the most common housing call is not "I need a pet-friendly apartment." It is "I have an apartment, my landlord is changing the rules, I have 30 days." That is a completely different intervention than helping someone move.

Two, vet cost calls cluster heavily on chronic care, not on emergency vet. People are managing a diabetic dog or a senior cat with kidney issues, and one missed paycheck collapses the math. Emergency vet is loud and rare. Chronic care is quiet and constant.

I am curious how others are handling this. A few specific questions for the room.

Do you track surrender driver as a tree (housing > pet rent change > can't cover) or just as a top-level bucket? If you track at the leaf level, are you finding patterns that change how you allocate diversion funds? And for anyone using Shelterluv, Animals First, or one of the other major platforms, how have you handled the coding gap, custom fields, free text, post-call categorization?

Hi BJ,

I don't have specific answers to your questions yet and need to check with my adoption team. I really appreciate the topics you bring to this group!

Something I keep running into as we build out our Pet Help Desk is how badly standard intake reason codes describe what actually drives surrender.

A caller says housing. We code housing. But the real chain is more like: pet rent went from $25 to $50, the security deposit was already a stretch, the apartment they could afford requires renters insurance with a breed exclusion, and the only "yes-pet" landlord they found wants a $400 nonrefundable fee they don't have. Housing is the bucket. None of those five barriers are the bucket.

Same thing on the cost-driven calls. Sara Pizano's 2026 Go-To Guide cites 77% of surrenders as cost-driven, which tracks with what we hear. But "cost" can mean a $90 vet visit they can't pay this week, a chronic med refill that ran out, a landlord pet rent they didn't budget for, or a vacuum-sealed combination of all three. If we code it as "financial," we lose the intervention point.

So we built a longer reason field on our call intake. Pet deposit help, pet fee help, pet rent help, lease violation pet, eviction threat pet, landlord dispute pet, insurance help pet, ESA question, temporary housing pet, behavior emergency, neglect report, stray found, community cat help, rehoming request, and a few more. Sixteen total right now. It is not elegant. But the field tells us where to send the family before they ever reach a shelter door.

Two things that surprised me once we started coding at this resolution.

One, the most common housing call is not "I need a pet-friendly apartment." It is "I have an apartment, my landlord is changing the rules, I have 30 days." That is a completely different intervention than helping someone move.

Two, vet cost calls cluster heavily on chronic care, not on emergency vet. People are managing a diabetic dog or a senior cat with kidney issues, and one missed paycheck collapses the math. Emergency vet is loud and rare. Chronic care is quiet and constant.

I am curious how others are handling this. A few specific questions for the room.

Do you track surrender driver as a tree (housing > pet rent change > can't cover) or just as a top-level bucket? If you track at the leaf level, are you finding patterns that change how you allocate diversion funds? And for anyone using Shelterluv, Animals First, or one of the other major platforms, how have you handled the coding gap, custom fields, free text, post-call categorization?

Something I keep running into as we build out our Pet Help Desk is how badly standard intake reason codes describe what actually drives surrender.

A caller says housing. We code housing. But the real chain is more like: pet rent went from $25 to $50, the security deposit was already a stretch, the apartment they could afford requires renters insurance with a breed exclusion, and the only "yes-pet" landlord they found wants a $400 nonrefundable fee they don't have. Housing is the bucket. None of those five barriers are the bucket.

Same thing on the cost-driven calls. Sara Pizano's 2026 Go-To Guide cites 77% of surrenders as cost-driven, which tracks with what we hear. But "cost" can mean a $90 vet visit they can't pay this week, a chronic med refill that ran out, a landlord pet rent they didn't budget for, or a vacuum-sealed combination of all three. If we code it as "financial," we lose the intervention point.

So we built a longer reason field on our call intake. Pet deposit help, pet fee help, pet rent help, lease violation pet, eviction threat pet, landlord dispute pet, insurance help pet, ESA question, temporary housing pet, behavior emergency, neglect report, stray found, community cat help, rehoming request, and a few more. Sixteen total right now. It is not elegant. But the field tells us where to send the family before they ever reach a shelter door.

Two things that surprised me once we started coding at this resolution.

One, the most common housing call is not "I need a pet-friendly apartment." It is "I have an apartment, my landlord is changing the rules, I have 30 days." That is a completely different intervention than helping someone move.

Two, vet cost calls cluster heavily on chronic care, not on emergency vet. People are managing a diabetic dog or a senior cat with kidney issues, and one missed paycheck collapses the math. Emergency vet is loud and rare. Chronic care is quiet and constant.

I am curious how others are handling this. A few specific questions for the room.

Do you track surrender driver as a tree (housing > pet rent change > can't cover) or just as a top-level bucket? If you track at the leaf level, are you finding patterns that change how you allocate diversion funds? And for anyone using Shelterluv, Animals First, or one of the other major platforms, how have you handled the coding gap, custom fields, free text, post-call categorization?

So happy to read that you're taking a more targeted approach to this. We need to know the specific reason to be able to cultivate effective resources. I've found, too, that there is often a surrender reason that actually looks quite different than the surface reason. This usually happens with behavior.  The reason given will be "moving", but with more discussion, you come to understand that the cat can't move to new housing with the owner because of long-standing inappropriate elimination problems. Or the given reason is "new baby" but the underlying concern is the dog's resource guarding behavior with bite history. In those cases, it is really a combination of factors. 

I once adopted a dog who turned out to have terrible allergies. He would develop these awful fungal infections in the skin folds of his neck. His surrender reason at the shelter was the "wife's breathing problems". I actually spoke to the prior owners at one point to learn more about what interventions they had tried already with his allergies. The husband told me that the infections smelled so bad his wife couldn't tolerate it anymore. That was the "breathing problem." Talk about a euphemistic surrender reason!  

I think shelter software systems need to be able to track multiple codes for each animal and to include detailed options, perhaps as a subset for more broad codes. If there's a crusade, I'll join! 

Something I keep running into as we build out our Pet Help Desk is how badly standard intake reason codes describe what actually drives surrender.

A caller says housing. We code housing. But the real chain is more like: pet rent went from $25 to $50, the security deposit was already a stretch, the apartment they could afford requires renters insurance with a breed exclusion, and the only "yes-pet" landlord they found wants a $400 nonrefundable fee they don't have. Housing is the bucket. None of those five barriers are the bucket.

Same thing on the cost-driven calls. Sara Pizano's 2026 Go-To Guide cites 77% of surrenders as cost-driven, which tracks with what we hear. But "cost" can mean a $90 vet visit they can't pay this week, a chronic med refill that ran out, a landlord pet rent they didn't budget for, or a vacuum-sealed combination of all three. If we code it as "financial," we lose the intervention point.

So we built a longer reason field on our call intake. Pet deposit help, pet fee help, pet rent help, lease violation pet, eviction threat pet, landlord dispute pet, insurance help pet, ESA question, temporary housing pet, behavior emergency, neglect report, stray found, community cat help, rehoming request, and a few more. Sixteen total right now. It is not elegant. But the field tells us where to send the family before they ever reach a shelter door.

Two things that surprised me once we started coding at this resolution.

One, the most common housing call is not "I need a pet-friendly apartment." It is "I have an apartment, my landlord is changing the rules, I have 30 days." That is a completely different intervention than helping someone move.

Two, vet cost calls cluster heavily on chronic care, not on emergency vet. People are managing a diabetic dog or a senior cat with kidney issues, and one missed paycheck collapses the math. Emergency vet is loud and rare. Chronic care is quiet and constant.

I am curious how others are handling this. A few specific questions for the room.

Do you track surrender driver as a tree (housing > pet rent change > can't cover) or just as a top-level bucket? If you track at the leaf level, are you finding patterns that change how you allocate diversion funds? And for anyone using Shelterluv, Animals First, or one of the other major platforms, how have you handled the coding gap, custom fields, free text, post-call categorization?

Hi Karen,

Yes. The breathing problems story is exactly the pattern. The surface reason is a socially acceptable version of what the family couldn't bring themselves to say. Skin allergy and ongoing medical care is a completely different intervention than "wife can't tolerate the smell," but only one of those gets you to a real solution.

We're already tracking multiple intake reasons per animal in the AWRN, with sub-codes that drill into what's actually driving the surrender. Your cat example (moving plus long-standing elimination issues) would show up as "moving" with a sub-code of "behavior, inappropriate elimination" so the prevention team can offer housing support AND a behavior specialist referral. That layered tracking is exactly what changes the outcome.

If you want to see how we're building this, I'd love to set up a quick call. The crusade is underway. We'd be glad to have you in it.

calendly.com/animal-angels

Thank you for jumping in, BJ

So happy to read that you're taking a more targeted approach to this. We need to know the specific reason to be able to cultivate effective resources. I've found, too, that there is often a surrender reason that actually looks quite different than the surface reason. This usually happens with behavior.  The reason given will be "moving", but with more discussion, you come to understand that the cat can't move to new housing with the owner because of long-standing inappropriate elimination problems. Or the given reason is "new baby" but the underlying concern is the dog's resource guarding behavior with bite history. In those cases, it is really a combination of factors. 

I once adopted a dog who turned out to have terrible allergies. He would develop these awful fungal infections in the skin folds of his neck. His surrender reason at the shelter was the "wife's breathing problems". I actually spoke to the prior owners at one point to learn more about what interventions they had tried already with his allergies. The husband told me that the infections smelled so bad his wife couldn't tolerate it anymore. That was the "breathing problem." Talk about a euphemistic surrender reason!  

I think shelter software systems need to be able to track multiple codes for each animal and to include detailed options, perhaps as a subset for more broad codes. If there's a crusade, I'll join! 

Something I keep running into as we build out our Pet Help Desk is how badly standard intake reason codes describe what actually drives surrender.

A caller says housing. We code housing. But the real chain is more like: pet rent went from $25 to $50, the security deposit was already a stretch, the apartment they could afford requires renters insurance with a breed exclusion, and the only "yes-pet" landlord they found wants a $400 nonrefundable fee they don't have. Housing is the bucket. None of those five barriers are the bucket.

Same thing on the cost-driven calls. Sara Pizano's 2026 Go-To Guide cites 77% of surrenders as cost-driven, which tracks with what we hear. But "cost" can mean a $90 vet visit they can't pay this week, a chronic med refill that ran out, a landlord pet rent they didn't budget for, or a vacuum-sealed combination of all three. If we code it as "financial," we lose the intervention point.

So we built a longer reason field on our call intake. Pet deposit help, pet fee help, pet rent help, lease violation pet, eviction threat pet, landlord dispute pet, insurance help pet, ESA question, temporary housing pet, behavior emergency, neglect report, stray found, community cat help, rehoming request, and a few more. Sixteen total right now. It is not elegant. But the field tells us where to send the family before they ever reach a shelter door.

Two things that surprised me once we started coding at this resolution.

One, the most common housing call is not "I need a pet-friendly apartment." It is "I have an apartment, my landlord is changing the rules, I have 30 days." That is a completely different intervention than helping someone move.

Two, vet cost calls cluster heavily on chronic care, not on emergency vet. People are managing a diabetic dog or a senior cat with kidney issues, and one missed paycheck collapses the math. Emergency vet is loud and rare. Chronic care is quiet and constant.

I am curious how others are handling this. A few specific questions for the room.

Do you track surrender driver as a tree (housing > pet rent change > can't cover) or just as a top-level bucket? If you track at the leaf level, are you finding patterns that change how you allocate diversion funds? And for anyone using Shelterluv, Animals First, or one of the other major platforms, how have you handled the coding gap, custom fields, free text, post-call categorization?