City Avenue Special Services District retired its spreadsheets and moved every record onto a single connected platform with District360.

A growing district whose spreadsheets had become its database.

City Avenue Special Services District is a business improvement district along the Pennsylvania border with Philadelphia, stewarding the properties, businesses, and public realm that line the City Avenue corridor. Like many districts at its scale, the team's day-to-day data work had grown up inside a series of spreadsheets that started small, served their purpose, and never stopped getting bigger.

For years, those spreadsheets were the system. Property records lived in one file. Contact data lived in another. District activity, reporting figures, and historical context were scattered across more files than any one person could keep current. As the district grew, the spreadsheets grew with it, and the maintenance work grew faster than anyone had budgeted for.

Three problems made the situation harder every quarter:

• Data overload: Each spreadsheet was its own system, with its own version history, its own sheet structure, and its own quiet errors. Finding a single piece of information meant knowing which file it was in, who had last updated it, and whether the version on the shared drive matched the one circulating over email.
• Errors and inconsistencies: Manual entry produced duplicate records, outdated entries, and figures that rarely matched across files. Reconciling them was a recurring tax on the team's time.
• Collaboration friction: Two team members editing the same file at the same time meant conflicting versions, lost edits, and an ongoing question about which copy was authoritative.

When leadership needed a clean number for a board update or a partner conversation, the work started by hunting through files, reconciling them, and rebuilding the answer from scratch. The team had the knowledge. What they didn't have was a system that let them operate as one.

One platform, shaped around the way the district already managed its data.

As their technology partner, District360 worked alongside the City Avenue team to understand what the spreadsheets were actually doing before designing what would replace them. The point of the project was never to digitize the team's work for the sake of it. It was to remove the friction that had built up around the data the district relied on every day.

The District360 platform became the new system of record for the district. Property data, contact records, district activity, and reporting structures were migrated from their respective spreadsheets into a single relational database, with the relationships between records preserved instead of flattened. What changed was the data model underneath.

• Property data: parcels, owners, tenants, and historical context, brought into one structured table with a complete change history rather than a patchwork of file versions.
• Contact records: stakeholders, property owners, and member contacts, deduplicated on import and linked back to the properties and activity each contact was associated with.
• District activity: program records, service touches, and operational entries, captured in structured fields that can be filtered, reported on, and trusted, instead of free-text spreadsheet cells.
• Reports and dashboards: a configured dashboard layer for the figures the team and the board most often ask for, calculated from the live data and refreshed automatically.

A staff member updating a contact does it in one place, and every record that references that contact updates with it. A report request from the Executive Director is answered through a dashboard view rather than through a fresh round of file reconciliation. Two team members editing district activity at the same time work inside the same record, with changes visible to each other in real time. The district's data finally behaves like a database instead of like a folder of files that happen to live in the same drive.

The cultural shift matters as much as the technical one. A team that once spent the first hour of every reporting cycle tracking down the right file now spends that time on the work the file was supposed to support.

A district that runs on accurate data, not reconciled files.

A month at City Avenue Special Services District now runs through a system instead of a folder. Property records, contact data, and district activity sit in one place, owned by the team that maintains them, accessible to the people who need them. The week-of-the-board-meeting scramble to assemble accurate figures has become a dashboard view leadership can pull on demand.

What a structured platform actually delivers

Every entry the team makes goes into the same record everyone else is looking at. Duplicates are caught at the point of entry rather than discovered weeks later in a quarterly clean-up. Dashboards show the numbers that matter most without anyone having to reformat them. When a question comes from leadership, a property owner, or a board member, the answer is in the system, not waiting to be reassembled across three different files.

More than the platform itself, what has stuck is the change in how the team relates to its own data. The maintenance work that used to absorb hours every week now takes minutes. The team's attention has moved from keeping the spreadsheets alive to using the data to do the work the district was set up to do.