SMART Goal Statement Calculator
Test your Define phase goal statement against all five SMART criteria before it reaches the charter. Paste the statement, get a weighted clarity score, see the exact evidence found for each element and get a rewritten version you can use.
📘 What the SMART Goal Statement Calculator does
A goal statement is the promise your project makes to the business. It sits in the project charter, it drives the measurement plan and it decides whether the tollgate review passes or stalls. Most goal statements fail for the same reason. They sound confident and say nothing you can test.
This calculator reads the goal statement you write and scans it for the evidence that each SMART element actually needs. It looks for action verbs, named outputs, numeric baselines and targets, currency values, resource and sponsor references, business purpose language and hard deadlines. Each element receives a score from 0 to 100 based on the evidence it finds, then the five scores are weighted into one clarity score.
It also runs a Define phase check that most SMART tools miss. A goal statement should state what you will achieve, not how you will achieve it. Any statement that names a solution before the Analyse phase locks the project into an answer nobody has proven yet. The calculator flags that language and deducts from the score.
The formula
How the clarity score is built
In plain words: score each SMART element out of 100 from the evidence found in your text, weight the five scores by how much each one matters in a Six Sigma charter, add them together, then subtract a penalty for any solution language hidden in the goal.
Measurable and Time bound carry the heaviest weight at 25 per cent each, because a goal without a number and a date cannot be tested at a tollgate. The solution penalty is 8 points for each solution phrase found, capped at 15 points.
How to use it
- Open the Calculator tab and load one of the four sample statements to see how the scoring behaves.
- Enter your project name and the name of the person who prepared the statement.
- Paste or type your draft goal statement into the text box. Watch the five element indicators update as you type.
- Fill in the rewrite builder fields underneath. These are optional, but they let the tool return a corrected statement rather than a template with gaps.
- Select Analyse goal statement. The Results tab opens with the score, the element breakdown and the evidence found.
- Read the element table. Every row shows what the calculator found and what it could not find.
- Apply the recommended actions, paste the improved wording back into the text box and run it again.
- Download the Excel workbook once you reach 85 or above and attach it to your project charter as evidence.
Score bands
| Score | Band | What it means | What to do next |
|---|---|---|---|
| 85 to 100 | Charter ready | Every element carries testable evidence and the goal describes an outcome rather than a solution. | Lock it into the charter and build the measurement plan from the stated metric. |
| 70 to 84 | Nearly there | The core is sound. One element is thin, usually the achievability evidence or the scope boundary. | Add the missing evidence and rerun. This is a ten minute fix. |
| 55 to 69 | Needs work | Two elements are weak, or a solution has been written into the goal. | Rewrite before the Define tollgate. Do not build a measurement plan from this yet. |
| 40 to 54 | Weak | The statement names a direction but nobody can prove whether you hit it. | Go back to the baseline data and set a real number and a real date. |
| Below 40 | Rewrite required | The statement is an intention, not a goal. It will not survive a tollgate review. | Start again using the rewrite builder in the Calculator tab. |
What each element needs
| Element | Weight | Evidence the calculator looks for |
|---|---|---|
| Specific | 20% | An improvement verb, a named output or metric, a named scope such as a site, line, ward or team, and a stated starting point. |
| Measurable | 25% | A percentage, a baseline to target range, a number with a unit, a currency value or a rate denominator such as per month. |
| Achievable | 15% | Budget or resource reference, sponsor or approval evidence, existing capability language, or a benchmark that proves the target has been reached before. |
| Relevant | 15% | A business purpose clause, a business impact term such as margin or compliance, a link to strategy, and a named beneficiary. |
| Time bound | 25% | A specific date, a deadline preposition, a quarter or financial year reference, a relative window such as within 12 weeks, or an interim milestone. |
Common mistakes
- Writing the solution into the goal. Phrases such as through training, by implementing a new system or by hiring two analysts commit the project before the Analyse phase has run.
- Setting a target with no baseline. Reduce complaints to 75 per month means nothing until the reader knows you started at 100.
- Using soft time language. As soon as possible, ongoing and in the near future all fail the time bound test.
- Claiming zero defects or 100 per cent with no resource or benchmark evidence behind it. The calculator deducts points for absolute claims that nothing supports.
- Leaving the scope open. A goal that does not name the site, line, team or product family gets tested against the whole business, which is a fight you will lose at the review.
💡 Pro tips
- Write the metric first. If you cannot name the metric, you do not have a project yet, you have a complaint.
- Pull the baseline from at least four weeks of data before you write the number into the goal.
- Set the target at the gap between your current performance and the best comparable performance you can evidence, then take half of it for the first cycle.
- Use a hard calendar date rather than a duration. Within six months moves with every delay. 30 June 2026 does not.
- Name the sponsor and the budget in the goal statement. It converts achievability from an opinion into a fact.
- Read the finished statement to somebody outside the project. If they cannot tell you what number changes and by when, rewrite it.
Where this sits in DMAIC
This is a Define phase tool. The goal statement is written after the problem statement and the business case, and before the project charter is signed. It feeds three later steps directly. The metric named in the goal becomes the primary Y in the Measure phase. The baseline named in the goal becomes the reference for capability analysis. The target named in the goal becomes the pass condition for the Control phase.
Run this calculator at the end of Define and again at the Define tollgate. If scope changes during Analyse, rerun it and update the charter rather than letting the goal quietly drift.
⚠️ What to avoid before the Analyse phase
A goal statement states the outcome. A solution statement states the method. Reduce order processing time from 9 days to 4 days is a goal. Reduce order processing time by installing workflow software is a solution wearing a goal statement costume. Keep the method out until the data tells you what the method should be.
🧮 Score your goal statement
Load a sample to see the scoring in action, or enter your own statement. The five indicators below the text box update as you type.
Project details
These carry through to the Excel workbook so the report is traceable.
Your goal statement
Aim for 25 to 60 words. Long enough to carry the evidence, short enough to read out at a tollgate.
Rewrite builder
Optional. Fill these in and the calculator returns a corrected goal statement instead of a template with gaps. Every field maps to one SMART element.
No analysis yet
Open the Calculator tab, enter a goal statement and select Analyse goal statement. Your score, element breakdown and recommended actions appear here.
SMART goal statement calculator for the Six Sigma Define phase
A SMART goal statement turns a vague improvement wish into a testable commitment. The five criteria have been used in project management since the early 1980s, but a Six Sigma charter asks more of them. It needs a metric the Measure phase can collect, a baseline the capability study can compare against, and a target the Control phase can hold. This calculator scores your statement against all five criteria and returns the exact wording gaps that stop it passing a tollgate review.
Why most goal statements fail the Define tollgate
Three failures repeat across almost every project review. The first is a missing baseline. A target with no starting point cannot show improvement. The second is soft time language, where a statement promises delivery soon or on an ongoing basis and therefore never becomes overdue. The third is the solution written into the goal, where the project commits to training, software or headcount before any root cause work has run.
The calculator checks all three. The Measurable score drops when a target has no baseline. The Time bound score drops when only soft language appears. A separate Define phase check deducts points for solution language and names the exact phrase that triggered it.
How the SMART clarity score is weighted
Not every SMART element carries equal weight in an improvement charter. Measurable and Time bound sit at 25 per cent each because they decide whether the project can be assessed at all. Specific sits at 20 per cent. Achievable and Relevant sit at 15 per cent each. They matter for sponsorship and support, but a project with weak relevance and a hard number still gets measured, whereas a project with strong relevance and no number does not.
Turning the goal statement into a measurement plan
Once the statement scores 85 or above, three things fall out of it automatically. The metric named in the goal becomes the primary Y for data collection. The baseline becomes the input for your process capability and sigma level calculations. The target sets the control limits your Control phase has to defend. That is why the wording matters. A loose goal creates a loose measurement plan, and a loose measurement plan creates a project that cannot prove it worked.
Frequently asked questions
What is a SMART goal statement in Six Sigma?
It is the sentence in the project charter that states what the project will change, by how much and by when. It must be Specific, Measurable, Achievable, Relevant and Time bound. In Six Sigma it also has to name a metric that the Measure phase can actually collect.
What score should my goal statement reach?
Aim for 85 or above before the Define tollgate. Between 70 and 84 the statement usually needs one addition, most often the achievability evidence. Below 55 the statement will not support a measurement plan and needs rewriting.
Why should a goal statement not contain a solution?
Because the solution has not been proven yet. Writing through training or by installing new software into the goal commits the project to an answer before the Analyse phase has identified the root cause. It also makes the project impossible to fail honestly, since success gets measured against the activity rather than the outcome.
Do I need a baseline in the goal statement?
Yes. A target without a baseline cannot demonstrate improvement. Write both values, as in from 4.8 per cent to 2.0 per cent. The calculator scores a baseline to target range far higher than a target on its own.
How long should a goal statement be?
Between 25 and 60 words. Shorter than 15 words and it will be missing evidence. Longer than 70 words and it usually contains scope creep, a solution or a second goal that belongs in its own project.
Can I export the analysis?
Yes. The calculator generates a branded four sheet Excel workbook containing the summary and score, your input statement and builder fields, the full element analysis with detected evidence, and a prioritised action plan.
