The Tenderloin Community Benefit District moved its 2020 charter renewal onto District360. With 800-plus properties and 500-plus owners on the rolls, vote weight now aggregates automatically, outreach is tracked against the owners who matter most, and leadership sees the campaign's position in real time.
Schedule a Demo
The Tenderloin Community Benefit District partnered with District360 to retire the spreadsheets it had been using to run its charter renewal campaign and move every property, owner, contact, and vote into one structured platform.
One platform holding all 800-plus properties and 500-plus owners, with vote weight that totals automatically and owners ranked by the weight they control in real time, outreach tracked against the records it relates to, and a 2020 Renewal Campaign dashboard that shows milestone progress at a glance.
Vote totals that update the moment a record changes, ranked outreach prioritization that focuses staff time on the highest-weight owners, multi-user editing without lost edits, and a clean baseline data model the district can carry into every future renewal cycle.
The Tenderloin Community Benefit District is a nonprofit serving one of San Francisco's most complex neighborhoods, responsible for sidewalk cleaning, trash removal, safety ambassador patrols, beautification, and policy advocacy across the Tenderloin corridor. Under California law, the district must periodically run a charter renewal campaign, calling on its property owners to vote on whether the district continues for another term.
The 2020 renewal cycle was the trigger that exposed how fragile the team's existing tooling had become. Renewal in California is not a casual process. The district has to produce a petition signed by owners representing more than 30 percent of the assessment weight, and then win a ballot at the same threshold. With 800-plus properties and 500-plus distinct owners on the rolls, every percentage point of vote weight had to be tracked, attributed, and totaled accurately, in real time, as the campaign progressed.
The existing setup kept creating the same three problems.
The district needed a platform that could hold the campaign as a living dataset, one place where property, ownership, contact, vote, and outreach data lived together, where the system handled the math instead of people, and where leadership could see progress against the 30 percent threshold without waiting for a staff member to assemble the answer.
District360 worked alongside the Tenderloin team to understand how a renewal cycle actually moves before designing what would replace the spreadsheets. The unit of work in a renewal is not a row in a file. It is a property, with its owners, their vote weight, the contacts who can be reached, and the outreach history that determines what happens next. The platform was built around that unit.
The District360 platform became the new system of record for the district. 800-plus properties, 500-plus owners, every contact associated with each owner, and the vote weight each property carries were brought into one relational database with the relationships between records preserved instead of flattened into rows. Property data, owner records, individual contacts, vote intent, and outreach activity all sit in the same system, so pulling a clean view of the campaign no longer means reconciling files by hand.
The platform sums vote weight per property and rolls those totals up to the owner level, then ranks owners by the weight they control. A single owner holding several large parcels is recognized as the high-impact target, rather than appearing as one row alongside owners with far less weight. The ranked list tells the team where the next conversation matters most, and it updates the moment a record changes.
Every call, email, meeting, and lobbying touch is logged against the property and owner it relates to, captured in defined fields rather than free-text notes. The team can see at a glance who has been contacted, by whom, and what was said. Duplicate calls are caught before they happen, and high-priority owners stop falling through the cracks.
A configured dashboard built specifically for the 2020 campaign shows live progress against the 30 percent threshold, breakdowns by ownership type, and the highest-priority targets remaining. Leadership and the board pull the same view that staff work from, so there is no version-of-record question to resolve before a meeting. When a vote is logged or an owner record changes, the dashboard reflects it the next time it loads.
Renewal-specific fields can be hidden between cycles to keep the working database uncluttered, and brought back when the next renewal begins. The district now has a structured baseline it can carry into every future renewal cycle without rebuilding from scratch. The system ramps up cleanly when a campaign starts and stays useful as a day-to-day platform in the years between.
A staff member updating a contact does it in one place, and every record that references that contact updates with it. A vote logged against a property is reflected in the campaign dashboard the moment it is saved. Two team members can work the phones in parallel without overwriting each other's notes, because each record exists once and updates in real time. The Executive Director can pull the current state of the campaign without asking anyone to assemble it first.
The cultural change matters as much as the technical one. Staff time has shifted from reconciling spreadsheets to running outreach. The team's daily question has moved from "what does the data say" to "who do we call next."
Whether it's a renewal, an assessment cycle, a board report, or a month of service requests, place managers deserve a platform that keeps up with the work. Let's show you what that looks like.
Start a conversationA working week on the Tenderloin renewal now runs through a system instead of a folder. Properties, owners, contacts, vote intent, and outreach activity sit in one place, owned by the team that maintains them, accessible to the staff who need them. The week-of-the-deadline scramble to assemble a clean total for leadership has become a dashboard view available on demand.
Every entry the team makes goes into the same record everyone else is looking at. Vote weight aggregates automatically as records update, so leadership and the board see the campaign's current position without anyone reconstructing it. Outreach is captured against the properties and owners it actually relates to, which means duplicate calls are caught before they happen and high-priority owners stop falling through the cracks.
Beyond the 2020 campaign, what has stuck is the shape of the database itself. The district now has a structured baseline it can carry into every future renewal cycle, with the option to retire renewal-specific fields between cycles and bring them back when the next campaign begins. The maintenance work that used to absorb hours every week now takes minutes, and the team's attention has moved from keeping the data alive to using it to do the work the district was set up to do.
A campaign dashboard in District360 reads directly from the underlying records, so every figure on it is calculated from the live database rather than entered by hand. It shows the current position against whatever thresholds the campaign is working toward, breakdowns by the categories that matter to the team, ranked lists of the highest-priority targets remaining, and outreach activity over the campaign window. When a record changes, the dashboard reflects it the next time it loads. Place leaders and staff pull the same view, so there is no version-of-record question to resolve before a board meeting. For the Tenderloin Community Benefit District, that meant the Executive Director could see the campaign's position against the 30 percent renewal threshold on demand, without waiting for someone to assemble it first.
Most districts are working inside District360 within a few weeks, not a few quarters. The first phase is getting property, stakeholder, and contact data onto the platform cleanly and mapping it to how the team actually works. From there, campaign-specific fields, dashboards, and workflows get layered on in the order they are needed. Place managers do not need to pause operations to get started, and the platform can carry the first real campaign or cycle while refinements continue in the background. The goal is a working system early, not a perfect system eventually.
Every record exists once and updates in real time, so multiple staff can work the same campaign, the same day, without the lost-edit problem that defines spreadsheet work. Two team members on parallel calls update separate records, and any running totals across the database reflect both updates as they happen. Aggregations recalculate from the live data, which removes the manual tabulation step where errors tend to accumulate. The number leadership sees is the number the records contain. For the Tenderloin team, that meant staff could run outreach in parallel through the final weeks of the renewal campaign without stopping to reconcile a master file.
District360 is designed to sit in the center of the stack, not to replace every tool a place management organization already runs. It connects to the systems most districts already have in place for accounting, email, document storage, and field operations, so stakeholder records, assessment data, outreach history, and service activity can all be held together without forcing the team to abandon tools that are working. The integrations get mapped to the workflows the team actually uses, so data moves where it is needed and stops living in parallel in three places.
No. District360 is built for small teams where no one has "platform admin" in their title, and the day-to-day work (updating records, logging outreach, running reports, pulling a dashboard for the board) is designed to feel familiar from the first week. For configuration work and ongoing adjustments, District360 stays close to the team, which means place managers do not need to translate their needs through an in-house technical lead. Districts that do have a data or operations lead on staff get a platform that gives them more leverage, not one that creates a second job.