University City District, District360 Customer Story

At a glance

Vision

One platform to run the work of a dense, multi-program improvement district, with District360 as the technology partner putting field activity, property data, and stakeholder reporting in the same place, and no specialist required to keep it moving.

What We Built Together

A connected platform shaped around how the district actually operates, with a data model built for improvement district work and District360 Streets configured for the ambassador workflow in the field. Property and business records live inside the same system, alongside a long library of case types covering safety, hospitality, cleaning, and outreach. Dashboards then bring it all together for leadership and the board.

Impact

University City District now has a single place to run the entire district, from a sidewalk incident to a board update, with the first measurable improvements landing within the first few weeks of the engagement.

The Brief

One of Philadelphia’s busiest corridors was being run on spreadsheets and paper.

University City District stewards one of the most active stretches of West Philadelphia. The team handles public safety, cleanliness, social service outreach, and economic development across a corridor that serves residents, students, hospital staff, and visitors every day. The work was happening. The system around it was not keeping up.

Field activity was being recorded by hand or entered into spreadsheets after the fact. Reporting to leadership and the board meant pulling numbers from disconnected tools and assembling them manually. Supervisors had limited visibility into what their ambassadors were doing in real time, and the data that did exist sat in places where it could not easily be queried, linked, or trusted. Stakeholders kept asking for cleaner answers, and the team kept finding it hard to give them.

University City District wanted one place to capture field activity, one place to hold property and business records, one place to run reporting from, and a setup the team could operate on its own without specialized engineering help.

District360 gave University City District one place to run every part of the district, from a sidewalk incident to a board update, with every workflow connected and every record where it belongs.

What District360 Built

From the ambassador’s phone to the leadership dashboard, every part of the district in one connected platform.

As their technology partner, District360 built the entire system from the ground up, configuring the data model, the mobile app for the field, the property and business records, and the reporting layer over the top. Spreadsheets and paper logs are no longer how the work gets done.

A data model structured for how the district operates

The platform was set up with the core objects an improvement district actually uses, covering businesses, contacts, cases, and a property management layer, each connected to the others. A service request links to the location where it happened, the property at that address, and the contacts associated with it. That structure is the foundation everything else sits on.

District360 Streets

District360 Streets is the part of the build that lives in ambassadors’ pockets. The Streets app is mobile-first, designed to be opened on shift and used without training, with clean tile-based navigation and a small set of fields per case. Each entry captures what kind of work happened, when, where, and who handled it, and flows back into the same platform the office team uses.

A case-type library shaped to the work

The team’s ambassadors do a wider variety of work than a generic CRM would ever anticipate. District360 worked with University City District to configure a library of 21 case types that covers the full range, from safety and incident reports to ambassador outreach, escorts, lockout and jumpstart calls, bike inspections, graffiti reports, quality conditions, zone reports, equipment repair, vehicle inspections, event summaries, and program-specific reports. Whatever the work is, there is a place for it to land in the system.

Property data, business records, and reporting on top

Property and business records sit inside the same platform as the field cases, so the team can move from a service request to the property to its business and contact history without leaving the system. On top of all of it, dashboards are built directly from the data the team already captures day to day, so leadership and the board can see what is happening across the district without anyone manually assembling a spreadsheet at the end of the month.

District360 Streets home screen in the University City District build with case-type tiles for Incident Report, Special Check, Outreach Ambassador, Escort, Lockout and Jumpstart, and Bike Inspection

District360 Streets incident report form in the University City District build with fields for date, type, emergency service, and narrative

District360 Streets open cases list in the University City District build with three cases at 3940 Chestnut Street

The Impact

The team that runs the district, now easily runs its platform too.

Stakeholders used to ask University City District for cleaner answers about the work happening on the ground, and the team did not always have a clean way to give them. They do now. Field activity, property data, business records, and the reporting that sits over all of it run through one connected platform, and the first measurable improvements landed within the first two to four weeks of the engagement.

Fragmented to centralized

University City District moved from a fragmented stack to a single connected system. The team no longer reconciles spreadsheets at the end of the month or hunts for data across disconnected tools. Every part of the operation, from a sidewalk case to a property record to a board-ready dashboard, sits in the same place and links back to everything else.

Built to grow with the district

The case-type library, the data model, and the dashboards are all structured to add capacity over time. As the team takes on new programs, new categories of field work, or new reporting needs, the platform extends without a separate tool to integrate or a specialist to bring in. The build at University City District is set up for the long run.

Frequently Asked Questions

What place management leaders ask about District360.

Most districts go live within a few weeks rather than a few quarters. District360 is pre-shaped for improvement district work, so configuration rather than custom development is usually all it takes. The foundations, covering the data model, the mobile field app, property and business records, and reporting, are rolled out together, and teams are running live workflows within the first stretch of the engagement instead of waiting months to see value.

No. District360 is built so the teams who run the district can run the platform too. Case types, fields, dashboards, and workflows can all be adjusted by the people closest to the work without pulling in an engineer every time something changes. Training is focused on giving the team that independence from day one, which is why most operations teams manage their own configuration after go-live.

Yes. District360 is built around the actual variety of work a place management team does. Case-type libraries can cover safety and incident reporting, hospitality and wayfinding, cleaning and quality conditions, social service outreach, escorts, lockout and jumpstart calls, equipment and vehicle checks, event summaries, and the long tail of program-specific reports. If the work is happening in the district, there is a place for it to land in the system.

Property, business, contact, and case records are native to the same platform and linked by default. A service request in the field is tied to the location, the property at that address, and the business or contact associated with it, so the office team can move from a sidewalk incident to a tenant record to a stakeholder conversation without leaving the system or reconciling separate tools.

District360 is structured to extend as the district grows. New case types, new programs, and new reporting requirements can be added inside the same platform without a separate tool to integrate or a specialist to bring in. The foundation stays consistent while the work on top of it keeps evolving with the team.

Most districts start with a stack that includes a field app in one place, a spreadsheet somewhere else, a CRM or property tracker in a third, and reporting pulled together by hand at the end of the month. District360 consolidates all of that into one connected system. Field activity, property and business data, and dashboards share the same source of truth, so teams stop reconciling and stakeholders get cleaner, faster answers.

University City District replaced spreadsheets and paper logs with one single platform.

Vision

What We Built Together

Impact

One of Philadelphia’s busiest corridors was being run on spreadsheets and paper.

From the ambassador’s phone to the leadership dashboard, every part of the district in one connected platform.

If your district is still run on spreadsheets and paper, we should talk.

The team that runs the district, now easily runs its platform too.

What place management leaders ask about District360.

University City District replaced spreadsheets and paper logs with one single platform.

Vision

What We Built Together

Impact

One of Philadelphia’s busiest corridors was being run on spreadsheets and paper.

From the ambassador’s phone to the leadership dashboard, every part of the district in one connected platform.

If your district is still run on spreadsheets and paper, we should talk.

The team that runs the district, now easily runs its platform too.

What place management leaders ask about District360.

More customer stories

DowntownDC BID

Downtown Dallas Inc.

Times Square Alliance

Want a build like this for your district?