This document is a template for recording known errors and incidents in a database to track their resolution over time. It includes fields for the incident details, affected services, activities to resolve the issue, related problems, assignments, workarounds, root cause, permanent fix, applicable changes, estimated fix date, comments, status, title, description, risk ID, and phase. Maintaining this known error database allows organizations to document errors as they occur and monitor their resolution.

1. Incident
SRS
Severity
P1 / P2
Start
Date / Time
Resolve
Date / Time
Impacted
Services
Incident
Description
Activities undertaken to
resolve the incident
Parent
Problem SRS
Child
Problem SRS
Assignment
Group
Problem Analyst
Temporary
Workaround
exists?
(Yes / No)
Workaround
information
Root cause
known?
(Yes / No)
Permanent Fix
Determined
(Yes / No)
Permanent Fix information
Change
SRS, if
applicable?
Estimated
Fix Date
Comments
Known Error Status
(Open, Deferred,
Closed, Awaiting
Change, Risk
Accepted, etc)
Known Error Title
(Short Summary)
Known Error
Description
(more details of the
Known Error/Risk)
Risk ID
(if required,
please add Risk
ID here and
reference
Problem SRS into
the Risk Register)
Known Error Database
(KEDB)
This Known Error Database consists of all such known errors, recorded as
they are and when they happened – and they’re maintained over time.
Known Error Phase