How inspection scoring works

What scoring means

When scoring is on for a template, each completed inspection can show points earned versus points available across the questions that count, plus a percentage. Scoring answers one question: of the credit this inspection could earn, how much did it actually earn? It adds a consistent numeric rollup on top of your pass/fail checks, photos, and notes — it doesn't replace them.

Turning scoring on

Scoring is controlled per template, not for your whole account. Open the template in the builder and use the Enable inspection scoring toggle near the top, above the description.

• When scoring is off, completed inspections don't compute or store a score for that template.
• When it's on, the score is calculated at completion and snapshotted with that inspection — so later edits to the template never rewrite the scores of inspections already finished.

Your administrator may also control whether the scoring feature is available at all. If scoring never appears, that's usually a configuration choice.

The two numbers to understand

For each scored question, the system tracks:

The overall score is the sum of earned points; overall possible is the sum of the caps. The percentage is earned ÷ possible × 100 when possible is greater than zero. If nothing on the inspection could earn points, no percentage is shown. Scores can also roll up by section.

Which questions count

A question participates in scoring when all of these are true:

• The template has scoring enabled.
• It's a standard scored question.
• It's not marked exclude from scoring.
• It was visible during that inspection (see conditional logic).

How answers earn points

• Single choice — options carry relative weights; the app scales them so the best option matches the question's maximum score, and worse options earn proportionally less.
• Multi-select — points from each selected option are added, then capped at the question's maximum.
• Checkbox / yes–no — a checked or affirmative answer earns the credit set for it; the other state earns none.
• Slider — the position maps linearly from zero up to the question's maximum.
• Number — the value counts as points up to the maximum (below zero counts as zero; above the cap counts as the cap).

Question weight

Each scored question can carry a weight (multiplier). Both its possible and earned points are multiplied by the weight, so a question with weight 2 counts twice as much as the same question at weight 1. With no weight set, the app treats it as 1.

Excluding a question

Exclude from scoring removes a question from both the earned and possible totals. Use it for labels, instructions, or informational fields that shouldn't move the result.

Conditional logic and hidden questions

Questions hidden by logic rules for a given inspection are omitted from scoring entirely — not scored as zero. This keeps the percentage aligned with what the inspector actually saw. For accurate results with heavy conditional logic, conduct inspections on current apps.

What gets saved

When a scored inspection completes, it stores the rollup earned, possible, and percentage, plus a per-question and per-section breakdown snapshot for reports and audits. That snapshot preserves what the rules produced at completion, even if the template changes later.

Tips for template authors

1. Turn scoring on only when you need a number — leave it off for purely qualitative checklists.
2. Set a clear maximum per scored question so importance is obvious.
3. Keep option points and maximums at zero or above.
4. Use exclude from scoring for labels and fields that shouldn't affect results.
5. Test one completed inspection after changing weights or option scores — the percentage should move as you expect.

Related articles

• Create templates
• Set up question logic and answer actions
• Templates and inspections
• Response types
• Analytics quick start