Time to complete task list calculator
Three tasks of 45, 30 and 15 minutes starting at 09:00 take 1h 30m and finish at 10:30. Enter your estimates in order and see each item's start and end, plus the day count if the work runs past midnight. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Start time
- 09:00
- Duration unit
- Minutes
- Task count
- 3
- Start hour
- 9
- Start minute
- 0
- Total minutes
- 90
A project does not finish when the last ticket is named; it finishes when every estimated minute on the list has actually elapsed from a real start clock. Planners, scrum masters, and solo operators already keep task durations, yet they still add those figures by hand, lose a wrap past midnight, or disagree with a spreadsheet that counted hours as minutes. This time to complete task list calculator accepts a list of estimated durations, a start clock, and an optional minutes-or-hours unit. It adds every duration in sequence, builds a running schedule, and reports the project total plus the finishing clock time, including how many calendar days the work spills past the start.
What a sequential task-list total actually measures
A time-to-complete figure for a task list is not a calendar span and it is not a travel ETA. It is the sum of every estimated duration on the list, applied in order from a start clock, as if one person or one sequential crew works the items without overlap. That model matches how most daily plans, catering runs, content pipelines, and personal focus blocks actually run: you cannot start the review until the draft is done, and you cannot send the file until the review is done.
The finishing clock is therefore start plus the running total, wrapping at midnight and reporting a day offset when the work spills into later calendar days. This is different from a Gantt bar duration, which counts inclusive calendar or working days between two dates and says nothing about minutes inside a day. It is different from eat-the-frog ordering, which ranks tasks by difficulty and never adds time.
It is different from a travel ETA, which divides remaining distance by average speed. When two teams share a start time, they still need the same arithmetic so a printed run-of-show and a bot digest do not drift by a quarter hour. Use this calculator when the decision you care about is how long the whole list takes and what the clock reads at the finish, not which ticket is hardest or how many weekdays sit between two dates.
Where a task-list completion time earns its keep
Operations and studio producers keep a run-of-show with minute estimates and a call time; they need one source of truth that adds those minutes and prints the clock when the last cue ends, including a wrap that lands after midnight. Scrum masters and delivery leads collect story-point-free hour or minute estimates on a same-day punch list and must answer when the last ticket finishes if the team starts at nine, without rebuilding the sum in every spreadsheet.
Caterers, movers, and field crews sequence load, travel, setup, and breakdown and need a finish clock they can text to the client. Content sites that rank for time to complete task list calculator benefit from a live free tool whose browser path matches the paid path. Failed validation does not consume balance.
What you can do with it
Daily punch lists and standup plans
Add today’s minute estimates from a start clock so the last ticket has a finish time the standup bot and the printed plan both share.
Run-of-show and production call sheets
Turn a sequential cue list with durations into a running schedule and the clock when the last cue ends, including a wrap past midnight.
Field crews and same-day service windows
Sequence load, setup, work, and breakdown estimates so a client gets a deterministic finish clock from the agreed start.
FAQ
What unit should I use for task durations?
One unit applies to the whole list. Fractional hours are allowed: 1.5 hours becomes ninety minutes on the running clock.
Does this account for parallel work or breaks?
No. The model is sequential: one owner, no overlap, no inserted breaks. If two people work at once, or you need lunch buffers, fold those choices into the durations you send or split the list.
How is the finish time calculated?
Every duration is added in order to the start clock. Tasks of 45, 30 and 15 minutes from 09:00 total 90 minutes, so the list ends at 10:30, and each item gets its own start and finish time.
What happens if the work runs past midnight?
The clock wraps at midnight and the result says how many calendar days the work spills past the start day, so a late run-of-show still prints the right finishing time instead of an impossible hour.
How are decimal durations handled?
Each duration is converted to whole minutes before the clock moves. In hours, 1.5 becomes 90 minutes; in minutes, 45.4 becomes 45. Choose one unit for the whole list, minutes or hours.
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/biz/tasklist-total-time \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"tasks":[{"name":"Write brief","duration":45},{"name":"Review copy","duration":30},{"name":"Send for approval","duration":15}],"start_time":"09:00"}'const res = await fetch("https://api.kit.forhosting.com/biz/tasklist-total-time", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"tasks": [
{
"name": "Write brief",
"duration": 45
},
{
"name": "Review copy",
"duration": 30
},
{
"name": "Send for approval",
"duration": 15
}
],
"start_time": "09:00"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/biz/tasklist-total-time",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"tasks": [
{
"name": "Write brief",
"duration": 45
},
{
"name": "Review copy",
"duration": 30
},
{
"name": "Send for approval",
"duration": 15
}
],
"start_time": "09:00"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/biz/tasklist-total-time", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"tasks":[{"name":"Write brief","duration":45},{"name":"Review copy","duration":30},{"name":"Send for approval","duration":15}],"start_time":"09:00"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"tasks":[{"name":"Write brief","duration":45},{"name":"Review copy","duration":30},{"name":"Send for approval","duration":15}],"start_time":"09:00"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/biz/tasklist-total-time", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"tasks": [
{
"name": "Write brief",
"duration": 45
},
{
"name": "Review copy",
"duration": 30
},
{
"name": "Send for approval",
"duration": 15
}
],
"start_time": "09:00"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "biz.tasklist_total_time",
"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.
Limits
max_items | 100 |
max_duration_minutes | 10080 |
max_total_minutes | 525600 |
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 same pure analytic path powers the free browser tool and the API, so a standup bot and a printed daily plan never disagree on when the last item ends.
What a sequential task-list total actually measures
Difficulty scores, holidays, parallel owners, and buffer percentages are out of scope: you already decided the estimates; this endpoint only adds them and tells you when the last item ends.
Input contract, running schedule, and validation rules
The tasks array must contain between one and one hundred objects. Durations convert to whole minutes before the clock moves, so 1.5 hours becomes ninety minutes and 45.4 minutes becomes forty-five. POST a JSON body with two required fields: tasks (aliases list, items, todos) and start_time (aliases start, begin, start_clock). Each object requires duration (aliases estimate, duration_value), a non-negative finite number in the unit given by duration_unit. Optional name (aliases label, title) is a short string; when missing or blank after trim, a stable Task N label is assigned from the one-based rank. duration_unit (aliases unit, units) is optional and must be minutes or hours; it defaults to minutes and applies to every row. start_time is a 24-hour clock as HH:MM or H:MM, for example 09:00 or 14:30. Empty arrays, non-arrays, missing duration, negative estimates, clocks that are not HH:MM, more than one hundred rows, a single task longer than seven days, and a list whose summed minutes exceed a planning year fail with invalid_input and are not billed. On success the body returns task_count; the resolved duration_unit; start_time, start_hour, and start_minute; total_minutes, total_hours, and total_formatted; finish_time, finish_hour, and finish_minute; day_offset and day_note; a schedule array with rank, name, duration_minutes, start_time, finish_time, day_offset, and original_index for each row in input order; plus formula and a short English summary. The endpoint does not insert breaks, model two people working in parallel, or parse free-text estimates such as afternoon; call it when the numbers are already decided and you need a deterministic total and finish clock.
Where a task-list completion time earns its keep
Personal productivity apps and Notion-style templates call a tiny parse endpoint so the free browser path and automation webhooks stay byte-aligned on the same module.
Technical questions
How does the time to complete task list calculator work?
Send a non-empty tasks array with a non-negative duration on each item and a start_time as HH:MM. The API converts every duration to whole minutes, adds them in order from the start clock, and returns the project total plus the finishing clock, wrapping at midnight.
What happens if the work runs past midnight?
The finish clock wraps every 1,440 minutes. day_offset counts how many calendar days the finish sits after the start, and each schedule row carries its own day_offset so a cue that lands after midnight is still labeled with a 24-hour clock.
What does the task list completion time calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.