Research question and scope
This protocol measures how much of a weekly owner report is copied from the queue rather than interpreted for the owner. The unit is one report line or table row. A copied line repeats a queue field without adding context. An interpreted line explains what changed and what decision it supports. The measure describes report efficiency, not the quality of the underlying work.
Set the scope to one team, one report format, and a fixed number of weekly reports. Record the report template and the queue fields available at the start. If the template changes during the window, keep the earlier version or split the sample. A new template can change the copied share without improving the report.
Keep the review separate from a judgment of the writer. The purpose is to make the report shorter and more useful. A neutral framing makes it easier to remove fields that nobody uses. State the template version in the report.
Record whether the report was written by a person or generated from a template. A generated report may copy more by design. A hand-written report may add interpretation but vary by writer. Note the method with the sample.
Record whether the report has a fixed template or is written from scratch. A fixed template may encourage copying, while a blank page may produce a long narrative. Note the format. The design shapes the content.
Population and unit of analysis
Define the population as every line and table row in the selected reports. The unit is the line, not the report, because one report can mix copied and interpreted content. A line that repeats a queue count with no comparison is copied. A line that compares this week with last week is summarized or interpreted.
Exclude headings, page numbers, and the signature block from the count. Include footnotes if they carry a caveat or a decision. A long footnote that explains a number is part of the interpretation. Record the exclusion rule so the count is reproducible.
Record whether the line led to a decision, a question, or no response in the following meeting. The response is the best evidence of value. A copied line can still lead to a decision, but it is less likely. Compare the two groups.
Count a table row as one line even when it contains several numbers. A row that repeats a queue count is still one copied line. A row that compares two periods is summarized. Keep the unit consistent across reports.
Include the appendix in the count if it repeats queue data. An appendix is often where copied tables accumulate. A report can look short on the first page and long in the appendix. Count the whole document.
Definitions that make the measure reproducible
Define a copied line as a direct repetition of a queue field without comparison or explanation. Define a summarized line as a count or trend with a short comparison. Define an interpreted line as a statement of what changed, why, and what it means for the owner. Publish one example of each.
Define a decision line as a line that names a choice or an approval the owner must make. A line that only describes the week is not a decision line. A report can have no decision line, and that is a finding. Count it explicitly rather than inferring one.
Apply the same definitions to every report and use a second reviewer on a small overlap sample. If the reviewers disagree, the distinction between summarized and interpreted is probably too fine. Simplify the categories before continuing. A clear rule is more useful than a detailed one.
Define a decision line as a line that asks for an approval, a choice, or a change in scope. A line that requests information is a question, not a decision. Count the two separately. A report full of questions may still be useful but it is not decision-ready.
Check whether the report repeats the same number in several places. Repetition adds length without adding information. Count a repeated number once and note the duplication. A shorter report is easier to read.
Sampling and data collection
Select consecutive weekly reports rather than the best examples. Record the report date, the writer, and the template version. Include reports from busy and quiet weeks so the result is not skewed. If the team has several report formats, treat each as a separate sample.
Capture each line as text, its classification, and the meeting response. Add the length of the report and the number of decisions. Store the reports with the classification so the count can be checked. A number without the source reports is not auditable.
Ask the owner after the sample which lines they remember and which they skip. The answer is a useful check on the classification. A line classified as interpreted but never read may not be valuable. Record the owner's comments separately from the line count.
Ask the owner to mark the lines they used in the meeting. A line that was read but not used is different from one that changed a decision. The mark is a simple value check. Use it to test the classification.
Ask the owner how long the report takes to read. A report that takes twenty minutes will be skimmed. A five-minute report is more likely to be used. Record the reading time as context.
Measuring copied share and decision value
Report the share of lines that are copied, summarized, or interpreted. Also report the share of reports with at least one decision line. A report can be long and mostly copied while still containing one useful decision. Show both the composition and the decision value.
Compare report length with the number of decisions and the owner's response. A longer report with no additional decision is a candidate for trimming. A short report with a clear decision is the target. Use counts as well as shares when the sample is small.
Break the result down by writer and by week. A writer with a high copied share may be following the template rather than choosing the content. A busy week may produce more copying because there is less time to interpret. The pattern suggests a template or workload fix.
Compare the copied share in a busy week with a quiet week. A busy week may produce more copying because there is less time to interpret. If the pattern holds, the fix may be a shorter template rather than more training. Report the comparison.
Limitations and next action
The classification cannot capture the value of a copied line that the owner happens to need that week. It also cannot capture a decision that was made outside the meeting. Treat the result as a guide to report design, not as a complete measure of value. Note the meetings that were not observed.
Give the finding to the report writer and the owner together. Remove one copied field and add one interpretation line. Test the new format for a month and repeat the classification. A shorter report that leads to one decision is a better outcome than a complete report that is ignored.
Review the template after the test and keep the fields that changed a decision. A report format should earn its length. The goal is not a perfect classification but a habit of asking what the owner will do differently after reading. Remove a field that never changed a decision.
Remove one copied field and add one interpretation line in a trial report. Ask the owner whether the trial was more useful. A small experiment is more convincing than a debate about report design. Record the result and the date.
Keep the trial report beside the old report for one month. A side-by-side comparison makes it easier to see what was gained and what was lost. Ask the owner which version they would keep. Record the answer and the reason so the next template change starts from a real preference.
Ask the owner to circle one line that changed their thinking. A line that changed a decision is worth keeping, even if it is copied. A line that was never read is a candidate for removal. Use the circles to guide the next template.
