Capital Improvement Program Portal

The city's 48-project, $74.9 million five-year capital program lives in a council PDF map and a spreadsheet, so residents, council members, and project managers each work from a different version and the Engineering Division answers the same "when are you fixing my road" call every week.

Project managers update phase, schedule, spending, and documents once a month from a spreadsheet or a short form; communications staff approve what is public; residents and council members find any project by street, district, phase, or fiscal year on a phone.

The outcome is one map, list, and timeline that answers what is happening on a street and when, a link for every project that can go in an email or a council packet, and a staff view that tracks spending against budget.

1. The spreadsheet template's columns are the data model in section 5, so the import is a validation and an update, not a translation.
2. The public portal reads only the public layer view; staff sign in to the same portal to see spending and project-manager contacts.
3. The Starter tier is an Experience Builder app on the same layers; the custom portal replaces it at Standard without changing the data.

These tables are generated from the same schema file the demo app and the data generator use, so the sheet cannot drift from the data. Computed fields are derived in the office, not collected.

• The public portal reads only a public layer view. Spent to date and project-manager emails are internal fields and are not in that view; residents see the division's shared address.
• Public layers contain no personal information. Subscription emails, if collected, go to the city's notification service, not to the GIS.
• Project managers edit only their own projects (ownership-based editing); only the coordinator and the consultant can add or delete projects.
• The portal's basemap key is scoped to basemaps only and restricted to the city's domains.
• At handover the consultant's admin role is converted to a named support account or removed, per the city's policy.

• Esri US list prices as of 2026-10-08; confirm at purchase. Licenses are bought in the city's name.
• The consultant's own Creator seat is separate and not billed to the client.
• Worked total for the roles above: $1,700 per year to Esri.

The demo on this site is the Standard tier.

The client signs this list at Issued for Use. The final 20% is invoiced on signature.

1. 1A filter URL shared by email opens to the same view: the same filters, list, timeline, and map.
2. 2Public mode shows no internal columns (spent to date, project-manager email) in the list, project page, charts, or export.
3. 3The monthly import runs in under 10 minutes on the full CIP spreadsheet and produces a validation report.
4. 4List, map, and timeline always show the same set of projects (checked on five filter combinations).
5. 5A project link opens with that project selected and zoomed.
6. 6Budget totals on the portal equal the sum of the listed projects to the dollar.
7. 7Every field in the data model is populated or explicitly null on 100% of loaded projects.
8. 8The core workflows (monthly update, onboarding, fiscal-year rollover) run end to end by city staff without the consultant present.
9. 9The portal loads and is usable on the city's phones and embeds in the city site.
10. 10The record set is delivered.

• City: project managers update monthly; communications staff approve public changes; the coordinator runs or monitors the import and reads the validation report.
• Monthly (consultant, under retainer): import health, usage and credit check, broken document links.
• Quarterly: SDK and dependency updates to the portal, backup export of the hosted layers to GeoPackage, health report.
• Fiscal-year rollover each October: archive completed projects, add the new fifth year, move the portal's fiscal-year range, re-check district totals.
• Annually: ArcGIS Online renewal reminder, review of the public and internal field split with communications.
• Retainer covers 2 hours of small changes per month; beyond that at the hourly rate with a not-to-exceed.

Demo data is synthetic. Ridgeline County and the City of Ridgeline do not exist. Projects, budgets, and dates are generated; the data model, the SDK, and the workflows are real.

What to tap

1. Filter to Construction and tap a project bar on the timeline
2. Open a project page and check its milestones
3. Toggle 'View as public' to see what the city hides

Generator seed 102 · demo clock 2026-10-01 · projects 48 · projects_pt 18 · projects_ln 20 · projects_pg 10 · districts 5 · documents 84 · milestones 217 · program budget $74,923,000 · in construction 12 · lane closures 6