---
title: "Technical Debt Register"
description: "Track, prioritize, and communicate technical debt. Log debt items with severity and effort, calculate interest cost, and generate stakeholder reports."
url: https://findutils.com/productivity/tech-debt-register/
category: productivity
---

# Technical Debt Register

Track, prioritize, and communicate technical debt. Log debt items with severity and effort, calculate interest cost, and generate stakeholder reports.

**Use this tool:** [Technical Debt Register](https://findutils.com/productivity/tech-debt-register/)

## Programmatic access

- REST id `tech-debt-register`: POST https://api.findutils.com/api/tools/tech-debt-register/execute (reference: https://findutils.com/api/tech-debt-register/)
- MCP tool `tech_debt_register` on https://mcp.findutils.com (reference: https://findutils.com/mcp/tech-debt-register/)

## Why use Technical Debt Register?

Technical debt accumulates silently until it becomes a crisis. Every shortcut, every 'we'll fix it later' adds up. This tool helps you make debt visible, prioritize what to fix first, and communicate the cost of not addressing it to stakeholders.

## Tips for Managing Technical Debt

- Log debt at the moment you discover it. Delayed entries lose context and accuracy.
- Re-estimate interest rates monthly. A workaround that costs two hours a week today may cost five after the next feature ships.
- Celebrate resolved items visibly. Marking debt as done reinforces the habit of paying it off.
- Use the Won't Fix status honestly. Some debt is cheaper to live with than to remove.
- Pair the register with your retrospective process so debt items surface naturally after each sprint.

## Frequently Asked Questions

### What is technical debt?

Technical debt is the implied cost of additional rework caused by choosing an easy solution now instead of a better approach that would take longer. Like financial debt, it accumulates 'interest' over time in the form of slower development, more bugs, and harder maintenance.

### How do I estimate the interest rate?

Think about how much time you waste each week because of this debt. Extra debugging time, workarounds, explaining the quirks to new developers, or slower feature development. Even a rough estimate helps prioritize.

### Should I fix all technical debt?

No. Some debt has low interest and would take too long to fix - it's not worth the investment. Focus on high-severity, high-interest debt that's blocking you regularly. Use the priority matrix to identify what to tackle first.

### How do I get buy-in from management?

Use the weekly interest metric. Show them 'We're losing X hours per week due to technical debt.' Frame it as an investment: 'If we spend 20 hours fixing this, we save 5 hours every week going forward.'

### What categories of technical debt should I track?

The register includes six categories: Code Quality, Architecture, Testing, Documentation, Security, and Performance. Most teams find that Architecture and Code Quality items carry the highest interest, but Security debt often has the most severe consequences if left unaddressed.

### How often should I review the register?

Review it at least once per sprint. Many teams add a five-minute debt review to their sprint planning or retrospective. Monthly deep reviews are useful for updating interest rate estimates and generating stakeholder reports.

### Can I export my data?

You can export the full register as a PNG image. There is no Markdown export.

### Is my data stored on a server?

No. All data stays in your browser's local storage. Nothing is uploaded to any server. This makes it safe for tracking debt in proprietary or sensitive codebases.

### How do I prioritize debt when everything feels critical?

Start with the priority matrix. Items in the Quick Wins quadrant have high severity and low effort, giving you the best return for your time. If multiple items tie, compare their weekly interest rates and fix the one costing the most hours first.

### What is the difference between severity and interest rate?

Severity measures how badly the debt affects your system right now, from minor annoyance to critical risk. Interest rate measures the ongoing weekly cost in developer hours. A high-severity item with low interest might be dangerous but rarely triggered, while a medium-severity item with high interest drains your team every single week.

## Related Tools

- [Scope Creep Tracker](https://findutils.com/productivity/scope-creep-tracker/)
- [Sprint Capacity Calculator](https://findutils.com/productivity/sprint-capacity-calculator/)
- [Dev Request Prioritizer](https://findutils.com/productivity/dev-request-prioritizer/)
- [Story Point Poker](https://findutils.com/productivity/story-point-poker/)
- [Retro Meeting](https://findutils.com/productivity/retro-meeting/)
- [ROI Calculator](https://findutils.com/finance/roi-calculator/)
- [Diff Checker](https://findutils.com/text/diff-checker/)
- [Pomodoro Timer](https://findutils.com/productivity/pomodoro-timer/)