Data Modelling

Part of BI for operations management

Comparing locations without ignoring their different conditions

Compare operational sites using aligned definitions, useful denominators and case-mix context while keeping raw results and uncertainty visible.

Compare locations by aligning measure definitions and reporting periods, then show the conditions under which each works. Raw totals give context, but rarely settle which location performs better when volumes, work mix and resources differ.

Make the measure comparable

Agree the service population, entry and completion events, reporting timezone and cutoff. Check that each location records cancellations, transfers and reopened cases the same way. If one reports completed requests and another reports every closed record, a side-by-side chart compares definitions.

Choose a denominator that matches the question. Completions per available staff hour may inform a productivity discussion if work types, hours and completion rules are aligned. The proportion completed within an agreed interval informs timeliness if the eligible population and observation window match. Show the component counts with each rate, particularly for small locations.

Comparing location performance with aligned measures and context

Service population
Agreed across locations
Reporting period
Aligned timezone and cutoff
Completion definition
Completed requests vs. closed records
Denominator
Completions per staff hour (aligned work types)

Show conditions that affect interpretation

Keep a short context register beside the results. Include conditions relevant to the decision: demand volume, work type and complexity, opening hours, staff skills, resource constraints, service area and data coverage.

Australian government-service reporting includes statistical context — such as population size, trends and language or cultural barriers — to assist interpretation of performance information. Context should guide investigation; it does not automatically explain away a poor result.

QuestionUseful displayCaution
Is one site handling more work?Arrivals and completions by typeA larger site may have larger totals.
Is service slower?Timeliness rate and elapsed-time distributionCheck work mix, cutoffs and unfinished cases.
Is capacity constrained?Usable hours or slots against workloadScheduled hours may exceed usable resources.
Is the difference persistent?Several comparable periods with countsA short period or small count can be volatile.

Key contextual conditions affecting interpretation

Demand volume
High in Location A, moderate in B
Work type complexity
More complex cases in Location B
Staff skills
Specialised teams in both locations
Resource constraints
Limited support staff in Location A

Compare within meaningful groups

Start with work types both locations handle. An overall average can change because of the mix even when results within each type tell a different story. Do not force a combined comparison when services or records are genuinely unlike.

A common-mix summary is an option when both sites have enough comparable observations for the relevant types. Choose a shared distribution of types, calculate each site's result within each type and weight both sets of results by that distribution.

Show raw results too, identify excluded types and state the chosen weights. An adjusted figure answers a different question from the actual overall result; neither should silently replace the other.

Australian government-service statistical reporting includes population characteristics, such as differences in age distribution, as context for interpreting performance information. That context helps explain why composition can matter, but it does not justify adjusting every location difference.

An adjustment can hide an access or quality problem if it controls for a condition the service should improve. Decide which conditions are appropriate to account for before applying the method.

Adjusting for case mix: benefits and risks

  • ProsReduces bias from differing work mixes; enables fairer comparison
  • ConsMay mask access or quality issues if adjusting for conditions the service should improve

Keep uncertainty and gaps visible

A percentage based on few cases can change substantially when only a few outcomes change. Show its denominator and avoid declaring a winner from a narrow or incomplete comparison.

If the data represent a sample, consider sampling uncertainty as well; if they cover all recorded cases, small counts still produce period-to-period volatility, but a sampling margin of error is not automatically applicable.

Check whether missing fields or delayed updates are concentrated at one location. If definitions or coverage cannot be aligned, present separate local trends and explain the barrier. Where they can be aligned, use the result to choose a specific investigation, then check case records and local operational context before attributing the difference to management practice.

Ensuring uncertainty and data gaps are visible

  • Show denominator for all percentagesRequired for transparency
  • Flag small countsAvoid declaring winners from volatile data
  • Check for missing fields or delaysConcentrated at one location? Report separately.
  • Use aligned data to guide investigationDo not assume management practice is the cause without review

More from Data Modelling