Research question and scope

This protocol measures how many escalation briefs contain the information an owner needs to decide. The unit is one escalation event, identified by the case, the sender, the receiver, and the time it was sent. A brief is complete when it names the decision, the facts, the customer impact, the options, the recommendation, the deadline, and the fallback. The study measures brief completeness, not the quality of the decision.

Set the scope to one client, one support team, and one escalation channel for a fixed window. Record the template version, the owner group, and the service expectation at the start. If the template or channel changes during the window, keep the earlier definition for the full sample or analyze the change separately. A new template can change the measured rate without changing the underlying habit.

Unit and population

Define the population as every escalation sent during the window. The unit is the escalation event, not the case, because one case can be escalated more than once. An escalation that is reopened or re-sent remains one unit with a second event. Record each event so the analysis can show whether the second attempt was more complete.

Exclude messages that only notify an owner without asking for a decision, and record the exclusion count. Include escalations sent through chat if that is the channel the team uses. Include escalations that were answered immediately, because a fast answer can hide an incomplete brief. Test the unit definition on five real escalations before collection begins.

Defining a complete brief

Define the decision question as the specific choice the owner must make. Define the facts as the customer, commitment, current state, and evidence needed to evaluate the choice. Define the impact as what the customer will experience if the owner does nothing. Define the options, recommendation, deadline, and fallback as separate fields. A brief that omits any field is incomplete.

Do not score the brief on length or politeness. A short brief can be complete, and a long one can omit the decision. Use a binary present or absent score for each field, plus a short note for a field that is present but unusable. The binary score keeps two reviewers consistent; the note explains the gray cases.

Evidence standard

For each escalation, capture the message, the case record, the sender, the receiver, the time, and the response. Add the template version and the channel. Store the brief with the case so the evidence survives a later review. A message without the case record cannot show whether the facts were accurate or whether the owner had context.

Record whether the owner asked a follow-up question and what field it concerned. A follow-up is evidence that a field was missing or unclear even if the brief technically included it. Record whether the sender was available to answer during the decision window. If the reason code is other, require a short note from the scorer.

Sampling and collection

Draw the sample from the escalation channel rather than from a list of difficult cases. Record the export date, filters, row count, and selection rule. Include every sender and every owner group so the result is not dominated by one person or one busy week. If the channel is ordered by time, a fixed interval spreads the sample across the window.

Collect the brief as it was sent, not as it looks after later edits. If the sender added facts in a follow-up message, record the edit time and score the first version separately. Do not reconstruct a missing field from the owner's reply. Note the collection date separately so the reader can see how much of the record has aged.

Scoring the brief

Score each of the seven fields as present or absent, then calculate the share of complete briefs and the average number of fields present. Report the fields that are most often missing. A brief with six of seven fields may still be unusable if the missing field is the decision. Show the field-level result, not only the total.

Have a second reviewer score a sample of ten briefs independently and compare the results. Where the two disagree, refine the definition or the example. A scoring rule that cannot survive two reviewers is not ready for a wider sample. Publish the scored examples, with identifying details removed, beside the result.

Analysis and reporting

Report the number of escalations, the share that were complete, and the field-level completion rate. Break the result down by sender, owner group, and request type. Use the same denominator for every rate and state the exclusions. A percentage without its base is not actionable for the operations owner. Show the field-level table beside the headline rate so the owner can see what to fix.

Compare the completion rate with the template version and the training dates. If completion rose after a template change, the template may be doing the work. If it rose only for one sender, the training or the person may be the cause. Do not present a difference as causation without a controlled comparison.

Limitations and sources of error

The record cannot show briefs that were never sent because the specialist solved the case alone. It also cannot show a complete brief that the owner ignored. A brief may be complete in the message but rely on a link that later broke. The study measures recorded completeness, not the quality of the eventual decision.

Messages can be edited or deleted, and a decision may happen in a call that leaves no record. A sender may write a better brief when they know the sample is being scored. Record those cases and their treatment rather than dropping them. If the person who wrote the template also scored the briefs, note the independence limitation.

Review cadence and next action

Give the result to the support lead and the owner group and ask for one observable change. The change might be a required first line, a shorter template, or a rule that the fallback must be pre-approved. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the template and the training at the same time.

Repeat the protocol with the same definitions after the change and compare the same fields. If completeness rose but the number of escalations fell, the team may be solving more cases alone rather than writing better briefs. Ask the owner group to confirm that the same cases still reach them. Close the review when the owner accepts the finding and the next sample is scheduled.

Training implications

Use the missing fields as training material, not as a general reminder to communicate better. Give each specialist two real briefs, one complete and one incomplete, and ask them to name the missing field. Practice rewriting the first three lines until the decision and impact are clear. The exercise should take fifteen minutes and produce one corrected brief.

Train the owners as well. An owner who answers a vague brief without asking for the decision teaches the team that completeness is optional. Give owners a short response they can use to return an incomplete brief with the missing field named. The standard has to hold on both sides of the escalation.

Reporting to the client

Report the result in a form the client can act on: which fields are missing most often, which request types produce incomplete briefs, and what the team will change. Avoid presenting the numbers as a grade for individual specialists. Use examples with identifying details removed. The client should leave with one change it can approve.

Show the denominator and the exclusions so the client can judge the sample. If the sample is too small to support a conclusion, say so. A cautious report is more useful than a confident one built on a handful of messages. Offer to repeat the measurement after the change and name the date.

Replication and version control

Keep the definitions, the template version, and the export query with the report. A second analyst should be able to repeat the measurement on a later window and compare the same fields. If the definition changes, publish a new baseline rather than mixing periods. Replication is what turns a one-time review into an operating measure.

Schedule the next measurement before the first report is filed. The date should be far enough away for the change to take effect but close enough to keep attention. Assign the owner who will run it. A protocol that is never repeated becomes a story about the past. Put the date in the same calendar as the template review so it is not forgotten.