Using Information Request Playbook
If you're an information request case agent or manager, you can use the Information Request Playbook for Public Sector Digital Services to manage and resolve requests for information and public records.
A playbook provides you with step-by-step guidance through the life cycle of an information request case.
- View the playbook stages and activities.
- Select an activity and perform the work to complete that activity.
- Mark an activity as complete and move to the next activity or stage.
- Complete the stages and activities to resolve the case.
The workflows for a type of case and the activities that you need to resolve these cases are in the playbook. By using a playbook, you can visualize the entire life cycle of the information request workflow.
Playbook stages
| Task | Description |
|---|---|
| Intake | Guides you through the record creation process by capturing the details of the information request and assigning it to the right agent. |
| Review | Acts as a checkpoint for duplicate cases and provides you with an opportunity to review the case details to verify that the issue is valid and needs to be resolved. |
| Process | Guides you through the activities for the information request fulfillment. |
| Decision | Captures and communicates the documents and information to the constituent and any other agents or involved parties. |
Playbook layout
A playbook is made up of several areas, including the playbook life cycle, the playbook work area, and the contextual side panel. The activity view determines how the stages and activities appear in the playbook.
The default activity view for the Information Request Playbook is the Process-based experience view. This view, which is shown in the following example, shows constituent or business information and case task information at the forefront of the playbook work area as you work on it.
- A horizontal stage picker that gives the agent a complete view of the entire process and where they currently are in that process. Agents can use the stage picker to track their overall progress as they work on cases.
-
Record information on the left side of the page, such as the contact information that is always available.
- Related records in the contextual side panel supported by the dynamic related records component.
| Playbook area | Description |
|---|---|
| Playbook header |
|
| Playbook Lifecycle |
|
| Playbook work area |
|
| Contextual side panel |
|
| Constituent or Business Card |
|
- Intake
- Review
- Processing
- Decision
Stages in an Information Request Playbook
The Information Request Playbook experience starts with the Intake stage. This stage is the default playbook stage for a new information request case. Use this playbook stage to gather information about the requester, the documents being requested, and any exemption categories that the request falls into. You can also request additional information from the requester.
The playbook continues with the Review stage. In this stage, you can do the initial troubleshooting on the case, evaluate similar or duplicate requests, and determine whether the information requested can be released and if a fee needs to be charged. You can move the case to the next stage when the requester accepts the fee, or if a fee waiver is submitted and approved.
The playbook continues with the Process stage. In this stage, you can assess resources, request a fee approval, create case tasks, and add or request new information before the case resolution begins. The case status changes to Work in Progress once the fee payment is processed or waived. The case is then sent for legal review. After legal review is complete, the case is moved to the Decision stage. You may solicit additional information from the requester at any time during this stage.
The final stage of the Information Request Playbook is the Decision stage. At the Decision stage, the status of the case is updated from Review in Progress to Ready for Decision after the case has passed legal review. A notification is sent to the requester that lets them know that case approval has been has obtained and the requested documents have been uploaded. The requester can then either accept or reject the document. If the requester accepts the documents, the case is automatically closed. If the requester rejects the solution, the case is reopened, and the agent must propose another outcome.