Product tour · about 3 minutes
See how DataStruct checks a supplier’s evidence
Follow one review from upload to report: a buyer checking Halvern Precision Components against six requirements. Every screen comes from the DataStruct app.
Sample data: Halvern Precision Components and Northbridge Engineering are fictional companies.
Step 1 of 9
Drop in the supplier’s pack
Certificates, policies, registers and questionnaires, in PDF, Word or Excel, including scanned pages. Each file is read and indexed as it arrives.
- Drag in a whole pack at once.
- Each file is marked Completed once it’s read and ready to search.
Ask in plain English. See the source.
Ask what you would ask a colleague. The answer comes from the supplier’s documents, with the text it relied on shown under each claim.
- The answer: valid until 2 June 2028, with design excluded from the scope.
- The words from the certificate itself, so you can check them in seconds.
Down to the spreadsheet row
Registers and logs are read row by row. Ask which gauges are overdue and the answer cites the rows that say so.
- HG-31 and TW-11, with their due dates.
- The register rows behind the answer.
When the evidence isn’t there, it says so
The supplier’s questionnaire says yes to a business continuity plan, with nothing attached. DataStruct reports that as the supplier’s claim and tells you no document evidences it.
- “No document evidencing this was located.”
- The questionnaire is listed as cited, not confirmed. A supplier’s own answer is shown as a claim, not as evidence.
Check every requirement in one run
Write your requirements in your own words and run them together. Each one comes back as a finding with its evidence, and every run is kept in history.
- Add requirements the way you’d write them.
- Run them all at once; results arrive in the background.
- Evidence located, with the source document.
- Export to Word, Excel, CSV or JSON.
Gaps are named, not glossed over
Asked to show that no measuring equipment is overdue, DataStruct finds the calibration policy and the two overdue items, and names the gap instead of passing the requirement.
- HG-31 and TW-11 are overdue.
- Cited to the calibration register’s rows.
A claim is not evidence
There is no Cyber Essentials certificate in the pack, only the supplier’s yes. The finding says exactly that, so nobody signs off on a claim.
- Cited — not confirmed.
- Evidence located: none confirmed.
You decide, on the record
DataStruct prepares the evidence; a person makes every call. Confirm, reject or flag each finding for follow-up, and every decision carries a name and a time.
- Reviewed and confirmed.
- Who decided, and when.
A report for your file
Export the run as a report with every requirement, what was found, where it came from and who decided. It states plainly that it is not a certificate of compliance.
- Clear about what the report is, and what it isn’t.
- Review status and evidence, summarised for every requirement.