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. 5 findings visible.
Structural or workflow friction impacting day-to-day usage.
3 items
Why it matters
Categorical values stored in text fields drift over time, making grouping, filtering, and generated controls inconsistent.
Suggested fix
Convert the field to single select or multi-select and backfill the existing values into a controlled option set.
Why it matters
Shared field names that represent different workflows make filters, documentation, and generated UI harder to trust.
Suggested fix
Rename overloaded fields or align them to a shared lifecycle model so the same label means the same thing everywhere.
Evidence
Why it matters
Free-text people fields create duplicate spellings, weaken reporting, and make generated assignments or workload views unreliable.
Suggested fix
Create a dedicated People table or use collaborator fields, then replace repeated text references with linked records.
Evidence
Targeted cleanups that improve consistency and maintainability.
2 items
Why it matters
Without audit metadata, it is harder to debug stale records, build recency-based views, or explain when work changed.
Suggested fix
Add Created Time plus Last Modified Time fields to operational tables so records can be sorted and monitored reliably.
Evidence
Why it matters
Ambiguous primary fields make linked records, search results, and generated previews less legible for end users.
Suggested fix
Use more descriptive primary field labels or compose them from the entity plus its distinguishing detail.
Evidence