Skip to content
Litigation.Held together.
Request a demo
← All features

The record

Work the other side can check.

Give opposing counsel, the court or the client work they can check without a BRON account: a fixed version on a signed link, or an export with its manifest.

Availability: Available

Request a demoSee an example ↓
BRONThe recordPublic lookup
Digest lookupNo account needed

Check a file against the digest recorded for it.

sha256:9f2c...41ab

Illustrative digest · abbreviated

RecordedWhen, with the strength of its timestamp proofIn the record
Inspect the supporting record
NamesNo matter, party, title or fileIn the record
Cannot showThat nothing else existsFor review
About this example
Illustration · fictional matterThe names, dates and documents are invented for this example.

In practice

What leaves, and how to check it.

  1. Share the version you mean.

    A signed link opens the version you shared and the documents it cites, never the rest of the matter. A later edit does not change what it serves.

    BRON / Export evidence01

    Shared link

    v1

    The recipient gets the version you shared.

    Shared briefVersion and digest fixed at sharing
    Illustration · fictional matter · Sample export, not a verification result

  2. Let them check each file.

    The manifest lists each file's SHA-256 digest. The recipient checks the files against it without a BRON account, on the verify page or offline.

    BRON / Export evidence02

    Checking an export / no account

    Send the files with their manifest.

    01Document bytes

    Compare each file with the digest in the manifest.

    02Source evidence

    Check the quoted words against the source supplied.

    03Evidence manifest

    Recompute the recorded checks with the offline verifier.

    The check uses only the files supplied.

    A source that was never opened is recorded as advisory. A matching file does not show the work is right.

    Illustration · fictional matter · Sample export, not a verification result

  3. See what was removed.

    A removal is disclosed in the record: who removed what, and why. A gap no disclosure explains still counts against the activity log when it is checked.

    BRON / Export evidence03

    Activity log / disclosed removal

    The log records what was removed.

    1. Recorded entry

      Sequence number and digest kept

    2. Removal disclosed

      Who removed what, and why.

    3. Later entries

      Each is linked to the one before it, so the disclosure cannot be backdated.

    This check covers the files supplied, not the rest of the matter.

    Illustration · fictional matter · Sample export, not a verification result

What this carries into the rest of the matter

  • Each shared version, fixed when it was shared.
  • Approvals, attached to the version they approved.
  • Key acts and disclosed removals, in a log that can be checked for tampering.

One decision in practice

The May 2 email and its attachment, checked against the manifest.

defect-email.emlDigest in the manifest

The recipient checks the file against its digest, with no BRON account.

defect-report.pdfDigest in the manifest

Checked the same way. A file changed after the export will not match.

EXPORT RECEIPT
Timestamp proofPending, then confirmed

The proof over the manifest shows as pending until it is confirmed, usually within about a day.

Your next decision

Decide what the export carries and who receives it. The preview names anything the export cannot include before you download it.

How it works, in detailCheck the sample yourselfSee every feature

Run the sample on our verify page, and see what a match does and does not show.

Request a demo