Running 12 Drop-Ins a Day: Windows, Routes, and Not Being Late for the Cat

Twelve visits sounds fine until you write out the day. Three morning drop-ins that all want to be before 9. A midday walk that has to happen between 11:30 and 1:30 because the dog can't hold it longer. Two more walks in the same window in a different neighborhood. Evening feedings that can't start before 5. An overnight that begins at 8.

The visits fit. The windows don't. That's the actual constraint in pet care, and it's different from every other route-based business — a plumber's jobs can slide an hour, a cat's breakfast can't.

Windows are the real capacity limit

Most sitters think about capacity as visits per day. It isn't. Capacity is visits per window, and you have three or four of them.

A morning window of 7:00–9:00 is 120 minutes. A 30-minute drop-in plus 12 minutes of driving is 42 minutes per stop. That's two stops with a little slack, or three if the houses are close and nothing goes wrong. Not five, no matter how early you start — because starting at 6:30 means you're feeding a cat whose owner said "morning," and some of them will mind.

Work out each of your windows this way once:

window length ÷ (visit length + travel + buffer) = stops

Do it for morning, midday, and evening separately. The number you get is your honest daily maximum, and it's usually lower than what you've been saying yes to.

Route by neighborhood, not by request order

The single biggest time recovery available to most sitters is clustering. Not clever routing software — just refusing to zigzag.

Sort your client list by area. Two or three clusters, named however makes sense to you: north of the highway, the condos, the hill. Then, when a booking request comes in, you know immediately whether it fits a cluster you're already serving that week or whether it's a twenty-minute detour each way.

This changes what you say yes to. A new client four miles past your furthest current stop isn't a $25 visit, it's a $25 visit minus forty minutes of driving — which on a full day means the visit you can no longer fit. Clustering also means that when someone cancels, you lose a stop rather than an entire loop.

Practical version: keep the cluster in the client's record, not in your head. When you're building a Tuesday, you want to see "north" next to five names, not try to remember where everyone lives.

Build the buffer in, or the day eats it

Every pet-care day has variance that a delivery route doesn't. The cat who won't come out from under the bed and needs to be seen before you can log the visit. The dog who has an accident you have to clean. The lockbox that sticks. The client who texts mid-visit asking for a photo and a status update.

Two minutes each, five times, is ten minutes — and ten minutes is the difference between arriving inside a window and arriving after it.

The fix is unglamorous: add a fixed buffer per visit in your planning, not just travel time. Five minutes is usually enough for drop-ins; ten for anything involving medication, a nervous animal, or an unfamiliar house. Plan the day with the buffer included, and the buffer is what absorbs the bad stop instead of your evening.

And leave one genuinely empty slot in the middle of a full day. Not for a visit — for the day going sideways.

Overnights change the geometry

An overnight isn't a stop, it's a wall. Everything after 8pm and before 7am the next morning happens at one address, which means:

• Your evening route has to end at the overnight house, not pass through it
• Your next morning starts from there, not from home — so the first drop-in should be the one nearest that house, which is rarely the one nearest you
• Mileage for the next morning is measured from a different origin

Sitters who take overnights and plan their mornings from home end up driving a big empty leg back across town before their first visit. Planning the morning from the overnight address usually saves ten or fifteen miles.

What to log per visit, and why it pays

The temptation is to log nothing and rely on memory. What experienced sitters log, at minimum:

• Arrival and departure time. Protects you if a client asks whether a visit happened, and makes your next capacity calculation real rather than optimistic.
• The care checklist. Fed, meds given, walked, water refreshed, litter, plants, mail. A short tick list per household, because every house is different and the one thing you forget will be the one thing the client asks about.
• Anything unusual. Vomit, limping, not eating, a door found unlocked. Write it the day it happens.
• Miles. Drop-in to drop-in is business mileage. Home to your first stop and last stop home is generally commuting and generally not deductible — and if you walk or bike between visits, those miles aren't deductible at all, even though they're work. Worth knowing before you build a mileage claim on a walking route.

The logging habit pays twice: once in the moment a client questions something, and once a year when you can price your services from real numbers instead of a guess about how long visits take.

Standing visits are your floor, bookings are your ceiling

The healthiest pet-care weeks I've seen have a base of standing visits — the Monday/Wednesday/Friday midday walk, the every-weekday cat drop-in — and vacation bookings layered on top.

Standing visits are predictable, they cluster naturally because they repeat, and they're the reason a slow week isn't an empty week. The risk is that they're also the easiest to forget, precisely because nobody re-books them. A standing walk that quietly stops happening because you didn't write it down for a holiday week is how you lose a long-term client.

Whatever system you use, standing visits should generate themselves onto the calendar rather than rely on you remembering them.

A day that actually works

Here's the shape of a well-built full day, without naming a tool:

7:00–9:00, north cluster. Two drop-ins, the further one first so you're driving toward the rest of your day, not away from it.

9:00–11:00, admin and travel. Booking replies, invoices, the drive to the midday area.

11:30–13:30, condo cluster. Three walks, all within half a mile. This is your densest window and the one to protect — don't accept a midday walk outside your cluster unless the rate makes the drive worth it.

13:30–16:30, the gap. Deliberately light. This is where a cancelled visit gets made up, a vet trip fits, or you eat lunch sitting down.

17:00–19:00, evening feedings. Same cluster as the morning if you can manage it, ending at the overnight house.

20:00, overnight. Tomorrow morning starts from here.

Eight paid stops plus an overnight, and nobody was late. That's a better day than twelve stops where three were rushed and the cat's owner got a text apology.

Where Casedaisy fits

Casedaisy builds the day inside your windows: it orders each window's visits by real drive time, respects per-household morning/midday/evening windows, blocks the overnight span and starts the next morning from that address, and logs mileage automatically. Bookings generate the individual visits across a date range, standing walks repeat without being re-entered, and each visit carries the household's care checklist and access notes.

If you'd rather stay on paper for now, start with the households and pets template — it has the window columns and the per-pet care fields, which is most of what a good day-plan needs. The pet care info sheet and vaccination tracker covers the rest.