Manage information requests
How manage information requests are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Manage information requests is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: In the absence of seeded child occupations, the scalar is derived entirely from the process name 'Manage information requests' and its government framework context. Handling, retrieving, and routing informational queries are inherently knowledge-work activities executed via databases, email, and software, placing this process firmly in the center of the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Manage information requests sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Manage information requests inherits.
Where Manage information requests sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: A citizen, journalist, or internal stakeholder submits a formal request for government records or data.
- Receive and log the formal information request
- Evaluate the scope and legal validity of the request
- Identify and query the relevant departments or data custodians
- Compile the requested records and data
- Review the materials and redact protected or exempt information
- Transmit the final information package to the requester
- Document the fulfillment and close the request record
Outcome: The requested information is compiled, reviewed, redacted as required by law, and delivered to the requester.