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.
- Election Management
- Features
- Requirements
Requirements
A requirement line records the item the office must examine for a case.
OverviewPending requirement lines×
Election Management · Requirements
New
Pending requirement lines
Approval conditions
| Parent | Sequence | Description | Outcome | Observed on | Source reference | |
|---|---|---|---|---|---|---|
| CSS-97526 | 20 | Pending ar-442 | Pending | 08 Oct | SR-874 | |
| CSS-63579 | 60 | Pending ar-117 | Pending | 25 Oct | SR-589 | |
| CSS-23750 | 90 | Pending ar-324 | Pending | 12 Oct | SR-703 | |
| CSS-14984 | 80 | Pending ar-908 | Pending | 15 Oct | SR-648 | |
| CSS-65038 | 40 | Pending ar-556 | Pending | 07 Oct | SR-885 |
6 of 6 records
Pending ar-442Application requirements · AR-90593
PendingParentCSS-97526
Sequence20
Observed on08 Oct
Source referenceSR-874
What you can do
Keep the working record clear
A requirement line records the item the office must examine for a case. The Case Officer can record its description, sequence, quantity, unit, observed date and source reference. Each line carries an outcome, so a pending item remains visible until the team accepts or rejects it. The parent case ties the line to the application being reviewed. A decision reason can explain a rejected item without losing the original observation.
Application requirements holds observation-level detail for the case: sequence, description, quantity, unit, observed date and source reference. The outcome can remain pending or be marked accepted or rejected. A rejection can carry a decision reason. The parent link keeps each line with its case so the Authorized Reviewer can see what was examined for the submitted revision. The Case Officer should preserve the original source reference when a line is corrected.
How the work is organized
- Record. application requirements holds observation-level detail for the case: sequence, description, quantity, unit, observed date and source reference.
- Review. Agree which observations need separate lines and how officers order them.
- Handoff. At handoff, show the reviewer the source reference and outcome for every material line.
What to agree during setup
Agree which observations need separate lines and how officers order them. Decide which source reference identifies each item, who may mark its outcome and when a rejected line needs a reason. An unresolved line should remain visible in the pending view until the evidence question is answered. Do not treat a completed-line count as a substitute for reading the individual outcomes.
Rehearse one application with lines that have different outcomes. The Case Officer records the observation and source for each, then checks the parent case link. Ask the Authorized Reviewer to explain which lines can support a decision and which need follow-up. If a correction changes a line after review, identify the successor case revision and request another independent decision.
Check the handoff on an actual case
Choose a case with several different evidence items. Enter each item as a separate requirement line with a source reference. Mark one line accepted and another rejected with a reason, leaving an unresolved item pending. The reviewer should be able to see which source each conclusion relies on. Correct a mistaken line through the case revision process rather than silently changing the basis of an earlier decision.
At handoff, show the reviewer the source reference and outcome for every material line. A rejected line should have a reason that another officer can understand. If one line stays pending, assign the evidence question through a case action and keep it visible in the pending list.
What your team sees
- Pending requirement lines — Find observations still awaiting an outcome.
- Rejected requirement lines — Read reasons and source references for rejected items.
Follow the work through
Follow case review from preparation to independent decision. Use delivery and correction when an approved outcome needs execution or an earlier revision needs correction.
What it keeps track of
Data model- Application requirements
- Observation-level requirement, document and line detail captured against a service application.
- Cases
- Election case records for Election Management. The parent record for requirements, documents, actions and decisions.
Who uses it
Permissions- Case Officer
- , Authorized Reviewer
Set up Election Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.