Discrepancy register design
How to structure a records discrepancy register
Structuring a discrepancy register means designing the fields and rules that turn a list of records findings into a tool a team can close items from. It is read by records teams setting up a tracker for an audit, a return, or a self-inspection. The work covers the fields each entry carries, the source document and trace attached to every finding, the severity scheme, the closure owner and due date, and the definition of closed that requires evidence. You end with a register schema, a worked example entry, and the closure rules the team will run it by.
When this review is needed
- An audit or review has produced findings and the team needs a structure to track them to closure.
- A prior register stalled because entries lacked a source, an owner, or a clear definition of closed.
- Several parties are working the same findings and need one shared, consistently structured list.
- A return or transaction requires a defensible record of what was found and how each item was resolved.
The problem
A finding without its source document is an opinion, and an opinion cannot be verified, disputed, or defended later. A register without an owner and a due date on each open item turns into a list nobody acts on between reviews. The most common quiet failure is closing items on a status change alone, so a register can read as fully closed while the underlying records still carry the gaps it was meant to drive out.
What gets reviewed
- The fields each entry carries, from the finding to its closure status
- The source document and evidence trace attached to every finding
- A severity scheme that ranks impact rather than treating all items alike
- The closure owner, the due date, and the definition of closed
- The link from each finding to the clause or standard it affects
- The rules that keep the register the single working list
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Every entry names the source document the finding came from
- Each finding carries a severity tied to its actual impact
- Every open item has an owner and a due date
- The closed definition requires evidence, not just a status change
- Each finding links to the clause or standard it touches
Evidence normally required
- The raw findings from the audit, review, or self-inspection
- The source documents each finding was drawn from
- The contract or standard that sets what each finding affects
- The list of parties who will own and close items
Common discrepancies
- Entries with no source document, so a finding cannot be verified or disputed
- A flat list with no severity, so high-impact items get the same attention as trivia
- Open items with no owner that sit untouched between reviews
- Items marked closed with a status change but no closure evidence
- Findings with no link to the clause or standard they affect
What is at stake
A register that lets items close without evidence gives false comfort, and the gap resurfaces at the next audit or in a buyer's diligence with no trail of what was actually done. A flat list with no severity spreads attention evenly, so a high-impact finding competes for time with trivia and can sit while the low-value items get worked.
How the work runs
Define the fields
Decide the fields each entry carries, from the finding and its source through severity, owner, due date, and status.
Bind source to finding
Require every entry to name the source document and trace, so each finding can be verified rather than asserted.
Set severity and ownership
Apply a severity scheme that ranks impact and assign an owner and due date to every open item.
Write the closed rule
Define closed as evidence-backed resolution, not a status change, so the register reflects real records work.
What the buyer receives
- A register schema with the fields and severity scheme defined
- A worked example entry showing finding, source, impact, and owner
- A set of closure rules defining what counts as resolved
Who uses the output
- Records leads running the findings to closure
- Quality teams reporting status against the register
- Counterparties confirming how each finding was resolved
How the work fits into the transaction or program
The register is where the findings from an audit, a return, or a surveillance live until they close. It sits downstream of the review that produced the findings and becomes the shared list every party works the closures from.
Regulatory limits
A register tracks and structures findings. It does not make an airworthiness determination, does not itself close any regulatory obligation, and an item marked closed in the register reflects records work done rather than acceptance by an authority.
What this review does not cover
- Performing the records work that closes the findings
- Setting the contract or standard the findings are measured against
- Any airworthiness determination or regulatory approval
Specific to this review
- A finding without its source document is an unverifiable opinion, so the source field is what makes a register usable rather than just a list.
- Closing an item on a status change alone is the most common way a register quietly fails, which is why the closed definition has to require evidence.
- A severity scheme is what keeps a high-impact finding from competing for attention with trivia, because a flat list treats every item as equally urgent.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
What single field matters most in a discrepancy register?
The source field. A finding tied to the document it came from can be verified, disputed, and defended, while a finding with no source is an opinion. The source is what turns a list into a register a team can actually close items from.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Adapt the checklist to your asset, event, and jurisdiction.