Debate speaking time split
Speech and cross-examination clocks make or break a fair debate round. Coaches, tournament directors, and classroom teachers need a single place to turn a chosen format into concrete minutes for every constructive speech, rebuttal, and cross-examination block—especially when a class period is shorter than a full tournament schedule and every speech must shrink by the same proportion. This debate speaking time split calculator accepts a format (policy, Lincoln-Douglas, Public Forum, British Parliamentary, or custom role weights), optionally a total round budget in minutes, and returns an ordered period schedule plus role totals. Named formats ship with standard speech lengths; providing total_minutes scales every period so the sum matches your clock. Custom mode allocates the budget by constructive, rebuttal, and CX weights when your league uses a house rule. The same pure logic powers the free browser tool and the API path, so printed ballots and automation scripts never disagree on how many minutes the 2AR or Grand Crossfire should get.
Run — free
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
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/edu/debate-time-split \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"format":"policy"}'const res = await fetch("https://api.kit.forhosting.com/edu/debate-time-split", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"format": "policy"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/edu/debate-time-split",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"format": "policy"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/edu/debate-time-split", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"format":"policy"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"format":"policy"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/edu/debate-time-split", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"format": "policy"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "edu.debate_time_split",
"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. |