Trust & boundaries
The safety mechanics, in plain English.
BoltScope is built on one idea: a supplier response is only worth sending if you can stand behind it. Here is how the workflow enforces that — and exactly what BoltScope does not claim to be.
How the workflow keeps responses honest
- Source-linked or unsupportedEvery answer in a response pack cites the specific documents behind it — an invoice, a utility bill, a certificate, a policy. If no source document supports an answer, it is marked unsupported and excluded from claims. BoltScope never invents evidence.
- Visible gapsWhen evidence is missing, the pack says so. Gaps become explicit disclosures your buyer can see, not silent omissions. This is deliberate: an honest gap costs you less than an unsupported claim.
- Approved by a person before exportNo pack leaves the workspace on autopilot. A person reviews and signs off every export, and that approval is recorded in the audit trail with who and when.
- Blocked export stateIf any required answer is neither approved nor explicitly disclosed as a gap, the buyer-facing export is withheld. The blocked state is visible in the workspace — you can see it in the demo.
- Audit trailImports, review decisions, approvals and export attempts are recorded as events, so you can reconstruct how a pack was produced.
What BoltScope is not
- Not legal advice
- Not audit assurance
- Not certification
- No guarantee of buyer acceptance
- Not proof of carbon-neutral or net-zero status
- Not automatic sustainability-reporting compliance
BoltScope organises your evidence and keeps your responses within what that evidence supports. It does not audit your business, certify your claims, or promise that any buyer will accept your response. Your team remains responsible for reviewing every pack before it goes out.
See also the disclaimer and security posture pages.