Report export
Use the browser print dialog to export the current analysis and redesign bundle as a PDF-style report.
Airtable Base Doctor
Northstar Agency Ops Demo currently carries 22 deterministic findings and an overall health score of 62. The recommended redesign proposes 20 changes, fully resolves 9 findings, and packages 20 migration steps across 2 phases; 17 steps materially improve generated previews. 5 of 5 report sections are export-ready.
Export intent
This report packages the current deterministic analysis, evidence summaries, redesign recommendation set, and rollout guidance into a single browser-printable artifact.
Health score
62/100
Deterministic findings
22
Recommended changes
20
Report readiness
5/5 sections
Current findings
22 deterministic findings were detected across 4 scoring categories.
Evidence summary
22 finding evidence bundles and 20 proposal evidence bundles are available for the current report.
Recommended redesign
20 changes are grouped into 4 change sets. The recommended path is "Balanced redesign".
Migration guidance
20 migration steps are ordered across 2 phases, with 17 steps affecting generated previews.
AI synthesis
4 root-cause findings, 5 remediation recommendations, and 2 missing-risk suggestions were generated as a secondary synthesis layer.
critical
0
warning
10
suggestion
5
opportunity
7
Schema
60
5 findings
Workflow
61
4 findings
Data
55
6 findings
UX
73
7 findings
Evidence baseline
Evidence summaries stay traceable back to field metrics, table context, and proposal-linked findings so the report remains grounded in the profiled base state.
Top findings
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.
Location: Requests / Category
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.
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.
Large status lists slow down triage, create near-duplicate states, and make dashboards harder to interpret.
Suggested fix
Collapse adjacent statuses into a smaller lifecycle or split planning-only states into a separate field if they truly serve a different purpose.
Location: Projects / Status
Workflow tables without ownership make queues harder to route and make generated workload views incomplete.
Suggested fix
Add an owner or assignee field, ideally as a collaborator or linked People record, so each item has clear accountability.
Location: Requests
Operational work without a target date is hard to prioritize, escalate, or surface in overdue views.
Suggested fix
Add a due date, deadline, or SLA field so time-based reporting and reminders can work consistently.
Location: Approvals
Evidence highlights
Categorical values stored in text fields drift over time, making grouping, filtering, and generated controls inconsistent.
Shared field names that represent different workflows make filters, documentation, and generated UI harder to trust.
Free-text people fields create duplicate spellings, weaken reporting, and make generated assignments or workload views unreliable.
Large status lists slow down triage, create near-duplicate states, and make dashboards harder to interpret.
Recommendation set
Best long-term structure and reuse, but the shared People model increases migration breadth.
Operational tables benefit from automatic timestamps for sorting, recency filters, and audit trails.
Tracking last modification helps identify stale records and powers recency-based views.
Operational tables benefit from automatic timestamps for sorting, recency filters, and audit trails.
Tracking last modification helps identify stale records and powers recency-based views.
Operational tables benefit from automatic timestamps for sorting, recency filters, and audit trails.
Change-set focus
Standardize the operational lifecycle so workflow tables gain timestamps, due dates, and cleaner status values.
Low-friction field additions and lifecycle normalization remove ambiguity before deeper structural changes.
Add explicit ownership fields so work can be assigned and workload views stay reliable.
Operational tables without an owner field are harder to route, review, and summarize consistently.
Replace drift-prone text categories with controlled vocabularies and stronger field types.
Normalization reduces reporting fragmentation and improves generated forms, filters, and dashboards.
Migration guidance
Safe additive changes that introduce new structures without altering existing data.
Moderate-risk changes that rename or convert existing fields. Automations and formulas referencing old names may need updating.
Impact preview
Representative mapping
9 representative records across 4 tables show how the recommended redesign changes field structure and backfill work.
AI synthesis
This agency project-management base has strong foundational structure with clear table roles, but lacks audit trails, uses free-text for people references, and has inconsistent status vocabularies across tables. The highest-impact fix is adding audit timestamps (non-breaking), followed by creating a People table to replace text-based owner fields. These two changes alone would resolve most critical and warning-level findings.
Top remediation ideas
Missing-risk watchlist