In the heart of Philadelphia, ambassadors log every encampment, every sweep, and every business contact through District360 Streets, a mobile experience shaped, refined, and rebuilt around how Center City District actually operates.
Schedule a Demo
Center City District partnered with District360 to give its ambassadors and operations team a single mobile platform for logging, tracking, and resolving every clean and safe issue across one of the busiest downtowns in the United States.
District360 Streets, with case categories shaped around the team's specific verticals, custom workflows for business contacts and stakeholder engagement, geofenced location capture, and a platform that keeps evolving with the team.
Ambassadors log cases from the field in seconds. Operations leadership sees every open request in one place. When the team has feedback on how something should work, the platform gets reshaped around them.
Center City District is the special services district that keeps the heart of Philadelphia clean, safe, and welcoming. Every day, ambassadors walk the blocks around Walnut, Chestnut, and Market Streets, fielding everything from a sidewalk sweep request to an encampment observation to a check-in with a local business owner.
Before the partnership with District360, much of that field work lived in unstructured data. Notes were scribbled in the moment, messages moved across separate tools, and handoffs depended on people remembering to follow up. Cases got captured later from memory instead of being logged the moment they happened. Supervisors had no clean way to act on what their teams were seeing in real time, and leadership had no clear view of the public space management work happening across the district.
Center City District's ask of District360 was direct. A mobile app for ambassadors that fit how the team actually operated, with case categories that matched their verticals and workflows that could keep being shaped as their needs sharpened. That mattered not just for field teams, but for place managers and place leaders who needed a clearer picture of what was happening across the district.
District360 Streets, the mobile experience built for Center City District, was not configured from a template. It was shaped for this team, with the exact categories, verticals, and workflows ambassadors, supervisors, and place managers needed from day one.
When an ambassador opens the app, the five case types on the screen are not generic field service buckets. They are the actual verticals Center City District organizes its work around: Business Contact, Homeless and Panhandlers, Hospitality and Ambassador, Public Space and Environment, and Security and Safety. Each one opens into sub-types and sub-sub-types that mirror the real decisions ambassadors make in the field, from logging the materials involved in an encampment observation to tagging a sweep as a special-project request. Every logged case carries enough specificity for a supervisor or downstream team to act on it without a follow-up call.
Every case in the app is anchored to a real Philadelphia address. Ambassadors can drop a pin on the map, use their current location, or search by street name. The location flows automatically into the case record, so when leadership pulls a report or analyzes a hotspot, the geographic data is already there. Geofencing capabilities are also being layered in to refine how cases are routed and tracked across the district.
As the team's work evolved, so did the platform underneath it. Workflows for adding businesses and updating business contacts were rebuilt to mirror how the team actually handles the businesses it serves. The product Center City District uses today is meaningfully different from the one that launched, which is exactly what a strong technology partnership should look like.
Place management teams deserve a platform that captures the work the moment it happens, not an hour later at a desk. If your field operations still run on notebooks, we should talk.
Start a conversationA shift now starts with Streets open on a tablet. As an ambassador walks Walnut, Chestnut, and Market Streets, every encampment, every sidewalk sweep request, every business contact, and every safety concern goes straight into the app, structured and located, before they move on. No notebook to type up at the end of the day, no spreadsheets to patch together at the end of the week, no supervisors chasing details on cases logged three days ago. What used to take a hand-off conversation now takes seconds on the sidewalk.
Time. Cleaner data. Fewer handoffs. A clearer picture of what is actually happening across the district. Supervisors can pull up open cases and see exactly where ambassadors have been and what they have logged. Leadership can run reports without first hunting down where the data lives. The unstructured data problem that brought Center City District to District360 has been replaced with a system the team trusts and uses every day.
More than the technology, what has stuck is the way the partnership works. When the team has feedback, the platform gets reshaped. When a workflow does not fit, it gets rebuilt. The product the team uses today is not the product they started with, and that is exactly how it was supposed to work. That is what place managers and place leaders need from a technology partner, a system that keeps getting better as the work evolves.
Most place managers see ambassadors logging work inside District360 within a few weeks, not a few quarters. The first phase is getting the case categories, verticals, and field workflows mapped to how the team actually operates. From there, location capture, supervisor views, and reporting get layered on in the order the team needs them. Field teams do not need to pause operations to get started, and the platform can carry real shifts while refinements continue in the background.
District360 starts from how the team actually operates. The categories ambassadors see on their mobile screen, the sub-types under each category, the fields that capture location and context, and the downstream workflows that route cases to supervisors are all shaped around the specific verticals the district runs. Two place management organizations rarely look alike on the inside, and District360 is built on the assumption that the platform should reflect the team, not the other way around.
A day in the field rarely follows one workflow. Ambassadors log encampment observations, sidewalk sweep requests, business contacts, safety concerns, and hospitality interactions, often inside the same shift. District360 holds all of it in one system, with case types and sub-types specific enough that a supervisor can act on an entry without a follow-up conversation. Every case carries location, timestamp, context fields, and the person who logged it, so the record is complete the moment the ambassador moves on.
District360 is designed to keep being shaped as the work evolves. When a team's verticals change, when a workflow needs to be rebuilt, or when a new category of field activity becomes important, the platform is reconfigured around it rather than worked around. That ongoing refinement is part of the engagement, not a separate project. Place managers who have been on District360 for years are usually working with something meaningfully different from what launched, because their operation itself has kept moving.
No. District360 is built for teams where no one has "platform admin" in their title. Daily work, from logging cases to updating records to pulling a supervisor view to exporting a report for leadership, is designed to feel familiar from the first week. For configuration changes and workflow 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 more leverage out of the platform, not a second job.
Every district is different. We'd love to hear about yours, and show how District360 can support your team as a technology partner.
Schedule a Demo