# Example weekly operations report

Original Culvion Technologies example · 7 November 2026

SYNTHETIC DATA ONLY. This is a fictional reporting week for an illustrative support queue. No figures describe Culvion clients, employees or live performance. Targets and measures for actual work must be agreed for the scope.

## Definitions for this example

- A case is one tracked request in this simplified data set.
- Opening backlog is unresolved work carried into the example week.
- Received means new cases recorded during the week.
- Resolved means cases from opening or newly received work that meet the example completion rule.
- Closing backlog = opening backlog + received − resolved.
- There are no reopened, merged, transferred-out or deleted cases in this simplified example. A real report must show those movements where they occur.
- Channel is the intake channel, assigned once per case in this data set.

## 1. Work reconciliation

| Intake channel | Opening backlog | Received | Available work | Resolved | Closing backlog |
| --- | ---: | ---: | ---: | ---: | ---: |
| Voice | 20 | 320 | 340 | 310 | 30 |
| Email | 20 | 300 | 320 | 290 | 30 |
| Chat | 10 | 180 | 190 | 160 | 30 |
| TOTAL | 50 | 800 | 850 | 760 | 90 |

Check: 50 + 800 = 850 available cases. 850 − 760 = 90 closing cases.

Channel check: 30 + 30 + 30 = 90 closing cases.

Change in backlog: 90 − 50 = 40 more unresolved cases at the end of the week.

Resolved share of available work: 760 / 850 × 100 = 89.4%, rounded to one decimal place. This is not first-contact resolution, an SLA result or the resolution rate of only the new-case cohort.

## 2. Quality review example

| Item | Synthetic value |
| --- | ---: |
| Interactions reviewed | 30 |
| Possible points per interaction | 100 |
| Total possible points | 3,000 |
| Total earned points | 2,520 |
| Aggregate QA score | 84.0% |

Check: 30 × 100 = 3,000 possible points. 2,520 / 3,000 × 100 = 84.0%.

The reviewed sample is not necessarily representative of every case. A real report should state how samples were selected and separate any critical issues from the average score. The worked QA example demonstrates the scoring method; it is not the underlying 30-row data set.

## 3. What this summary cannot establish

The data above does not contain arrival/answer timestamps, response deadlines, customer survey responses or repeat-contact links. It therefore cannot establish answer speed, SLA attainment, CSAT or first-contact resolution. Those measures need their own definitions and underlying evidence.

## 4. Illustrative decisions for review

| Finding from this synthetic report | Question or action | Proposed owner role | Review point |
| --- | --- | --- | --- |
| Backlog increased by 40 cases | Examine case age and reasons before changing coverage | Queue owner | Next operating review |
| Each channel closes with 30 open cases | Check whether the age/priority mix differs by channel | Operations analyst or queue owner | Before allocating the next block of work |
| Quality average is 84.0% in the selected sample | Review the category detail and sample selection | Quality reviewer | Calibration review |
| The summary cannot establish SLA attainment | Confirm required timestamp data and measure definition | Reporting owner with client | Before publishing an SLA result |

These are example roles and decisions, not people assigned to a live engagement. Dates, targets and authority must be agreed in actual work.

## 5. Questions for the client review

1. Which backlog items need a business decision rather than more agent time?
2. Are the handling instructions complete for the recurring contact reasons?
3. Are promised updates recorded with an owner and time?
4. Which change is approved, who owns it and what evidence will be reviewed next?

A useful report ends with decisions and responsibilities. A more elaborate dashboard does not repair unclear definitions.