Health score, table summary, and top recommendations for the seeded base.
This overview combines the full heuristic pass with a structural snapshot, surfacing where the model is solid and where fixes would improve operations.
62
Needs attention
The model is workable, but the analysis found several points of friction.
0
Critical
10
Warnings
5
Suggestions
7
Opportunities
Schema
60
5 issues detected
Workflow
61
4 issues detected
Data
55
6 issues detected
UX
73
7 issues detected
High-level scan of each table before drilling into schema details.
Client contacts and account segmentation for the agency.
6 records · 5 fields
Name
Primary · Text-heavy
0
Linked fields
2
Select fields
Active and historical delivery work tied to each client.
7 records · 8 fields
Name
Primary · Text-heavy
1
Linked fields
2
Select fields
Operational task tracking for project work.
8 records · 6 fields
Title
Primary · Text-heavy
1
Linked fields
1
Select fields
Incoming client asks before they become scoped project work.
6 records · 7 fields
Title
Primary · Text-heavy
1
Linked fields
1
Select fields
Client-facing approval history for key deliverables.
5 records · 6 fields
Deliverable
Primary · Text-heavy
1
Linked fields
1
Select fields
Highest-signal fixes, sorted by severity and confidence.
Categorical values stored in text fields drift over time, making grouping, filtering, and generated controls inconsistent.
Fix
Convert the field to single select or multi-select and backfill the existing values into a controlled option set.
Requests / Category · 87% confidence
Shared field names that represent different workflows make filters, documentation, and generated UI harder to trust.
Fix
Rename overloaded fields or align them to a shared lifecycle model so the same label means the same thing everywhere.
Base-wide · 81% confidence
Free-text people fields create duplicate spellings, weaken reporting, and make generated assignments or workload views unreliable.
Fix
Create a dedicated People table or use collaborator fields, then replace repeated text references with linked records.
Base-wide · 79% confidence
Large status lists slow down triage, create near-duplicate states, and make dashboards harder to interpret.
Fix
Collapse adjacent statuses into a smaller lifecycle or split planning-only states into a separate field if they truly serve a different purpose.
Projects / Status · 93% confidence