Request. Sedge Operations has two February totals that appear inconsistent. One report uses a created cohort and another uses solved dates. Build both reports, inspect reply and resolution observations, and explain the difference before choosing an operational follow-up. The supplied records include unanswered and reopened requests.
Done. A good conclusion names the population, timing measure and contributing observations. Each case step preserves the report definitions and ticket evidence from earlier work. Changing a valid source date to make the totals match would destroy the explanation rather than repair a reporting defect.
Sedge Operations has two February totals that appear inconsistent. One report uses a created cohort and another uses solved dates. Build both reports, inspect reply and resolution observations, and explain the difference before choosing an operational follow-up. The supplied records include unanswered and reopened requests.
A good conclusion names the population, timing measure and contributing observations. Each case step preserves the report definitions and ticket evidence from earlier work. Changing a valid source date to make the totals match would destroy the explanation rather than repair a reporting defect.
Worked example: sedge operations review.