A capstone topic viability checker is a feasibility audit for your topic, not a judge of its quality. You answer twelve weighted questions across five categories — scope, data and access, skills and tools, supervisor and program fit, deadline and personal constraints — and the page returns a 0-100 score, a four-band verdict, per-category bars and a red-flag list of concrete fixes. Everything runs in your browser; nothing you type leaves your device.
Capstone topics rarely fail on interest. They fail on logistics: the survey population that never answers, the archive that is not in the library, the supervisor who is on leave, the data collection that lands in exam week. This page measures that layer — whether the project you described can actually be run by you, this term, with what you have.
What it does not do: rank how smart, original or impressive the idea is. A topic scoring 90 can still be dull, and a sharp question can score 30 because its data sits behind an ethics committee. Read a low score as a list of engineering problems, not a verdict on your thinking — and read a high score as permission to start, not a promise of a grade.
The questions are deliberately blunt, and the answers are yours to give. Score what is true, not what you hope will become true by week six.
Run the viability check on your topic
Name the topic, answer the twelve questions, and the score fills in as you go — there is no score button to wait for. Each question takes a yes, partly or no answer, and the weight carried by each one is printed next to it. Red flags appear the moment a "no" lands on a heavily weighted question, so you can start fixing before the audit is even finished. If you want to see the mechanics first, load the demo topic: an invented, illustrative survey study that scores 58 — Fixable — with three red flags showing. Your answers live in this browser only (key csw-ctv-v1); Reset wipes them and the compare strip.
Capstone topic viability scorer
100% private — runs in your browserAnswer honestly — the score only helps if the answers describe your situation, not your intentions.
Scope — 3 questions, weight 13 of 50
Is the topic narrow enough to cover in one term?
w5Does the deliverable fit the word or page cap your program sets?
w4Does the topic hold a single clear question you could write in one sentence?
w4Data & access — 3 questions, weight 14 of 50
Are the main sources findable in your library or in public archives?
w5Are the participants or the sample reachable within your timeline?
w5Are permissions and ethics approval realistic for this population?
w4Skills & tools — 2 questions, weight 7 of 50
Do you already have the method skills — or weeks to learn one?
w4Is the software or equipment you need available to you (free tiers count)?
w3Supervisor & program fit — 2 questions, weight 9 of 50
Is there a supervisor on your list who actively works in this area?
w5Does the topic match what your program's rubric asks you to demonstrate?
w4Deadline & personal constraints — 2 questions, weight 7 of 50
Can data collection realistically finish before your deadline?
w4Does the topic fit the hours you actually have each week?
w3—
Where the points sit — five categories
Red flags + the fix for each
Compare saved topics
Saved to this browser only (same key as your answers), so the strip survives a reload. Reset clears it along with the check. The strip holds three topics; remove one to add another.
One scoring pass takes about three minutes. The sections below document the weights, the four bands, the red-flag rules and the rescue moves — read them once and the score will mean twice as much.
How the 12 questions are weighted
Every question is scored yes = 2, partly = 1, no = 0, then multiplied by that question's weight. The weights across all twelve questions sum to 50, so a perfect audit lands on exactly 100. The weights are not decoration — they encode how capstone projects actually die. A topic with unreachable data cannot be rescued by hard work, while a topic with the wrong software usually can. That asymmetry is why "participants reachable in time" carries weight five and "specialist software available" carries weight three.
| Category | Questions | Weight | Why it weighs this much |
|---|---|---|---|
| Scope | Narrow enough for one term; fits the word or page cap; one clear question. | 13 of 50 | Over-broad topics drift for a term, and a deliverable that ignores the cap gets cut in half at week nine — both are cheaper to prevent than to repair. |
| Data & access | Sources findable; sample reachable; ethics and permissions realistic. | 14 of 50 | The classic capstone killer: a semester plan with no data behind it. No fix downstream recovers data you cannot collect. |
| Skills & tools | Methods skills (or time to learn); software and equipment available. | 7 of 50 | Mostly learnable in weeks and mostly solvable with free tiers, so it earns less weight than access — a skill gap has a syllabus; an unreachable sample does not. |
| Supervisor & program fit | A supervisor active in the area; the rubric's demands matched. | 9 of 50 | No supervisor means no sign-off, whatever the topic's other merits. A rubric mismatch costs marks even when the work is good. |
| Deadline & personal | Collection ends before the deadline; weekly hours fit. | 7 of 50 | The plan has to fit the calendar you actually have, including the weeks other courses take from you. |
The point of printing the weights is that you can argue with them. If your program grades originality heavily, your own mental weights will differ, and that is fine — as long as the audit catches the two failure modes no amount of writing skill repairs: data you cannot reach and a supervisor you cannot get. Treat the numbers as this page's documented heuristic, not a standard any university publishes.
What the four bands mean
The score maps to four bands, each with its own color and its own instruction. The bands are deliberately wide — a 61 and a 73 call for the same move — because the useful precision is not in the last two points. It is in which category bar is shortest.
| Band | Score | What it means | The move |
|---|---|---|---|
| Green light | 75-100 | The logistics hold end to end. | Write the proposal — then re-check after your supervisor reshapes the scope, because approval usually moves something. |
| Fixable | 55-74 | The core holds, but one or two categories drag. | Work the red-flag list top-down, then re-score. The delta badge shows whether the fixes actually paid. |
| Risky | 35-54 | More than one category is fighting the calendar. | Fix data access first; if two high-weight flags stay red after honest answers, rethink the population rather than the plan. |
| Rethink | 0-34 | Too much is missing at once. | Keep the theme, rebuild the study around data you can reach this term. The theme is rarely the problem. |
Two honest notes on the banding. First, these bands are the page's own heuristic — your program does not score topics this way, and no band predicts a grade. Second, a green light audits the plan you typed, not the plan you will run. If you answered "yes" to reachable participants on the strength of a cousin who "knows loads of people", the audit is only as good as that answer.
Reading the red-flag list
The red-flag list is rule-mapped, not mood-based: every "no" emits the concrete fix for that exact failure, ordered by weight, with the weight-five questions tagged high. "Partly" answers never flag — a partly is already half a fix, and the category bars show where the remaining half sits. What the mapping looks like in practice:
- "No" on sources findable (weight 5): switch to secondary data — published datasets, annual reports or an archive your library already licenses. The fix is not "try harder to find sources"; it is change the evidence base.
- "No" on participants reachable (weight 5): swap the survey for six to eight interviews with people you can already reach, or study documents instead of people. The population narrows before the method changes, not after.
- "No" on narrow enough (weight 5): narrow the population to one site — "customer satisfaction" becomes checkout satisfaction at two branches of one chain.
- "No" on supervisor fit (weight 5): email two supervisors this week with a one-paragraph pitch. No supervisor means no topic, and no fix on any other line changes that.
- "No" on collection finishing in time (weight 4): move collection to the first three weeks, or cut it to a two-week sprint with a smaller sample.
The fixes are ordered by weight rather than by ease, because the high-weight failures are the ones that end projects. Treat the list as a to-do queue for the week before the proposal is due: top item first, re-score after each fix, and let the delta badge tell you whether the change was cosmetic or structural. A red-flag list that shrinks from five items to two while the score climbs twenty points is the tool working as designed.
Comparing topics side by side
One score is a snapshot; two or three are a decision. After a complete scoring pass, save the topic to the compare strip — it holds up to three saved topics, each with its score, band and five category mini-bars, plus a session table so you can see which candidate wins on scope and which wins on access. The strongest score gets marked. Saving is the moment to give the topic a real name: "Untitled topic" is hard to choose between late at night, and the strip has no way to know that "idea 2" was the one about the warehouse.
The strip lives in the same browser key as your answers, so it survives a reload — which is the point, because topic choice is rarely settled in one sitting. Score three candidates on Sunday, sleep on them, and the table is still there. When a supervisor vetoes the front-runner, remove its card and the remaining two are still scored. Compare the bars as much as the totals: a 70 built on weak data access is a more fragile topic than a 66 with full marks on access and a soft deadline.
Viability is a function of the calendar
The same topic changes score as the term burns down. A plan that scores 80 in October can score 55 in November without changing at all — what changed is the distance between today and the deadline, which quietly tightens the answers to sample reachability and collection timing. So run the check at three moments: before you write the proposal, after the supervisor meeting reshapes the scope, and again mid-term when the calendar has eaten a few weeks.
If you want the calendar itself audited, the dissertation timeline generator turns a start date and a defense deadline into twelve editable milestones, simulates slips and exports the plan as an .ics file — it owns the sequencing question that this page can only ask about ("can collection finish in time?"). Use them in that order: viability first, then the timeline for the topic that survives.
Rescue moves for a topic that scores low
Most low scores trace back to one root cause: the topic was written at the width of a bookshelf when it needed the width of a shelf slot. Narrowing is subtraction, and it is the cheapest points on the board. Each rewrite below keeps the theme and swaps the population for one a single student can actually reach — which is what moves the scope and access bars at the same time:
| As first written | After narrowing |
|---|---|
| "How social media affects consumer behavior." | "How two branches of one supermarket chain describe checkout satisfaction." |
| "The impact of technology on education." | "How one sixth-form college's maths department uses a spaced-repetition app for homework." |
| "Employee motivation in organizations." | "What keeps night-shift warehouse staff at one logistics depot from leaving in their first year." |
| "Sustainable packaging: attitudes and perceptions." | "What a weekly farmers' market's stallholders say about switching to compostable packaging." |
Notice what the rewrites share: a population you could email this week, a setting you could visit, and a question that fits in one sentence. If narrowing alone does not clear the red flags, the next move is changing the evidence base — interviews instead of surveys, documents instead of people, secondary data instead of fieldwork. The capstone project ideas page is the place to harvest replacement candidates, and once one scores in the fixable range or better, the capstone proposal builder turns it into a structured draft. Neither page will run out of topics before your deadline does.
What this checker cannot do
The honest limits, because this page asks you to trust tools that state theirs:
- It does not judge the idea. Originality, interest and academic value live outside the audit. A 90 means "runnable", nothing more.
- It cannot check your program's facts. Word caps, ethics forms and supervisor lists come from your handbook; the questions are only as accurate as the answers you type against them.
- The weights are a heuristic. They are documented, they are arguable, and they are not a grading scale any university publishes. Two honest people could defensibly disagree by a few points.
- It does not write the proposal. Feasibility first, structure second: the proposal builder handles the draft, and the capstone research paper guide covers how the finished document is assembled.
- The score is only as honest as you are. "Partly" answers that are really "no" answers inflate the total and hide the flags — the tool cannot audit your candor.
For the wider toolkit — counting, readability, citation, planning — the free writing tools hub collects everything on the site, and the study guides hub holds the craft guides this page assumes. Both are worth a bookmark before term starts.
Every flag fixed and the topic still fights the calendar?
If the deadline is close and the topic needs a scope you cannot run alone, a quoted, deadline-bound writer can draft the proposal around the topic you scored — your question, your data, your citations. Get a free price quote and see the terms first.
Quiz: five questions on topic viability
Five questions on feasibility — what the weights reward, which category kills the most topics, and what a mid-band score is actually asking for. Every wrong answer explains itself, and four options keep the guessing honest.
1. What does this viability score actually measure?
2. Your topic needs interviews with twenty managers, the deadline is six weeks away, and you know none of them. Which category takes the hit?
3. Which of these is narrow enough to run in one term?
4. Why does "participants reachable in time" carry more weight than "specialist software available"?
5. Your topic scores 58 — Fixable — with red flags on data access. What is the right next move?
Frequently asked questions
What does a capstone topic viability checker actually do?
It audits execution risk, not brilliance. Twelve weighted questions across five categories — scope, data and access, skills and tools, supervisor and program fit, deadline and personal constraints — produce a 0-100 score that says how likely the topic is to survive a full term of work. A high score means the logistics hold; it does not promise the findings will be interesting, and a low score is a list of engineering problems, not a verdict on your thinking.
What score should I have before committing to a topic?
Treat 75 or above as the green-light zone and 55-74 as fixable: work the red-flag list, then re-score and watch the delta. Below 55, pause before writing the proposal. A topic scoring 40 does not need willpower — it needs a narrower population, reachable data or an earlier collection start, and the red-flag list names which fix belongs to which question.
Can a risky topic be fixed, or should I start over?
Most risky scores are one or two fixes away. Swapping a survey of strangers for interviews with people you can already reach, narrowing a population to one site, or moving data collection three weeks earlier routinely adds double digits on the 100-point scale. Start over only when the supervisor-fit question stays red after two honest passes — no supervisor means no topic, whatever every other answer says.
Does a high score mean my topic is good?
No, and that is the honest limit. This is a structured feasibility audit: it measures whether you can run the project you described, not whether the question matters. A topic can score 90 and still bore everyone, and a sharp question can score 30 because its data sits behind an ethics committee. Use the score to protect the semester; bring the taste and the argument yourself.
When should I run the check — before or after the proposal?
Before, and again after every big change. Checking first saves you from writing a full proposal around a topic that cannot be executed; re-checking after your supervisor narrows the scope shows whether the fixes actually moved the number. The delta badge tracks that movement between checks, which turns the score from a one-off verdict into a running log.
Did the check surface a red flag you can fix this week?