Administrative Procedure / Case
Describe one public-law administrative case with stable identity, procedural evidence and qualified outcome references.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 6 findings · 12 questions
Case and parties What the case is about and who is involved.
Initiation
How the case began and under which legal basis.
Legal basis and subject
The provision and subject matter of the case.
- Which legal provision does the authority act under in this case?
- Was the case started on application or by the authority on its own initiative?
Parties and representation
The applicant, affected parties and their representatives.
- Who are the parties to the case, and are any represented?
- Were all persons whose rights are affected notified?
Procedure The steps the authority takes before deciding.
Investigation and hearing
Evidence gathering and the right to be heard.
Right to be heard
The opportunity given to parties to comment before a decision.
- Were the parties given access to the file and a chance to comment?
- Which evidence and opinions did the authority obtain?
Time limits
Statutory deadlines for handling and deciding.
- Which deadline applies to the decision, and has it been extended?
- Does silence of the authority have a legal effect after the deadline?
Decision and review The outcome and the remedies against it.
Decision and remedies
The administrative decision, its reasons and available review.
Decision
The decision with its operative part and statement of reasons.
- What did the authority decide, and on which date was it notified?
- Does the decision state reasons and information on available remedies?
Review
Internal objection, appeal or judicial review.
- Was an objection or appeal lodged, and within the time limit?
- Is the decision final, or is review still pending?
Classifiers Filled
- Family
- World Models
- Category
- Society, people and institutions
- Entry kind
- entity
- Navigation path
- NAV.SOC.POL.ADM
- Domain
- SOC.POL.ADM
- Industry
- Cross-industry
- Tags
- administrativeprocedurecasesoc.pol.adm
What it is Filled
An administrative procedure case is a matter handled by a public authority under public law that leads to an administrative decision, such as granting, refusing or revoking a right or imposing an obligation on a party. It covers the case from initiation to final decision and internal review; court litigation and private service tickets are outside it.
In scope
- Authority-qualified case identity, subject matter, linked cases and applicable procedure profile
- Initiation, participants, representation, impartiality, evidence, participation and restricted file access
- Procedural progress, uncertain time limits, outcome and notification references, review and record continuity
Out of scope
- Procedure definitions, legislation, authority and party master records
- Court litigation as an independently mastered case; private service tickets
- Issuing or serving decisions, filing appeals, determining legal validity, executing enforcement or implementing a universal deadline engine
Why it exists Filled
Describe one public-law administrative case with stable identity, procedural evidence and qualified outcome references.
Distinguishing features Filled
- It is decided by a public authority under public law, not by a court.
- It ends in an administrative decision with legal effect on a party, unlike a general service ticket.
- Procedural rights such as the right to be heard and to reasons are part of the subject.
- Distinct from the public service description, which describes the offering rather than one case.
What robots and AI may and may not do Filled
Must not
- Issue or sign an administrative decision on the authority's behalf.
- Disclose case files to persons who are not parties or otherwise entitled.
- Omit evidence favourable to a party when summarising the file.
- Advise a party that a deadline is met when it is not verified.
- Make a fully automated decision where the law requires human assessment.
Only with a human decision
- Deciding the case and signing the decision.
- Granting or refusing access to the file.
- Deciding on an objection or internal appeal.
May
- Report the status, deadlines and next steps of a case to its parties.
- Check an application for completeness against the stated requirements.
- Remind case officers of approaching statutory deadlines.
- Prepare a draft summary of the file for a case officer.
Moral aspects Filled
- Administrative decisions affect livelihoods, residence, property and freedom of action.
- Parties are entitled to be heard, to receive reasons and to seek review.
- Automation in case handling can hide errors and bias unless decisions stay reviewable.
Who is affected
- Applicants and other parties
- Third parties affected by the decision
- Case officers and the public authority
- Review bodies and courts
Owners Filled
Steward
The competent public authority, through its responsible case officer, answers for the case file and decision.
Roles
- Case custodian
- Maintain identity, file continuity and authorized stewardship
- Authorized case officer
- Record supported procedural events within evidenced delegation
- Legal reviewer
- Assess competence, exceptions, time rules and unresolved legal effects
- Access and records officer
- Approve recipient scopes, retention, legal holds and disposal
- Participant or representative
- Provide evidence and inspect only the permitted view within verified standing or mandate
Master systems
- Case management systems of public authorities
- Electronic records management systems
Links to other meta-models Filled
aligned
- WM-ACT-021 - Candidate generic case relationship only; inheritance and mandatory runtime dependency are not ratified.
- CMMN 1.1 - Selected logical case, file and event alignment; no executable conformance claim.
- CPSV-AP 3.2.0 - External public service and evidence definitions; no identity equivalence with a case instance.
- PROV-O 2013-04-30 - Assertion attribution and derivation; not proof of legal authority or truth.
references
- WM-REC-009 - Optional application or request master. Ex officio initiation does not require this record.
- WM-REC-010 - Optional decision or approval master with independent identity; open cases and other outcomes must remain valid.
- WM-POL-016 - Competent institution candidate reference; pin and verify the neighbor boundary before integration. Authority evidence remains necessary even if this model binding is unavailable.
neighbor
- WM-ACT-021 Service Case / Ticket - Registry parent is a candidate alignment, not ratified inheritance. Public-law competence and qualified procedural rights distinguish this instance from a generic service ticket.
- WM-REC-009 Application / Request Record - Optional external reference. Official initiative and referrals do not require an application; the candidate COMPOSE edge cannot imply mandatory containment.
- WM-REC-010 Decision / Approval Record - Optional external reference with its own identity, author and revision. An active case may have no decision and other outcomes must remain representable.
- Procedure model, public service and court case - The root persists across procedural events. CMMN models and CPSV-AP services are definitions or descriptions; a judicial challenge retains an external identity.
parent
- WM-ACT-021
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A case is identified by the file or reference number assigned by the competent authority.
- Decisions carry their own reference and date of notification.
Direct properties not applicable Not applicable
Not applicable
An administrative case is a legal procedure with no physical properties to measure.
Recognition optional Filled
- An administrative case has a competent authority, a legal basis, parties and ends in a decision.
- Often confused with court proceedings, a customer service ticket or a general enquiry.
Capabilities and actions required Filled
- Cases can be opened, suspended, decided, withdrawn and reopened on review.
- Files can be shared with parties and transferred to a review body.
Hazards and failure modes required Filled
- Missed deadlines that cause loss of rights or deemed decisions.
- Unlawful disclosure of personal data in case files.
- Decisions without reasons that cannot be effectively challenged.
Standards and interfaces required Filled
- SEMIC Core Public Service Vocabulary Application Profile (CPSV-AP) for the related public service.
- Records management standards such as ISO 15489 for the case file.
Context of use required Filled
- Used across national, regional and local public authorities.
- Governed by national administrative procedure law and, in the EU, by the right to good administration.
Sources Filled
- Case Management Model and Notation - Object Management Group
- German Administrative Procedure Act (VwVfG) - Federal Ministry of Justice and Federal Office of Justice
- The European Code of Good Administrative Behaviour - European Ombudsman
- EU Charter Article 41 - Right to good administration - European Union Agency for Fundamental Rights
- Core Public Service Vocabulary Application Profile - European Commission SEMIC
- PROV-O: The PROV Ontology - World Wide Web Consortium
- General Data Protection Regulation - European Union
- Date and Time on the Internet: Timestamps - Internet Engineering Task Force
- Charter of Fundamental Rights of the European Union, Article 41 Right to good administration (European Union)
- Recommendation CM/Rec(2007)7 on good administration (Council of Europe)
- European Code of Good Administrative Behaviour (European Ombudsman)
Open questions
- Verify current consolidated legal texts, effective dates, exception coverage and applicable records/privacy regimes for each adopting jurisdiction.
- Develop and test nested schemas and mappings with cases covering official initiative, disputed service, partial outcomes, reopening, confidentiality and lawful disposal.
- Restore independent external review before any canonical or publishable-draft promotion.
- Independent external review is waived; this local Codex self-audit cannot substitute for it.
- Live consolidated legal versions, full source retrieval, translation, licensing and case-specific applicability remain to be verified.
- Nested field schemas, executable deadlines, calendar rules, automated-decision authorization and remedy computations are not implemented.
- Sector-specific procedures, enforcement, mass participation, emergency derogations and non-European profiles need separate research.
- CMMN, CPSV-AP and PROV-O mappings, neighbor bindings and adversarial instance fixtures require conformance work.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-pol-017-administrative-procedure-case/spec.yaml, ver-cy/world-models/card-supplements/wm-pol-017-administrative-procedure-case.json