A council member asks what economic development produced this year. The honest answer is probably “quite a lot.” The provable answer is usually a number of visits and a feeling.
That gap is not a performance problem. It is a records problem, and it is the reason good retention work so often looks like nothing from the outside.
Why Do Retention Programs Fade?
Rarely for lack of intent. They fade because the visits happen and the record does not.
The sequence is always the same. Somebody from the city sits down with a business owner. The owner raises something real — a drainage problem, a permit that took four months, a building they would expand into if the parking worked. The conversation ends warmly. Acting on the concern requires somebody else in the city, and nobody writes down who, or by when. The loop closes on its own.
Repeat that forty times across a year and the city has had forty useful conversations it cannot do anything with. It cannot say who was visited, what was raised, or whether anything came of it. The program did produce something. Nobody can demonstrate it.
What Should a Visit Record Capture?
A business visit record is the structured note taken after a retention conversation, capturing what was raised and who owes what to whom afterwards. Six fields and a date will carry a program further than any amount of enthusiasm.
- Who and when — the business, the person, the date
- Who attended from the city
- What was raised, in the owner’s words rather than summarized into a category
- What was promised, if anything
- Who owns the follow-up — a name, not a department
- When it is due, and then what happened
The point of the format is not tidiness. It is that a conversation held by one person becomes something another person can pick up, which is what separates a program from a series of pleasant meetings.
What Does a Council Actually Want to See?
Usually some version of the same question: what did this produce.
A count of visits answers it poorly. Forty visits is an activity metric, and a council member who wants to be unconvinced will stay unconvinced. What answers the question is the pattern across visits — how many businesses raised the same infrastructure issue, how many were weighing expansion, how many were waiting on a permit question and how long resolution actually took.
That analysis is only possible if the underlying records were kept consistently, which is a clerical commitment made months before anybody asks. A city cannot reconstruct it at reporting time. This is the practical argument for the record-keeping: not compliance, but being able to answer.
How Does an Outreach List Stay Current?
By being somebody’s assigned job rather than a file refreshed the week before a report.
New business registrations, permit activity and sales tax records surface openings and closings. Local news, chamber activity and simply driving the corridor surface expansions, closures and ownership changes. None of that arrives on a schedule, so the list decays continuously and has to be maintained continuously.
A list rebuilt annually is wrong for most of the year, and a list that is wrong is worse than no list, because people stop trusting it and go back to memory.
What Can Be Delegated, and What Cannot
The division here is unusually clean.
Delegable: maintaining the business database and outreach lists, researching a business before a visit, logging what was raised, tracking follow-ups to closure, watching for openings and closings, and preparing the outreach and activity reports.
Not delegable: the visit itself, and the relationship that comes out of it.
That split favors the city. It puts city people in the room, where the value is, and puts the administrative weight — the part that causes programs to lapse — somewhere it can be done consistently. A municipal virtual assistant covers the second half without the city creating a position. Related reading: how small cities find the grants they’re missing.
Business Retention Tracking: Common Questions
Why do business retention programs fade?
Not for lack of intent. They fade because the visits happen and the record does not. A conversation produces a concern, the concern needs somebody else in the city to act, and without a tracked follow-up the loop closes on its own. A year later the city cannot say who it visited, what was raised or whether anything came of it, so the program looks like it produced nothing. It may have produced a great deal. Nobody can demonstrate it.
What should a business visit record capture?
Who was visited and when, who from the city attended, what the business raised, whether anything was promised, who owns the follow-up, and the date it is due. Then the outcome. Six fields and a date will carry a retention program further than any amount of enthusiasm, because they convert a conversation into something another person can pick up.
What does a council want to see from economic development?
Usually some version of the same question: what did this produce. A count of visits answers it poorly. What answers it is the pattern across visits — how many businesses raised the same infrastructure problem, how many were considering expansion, how many needed a permit question resolved and how long resolution took. That analysis is only possible if the underlying records were kept consistently, which is a clerical commitment made months earlier.
How does an outreach list stay current?
By being somebody’s assigned job rather than a file that gets refreshed before a report. New business registrations, permit activity and sales tax records surface openings and closings; local news and chamber activity surface expansions and ownership changes. The list decays continuously, so it has to be maintained continuously. A list rebuilt annually is wrong for most of the year.
Can business retention tracking be delegated?
Most of it, yes. Maintaining the business database and outreach lists, researching local businesses before a visit, logging what was raised, tracking follow-ups to closure and preparing the outreach reports are records work. What cannot be delegated is the visit itself and the relationship that comes out of it. That division is useful: it puts the city’s people in the room and the administrative load somewhere else.
Can a virtual assistant support economic development?
Yes. A VRA assistant maintains business databases, prospect lists and inquiry records, tracks development opportunities and incentives, researches local businesses, logs visits and the concerns raised, coordinates meetings and follow-ups, and prepares the outreach and activity reports. Pricing is flat at $1,500 a month full-time or $800 part-time, as a contracted service rather than a position.
Not sure what your outreach records would support? Book a short call and we’ll walk through what gets tracked now, what the reporting needs, and what covering the gap would involve.