These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Municipal Corporation ERP
- Features
- Independent decisions
Independent decisions
Record a reviewer's decision against the exact case revision and evidence considered.
OverviewPending Decisions×
Municipal Corporation ERP · Independent decisions
New
Pending Decisions
Approval conditions
| Case | Reviewer | Source revision | Decision | Evidence reference | |
|---|---|---|---|---|---|
| CSS-18438 | 690 | Pending | ER-384 | ||
| CSS-21114 | 960 | Pending | ER-661 | ||
| CSS-50959 | 170 | Pending | ER-858 | ||
| CSS-18891 | 420 | Pending | ER-296 | ||
| CSS-14200 | 30 | Pending | ER-388 |
6 of 6 records
ER-384Decisions · DCS-67309
PendingCaseCSS-18438
Source revision690
What you can do
Keep preparation and decision separate
The operator prepares the case and its evidence. A reviewer records the decision. Each decision links to a case, reviewer and source revision, with a date, reason and evidence reference. The decision can be Pending, Approved, Returned or Rejected. Tying the review to a revision matters when a returned application is corrected: the earlier decision still explains the version the reviewer actually saw.
Cases and Details shows pending decisions beside the selected case. The reviewer can inspect the case’s requirements, documents, status history and operation trace in context. A decision should be based on the current case facts and its supporting evidence, with a reason that another staff member can understand after the handoff.
How the work is organized
- Separate authority. The operator maintains cases and evidence; the reviewer records decisions against the case.
- Exact revision. A review identifies the source revision so later corrections do not rewrite an earlier approval.
- Reasoned outcome. Returned and rejected decisions carry a reason and evidence reference for the next action.
What to agree during setup
Agree which reviewers cover each service and organization, and how the team avoids self-review. Decide what evidence the reviewer must inspect before approving a case. A returned case should have an explicit action owner and a clear explanation of what needs correction. The team should also agree what constitutes a material case change that calls for a new revision and a fresh decision.
Take a submitted case with a verified supporting document and a pending requirement. The reviewer should be able to see the outstanding requirement and return the current revision with a reason. The operator records the correction and follows up with the applicant. When the revised case is ready, the reviewer considers that new revision without changing the earlier return. This preserves both the reason for the delay and the basis of the eventual approval.
Check the handoff on an actual case
Open Pending Decisions and choose a case assigned to the reviewer. Compare its revision with the decision’s source revision. Check requirement outcomes and document verification in Cases and Details. Record an approval only when the case and evidence are ready. For a return or rejection, enter the reason and the evidence reference that supports it. Another person should be able to find that explanation from the case later.
A decided case can proceed toward delivery. The state history records the status change and actor. If a later correction supersedes an executed revision, the earlier review and delivery record remain separate from the successor revision. A reviewer deciding that successor must examine its own evidence rather than relying on the prior approval.
What your team sees
- Pending Decisions — Decisions awaiting the reviewer’s action, with case and source revision visible.
- Returned Decisions — Returned cases with their reason and decision date for correction work.
Follow the work through
Use the independent decision process before delivery.
What it keeps track of
Data model- Decisions
- Independent reviewer decisions recorded against an exact source revision.
- Cases
- Requests, applications and cases submitted for a public service.
- Case requirements
- Observation-level requirement, document and line detail captured against a service application.
- Case documents
- Uploaded and verified supporting documents and source evidence.
- Case state history
- Immutable workflow-written status transition history for each case.
- People
- Staff, officers, reviewers and assigned team members.
- Follow up actions
- Assigned outstanding actions, corrections and outstanding requests for a case.
Who uses it
Permissions- Municipal Corporation ERP Reviewer
- Records the independent decision.
- Municipal Corporation ERP Operator
- Prepares the case and responds to returns.
- Read Only Analyst
- Reads authorized decisions.
- Municipal Corporation ERP Administrator
- Maintains the service definition without taking the reviewer's decision.
Set up Municipal Corporation ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.