Request handling
Triage incidents, document resolution and track requests.
Support adoption, monitor data quality and improve solutions.
Discuss this subjectAfter launch, usage evolves, data quality deteriorates and requests accumulate. Without a support channel or shared priorities, urgent fixes displace maintenance.
We propose support with an agreed scope: applications, coverage hours, responsibilities and prioritisation rules. Requests are distinguished from incidents and enhancements.
Triage incidents, document resolution and track requests.
Review data issues and support users.
Prepare tests, approvals and agreed updates.
Example coverage matrix to agree together. Hours, response targets and commitments are defined contractually.
| Request type | Required information | Handling to agree |
|---|---|---|
| Application incident | Impact, error and observed steps | Priority, diagnosis and escalation |
| Data issue | Source, period and affected example | Validation with the data owner |
| Enhancement request | Intended use and affected users | Scope, testing and approval |
Application inventory, initial assessment, request channel and priority matrix. Periodic review distinguishes recurring incidents, training needs and planned enhancements.
A few practical points to make scoping and acceptance clearer.
Simulate a report: find the channel, assess impact, assign the request and document its resolution or escalation. Check that the team knows the agreed coverage hours and can find procedures when a contact is unavailable.