operations

Rehashing a Territory Without Burning It

How to work the same streets a second and third time, which doors to re-knock, and the ones you must never touch again.

A territory is not consumed on the first pass. Most of it is barely touched.

Walk a thousand-door subdivision once and you will typically come back with a few hundred conversations, a pile of not-homes, a handful of appointments, and a small number of permanent refusals. The other several hundred doors are still inventory. Teams that treat a completed pass as a completed territory abandon most of their own work and then go hunting for new neighborhoods, which costs drive time, permit paperwork, and local knowledge.

Rehashing is working the same ground again on purpose. Done well it is the cheapest lead source a field team has. Done badly it produces complaints to the city and a neighborhood that recognizes your shirt and dislikes it.

Sort the territory before you re-knock it

The whole discipline is in the sorting. A second pass that re-knocks every door indiscriminately is not a rehash, it is a repeat, and it is how you burn turf.

Sort the doors into four piles.

Never again. Do-not-knock doors, posted no-soliciting signs, and anyone who asked in words not to be contacted. These come off the map permanently. The legal backdrop is not ambiguous: the Supreme Court observed in Martin v. City of Struthers that a city "can punish those who call at a home in defiance of the previously expressed will of the occupant," and many municipal solicitation ordinances say exactly that about posted signs. A rehash that re-knocks this pile is the single fastest way to generate the complaint that gets your company's permit pulled.

Highest value: not home. Nobody said no. You simply missed them. This is the biggest pile and the best one.

Worth a different angle: soft no. They answered, they declined, nothing hostile happened. Re-knockable, but only with a changed reason for the visit.

Lowest value: already in the pipeline. Callbacks, interested, appointments, sold jobs. These need follow-up, not a knock. Re-knocking a sold customer with a cold pitch is an own goal.

If your system cannot produce those four lists for a territory, the rehash will be done by memory, and memory will re-knock the refusals.

The not-home pile is an hour-band problem

The reason to be optimistic about not-homes is that most of them are not empty houses. They are houses you visited at the wrong time.

The Bureau of Labor Statistics' American Time Use Survey for 2025 found 81 percent of employed people worked on an average weekday against 30 percent on an average weekend day. That alone says a weekday-daytime pass and a Saturday pass will find different households at home. The same survey found 35 percent of employed people did some or all of their work at home on days they worked, which means a daytime pass is no longer the dead loss it once was: it just reaches a different set of people.

So the rule for rehashing not-homes is to change the variable that produced the miss. Shift the hour band. An evening territory gets a weekend morning rehash. A daytime territory gets an after-work rehash. Re-knocking the same doors at the same hour on a different day mostly reproduces the same not-homes and teaches you nothing.

Household composition also varies enough by neighborhood that it is worth checking before you plan the cycle. The Census Bureau's American Housing Survey publishes household and owner characteristics by metro area, which will tell you whether you are working a retiree area that answers at 10am or a dual-income new-build that does not.

A soft no needs a new reason to knock, not a better pitch

This is where most rehashes go wrong. A rep returns to a door that said no and delivers the same pitch with more energy. The homeowner's experience of that is harassment, and they are not wrong.

A soft no is re-knockable when something has genuinely changed. Legitimate changes:

• A storm. A hailfall over the neighborhood is a new fact about their roof, not a new sales angle.
• A job on the street. "We just finished your neighbor's roof at 412" is a different conversation than the one you had in March, and it is verifiable.
• A seasonal or program deadline. A real one, with a real date. Not a manufactured urgency.
• Time. Six months or a year later, with a new rep and a new reason, is a different visit. Six days later is the same visit.
• New ownership. The house changed hands. The prior refusal belonged to a person, not to an address. This one is worth checking, because a new homeowner is often the most receptive door on the street.

If you cannot name the change, the door is not ready.

Cycle length, and the thing that actually sets it

The most common question is how long to wait between passes. The honest answer is that there is no general number, and anyone who gives you one is guessing. What you can do is reason about it from the constraints you actually have.

The floor is set by neighborhood tolerance. Knock the same street every two weeks and you will get complaints regardless of how polite your reps are. The ceiling is set by your not-home pile going stale and by the housing stock: if you are selling roofs, the useful cycle is tied to roof age and storm events, not to a calendar.

Two practical tactics:

Stagger by sub-block, not by territory. Instead of re-knocking the whole subdivision in week six, re-knock a third of it, then another third. The streets get a longer rest and your reps get steady work.

Let the storm set the clock. In hail markets the rehash cycle is driven by weather, not by schedule. A territory you worked in April with no reason to return has a reason the day hail falls on it. That is the rehash that converts, because the reason to knock is genuine and the homeowner already knows.

Track pass number on the door

One small data decision makes rehashing manageable: record which pass a knock belongs to, not just the disposition.

Without it you cannot answer the questions that decide whether to rehash at all. Is the second-pass contact rate better or worse than the first? Does the set rate hold up on pass three, or does it collapse? Are complaints concentrated in territories on their fourth pass?

With it, rehashing stops being a matter of opinion. You can see the point at which a territory stops paying and move the team before the neighborhood tells you.

Signs you have burned a territory

Watch for these, because they appear before the complaints do.

• Refusals getting faster and more hostile at doors that used to be neutral.
• A rising rate of do-not-knock requests per hundred contacts.
• Reps volunteering to work anywhere else.
• Homeowners saying "someone from your company was already here" and being right.

When you see two of those, stop, let the territory rest, and go work the not-home pile somewhere else. A burned territory recovers. A burned territory that gets knocked anyway does not.

The short version

Rehashing works because a first pass only reaches a minority of households. It fails when the second pass does not distinguish between a door that missed you and a door that refused you.

Sort first. Change the hour band for not-homes. Bring a genuine new reason for soft noes. Never touch the never-again pile. And record the pass number so you can tell whether any of it is still working.

Canvass Pro keeps the disposition and timestamp on each door across passes, so a rehash can be sorted into those piles instead of guessed at.