Every issue in this report includes the problem, why it matters, a suggested fix, and supporting evidence where the heuristics have it. Filter by category, then expand the cards that need a closer read.
Drill-down paths
Review structure first
Cross-check table design and linked relationships before applying fixes.
Weighted category scoring shows where the base is structurally solid and where issue volume pulls the overall score down.
Overall score: 62
22
Total findings
Schema quality
5 issues · weight 30%
60
Mixed
Workflow design
4 issues · weight 30%
61
Mixed
Data quality
6 issues · weight 20%
55
Needs work
UX opportunities
7 issues · weight 20%
73
Mixed
Sorted by severity, then category and confidence. 6 findings visible.
Structural or workflow friction impacting day-to-day usage.
3 items
Why it matters
When near-categorical values stay as free text, reports fragment, filters become unreliable, and generated controls cannot trust the underlying options.
Suggested fix
Normalize the current values into a controlled option set or linked taxonomy table, then migrate existing records to the approved labels.
Evidence
Why it matters
High-null operational fields weaken filtering, reporting, and generated UI because important context is missing when records are viewed in bulk.
Suggested fix
Decide whether this field is truly optional. If not, backfill missing values and add defaults, automation, or process guardrails to keep it populated.
Evidence
Why it matters
Repeated free-text names invite spelling drift and prevent dependable workload, ownership, and approval reporting across tables.
Suggested fix
Move team members or approvers into collaborator fields or a dedicated People table, then replace repeated text entries with references.
Evidence
Targeted cleanups that improve consistency and maintainability.
3 items
Why it matters
High-null operational fields weaken filtering, reporting, and generated UI because important context is missing when records are viewed in bulk.
Suggested fix
Decide whether this field is truly optional. If not, backfill missing values and add defaults, automation, or process guardrails to keep it populated.
Evidence
Why it matters
High-null operational fields weaken filtering, reporting, and generated UI because important context is missing when records are viewed in bulk.
Suggested fix
Decide whether this field is truly optional. If not, backfill missing values and add defaults, automation, or process guardrails to keep it populated.
Evidence
Why it matters
High-null operational fields weaken filtering, reporting, and generated UI because important context is missing when records are viewed in bulk.
Suggested fix
Decide whether this field is truly optional. If not, backfill missing values and add defaults, automation, or process guardrails to keep it populated.
Evidence