How should teams read a technical debt audit?

Start with high-severity findings, then inspect source report provenance and recommendation priority before scheduling work.

What should be linked from a debt review?

Link the audit detail, tool report detail, relevant findings, recommendations, and any data-boundary context needed for review.

Guide

How to review a Flutter technical debt audit.

A useful debt review separates sourced evidence from priority decisions. The dashboard should make both visible without asking reviewers to read technical report data first.

Create account Upload your first audit

1. Start with provenance

Check which tool reports contributed to the audit and whether each finding or recommendation can be linked back to its source. This keeps a planning discussion grounded in available report data.

2. Sort by decision impact

Use severity, priority, repository, status, and category filters to move from broad audit data to the few items that deserve scheduling attention.

3. Keep data boundaries visible

Source code is not uploaded by design, but reports may include paths, branch and commit information, generated evidence, and summaries. Link reviewers to the data-boundary page when sharing reports.

Data boundary Use case Plans

FAQ

Should every finding become a ticket?

No. Use recommendations, severity, and repository context to decide what deserves work now.

Can Free support a trial review?

Yes. Free supports a small number of repositories and monthly uploads for evaluation.