The Simple Framework That Transform Request Processing
The Triage Challenge
In a large organization, IT support typically isn't handled by a single department. When requests come in, it is vital to efficiently route them to the correct supporting individual or department. This way, customers receive the best possible response to their issues .
Having a formal triage process empowers a complex IT organization to respond effectively to end users' needs. The University of Oregon has adopted a simple triage methodology for processing incoming technology service requests: the "Three Cs" — Clean, Clarify, and Conclude .
The Three Cs Framework
1. Clean
Cleaning the request is the process of editing the ticket attributes to ensure the information in the request accurately represents what is being asked .
Why it matters: Fixing data entry errors makes it easier for a technician to understand and complete the work. Cleaning also ensures good data for reporting on the kind of work requested and completed.
Common edits to make:
|
Edit Type |
Description |
|
Title or Subject Line |
Many service requests use generic titles. Edit to describe the work more accurately |
|
Request Type |
Edit to reflect the actual type of request for better reporting and routing |
|
Requestor |
If someone makes a request on behalf of another, ensure the correct person is the requestor |
|
Other metadata |
Check all fields to make sure information is correct or entered if missing |
Heavy duty cleaning: Sometimes you need to create entirely new requests or split requests into multiple tickets :
- New request for piggy-backed issues: If a requestor brings up a new issue while working on an existing request, generate a new service request. Multiple issues in one request cause confusion and inaccurate reporting.
- Split multiple issues: If a request involves multiple issues, each issue should be split into its own individual service request. If all issues can be resolved in one interaction, the extra effort may not be worth it. But if any part requires follow-up, separate tickets should be created.
Reasons for splitting requests :
- Clarity: Notes and conversations for each issue stay separate and easier to track
- Delegating: Different issues can be sent to the right department or team member
- Reporting: Categorizing each issue appropriately gives a more accurate picture of performance
2. Clarify
Clarify is the process of asking the follow-up questions necessary to accomplish the work. This may include requesting information needed to complete the cleaning process or to perform the work .
Why it's important: The clarify stage is often the most challenging and often skipped. The tendency is that whomever the request is assigned to can (and likely will) perform these steps. But working on the clarify step can significantly speed up the close time of a request.
The cost of skipping clarify :
- Request is received and cleaned
- Triage coordinator reviews and assigns the request
- Request waits for review by responsible party (unknown duration)
- Responsible party reviews the request (repeating the triage coordinator's work)
- Responsible party asks the clarifying questions
- Responsible party awaits response (unknown duration)
- Responsible party completes the work
Skipping the clarify step increases the time to close by adding multiple unknown-duration steps.
Benefits of clarifying at triage :
- Shortens the response time in gathering needed information
- Inserts an additional contact point with the requestor
- Builds trust — the requestor received a quick response with meaningful questions
Common clarifying questions :
|
Category |
Questions |
|
The problem |
What are the symptoms? Who is reporting? Full problem description. Is this the first occurrence? |
|
The environment |
What operating system? What hardware? What software is involved? Where does the problem occur? |
|
The timing |
When does the problem occur? Only at certain times? How often? |
|
Conditions |
Is it repeatable? Only under certain circumstances? Do other things fail at the same time? |
|
Recent changes |
Has there been a change to the environment? New equipment? New construction? Exposure to liquid or foreign material? |
3. Conclude
Conclude is the final step of triage: completing the triage process and routing the request to the appropriate service provider who will be responsible for completing the work .
The Big Picture
The concept of the Three Cs was developed to keep the triage coordinator focused on the three most important aspects of the process :
- Clean: Does the request accurately represent what's being asked?
- Clarify: Do we have enough information to complete the work?
- Conclude: Have we routed it to the right person?
Why the Clarify Step Matters Most
The clarify step is often the most challenging and most skipped. But it can also have the biggest impact on resolution time. Asking the right questions at triage prevents the request from bouncing between teams or waiting for clarification multiple times during the fulfillment process.
When organizations invest in clarifying at triage, they see :
- Shorter time-to-close
- Less rework
- Better trust with requestors
- More consistent service delivery
Conclusion: Triage Is the Foundation of Service Excellence
The Three Cs provide a simple, memorable framework for request triage. By cleaning data, clarifying requirements, and concluding with proper routing, organizations can dramatically improve the speed and quality of service request fulfillment.
Action Items for Your Organization
- Train your triage team on the Three Cs framework
- Create a checklist of common clarifying questions
- Measure how often clarify is skipped and the impact on resolution time
- Track improvements after implementing the Three Cs
