Where the work happens.
The public site is live at citylink.live. The staff and resident workspaces sit behind sign-in.
All productsOne front door,
One front door,
one staff queue.
Permitting, code enforcement and resident status in a single service layer. Residents get one place to file and check. Staff get one queue instead of four systems that do not talk to each other.
The application
What it is for
The situation it walks into.
- Permitting, code enforcement and resident requests live in separate systems, none of which a resident can check.
- Status questions arrive by phone because there is nowhere else to ask them.
- Staff re-enter the same information across systems that were never meant to connect.
- An incomplete application is discovered late, after it has already consumed staff time.
What it does
Four parts, in that order.
01 · Resident intake
One form, one place, with the fields that actually determine whether an application can proceed.
02 · Staff workflows
A single queue with routing, so a filing lands with the person who handles that filing.
03 · Screening
Incomplete applications flagged before a staff member opens them, which is where most of the time goes.
04 · Status communication
A status a resident can check without calling, updated by the workflow rather than by hand.
Where it runs
Live surfaces.
Next step
CityLink
Finished and ready to deploy. We are selecting the first jurisdictions to launch with.