A capstone presentation works when three budgets hold: a slide budget (roughly one to two minutes of talk per slide), a seconds budget (every slide gets an explicit allocation, and the total sits about ten percent under your limit), and a delivery budget (rehearsed out loud at least twice, with the opening and closing lines said from memory). Plan the deck slide by slide with a seconds value on each one, keep the total under the limit with room to spare, and prepare the question window with a repeat-answer-bridge frame. The planner below counts the seconds for you and flags overflow before the rehearsal does.
Honesty note: time limits and structures differ by program. Some capstones give you ten minutes plus questions; some give twenty and cut you off mid-sentence; a few publish a required slide count or a rubric that grades the deck itself. The ten-slide skeleton here is the common shape — your program's guidance outranks it wherever the two disagree, and the planner exists precisely so you can rebuild the deck around whatever rule you were handed. The worked example is an invented, illustrative capstone (a campus food-waste audit), the same teaching tradition as the rest of this shelf. Nothing here writes your slides for you; it gives each one a length and a job.
The slide planner
Most decks fail at the rehearsal, and most rehearsal failures trace back to a deck that was never budgeted — ten slides that all feel like "about two minutes each" until the run stops at minute nineteen with four slides still unread. The planner makes each slide carry a number. Every row has an editable title, a notes box for what you will say while it is up, and a timing input capped at 120 seconds, because a slide that needs longer than two minutes is two slides. The counter adds the seconds live and compares the total against your time limit, so overflow shows up as red text on a Tuesday evening instead of as a chairperson's cough on stage.
The default ten rows are the standard capstone skeleton, pre-weighted for a ten-minute talk. Set the limit field to your actual time and the rebalancing begins: the planner holds up to 30 rows, so a 20-minute talk can run longer or carry a backup bank. When the total sits under the limit with roughly a tenth of it spare, the deck is stage-ready — then the words-to-minutes converter can sanity-check the notes you wrote, one spoken-word estimate per slide.
Capstone presentation slide planner
100% private — runs in your browserYour slot's length. The counter compares slide seconds against it.
Blank is fine — name it later. The planner holds up to 30.
Title & welcome — your name, program, project title, one line on why it matters. Thirty seconds; the committee has read the abstract already.
The problem — who pays for it now, in time or money or risk, and the edge of your scope. Say the cost in one sentence; details live in the paper.
Research question — the question verbatim on the slide, read aloud once, slowly. It is the one sentence the committee writes down.
Literature in brief — one sentence on where the field stands, one on the gap you fill. Never a citation list; that is what the references slide is for.
Method — design, sample, and one bias guard, in that order. The committee probes method hardest; the capstone defense question bank lists exactly how.
Findings — the strongest result and the chart or number that carries it. This is the 120-second slide; split into two only if the deck runs long anyway.
So-what — the slide students skip and committees miss most. One concrete change of behaviour beats three vague implications every time.
Limitations — name the boundary before the committee does, and pair each limit with what it does not shake. A limit you own reads as command.
Takeaway — one sentence, the discipline of a thesis statement generator. This is the line the committee quotes in its deliberation.
Questions & thanks — thank the room, mention that backup slides follow, and stop talking. The question window is where defense questions land.
Timing & progress
At the limit with 0:00 spare — trim one timing for rehearsal headroom.
A slide counts as fully planned once it has a title, a timing, and notes of five words or more. The counters mark started, not rehearsed — say it out loud before you trust it.
Titles, notes, timings, slides you add and the time limit save to this browser only — one storage key, csw-cpr-v1. Adding, removing and reordering slides saves immediately; typing saves after a short pause. Reopening the page restores the plan. Reset erases the key and returns the default ten slides. The checklist, quiz, poll and answer-prep fields are never stored.
How to split a time limit across slides
Slide counts come from the clock, not from a rule someone memorized. Fix the cheap slides first — a title slide earns thirty seconds, questions-and-thanks the same — then hand the big blocks to the slides the committee will actually probe. Findings gets the single largest budget in almost every discipline, method the second. Everything else shares what remains. Two limits keep the budget honest: no slide runs past 120 seconds, and the total stays about ten percent under the limit, because the clock on stage runs faster than the clock at your desk.
| Time limit | Workable slide count | Per-slide budget | The trim that saves you |
|---|---|---|---|
| 10 minutes | 8–12 slides | 30–90 seconds each | Cut the literature slide to one sentence inside the problem slide |
| 15 minutes | 12–15 slides | 45–90 seconds each | Merge so-what and takeaway into one closing argument |
| 20 minutes | 15–20 slides | 60–120 seconds each | Split findings into two slides; method detail moves to backup |
| 30 minutes | 20–28 slides | 60–120 seconds each | Add a demo or walkthrough slide; keep the 120-second cap anyway |
The table is arithmetic advice, not data: divide the limit by a per-slide cost and leave room for the ends. Whatever the limit, keep the two-second slides (title, thanks) and the one 120-second slide (findings) and the deck breathes. If your notes run long for the budget, the word count cutter trims prose to a target, and spoken notes cut easier than written ones — contractions survive; paragraphs do not.
The ten-slide skeleton, section by section
The planner's default rows follow the shape most capstone rubrics expect, weighted for a ten-minute slot. Read it as a starting budget, not a law: a 20-minute talk adds findings detail and a demo; a 10-minute brutal slot merges literature into the problem. What the skeleton protects is the sequence — problem before question, question before method, method before findings — because a committee that has to reverse-engineer your logic spends its questions on reconstruction instead of substance.
| Slide | Job | Default seconds | What belongs on it |
|---|---|---|---|
| 1 · Title & welcome | Open, orient, sit down in the room | 30 | Name, program, project title |
| 2 · The problem | Make the room care | 60 | Who pays for the problem, scope edge |
| 3 · Research question | State the contract | 60 | The question verbatim, nothing else |
| 4 · Literature in brief | Place the study | 45 | The gap, one sentence, maybe two sources named |
| 5 · Method | Earn the findings | 90 | Design, sample, one bias guard |
| 6 · Findings | Pay off the promise | 120 | Strongest result + the chart that carries it |
| 7 · So-what | Convert result to behaviour | 90 | What a practitioner does differently |
| 8 · Limitations | Own the boundary | 45 | Each limit paired with what it does not shake |
| 9 · Takeaway | Leave one sentence | 30 | The quotable line |
| 10 · Questions & thanks | Hand over cleanly | 30 | Thanks, backup-slide note, stop |
If the project behind the deck has not settled yet, none of this budgeting has anything to push — the capstone project ideas bank is the step before planning slides, and the written core it feeds is covered by the capstone project guide. Slides are the last ten percent of the project; they just feel like the first because they are the part anyone sees.
The delivery checklist
Ten checks separate a rehearsed talk from a read one. Work down the list at the dress rehearsal, not on the day — every item below is cheap to fix the night before and expensive to discover live. The list resets with the page on purpose: it is a per-rehearsal instrument, not a saved plan.
- Eye contact — you looked up from the screen at least once per slide; the committee listens to a face, not a crown of your head.
- Pace — a full timed run came in under the limit; if you cannot say a slide's notes in its budget, the budget or the notes must change.
- Rehearsal out loud — the whole deck, standing, at least twice; silent read-throughs rehearse your eyes and the talk needs your mouth.
- Opening line — the first sentence after the title slide, said from memory; a stumbled opening colours how the room hears everything after it.
- Transitions — one bridge sentence into each new section, so the deck reads as an argument and not as a stack.
- Backup slides — the appendix deck exists behind a divider, each slide named after the question it answers.
- Key numbers memorized — the two or three numbers your findings rest on, sayable without looking down.
- Tech check — the deck opened on the presentation machine, fonts intact, plus a copy in your email and on a drive.
- Ending line — the final sentence rehearsed; "yeah, that's it" is not an ending, it is a vanishing.
- Hardest question pre-answered — the question you dread most, answered out loud once, using the frame in the next section.
Progress on the checklist: 0 of 10 delivery checks ticked
Three of the ten do most of the work. Pace catches a deck that was never really budgeted. Backup slides turn the question window from a threat into a demo of preparation. And the opening line buys the first thirty seconds back from nerves, which is where most talks are actually lost.
Answer prep: repeat → answer → bridge
The question window after the slides runs on a three-move frame. Repeat: restate the question in your own words — one line, which buys a breath and aims the answer. Answer: the actual response, claim first, evidence second, the size of one slide's notes. Bridge: one line that hands back to your material — "which connects to the scope decision on slide two" — so the exchange ends on your ground instead of trailing into silence. Most bad defense answers are not wrong; they are missing the repeat, so the committee cannot tell which question was answered, or missing the bridge, so the exchange dissolves.
Type the moves into the fields below and the assembled paragraph builds live; the amber gaps show where a move is still empty. Copy the result into your rehearsal notes. The fields are scratch — this page stores your slide plan, not your answers, because answers are what the capstone defense guide's bank and frame are for.
Answer prep builder
100% private — runs in your browserOne line. It buys a breath and tells the room which question you heard.
The size of one slide's notes. Claim in the first sentence; a nameable dataset second.
Ends the exchange on your ground: a slide, a decision, or a limitation you already own.
Assembled answer
Rebuilt live from the three fields; the amber gaps mark moves you have not drafted yet. The assembled text is scratch and never stored.
The example is an invented, illustrative capstone answer (the campus food-waste audit this shelf uses for teaching) — scratch state that never saves. Clear empties the three fields; it does not touch your slide plan.
Backup slides and the overflow plan
Two safety nets belong to every deck, and both are planned, not improvised. Backup slides sit behind a divider after your thanks slide: the full table you trimmed, the method step you compressed, the extra chart you promised in passing, the reference list in readable type. Three to six covers most defenses; name each after the question it answers, so when the question arrives, one click looks like foresight instead of a scramble. The planner's 30-row cap leaves room for a twelve-slide main deck and a real backup bank behind it.
The overflow plan is what you do when the rehearsal runs long, and it has exactly one correct form: cut a whole slide and redistribute its seconds, then re-time the run. Talking faster across every slide fails twice — the committee hears the rush and retains none of it. Skipping slides silently mid-deck fails louder, because someone always asks about the slide number that never came up. If the cut has to come from the middle, take it from literature or method detail, never from findings or the so-what — a talk that cannot say what changed for anyone is a tour of process with no destination.
Deck planned, deadline breathing down your neck?
The planner budgets the talk; the talk still needs a project behind it — the analysis the committee will probe, the sources that must hold, the formatting the rubric insists on. If the presentation date is fixed and the capstone behind the slides refuses to finish, a quoted, deadline-bound writer can take your data and your brief from raw draft to a formatted, referenced document while the argument stays yours. Your project, your slides, your voice. The form below is the way to ask.
What this page cannot do
The honest limits, because a page about planning your own talk should survive an audit:
- It cannot know your time limit. The ten-minute default is a guess; your program's slot, its rubric and any required slide count outrank everything here. Set the limit field to your real number before you trust the counter.
- It cannot rehearse you. The timing counter validates arithmetic, not delivery. A deck that sums to 9:20 can still run 12 minutes on stage if every slide is read instead of said — the checklist exists because the meter cannot hear you.
- The skeleton is a shape, not content. Ten rows with titles prove nothing about what you will actually say. If the notes boxes stay empty, the planner has budgeted a talk that does not exist yet.
- It cannot write your slides. Titles and notes are yours. What the tool adds is length discipline and a structure the committee expects — the substance comes from the project, and the study guides hub keeps every step of that build on one shelf.
- The mechanical checks live elsewhere. Speaking-time estimates for your notes belong to the words-to-minutes converter, and the wider toolbox — word counts, citations, readability — is the free writing tools page. This page owns the deck and the delivery; it does not try to own the rest.
Quiz: five calls from the rehearsal room
Five questions on the calls a presentation plan makes — where the budget earns its keep, what notes are for, what the repeat move buys, the fix for an over-running deck, and what backup slides are actually for. Every wrong answer reveals the right one, and four options keep the guessing honest.
1. Your slot is ten minutes. Where does a timing plan earn its keep?
2. What belongs in a slide's notes field?
3. The repeat move of repeat-answer-bridge exists to:
4. At the dress rehearsal the deck runs two minutes over. The strongest fix is:
5. Backup slides earn their place when they:
Frequently asked questions
How many slides should a capstone presentation have?
Budget slides from the time limit, not from a magic number. A workable rule of thumb is one to two minutes per slide: a ten-minute talk lands at eight to twelve slides including the title and the thanks slide, a twenty-minute talk at roughly fifteen to twenty. Two kinds of slide break the rule and both should stay rare — the title and thanks slides, which take seconds each, and evidence slides, which can hold the room for a minute and a half if the chart is doing real work. The planner on this page starts you at ten slides and lets you add, cut and reorder until the seconds add up to your actual limit.
How do I split my time limit across slides?
Fix the cheap slides first: thirty seconds for the title and welcome, thirty to sixty for questions and thanks at the end. Then give the heavy slides their budgets in order of how much the committee will probe them — findings usually earns the single largest block, method the second, and the problem, question and literature slides share what is left. Cap any one slide at two minutes, because past that point a slide stops being a visual and becomes a lecture. Type the budgets into the planner, compare the total against your limit in the counter, and keep trimming until you sit about ten percent under the limit — that spare minute is where a slow start and a paused sip of water live.
What goes on the slide versus in the notes?
The slide shows the claim and the one piece of evidence that carries it — a chart, a table, a single number large enough to read from the back row. The notes hold what you will say while it is up: spoken lines, not paragraphs pasted from the paper. A quick test for any sentence: if the room needs to hear it but not read it, it belongs in the notes; if they need to see it to follow the argument, it belongs on the slide. Slides crammed with full sentences force the committee to read instead of listen, and a presenter reading their own slides loses the room faster than any weak finding ever could.
What are backup slides and how many do I need?
Backup slides sit behind a divider slide after your closing slide and are never presented — they exist so that when a committee member asks for the full table, the cleaning rule or the chart you cut, one click produces it. Three to six cover most defenses: the complete version of a trimmed table, the method detail you compressed, the extra result you promised in passing, and the reference list in readable type. Name each backup after the question it answers so the click is instant. The planner holds up to thirty slides, which leaves room for a main deck of twelve and a backup bank behind the divider.
Does this page save my slide plan?
In this browser only. Slide titles, notes, per-slide timings, slides you add and the target time limit write to one local storage key, csw-cpr-v1 — immediately when you add, remove or reorder a slide, and after a short pause when you type. Reopening the page restores the plan. Reset erases the key and returns the default ten-slide skeleton. The delivery checklist, the quiz, the poll, the assembled answer-prep paragraph and the loaded example are scratch state and never stored. Nothing leaves the device — there is no account and no server copy.
The talk is the last mile of the capstone road this shelf paves. Pick the project from the capstone project ideas bank, build it with the capstone planner, bank the committee's questions in the capstone defense guide, and when the written core needs its skeleton rebuilt, the generic capstone project guide walks it start to finish. Budget the deck, tick the checklist, and stop talking when the total says so.
Did the planner get your deck under the limit?