---
title: "W Fencing: Unified Relational Data Operating System"
author: "Kamilla Gafurzianova"
category: "Relational Data Architecture & Operations"
kicker: "Data Architecture"
headline: "From fragmented spreadsheets to a unified relational data operating system."
summary: "Replacing fragmented spreadsheets with a normalized Airtable database schema, eliminating operational silos and establishing a single source of truth for leadership."
tools:
  - "Airtable"
  - "Relational Schema"
  - "Data Architecture"
  - "Executive Dashboards"
  - "Operations Unification"
  - "Automated Rollups"
metrics:
  - label: "Data Architecture"
    value: "Unified"
    detail: "Single source of truth eliminated fragmented spreadsheets across the academy."
  - label: "Operational Silos"
    value: "Eliminated"
    detail: "Student, billing, schedule, and competition records relationally linked."
  - label: "Schema Model"
    value: "Normalized"
    detail: "Architected with foreign keys, rollup computations, and lookup validation."
  - label: "Revenue Visibility"
    value: "100% Real-Time"
    detail: "Executive dashboards tracking program margins and athlete retention rates."
ogImage: "https://kamillek.com/og/og-case-study-w-fencing.png"
canonicalUrl: "https://kamillek.com/case-study-w-fencing.html"
contact: "https://kamillek.com/contact.html#inquiry-form"
---

# From fragmented spreadsheets to a unified relational data operating system.

Replacing fragmented spreadsheets with a normalized Airtable database schema, eliminating operational silos and establishing a single source of truth for leadership at **W Fencing**.

## The Challenge: Drowning in disconnected spreadsheets and operational blindness.

W Fencing's operational data lived scattered across disconnected spreadsheets, manual attendance trackers, and individual coach folders. Athlete records, class rosters, billing schedules, and tournament results existed in isolated silos with zero relational links between them.

Kamilla designed and implemented a normalized relational database schema in Airtable, connecting students, classes, coaches, billing statuses, and competition results into a centralized operating engine. Leadership gained comprehensive visibility across programs, coach utilization, athlete progression, and program revenue.

> Systems, not spreadsheets. Relational architecture turns operational friction into executive clarity.

## Core Operational Metrics

- **Data Architecture: Unified**
  Single source of truth eliminated fragmented spreadsheets across the academy.
- **Operational Silos: Eliminated**
  Student, billing, schedule, and competition records relationally linked.
- **Schema Model: Normalized**
  Architected with foreign keys, rollup computations, and lookup validation.
- **Revenue Visibility: 100% Real-Time**
  Executive dashboards tracking program margins and athlete retention rates.

## System Architecture & Technical Deliverables

### Unified Airtable Operating System
Engineered a fully normalized relational schema connecting athletes, rosters, coaches, billing schedules, and tournament milestones. Every record cross-references related entities, unlocking cross-functional queries and real-time executive reporting that was previously impossible.

### Student-Program Relational Links
Linked individual student profiles to enrolled class levels, assigned coaches, payment records, and competition results, surfacing the complete athlete development lifecycle in a single dashboard view.

### Automated Executive Reporting Views
Configured tailored filtered views and rollup formulas tracking revenue by program, coach workload distribution, student retention cohorts, and upcoming national competition entries without manual consolidation.

### Data Migration & Governance Runbooks
Cleaned, deduped, and migrated historical club records into the relational structure while authoring standard operating protocols for staff to guarantee perpetual schema integrity and zero duplicate entries.

## Operating Tooling

- **Airtable:** Relational database engine and custom views.
- **Schema Design:** Normalized entity-relationship modeling.
- **Antigravity:** Agentic workflow modeling and data transformation.
- **Data Migration:** Deduplication and automated import scripts.

## System Map: How the data operating system was built.

1. **Data Audit:** Inventoried every spreadsheet, coach logbook, and payment tracker to map all club data entities and dependencies.
2. **Schema Design:** Architected the normalized relational data model: entities, foreign key relationships, field types, and rollup logic.
3. **Build & Link:** Constructed the Airtable base with linked records, lookup fields, rollup formulas, and automated input validation.
4. **Migrate Data:** Sanitized, deduplicated, and imported legacy student records and financial histories into the unified base.
5. **Train & Launch:** Trained administrative staff and coaches on data entry protocols, ensuring lasting schema hygiene and adoption.

## Strategic Leadership Takeaway

Spreadsheets track tasks. Relational systems scale businesses.

Growing sports organizations and boutique academies inevitably hit a data ceiling: as athlete counts and program tiers expand, managing operations through disconnected spreadsheets creates administrative paralysis, billing errors, and customer churn.

At W Fencing, replacing fragmented sheets with a normalized relational database demonstrated how foundational data architecture creates immediate executive leverage. By unifying student histories, billing status, and coaching assignments into a single source of truth, leadership gained the clarity required to scale sustainably.

***

**Author:** Kamilla Gafurzianova
**Direct Contact:** [kamillek.com/contact.html#inquiry-form](https://kamillek.com/contact.html#inquiry-form)
**Portfolio Index:** [https://kamillek.com/work](https://kamillek.com/work)

---

## Omnidirectional Navigation (GLBL-PRTCL-036 §3.4)
* [← Previous Case: Technical Storytelling & Cloud Micro-Animations](case-study-visualizing-serverless-cloud-architecture.md)
* [All 25 Production Case Folios](work.md)
* [Next Case: Workforce Development: SharePoint & Power Automate Pipelines →](case-study-workforce-nonprofit.md)
* [Root Discovery Index](index.md)
