Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Municipal Corporation ERP
- Application sources
- Document sources
- Service delivery systems
Municipal Corporation ERP organizes public service applications around a case, its service definition, assigned person and supporting evidence. An operator records the application and its requirement lines.
verified waits for the municipal corporation ERP operator
| Number | Name | Submitted at | Assigned to | Definition | |
|---|---|---|---|---|---|
| CSS-76485 | Tree removal request at Pine Lane | 22 Oct | Rosa Jiménez | Sidewalk repair requests | |
| CSS-28533 | Sidewalk repair outside 18 Alder Street | 24 Oct | Elena Marquez | Streetlight fault reporting | |
| CSS-35435 | New food vendor permit application | 31 Oct | Elena Marquez | Residential waste collection | |
| CSS-12667 | Missed waste collection on Birch Road | 17 Oct | Kenji Sato | Accessible parking permits | |
| CSS-91978 | Streetlight outage at Market Square | 01 Nov | Kenji Sato | Streetlight fault reporting |
Municipal Corporation ERP Reviewer approves, returns or rejects the case revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep the responsible organization, service definition and staff assignment clear for each case.
Cases
| Number | Name | Completed at | Delivery reference | Definition | |
|---|---|---|---|---|---|
| CSS-20874 | Tree removal request at Pine Lane | NOTICE-260418 | Accessible parking permits | ||
| CSS-24249 | Sidewalk repair outside 18 Alder Street | NOTICE-260431 | Accessible parking permits | ||
| CSS-60534 | New food vendor permit application | NOTICE-260452 | Street tree maintenance | ||
| CSS-14306 | Missed waste collection on Birch Road | NOTICE-260467 | Residential waste collection | ||
| CSS-45101 | Streetlight outage at Market Square | NOTICE-260483 | Street tree maintenance |
Capture a public service application and give the next person a traceable case to work.
Cases
| Number | Name | Status | Submitted at | Definition | |
|---|---|---|---|---|---|
| CSS-88467 | Tree removal request at Pine Lane | Draft | 11 Oct | Sidewalk repair requests | |
| CSS-33493 | Sidewalk repair outside 18 Alder Street | Submitted | 27 Oct | Street tree maintenance | |
| CSS-84309 | New food vendor permit application | Verified | 22 Oct | Storm drain maintenance | |
| CSS-50587 | Missed waste collection on Birch Road | Decided | 11 Oct | Street tree maintenance | |
| CSS-15792 | Streetlight outage at Market Square | Delivered | 28 Oct | Street tree maintenance |
Keep each service requirement and supporting document tied to the case it supports.
Approval conditions
| Parent | Sequence | Description | Submitted at | Outcome | |
|---|---|---|---|---|---|
| Tree removal request at Pine Lane | 30 | Provide site photographs from both directions | 23 Oct | Pending | |
| New food vendor permit application | 70 | Attach current food safety certificate | 28 Oct | Pending | |
| Sidewalk repair outside 18 Alder Street | 60 | Confirm property access for inspection | 31 Oct | Pending | |
| Sidewalk repair outside 18 Alder Street | 70 | Submit marked plan of proposed bay | 20 Oct | Pending | |
| Accessible parking bay request | 90 | Provide proof of public liability cover | 24 Oct | Pending |
Record a reviewer's decision against the exact case revision and evidence considered.
Approval conditions
| Case | Reviewer | Source revision | Decision | Evidence reference | |
|---|---|---|---|---|---|
| Streetlight outage at Market Square | Maya Torres | 690 | Pending | PHOTO-260418 | |
| Sidewalk repair outside 18 Alder Street | Lena Müller | 960 | Pending | CERT-260431 | |
| Drainage complaint near Willow Park | Samuel Boateng | 170 | Pending | INSP-260452 | |
| Accessible parking bay request | Lena Müller | 420 | Pending | PLAN-260467 | |
| Accessible parking bay request | Ibrahim Okafor | 30 | Pending | SURVEY-260483 |
Trace execution attempts, delivery references and corrective work for a decided case.
Decisions
| Case | Reviewer | Source revision | Reason | Decided at | |
|---|---|---|---|---|---|
| Sidewalk repair outside 18 Alder Street | Noah Campbell | 850 | Street tree poses clear access risk | 28 Oct | |
| Streetlight outage at Market Square | Aisha Rahman | 760 | Certificate does not cover this activity | 16 Oct | |
| Accessible parking bay request | Samuel Boateng | 710 | Sidewalk damage meets repair threshold | 17 Oct | |
| Drainage complaint near Willow Park | Maya Torres | 570 | Site falls outside service boundary | 03 Nov | |
| Streetlight outage at Market Square | Ibrahim Okafor | 20 | Evidence supports permit approval | 13 Oct |
Explain case progress, review decisions and exceptions from linked records.
Case state history
| Source | From status | To status | Occurred at | Source revision | Actor | |
|---|---|---|---|---|---|---|
| New food vendor permit application | Submitted | Awaiting evidence | 24 Oct | 130 | Rosa Jiménez | |
| Tree removal request at Pine Lane | Awaiting evidence | Under review | 03 Nov | 930 | Rosa Jiménez | |
| Sidewalk repair outside 18 Alder Street | Under review | Inspection scheduled | 20 Oct | 810 | Lena Müller | |
| Missed waste collection on Birch Road | Inspection scheduled | Decision pending | 29 Oct | 320 | Aisha Rahman | |
| Sidewalk repair outside 18 Alder Street | Decision pending | Approved | 13 Oct | 380 | Sanjay Patel |
Service application to delivery ships ready to use. One step needs a named approval before the work moves on: Independent decision (Municipal Corporation ERP Reviewer).
Define the organization and public service.
Record the request and its assigned owner.
Check each requirement and supporting document.
A separate reviewer decides the case revision.
Follow the operation trace to a confirmed result.
Assign corrections and retain the earlier history.
Open any ca to see its case documents, the roles that work on it, its process stages and its approvals on one page.
Submitted at, Assigned to and Definition.
Each line is linked to this ca.
Municipal Corporation ERP Reviewer, Read Only Analyst and Municipal Corporation ERP Administrator, each with their own permissions.
Service setup, with the role that acts.
Independent decision, with who decides.
Sidewalk repair requests
| Case | Title | Document date |
|---|---|---|
| Missed waste collection on Birch Road | Tree condition photographs | 26 Oct |
| Streetlight outage at Market Square | Food safety certificate | 22 Oct |
| Sidewalk repair outside 18 Alder Street | Sidewalk damage inspection report | 04 Nov |
The reviewer records decisions and reads the case evidence that supports them.
Signed in as Municipal Corporation ERP Reviewer
| Decision | Approver | |
|---|---|---|
| Independent decisionA separate reviewer decides the case revision. | Municipal Corporation ERP Reviewer |
Everyone opens Municipal Corporation ERP to the work that is theirs. Pick a role to see what it starts with.
Reviews independent assigned municipal casework: record entry on Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.
This is the first screen this role sees.
Follow-up actions · Municipal Corporation ERP Reviewer
Reads authorized summaries and aggregates across every table plus the four municipal pages. No record creation or editing, no schema or administrative capability.
This is the first screen this role sees.
Operation runs · Read Only Analyst
Maintains approved municipal configuration: record entry on Public Services, read-only on all operational, review and provenance tables, and access to all four municipal pages. No schema editing, deletion, bulk operations or export grants.
This is the first screen this role sees.
Operation runs · Municipal Corporation ERP Administrator
Prepares assigned municipal casework: record entry on Cases, Case Requirements, Follow Up Actions and Case Documents, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.
This is the first screen this role sees.
Follow-up actions · Municipal Corporation ERP Operator
Oversees account access and service setup while operational decisions remain with the assigned municipal roles.
Follow service case outcomes and investigate the records behind each result.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 38 | ||
| Submitted | 11 | 29% | |
| Verified | 4 | 36% | |
| Decided | 2 | 50% |
Sample counts per stage
Group cases by service definition and current status to find pending casework.
Compare submitted and completed dates for delivered cases by service.
Show each case and its accepted, rejected and pending requirement lines.
Show each case with its document verification states and verifying people.
Show decisions, reviewers and reasons under each case and source revision.
Group outstanding actions by assignee, due date and status.
Trace failed or reconciliation-required runs through their ordered steps.
List delivered cases with completion dates and delivery references.
See how Municipal Corporation ERP fits your kind of team.
Coordinate resident service requests from intake through independent review and delivery.
Keep services, staff and case ownership distinct across municipal departments.
Review applications against a named program and preserve the decision trail.
Each stage of service application to delivery names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Ask Proto to prepare case context and help the team review its next action.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 14 tablesStart with one team and one process, then add the rest once the basics are running.
Agree the organization, public service definition, policy reference, effective dates and staff responsible for intake and review.
Map the source request to its citizen reference, case number, requirements and documents.
Move a representative case from Draft to Submitted and Verified, then have a separate reviewer approve or return the exact revision.
Inspect the run, attempts and external receipt before entering a delivery reference and completion date.
Assign open follow-up actions and check case history, returned decisions and failed runs with the people who own them.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Municipal Corporation ERP for your business. Start with one public service, its organization and staff, and a representative case from intake to delivery.
A case has a number, citizen reference, organization and public service definition. The assignee owns the next preparation step.
Each requirement line has its own description, source reference and outcome. The operator can keep an incomplete line Pending while working on its supporting evidence.
A supporting document retains its attachment, date, external reference, verification state and verifying person.
Municipal Corporation ERP Reviewer records an independent decision against a specific case revision, with a reason and evidence reference.
The reviewer records the reason. An operator can assign follow-up work, correct the case and present the successor revision for review.
Inspect the operation run, its steps and execution attempts. Record the delivery reference and completion date after the result is confirmed.
Case state history records transitions with an actor, time and source revision. Decisions retain the revision reviewed.
Use the failure reason, provider reference and operation trace to investigate. Assign a follow-up action with an owner and due date when work remains.
Start free, then use Proto to change fields, steps and approvals before your team goes live.