Data Contracts for Small Teams and Startups: Start With One File
Most writing about data contracts assumes a large company: producers and consumers in different teams, a platform, a governance group. A startup has none of that, and still gets bitten by the same problem: someone changes a column and a report quietly breaks. This guide shows how a small team gets the benefit of a contract with one file, one page of rules and a free tool.
Open the Data Contract Generator
What a small team actually needs
The core of a data contract is a written, checkable promise about a dataset. A small team needs three things: write it down, check it automatically or by hand, and know who to tell when it changes. Everything else can wait.
Start with the one file that hurts
Do not write contracts for everything. Pick the single file or table that has already caused trouble: the export your finance report depends on, the customer list a partner sends you, or the table behind the dashboard your founder checks every morning.
Step 1: generate, do not write from scratch
Load a good sample in the Data Contract tool. It profiles the file and suggests the rules: column types, which columns are never empty, which values are unique. You review and keep the ones you agree with. That takes minutes, and you end up with a YAML file in the standard ODCS format.
Step 2: keep only rules you can defend
A rule you cannot explain will fail a good file one day, and then people will stop trusting the contract. Start with types, required columns, a minimum row count and a unique key. Leave out ranges and lists until you know the real limits. See the rules explained.
Step 3: put the file in the repository
Save the YAML next to the code or the SQL that produces the data. It now has a history, and a change to it appears in a pull request where the people affected can see it.
Step 4: check it at the points that matter
- **Files you receive:** validate each one before using it. See validating a vendor CSV.
- **Tables you build:** if you use dbt, save the same rules as a `schema.yml` and let your normal runs check them. See from data contract to dbt tests.
Step 5: agree who to tell
A contract works only if the person who changes the data tells the people who use it. In a small team this is a message in a shared channel, or a pull request that must be approved by the person who owns the report. Write the owner's name in the contract or in the repository's readme.
What to skip for now
- A data catalogue, a governance process or a contract platform. They solve problems a small team does not have yet.
- Contracts for every table. Start with one, learn what breaks, then add the next.
- Strict rules everywhere. A short contract that is always right beats a long one that is sometimes wrong.
Limits of this approach
The free tool checks a file when you open it. It does not watch your data or alert you. It does not enforce the contract on the producer. The value is in the written agreement and the check; the enforcement is people and pipeline discipline. When you outgrow it, the contract is plain ODCS YAML, so it moves to a larger tool.
A good first week
- Day 1: pick the file that hurts and generate a contract.
- Day 2: remove the rules you cannot defend and test it on two older files.
- Day 3: commit it and tell the owner of the report.
- Day 4 onwards: validate each new delivery, and update the contract when the data legitimately changes.
Open the Data Contract Generator
Related tool pages
- ODCS Data Contract Generator: Generate an Open Data Contract Standard (ODCS) v3 YAML file from a CSV, Excel, JSON or Parquet file. Edit the rules, then download. Free, in your browser.
- Validate a CSV Against a Schema: Check a CSV or Excel file against a data contract: required values, types, unique columns, allowed values, ranges, patterns and missing or extra columns. Free, in your browser.
Also try
How to use the Data Contract Generator: step by step
- Pick the one file that has caused trouble.
- Generate a contract and keep the rules you can defend.
- Commit the YAML.
- Validate each new file and update the contract on real changes.
When to use the Data Contract Generator
- Getting started with data contracts without a platform
- Protecting one important report or partner file
- Writing the agreement down
Example
Input: orders.csv: order_id, status, unit_price
Output: kind: DataContract schema: - name: orders properties: - name: order_id logicalType: integer required: true unique: true
Frequently asked questions
Do small teams need data contracts?
They benefit from the idea, not from a platform. A written, checkable promise about the one dataset that has caused trouble is enough to start.
How do I start with data contracts?
Pick one file, generate a contract from a good sample, keep the rules you can defend, commit the YAML and validate each new file against it.
Do I need a data contract platform?
Not to start. The contract is a plain YAML file in the ODCS standard, which larger tools can read later.
Is there a free tool?
Yes. The Data Contract tool is free, needs no sign-up and runs in your browser.
Tip: Name one owner for each contract. A contract nobody owns goes out of date in a month.