Document change review
Compare specifications, procedures, datasheets, and contract appendices structurally. SpecTrace separates meaningful edits from reformatting, links every finding to the page it came from, and keeps a reviewable record of each decision you make.
Documents are processed on Motifuse servers, held in a private quarantine, and scanned for malware before anything reads them. The comparison is deterministic — no language model sees your files.
A pump datasheet compared across two revisions
Confidence shown per findingCSV & JSON export7
Document types read
PDF, DOCX, XLSX, CSV, plain text, plus PNG and JPEG images of scanned pages.
10
Project templates
Supplier specification change, SOP revision, tender requirement update, and 7 more.
4
Change types compared as values
Text, numbers, units, and dates — not just as strings that happen to differ.
2
Export formats, on every plan
CSV and structured JSON, with versions, fingerprints, coverage, and method limits attached.
The real product, on this page
This is the SpecTrace workspace. Create a project, upload a baseline and a revision, and work through the findings — the free tier is a working tool, not a preview.
Server-side processing
Files are uploaded, quarantined, and malware-scanned before anything reads them. Guest work stays in this browser and is deleted after 7 days.
Scanned documents and photographs need text recognition, which is a Pro capability. Recognition quality varies with the scan, so findings that depend on it are marked with lower confidence and shown alongside the region they came from.
From two files to a decision
SpecTrace is built around the judgement that follows a comparison, not the comparison itself. Each step leaves something behind — which is what turns a read-through into a record.
Step 1
Start from a project template — supplier specification change, SOP revision, tender requirement update, contract appendix, and more — or set it up yourself, with your reference numbers, tags, priority, and confidentiality level.
A project with your context attached
Step 2
Upload the baseline you already accepted and the revision you have been sent. Earlier versions are kept, never overwritten, so you can look back at how a document reached its current state.
A version history, not an overwrite
Step 3
SpecTrace compares the documents structurally rather than line by line, so a moved paragraph reads as a move and a reformatted table does not fill your review with noise. Numbers, units, dates, and amounts are compared as values.
Meaningful changes, separated from noise
Step 4
Work through the findings one at a time: confirm a change, reject it as formatting noise, adjust how important it is, write down what it means, and record what you are going to do about it.
A decision against every finding
Step 5
Download the findings and your decisions as CSV or structured JSON. Each export identifies the project, source versions, analysis date, document fingerprints, coverage summary, and the limitations of the method.
A review record you can hand over
See it work
The three screens a review passes through. Note what the first one shows: a low-confidence finding and thirteen formatting-only changes, both labelled — because a preview of five clean hits would misrepresent how documents actually read.
SpecTrace compares the two versions structurally, so a moved paragraph reads as a move and a restyled table does not fill your review with noise. Numbers, units, dates, and amounts are compared as values — and what it is unsure about is labelled as unsure.
Open any finding and the baseline wording, the revised wording, the page or section reference, and the detected value change stay together — so you verify the result before you decide, rather than trusting a badge.
Confirm, dismiss, re-rate, and annotate each finding. What you end up with is a record of decisions — exportable as CSV or structured JSON, with the source versions, fingerprints, coverage, and method limits attached.
Why not a file diff
Comparison tools are not scarce. These are the six things that stop being your problem once findings carry their evidence and your decisions stay attached to them.
A supplier sends Rev C and says 'minor updates'. Finding the one clause that moved a pressure rating means reading forty pages twice. SpecTrace surfaces the differences and tells you which ones carry a value change.
Structural comparison, not line-by-line
A generic file-diff reports every difference, including the thousands caused by a new template. SpecTrace separates formatting-only changes so what remains is the handful that need your judgement.
Noise counted, then set aside
Every finding keeps the baseline wording, the revised wording, the page or section reference, and the detected value change together. You confirm what the tool found instead of trusting it.
Source-linked evidence on every finding
A clean text PDF extracts reliably; a poor scan does not. SpecTrace records a confidence level per finding and marks the doubtful ones prominently rather than presenting them as fact.
Confidence recorded per finding
Six months later, nobody can say why Rev C was accepted. The decisions, the notes, and the follow-up actions stay attached to the comparison that produced them.
Decisions kept with their evidence
Findings and decisions export to CSV or structured JSON on both Free and Pro, with the source versions, fingerprints, coverage, and method limits attached to the file.
CSV and JSON on every plan
Documents it reads
PDF, Word, Excel, CSV, and plain text, plus PNG and JPEG images of scanned pages. Spreadsheet comparisons keep sheet and cell references; PDF and Word findings keep page and section references, so a finding always points back at something you can open.
Scanned documents and photographs need text recognition, which is a Pro capability. Recognition quality varies with the scan — so findings that depend on it are marked with lower confidence and shown alongside the region they came from, for you to confirm before accepting.
Page and section references kept on every finding.
Structural comparison; a moved paragraph reads as a move.
Sheet and cell references preserved in the findings.
Compared as content, not as a byte stream.
Text recognition on Pro; findings marked with lower confidence.
Numbers, units, dates, and amounts compared as what they mean.
Who it is for
SpecTrace is built for an individual reviewer, not a review committee — every project belongs to your account alone. These are the six roles the workflow was designed against.
The situation. A datasheet arrives at Rev C with 'minor clarifications', forty pages long, and a delivery decision waiting on it.
What they get. The pressure rating, material grade, and delivery window changes surfaced with their page references, and a note against each one recording what has to happen before acceptance.
The situation. An issuing authority republishes a tender document days before submission, with no change log.
What they get. A list of what actually moved between issues, separated from the restyling, so the bid team reworks the three sections that changed rather than re-reading the whole pack.
The situation. An SOP is revised and every controlled copy has to be reconciled against the previous approved version.
What they get. A structured comparison with the changed steps identified, a decision recorded against each, and an export that states the source versions and document fingerprints.
The situation. Counsel returns a marked-up appendix, and the redline does not survive the round trip through three file formats.
What they get. A comparison that reads the documents as they are, with amounts, dates, and clause text compared as values, and the wording on both sides kept side by side.
The situation. A standard or internal procedure is updated and the affected requirements have to be identified and signed off.
What they get. Findings ranked by significance, the low-confidence ones flagged for manual checking, and a record of what was reviewed and by when.
The situation. Client documents arrive in whatever state their systems produced, and the engagement is judged on the report you hand back.
What they get. A repeatable review method, a written record of every decision, and an export identifying the versions compared and the limits of what the method could read.
How we build it
SpecTrace is processed on our servers, and this page says so rather than borrowing the privacy language of products that run in a browser. Here is exactly what that means.
Not in your browser — and we say so
Files are uploaded, held in a private quarantine, checked for malware before anything reads them, and stored privately against your account. Describing this as browser-local processing would be untrue, so we do not.
Deleted when you delete the project
Files are retained for the period your plan allows. Work started without an account stays in that browser and is deleted after 7 days. Deleting a project deletes its files.
Free and Pro
The complete comparison and review workflow — three projects, five comparisons a month, findings review, notes, and CSV and JSON export — costs nothing. Pro raises the ceilings and adds text recognition for scanned pages.
Compare documents and review findings on your own, with modest limits.
For professionals who review specification and contract changes regularly.
₹199/ month
A requirements-led rollout for organisations that need SpecTrace beyond an individual account.
Pricing on request
Not available for self-service. Requirements are reviewed individually.
Tell us how your organisation reviews documents. We will scope security, retention, rollout, and workflow requirements with you; Enterprise is not an off-the-shelf self-service plan.
What it does not do
A tool used on specifications and contracts has to be honest about its edges. These are ours, in the same place as the capabilities — not in a footnote.
Proof, not adjectives
SpecTrace is new, and a page of five-star quotes would tell you nothing about whether it can read your datasheet. Here is what the claims above rest on, and where each one can be verified.
The plan cards below render each capability's state from the database as words — Included, Planned, or Not included — so nothing on this page can quietly imply a feature that does not exist yet.
Compare every planExtraction improvements, new document types, and limit changes are recorded as they land — including the corrections.
Read the changelogWhere files go, how they are scanned, how long they are kept, and what deleting a project actually deletes.
Review security & privacyWe publish no accuracy percentage, no customer count, and no testimonial we cannot attribute — a figure measured on our test documents would say nothing useful about yours. When there are real quotes, they will appear here with a name against them.
Questions
Where files go, how reliable extraction is, what the free tier includes, and what happens to your data afterwards.
Reviewing documents as an organisation?
Shared review is not in this version. Tell us how your process works and we will be straight about whether SpecTrace fits it today.
Works well with
Three products, one workspace, one account — data quality, document production, and change review.
Profile, clean, validate, and deduplicate business data in a private browser workspace — free, with no upload.
Open ReconovaDesign a document template once and generate a personalised PDF for every row of a spreadsheet.
Open DocForgeA free side-by-side text difference viewer for the quick checks that do not need a project.
Open the free toolStart with the revision on your desk
Three projects and five comparisons a month, free, with no account required to try it. Every finding keeps its evidence, and every decision you record comes back out as CSV or JSON.