🧾
IT & Product
Tech Debt Register Entry
A structured way for engineers to log tech debt — what it is, how much it hurts, and what it risks — so it lives in a register instead of in their heads.
Use this template10 fields · Free · Customize before publishing
What this form looks like
Preview · not interactiveTech Debt Register Entry
A structured way for engineers to log tech debt — what it is, how much it hurts, and what it risks — so it lives in a register instead of in their heads.
Reported by*
Your name
Repo / component*
Select…▾
Which component?
Name the repo or system
Type of debt*
Select…▾
Describe the debt*
Affected files, endpoints, or services
e.g. services/billing/*, POST /v2/invoices
Concrete pointers make the fix scopeable later.
How much does it hurt today?*
★★★★★
1 = mild annoyance, 5 = slows every change in this area.
Risk if we ignore it for the next year*
Barely noticeableIncident waiting to happen
Effort to fix*
S — under a day
M — a few days
L — a sprint
XL — multi-sprint project
Suggested fix (optional)
Submit