{{ interpretationLead }}
{{ dominantDomain.label }} is currently the highest-scoring domain ({{ dominantDomain.score }}), while {{ bestDomain.label }} is your relative anchor ({{ bestDomain.score }}).
| # | Domain | Item | Response | Score | Copy |
|---|---|---|---|---|---|
| {{ row.id }} | {{ row.domain }} | {{ row.text }} | {{ row.responseText }} | {{ row.domainScore }} |
Burnout questionnaires try to turn a diffuse experience of exhaustion into something structured enough to review. The Copenhagen Burnout Inventory, usually shortened to CBI, does that by separating strain into personal burnout, work burnout, and client-related burnout instead of collapsing everything into one undifferentiated score.
This package follows that three-domain frame with nineteen questions and then adds a few implementation-specific layers on top. After you answer every item, it calculates domain scores on a 0 to 100 scale, identifies the highest-pressure domain, computes a weighted pressure index, and shows whether the current profile crosses the alert cutoff you selected at the start.
That makes the page useful for repeated self-checks, supervision conversations, occupational health follow-up, or personal reflection when someone wants to describe more than "work feels heavy lately." A person might find that work burnout is high while client-related burnout is lower, which points to a different kind of strain than a profile dominated by difficult client contact.
The extra controls matter because they change the way the result is framed rather than the underlying answers. Review mode decides which domain the recommendation engine emphasizes, Operational alert cutoff decides when the alert badge flips, and Recommendation cadence changes whether the suggested next steps focus on stabilization, a short recovery sprint, or escalation.
The boundary is important. This is a self-report assessment, not a diagnosis and not a substitute for professional evaluation. The World Health Organization describes burn-out as an occupational phenomenon, not a medical condition, and this tool adds its own package-level interpretation layers beyond the original CBI scoring method. The result is most useful as a structured snapshot that helps you decide what deserves further attention.
Answer the full set in one sitting if you can. The app does not show a final result until all nineteen items are answered, so a consistent recall frame matters more than speed. The prompt in the interface asks for recent experience, and the cleanest comparisons come from using that same practical window each time you repeat the assessment.
The best reading order is domain scores first, then the dominant-domain badge, then the pressure index and alert status. That sequence tells you whether strain is broad or concentrated. A high pressure index with a narrow spread suggests generalized strain across domains, while a high dominant score with a wide spread suggests a more localized problem area.
Review mode is easy to misread. It does not rescore the questionnaire. Instead, it changes which domain the recommendation block treats as the main operational focus. Balanced mode follows the highest score overall, workload mode pushes attention toward work burnout, and client-boundary mode prioritizes the client-related domain if possible.
Operational alert cutoff also changes interpretation rather than raw scoring. A lower cutoff is more sensitive and will flag elevated strain earlier. A higher cutoff is more conservative and can be useful if the result is being used for internal review rather than early warning. The domain scores themselves stay the same either way.
Treat exports and shared links carefully. The scoring happens in the browser, which is good for server-side privacy, but the response state is still encoded into the page parameter r. That means copied URLs, CSV files, DOCX exports, and JSON saves can all carry sensitive answers if you share them without checking.
The tool uses nineteen CBI items divided into three domains: six personal items, seven work items, and six client-related items. The interface presents one common five-choice ladder for every question, but the scoring still follows the same 0, 25, 50, 75, 100 progression described in the original inventory family.
Each response is stored internally as an integer from 0 to 4. The package multiplies that value by 25 to produce the item score. Item 13, the leisure-energy question in the work domain, is reverse keyed, so its item score becomes 100 - 25r instead of 25r. Domain scores are the arithmetic mean of the item scores inside each domain, rounded to one decimal place.
The official CBI documentation allows scale-level non-response rules, but this implementation is stricter. The original first edition treats a scale as non-scorable only if too many items are missing. This package instead waits for all nineteen answers before showing any result. That is a product decision designed to keep the interpretation cards, ranking logic, and exports based on a complete response pattern.
After the three domain scores are computed, the app derives several package-specific values. overallScore is the simple mean of the three domains. pressureIndex is a weighted blend with 40 percent personal, 35 percent work, and 25 percent client-related burnout. strainSpread is the difference between the highest and lowest domain score, which helps distinguish concentrated strain from more even cross-domain load.
The banding logic is also package specific. The app labels the dominant domain as Lower strain below 50, Elevated strain from 50 to 74.9, High strain from 75 to 89.9, and Critical strain from 90 upward. The operational alert then compares that same dominant score with the chosen cutoff of 45, 50, 55, or 60.
Recommendations are generated from two moving parts: the focus domain and the coaching mode. Focus domain depends on the chosen review mode, while coaching mode decides whether the final step leans toward monitoring, a 14-day recovery sprint, or escalation toward professional support. The radar chart, CSV export, DOCX export, and JSON payload all read from this same scored state.
No dedicated scoring backend is involved. Responses are encoded as a 19-character string made from digits and hyphens, stored in the query-backed parameter r, and restored locally when that state is reopened. That design keeps scoring on-device, but it also means the page URL itself can carry assessment data.
| Domain | Item count | Question IDs | How the package uses it |
|---|---|---|---|
| Personal burnout | 6 | 1-6 | Feeds domain score, ranking, pressure index, and radar chart |
| Work burnout | 7 | 7-13 | Includes reverse-keyed item 13 and can be prioritized by workload mode |
| Client-related burnout | 6 | 14-19 | Can be prioritized by client-boundary mode and drives client-facing recommendation logic |
| Layer | Implemented rule | What changes when you adjust it |
|---|---|---|
Review mode |
Selects balanced, workload-first, or client-boundary focus for recommendations | Changes the lead domain for advice, not the raw scores |
Operational alert cutoff |
Flags the dominant domain at 45, 50, 55, or 60 points | Changes when the alert badge turns on |
Pressure index |
Weighted blend of personal, work, and client-related scores | Provides a single package-level load indicator |
Burnout band |
Uses the dominant domain to assign Lower, Elevated, High, or Critical strain | Gives a fast summary lane for the current profile |
Recommendation cadence |
Selects stabilize, recover, or escalate closing guidance | Changes the tone of the final action step |
The three domain scores are the anchor. Personal burnout reflects general exhaustion, work burnout isolates strain linked to work as such, and client-related burnout narrows the focus to work with recipients such as clients, patients, students, or similar roles. The highest domain is often more informative than the overall mean because it shows where strain currently concentrates.
The pressure index is useful when you want a single package-level summary, but it should not replace the domain view. A moderate pressure index can still hide one very high domain if the other two are lower. That is why the app also shows the dominant-domain badge, the band, and the strain spread.
The operational alert is a threshold tool, not a diagnosis. Crossing it means the dominant domain has exceeded the selected cutoff, not that burnout has been medically confirmed. The stricter the cutoff, the later that alert appears. The lower the cutoff, the earlier it flags elevated strain.
The most useful follow-up question is usually practical: where should recovery or boundary changes start first? If work burnout dominates, workload design may be the issue. If client-related burnout dominates, boundary fatigue may be more central. If personal burnout remains high even when the other domains are lower, the broader recovery picture may need attention beyond work configuration alone.
Someone completes the assessment with personal burnout at 52, work burnout at 79, and client-related burnout at 48. The dominant domain is clearly work burnout, the operational alert is likely triggered at the default 50-point cutoff, and workload mode will keep the recommendations focused on task load and workday recovery rather than client boundaries.
Another user scores 68, 71, and 66 across the three domains. The pressure index is elevated because strain is distributed rather than isolated. Even if no single domain looks extreme, the narrow spread shows that fatigue is not confined to one corner of working life.
A therapist, teacher, or support worker may score lower on personal and work burnout but much higher on the client-related scale. In that case, client-boundary mode is useful because it keeps the recommendations focused on exposure, decompression, and boundary scripts rather than generic workload advice.
No. It summarizes self-reported exhaustion patterns and adds package-specific interpretation layers to help with reflection and follow-up.
It is the reverse-keyed work-domain item, so agreement with having enough energy in leisure time lowers work burnout rather than raising it.
This implementation requires a complete 19-item response pattern before it shows scores, even though the original CBI documentation allows limited missingness at the scale level.
The scoring logic runs in the browser, but the encoded response state can still travel in the page URL and in exported files.