All tools

Four rows is not a complete handover

Compare your expected cable or port schedule with the evidence that came back. See exactly what is missing, duplicated, conflicting or still unknown.

The result, on the sample

This is the finished result, made on this page from the sample file below. It is not a picture of one.

1 identifiers have matching recorded evidence; 2 are missing evidence

  • 4 expected rows; 4 observed rows. Equal row counts do not prove completeness.
  • 1 duplicate findings; 0 conflicting findings; 1 unexpected records; 0 unknown findings.
  • Evidence present does not mean the cable passed. PASS/FAIL below is copied from the original export, not our certification or engineering sign-off.
  • Identifiers match exactly. No case, punctuation, whitespace, date, revision or unit guessing is applied.
  • Supports UTF-8 CSV files only (comma-delimited, RFC 4180-ish quoting; BOM, CRLF/LF, and quoted embedded newlines are handled). Both the expected cable/port schedule and the observed test-result export must be CSV with a header row; column names are mapped to canonical fields by explicit customer confirmation, never inferred. Proprietary vendor export formats (PDF, XLSX, device-specific binary logs) are NOT supported in this build. Recorded test-time values must be an ISO-8601 date-time with an explicit UTC offset to be treated as unambiguous; anything else (bare date, offset-less date-time, slash-separated date) is reported as an unknown finding rather than guessed. Identifier grouping defaults to exact byte-identical matching (case and punctuation preserved); a customer may instead select one of the named normalization rules listed here, and any collision it introduces is always surfaced on the finding, never merged silently.
  • Expected SHA-256: 2530766f5d7c830365d115e7320c864cbf894dda4d4d602a20a5e5aa3aebdb56. Observed SHA-256: 29a403a6839251238ddf57a58139be9623cfa19327fa23d5b82172dd78dcce4d.

Expected versus recorded evidence

IdentifierEvidence statusExpected sourceObserved sourceResult recorded by sourceRecorded timeReason / limitationEvidence version
Aevidence_presentexpected data row 1observed:row 1PASS2026-09-01T10:00:00Z661b2fc6d7e477a5
Bduplicate_identifierexpected data row 2observed:row 2; observed:row 3PASS | FAIL2026-09-01T10:01:00Z | 2026-09-01T10:02:00Zidentifier appears 2 times in the observed export5b7e8f77a5330250 | 841f834d48452bc9
Cmissing_evidenceexpected data row 3no observed record matches this expected identifier
Dmissing_evidenceexpected data row 4no observed record matches this expected identifier
Eunexpected_recordobserved:row 4PASS2026-09-01T10:03:00Zobserved identifier is not present on the expected scheduleac596214b0635d56
The sample it came from — Expected A/B/C/D versus observed A/B/B/E

expected.csv — The expected cable or port schedule

identifier,revision,evidence_class
A,R1,copper-link
B,R1,copper-link
C,R1,copper-link
D,R1,copper-link

observed.csv — The recorded test evidence

identifier,test_time,recorded_result,revision
A,2026-09-01T10:00:00Z,PASS,R1
B,2026-09-01T10:01:00Z,PASS,R1
B,2026-09-01T10:02:00Z,FAIL,R1
E,2026-09-01T10:03:00Z,PASS,R1

Sample data.

Run it on your own file

Pick a file and it runs here, in this page.

Your files remain in this browser. Nothing is uploaded, and closing the tab discards the working data. Downloads you explicitly save remain on your device.

The expected cable or port schedule (expected.csv)
Paste cells instead

Choose a CSV or paste spreadsheet cells. Nothing is uploaded.

The recorded test evidence (observed.csv)
Paste cells instead

Choose a CSV or paste spreadsheet cells. Nothing is uploaded.

Running your own file needs scripting turned on. The result above, and every word on this page, do not.

What it does

  • Separates matching evidence, missing identifiers, duplicates and unexpected records.

    It will not Equal row counts never establish complete coverage.

  • Keeps the original recorded result and evidence version visible.

    It will not This is evidence reconciliation, not cable certification or engineering sign-off.

What it will and will not do

  • Two CSV files or explicitly tab-separated spreadsheet rows, each with headers
  • Up to 5,000 rows and 2 MB per input.
  • Exact identifier matching only, without case or punctuation normalization.
  • Provide schedule revision and evidence class; timestamps without an explicit offset remain unknown.
  • Documented CSV exports only. Proprietary PDFs and tester formats need a separately supported adapter.

Your version

Three questions about the work, not about you. All optional, and there is no account.

If you want us to do it

$249.00 version 2026-09-18

A whole handover pack, reconciled on our server and returned as a findings file you download, plus a configuration you keep and can run again. Priced as a guess; nobody has bought it.

A price we have guessed at. Nobody has bought this, and the version is on the record.

The paid version runs on our server, not in this page: you send both the expected schedule and the observed evidence, we return every finding as a file you download, and a configuration file that runs the same job again next time.

Run it on the whole handover pack, on our server