Code tool

Shrinkage Calculator

Calculate paid-time losses, productive hours and headcount using explicit inputs and overlap rules.

In-browser processingNo account requiredPrivacy details ↗

Confirm categories are mutually exclusive. Direct values use paid time as denominator. Inverse: paid=productive/(1−rate). Headcount=ceil(team target/productive per person), without demand/service predictions.

A QUICK WALKTHROUGH

How to use this tool

  1. Choose categories, direct hours/rate, inverse or interval union.
  2. Enter explicit paid/productive values and the team target; declare category assumptions.
  3. Add optional scenarios, calculate, inspect all contributions and export the report.

Limitations

Each line: start | end, within [0, paid hours]. Union merges overlaps and touching intervals; report shows each contribution and overlap removed. Category mode requires user-declared disjoint categories and unique names, up to 12 categories. No default loss rate is assumed.

Limitations

Confirm categories are mutually exclusive. Direct values use paid time as denominator. Inverse: paid=productive/(1−rate). Headcount=ceil(team target/productive per person), without demand/service predictions.

Limitations

Exact nonnegative decimal inputs: at most 256 characters and exponent magnitude ≤ 1,000. BigInt rational arithmetic has no IEEE 754 finite-value or underflow gate. Exact decimal rational arithmetic and exact integer ceiling are used; nonterminating values are reported as exact fractions. Rates may be 0–100%; at 100%, productive hours are zero and staffing undefined. Inverse paid hours at 100% are undefined. Maximum 12 scenarios, 12 categories and 1,000 intervals each.

GOOD TO KNOW

Common questions

Can categories overlap?

Only interval mode detects and merges overlap. Percentage categories must be explicitly declared disjoint; duplicate names are rejected, but names alone cannot prove disjointness.

What does inverse mode calculate?

It derives paid hours per person from productive hours per person and a user-entered loss rate, then rounds staffing up for the team target.

Is this an attendance or staffing forecast?

No. It calculates input arithmetic locally and does not verify attendance, demand or service levels.