Reading Your Results·Beginner
Understanding the Finish Plan
Learn how to read and navigate your FinishKit Finish Plan.
Your Finish Plan is the output of a FinishKit scan. It's a prioritised list of everything standing between your app and a successful launch.
Layout
The Finish Plan is divided into two sections:
Blockers at the top: findings that will actively prevent your app from working in production. Fix these first.
Everything else below: findings organized by category (security, deploy, stability, tests, ui) and sorted by severity within each category.
Reading a finding
Each finding shows:
| Field | What it means |
|---|---|
| Title | Short description of the issue |
| Category | Which type of problem it is |
| Severity | How urgent the fix is (critical → low) |
| File | Where in your codebase the issue lives |
| Explanation | Why this matters for shipping |
| Suggested fix | What to do about it |
What to do first
- Read through all critical and high severity findings
- Fix blockers before anything else
- Work through security findings next. These protect your users.
- Then deploy, stability, tests, and ui in that order
Re-scanning
After fixing issues, run another scan from your project page. FinishKit will show you which findings have been resolved and flag any new ones.