Absence percentage calculator
Turn missed days into a rate you can compare: 6 days absent out of 22 scheduled workdays is an absence rate of 27.27%, whether the team has five people or 200. Half days count too. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Days absent
- 6
- Workdays total
- 22
- Absence percentage
- 27.27
If the days absent exceed the scheduled workdays — an impossible input — it refuses with a clear validation error instead of returning a meaningless figure above one hundred percent.
What the absence rate tells you
Absence rate is the simplest and most comparable measure of lost working time. A headcount of absences means little on its own: six missed days is serious in a twenty-day month and modest in a quarter. Expressing it as a percentage of the scheduled workdays normalizes the figure, so a team of five and a department of two hundred can be compared on the same scale, and one month can be tracked against the next even when the calendar lengths differ.
You send the days absent and the scheduled workdays for the same period, and you get back the percentage absent, rounded to the number of decimal places you ask for.
It deliberately refuses the one input that makes the metric meaningless: if the days absent are greater than the total scheduled workdays, something in the source data is wrong — a double count, a period mismatch, a typo — and the right answer is an error that names the two offending values, not a percentage above one hundred that quietly poisons a report downstream.
How the inputs are validated
Both inputs must be finite numbers, and the period definition is up to you: a month, a quarter, a contract year — the ratio is the same as long as both numbers describe the same window. Days absent must be zero or positive; scheduled workdays must be greater than zero, because a period with no scheduled days has no meaningful absence rate. Fractional values are accepted on both sides, since many payroll systems track half days.
The precision parameter controls rounding of the returned percentage and defaults to two decimal places, which matches how most human-resources dashboards display the figure; you can ask for anything from zero to six. Validation is strict on purpose. A negative absence count, a zero denominator, or days absent above the schedule all return an error that names the exact field and the offending values, so a calling pipeline can log the problem, skip the record, and alert whoever owns the source data instead of importing a bad number.
Inputs that arrive as numeric strings are coerced, because form submissions and query parameters often arrive that way, but anything that does not parse to a finite number is rejected with the same clarity.
Where it fits in practice
Teams wire this calculation into three kinds of flows. The first is reporting: a nightly job walks the attendance export, computes the absence percentage per employee, per team, and per site, and stores the series so trends are visible before they become problems. The second is alerting: a threshold — say five percent in a month — triggers a review, and computing the rate centrally means every alert uses exactly the same formula and rounding instead of each spreadsheet doing its own version.
The third is benchmarking: converting raw absence counts into percentages makes periods of different lengths and teams of different sizes comparable, which is the only honest way to read the numbers. The result object echoes back the two inputs alongside the computed percentage, so a stored record is self-describing and an auditor can see precisely which numbers produced which rate without re-deriving anything from logs.
What you can do with it
Build a monthly absence report
Compute the absence percentage per employee and per team from the attendance export, with one shared formula and rounding rule.
Alert on unusual absence rates
Trigger a review when a team's absence percentage crosses a threshold, computed the same way everywhere.
Compare periods of different lengths
Normalize a short month and a long month to percentages so the trend line is honest.
FAQ
How is the absence percentage calculated?
Days absent divided by total scheduled workdays, multiplied by one hundred, rounded to the precision you choose (two decimals by default).
Can I use half days?
Yes. Both inputs accept fractional numbers, so 4.5 days absent out of 22 workdays works fine.
Is any data stored?
No. The two numbers are processed and discarded; only the result is returned.
Can the scheduled workdays be zero?
No. A period with zero scheduled workdays has no defined absence rate, so the input is rejected.
What happens if the days absent are more than the scheduled workdays?
The calculator refuses and names both values instead of showing a rate above 100%. That situation always points to bad source data, such as a double count, a period mismatch or a typo.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/fin/absence-percentage \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"days_absent":6,"workdays_total":22}'const res = await fetch("https://api.kit.forhosting.com/fin/absence-percentage", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"days_absent": 6,
"workdays_total": 22
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/fin/absence-percentage",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"days_absent": 6,
"workdays_total": 22
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/fin/absence-percentage", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"days_absent":6,"workdays_total":22}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"days_absent":6,"workdays_total":22}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/fin/absence-percentage", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"days_absent": 6,
"workdays_total": 22
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "fin.absence_percentage",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
The absence percentage API computes an absence rate from two numbers: the days a person was absent and the total workdays scheduled in the same period. It divides the first by the second and returns the result as a percentage, rounded to the precision you choose.
What the absence rate tells you
This endpoint does exactly that normalization. Because the calculation is pure arithmetic, the same code runs free in your browser on this page and as a paid API call at $0.002 per request, so you can check a figure by hand and only pay when you automate it.
Where it fits in practice
The endpoint keeps no state and stores nothing: the two numbers come in, the percentage goes out, and nothing is retained. That makes it safe to run on sensitive workforce data.
Technical questions
What happens if days absent exceed the scheduled workdays?
The request is rejected with an invalid_input error naming both values, since that input cannot describe a real period.
What does it cost?
$0.002 per request. It is also free to run in your browser on this page.