DATA CONTRACT · SCHEMA GUARD · V0.8.0

Turn a good file into a repeatable contract.

Create a baseline from CSV or Excel, define the structure you expect, and catch schema drift, type changes, missing values, uniqueness failures and duplicate keys before the next import.

✓ No signup✓ No file upload✓ Contracts stay local

1. ProfileUnderstand shape & quality 2. CleanTransform and normalize 3. ContractDefine what must stay true 4. Validate & GeneratePrepare the import 5. CompareSource vs target 6. ReconcileReview migration issues

STEP 1 · BASELINE

Start from a known-good dataset

● processed locally

⇧ Drop baseline CSV or Excel Use a file you consider structurally correct CSV · TSV · XLSX · XLS

No baseline loaded.

CSV delimiter

RowMend uses the baseline profile to propose expected types, missing-value thresholds and identifier-like uniqueness rules. You can edit every rule before saving the contract.

Import contract JSON

STEP 2 · CONTRACT

Define what must stay true

All settings remain editable

No contract yet Generate one from a baseline or import a contract JSON file.

Contract name

Minimum rows

Maximum rows

Flag unexpected columns

Key	Column	Expected type	Required	Unique	Max missing %	Max mixed-type %

STEP 3 · CHECK

Run a new dataset against the contract

PASS or REVIEW REQUIRED

⇧ Drop the new dataset Compare it with the active contract CSV · TSV · XLSX · XLS

No candidate loaded.

Contract + candidate required Load or create a contract, then load the dataset you want to verify.

RESULT

Contract check report

Severity	Issue	Column / key	Details

NATURAL PRO PATH

Manual local checks stay useful. Automation is where Pro begins.

Future paid capabilities can add contract version history, scheduled checks, alerts, CI/API execution, shared team contracts and audit trails without removing the local free workflow.

WHY DATA CONTRACTS

Catch drift before downstream systems do.

A recurring file can keep the same filename while changing columns, types, null rates or key quality. A data contract turns those assumptions into explicit checks.

The free RowMend contract is stored locally or exported as JSON. No dataset content is sent to a RowMend backend.

Read the practical guide to CSV schema drift and data contracts →