How to Track Technical Debt
- 1
Log Each Debt Item
Open the Debt Register tab and click Add Debt Item. Give each entry a clear title such as 'Monolithic auth module' and choose a category like Architecture or Testing. A concise description now saves confusion later. - 2
Rate Severity and Effort
Assign a severity score from 1 (minor) to 5 (critical) and estimate the hours required to fix. Then set the weekly interest rate, the hours your team loses every week because this debt exists. These numbers drive the priority matrix. - 3
Review the Priority Matrix
Switch to the Priority Matrix tab. Items land in one of four quadrants: Quick Wins (high severity, low effort), Strategic (high severity, high effort), Low Priority, and Time Sinks. Start with Quick Wins for the fastest return. - 4
Generate a Stakeholder Report
Go to the Report tab, set your weekly debt budget, and export a Markdown or PNG report. The report includes an executive summary, ROI calculations, and a recommended payoff timeline managers can act on.
Use Cases
Sprint Planning
Engineering Budget Proposals
Post-Incident Reviews
New Team Onboarding
Why use Technical Debt Register?
Technical debt is the gap between how your codebase should work and how it actually works today. Every shortcut, deferred refactor, and 'temporary' workaround adds to that gap. The Technical Debt Register gives you a structured way to catalog every item, assign severity and effort estimates, and track the ongoing cost in developer hours lost each week. Unlike a spreadsheet or sticky note, the register calculates compound interest automatically so you can see exactly which items are bleeding the most time.
The built-in priority matrix plots each debt item on a severity-versus-effort grid, instantly highlighting Quick Wins you can knock out in a single sprint and Strategic items that need a larger investment. Use the Sprint Capacity Calculator to figure out how many debt hours fit into your next iteration, or run a Retrospective Meeting to surface new debt items your team has been quietly working around. If scope keeps expanding while you tackle debt, the Scope Creep Tracker helps you stay honest about what actually ships.
When it is time to present findings to leadership, the Report tab generates a polished executive summary with ROI projections. Pair it with the ROI Calculator to model the financial upside of a dedicated refactoring quarter, or use the Diff Checker to document exactly what changed after a debt payoff effort. Everything runs in your browser with no server uploads, so proprietary codebases stay private.
How It Compares
Most teams track technical debt in Jira tickets, spreadsheets, or not at all. Jira mixes debt with feature work, making it easy to deprioritize indefinitely. Spreadsheets lack the automatic interest calculations and visual priority matrix that turn raw data into decisions. Dedicated commercial tools like Stepsize or CodeScene offer deep integrations but come with per-seat pricing and require repository access. The FindUtils Technical Debt Register sits in the middle: it provides the priority matrix, interest tracking, and stakeholder reporting you need without any signup, installation, or recurring cost. Because everything runs client-side, your data never leaves your machine.
If your team already uses agile ceremonies, the register fits naturally into sprint planning and retrospectives. Export a Markdown report, paste it into your wiki, and you have a living document that leadership and engineering can reference together. For teams that want even more context, combining the register with the Story Point Poker tool lets you estimate debt payoff stories collaboratively.