Home / Capstone topic selection

Capstone decision guide

Capstone Project Topics: How to Test Feasibility Before Approval

A strong capstone topic is not merely interesting. It describes a verified problem, fits the program outcome, can be completed with available access and produces evidence that can answer a bounded question.

Problem evidenceAccess checkMeasure fitApproval path

Quick answer

Start with a documented problem, not a solution you already want

Write the problem as a measurable condition in a defined population, setting and period. Then collect baseline evidence. A topic such as improving diabetes education is too broad. A feasible problem statement identifies the observed education gap, affected group, site boundary and evidence showing the gap matters.

Run a red-flag review before approval: unavailable participants, protected data without a route to access, a timeline shorter than the intervention, an outcome that changes too slowly, dependence on a vendor or leader who has not agreed, and a scope that contains multiple independent problems.

Create a one-page feasibility memo for each candidate. Compare alignment, access, stakeholder support, measure quality, approval complexity, time, cost and risk. The highest-impact idea is not automatically the best capstone if it cannot produce credible evidence within the program window.

A decision-first method

Score each capstone topic before committing

A transparent comparison prevents enthusiasm from hiding a fatal constraint.

Verify the problem

Use local, organizational or credible published evidence to establish the gap.

Define the boundary

Name the population, setting, process and period that are actually in scope.

Test access

Confirm stakeholders, records, tools, permissions and site support.

Match measures to the question

Choose process, outcome and balancing measures that can answer the purpose.

Map approvals and ethics

Identify institutional, site, privacy and human-subjects determinations.

Stress-test the timeline

Include recruitment, implementation, data, analysis, revisions and delays.

Working decisions

Capstone topic feasibility matrix

Criterion Question Evidence
Alignment Does the topic meet the program and course outcome? Rubric and handbook mapping
Problem Is the gap documented locally or credibly? Baseline, audit or literature
Access Can the needed people, setting and records be reached? Written site confirmation
Measures Can change be observed in the time available? Operational definitions and data source
Approval What review must occur before activity begins? Institution and site requirements
Scope Can one learner complete it? Work breakdown and calendar

Use the current program, course or project requirements as the controlling source. The table is a planning aid, not an institutional ruling.

Original worked example

Narrowing an unworkable patient-safety idea

Broad idea: reduce medication errors across a hospital. Feasible version: improve completion of an existing high-risk medication double-check on one adult unit during a defined implementation period. Baseline audit data, unit leadership, a process measure and a balancing measure are identified before proposing the intervention.

Narrowing the setting and process makes access, measurement and ownership visible without claiming the intervention will succeed.

Common problems and repairs

Capstone topic problems that surface too late

Solution-first topic

Repair: establish the problem and causes before selecting the intervention.

No local baseline

Repair: identify the credible evidence that demonstrates the current gap.

Outcome outside the timeline

Repair: add a responsive process measure or change the scope.

Access assumed rather than confirmed

Repair: obtain written site and data-path clarification before approval.

Final control

Capstone topic pre-approval checklist

  • Problem is measurable and bounded.
  • Topic aligns with the active rubric.
  • Stakeholder and site access are credible.
  • Data source and measure definitions exist.
  • Approval path is documented.
  • Timeline includes delays and revision.
  • Topic can be completed by one learner.

Keep the record authentic

Do not invent baseline data, site support, participants or approvals. The proposal must describe authentic access and the determinations actually obtained.

Sources and version check

Sources used for this guide

Verify the active requirements

Requirements vary by institution, instructor, site and project version. Use the current instructions, rubric, handbook and approvals as the controlling sources.

Frequently asked questions

Capstone Project Topics: How to Test Feasibility Before Approval questions

What should I verify first for capstone project topics?

Verify the current institution, program, course or project requirements and identify the exact decision you need to make. Public examples do not override your active requirements.

Can Bright Writers help me plan capstone project topics?

Yes. Help can include requirement breakdown, planning, concept explanation, evidence organization, rubric review, feedback on your own draft and a prioritized revision plan.

Can I use the example on this page in my submission?

Use it to understand the reasoning moves, then create your own work from your assignment, approved evidence and authentic project record. Do not submit the sample as your answer.

What should I send when requesting help?

Send the current instructions, rubric or policy, your own attempt, relevant feedback, the exact point of difficulty and the deadline. Remove passwords and protected personal information.

Will Bright Writers complete or submit the work for me?

No. Support is educational and review-based. You remain the learner, author and person responsible for every submission and institutional decision.

What makes a good capstone project topic?

A good topic is important, aligned, bounded, feasible, measurable and supported by authentic access and approvals.

Can I use a national statistic as my baseline?

A national statistic can establish importance, but it may not prove the problem exists in your local project setting. Use the evidence required by your program.

Scroll to Top
Scroll to Top