See what changed before you trust the next delivery

A 71-second walkthrough of the RowMend workflow: establish a known-good baseline, load a changed recurring CSV delivery and use Run Insights to see the drift.

What the video shows

1. Create the preconfigured monthly vendor import demo.
2. Run a known-good delivery and establish a PASS baseline.
3. Load the next delivery with intentional drift.
4. Stop the workflow before unsafe output.
5. Compare the two runs with Run Insights.
6. Review row-count, completeness, duplicate and contract changes.
7. Keep privacy-minimized local history without storing source rows.

Video transcript

Recurring files change. See what changed before you trust the next delivery.

Create the demo project. Run the known-good delivery. Baseline established: PASS. Load the next delivery. The workflow stops before unsafe output. Run Insights compares the two deliveries. See exactly what changed. Keep lightweight local history. Your source file is not your run history. Run the next file. Know what changed.

For the underlying comparison model, continue with How to detect data drift in recurring CSV files.