Opening soon. Receipts and payments aren't open yet.
interface control document template

Keep the version and units behind the hand-off.

Interface control document template — Keep the version and units behind the hand-off. Use the free interface worksheet to record the document or data item, its stated units and the hand-off copy.

Your photos and files stay on your device, so keep them.

Your free interface control worksheet.

Keep the original source records alongside this supplementary worksheet.

  • Specification / data item
  • Stated units
  • Partner hand-off copy reference

Check your regulator's own form. The printable version lists the source behind every field. CSV versions have an instruction row above the headings.

Then date your filled-in copy.

Keep the completed copy and its source records. A time receipt dates those exact bytes; it does not establish that an entry is true or accepted. Save a new copy after each version or hand-off.

Your record, one step at a time.

Your photos and files stay on your device, so keep them.

Local preview: files are fingerprinted here. Notes and progress stay in this browser. Keep downloaded copies; browser storage is not a backup.

0 items
How?

Use the worksheet alongside the original records; use an official form where required.

Fill in

By making a receipt you agree to the Terms and Privacy Policy. The Bitcoin record is permanent.

Printable version

    0 items
    How?

    Add the exact original files for this part of the record. Keep them unchanged; a different export or edit has a different fingerprint.

    Add link and screenshots

    The link is recorded, not fetched or verified.

      0 items
      How?

      Record the date, time, place and who you spoke to. New notes are saved separately rather than editing an old note.

      How to keep notes that hold up
      Write it down

      By making a receipt you agree to the Terms and Privacy Policy. The Bitcoin record is permanent.

        By making a receipt you agree to the Terms and Privacy Policy. The Bitcoin record is permanent.

        How to keep notes that hold up

        Write notes as soon as you can. Keep the original account rather than replacing it later; the venue decides what weight it gets.

        1. Write it down straight away, on paper or in the box on a step.
        2. Put the date, time and place at the top, and who you spoke to.
        3. Use their words where you can; separate what you saw from what you were told.
        4. Sign or initial a paper note, photograph it and add the photo.
        5. Never edit an old note. Add a new dated entry when something changes. A device save time is not independent time evidence or proof of event order.
        Interface spec with units at hand-off

        01 · Keep the exact files

        Use the free interface worksheet to record the document or data item, its stated units and the hand-off copy.

        Records to keep: The interface control document or data file (with its stated units) as handed to the partner team

        Interface spec with units at hand-off

        02 · Date the file’s code

        Your device fingerprints the selected file or manifest. Dated follows an independent timestamp; Permanent follows Bitcoin anchoring.

        An independent time, tied to the exact bytes.

        Interface spec with units at hand-off

        03 · Keep the evidence

        Keep the exact specification, partner acknowledgment and any later version separately.

        Keep the originals too. A changed or compressed copy has a different fingerprint.

        Try a file. It stays here.

        Make a test receipt on this device.

        By making a receipt you agree to the Terms and Privacy Policy. The Bitcoin record is permanent.

        or drop a file here

        Real cases: why the saved copy matters.

        Real cases where dated records mattered. We don’t claim a time receipt would have changed the result.

        United States · 1999

        Match the data units to the specification

        A spacecraft team's software sent thrust data in units that did not match the written specification. The mismatch helped cause the loss of the orbiter. The inquiry found wider failures in team checks, rather than blaming one party.

        NASA investigation report; supplied verification could open the PDF but could not extract its text.

        Summarized on Oct 29, 2026

        Read the report ›
        United States · 1992

        A technical attachment may leave contract gaps

        A satellite buyer and launch firm disputed whether a technical attachment limited the buyer to a replacement launch. The court found no clear answer there or in the contract. It reopened some claims without choosing a final winner.

        Summarized on Oct 29, 2026

        Read the decision ›

        Related cases

        What courts, schemes and regulators say.

        Positions below refer to the cited rule or record type, not endorsement of Timevolt. This service is not represented as an eIDAS qualified timestamp provider. A non-qualified timestamp does not receive the qualified timestamp presumption.

        Accepts · United States (federal courts)

        Federal Rules of Evidence 902(14)

        Data copied from an electronic device, storage medium, or file is self-authenticating if authenticated by a process of digital identification (hash value), shown by a qualified person's certification.

        Supports hash-based identification of a file copy; a timestamp is an extra layer and still needs a custodian or expert to explain it.

        Source summary as of 2026-10-28. Check the current source and applicable local rules.

        Read the source
        Accepts · United States (federal courts)

        Federal Rules of Evidence 902(13)

        A record generated by an electronic process or system that produces an accurate result can be self-authenticating with a certification.

        May fit a receipt produced by a timestamp process; the certification step is for the proponent.

        Source summary as of 2026-10-28. Check the current source and applicable local rules.

        Read the source
        Accepts · United Kingdom (retained EU law); same text in the EU original

        eIDAS Regulation 910/2014, Article 41, as retained in UK law (legislation.gov.uk)

        Electronic or nonqualified form alone is not a reason to deny a timestamp legal effect or admissibility. Other evidence requirements still apply. Article 41(2) addresses the qualified-timestamp presumption, and Article 42 its requirements; provider status alone is insufficient.

        This describes the statutory evidence rule, not Timevolt qualification or a guarantee of admission. No claim about cross-border recognition is made here.

        Source summary as of 2026-10-28. Check the current source and applicable local rules.

        Read the source

        Other ways to do this

        Prices change. Check each provider’s site for current prices and service details.

        • Git or version control tags plus signed commits

          Provides shows version history inside your own repo.

          Visit site
        • Requirements tools such as Jama Connect or IBM DOORS

          Provides baselines and change history inside the tool.

          Visit site
        • DocuSign or other e-signature

          Collects signatures and records the signing workflow.

          Visit site
        • Free RFC 3161 timestamp tools (openssl ts plus a public authority)

          Requests RFC 3161 timestamp tokens through local tools.

          Visit site

        Proves / Doesn’t prove

        Proves

        A completed time receipt shows that the exact selected file existed by the independently witnessed time. You can check whether a later copy has the same bytes. It does not establish creation time, authorship, identity, event order, location or the truth of the contents.

        Doesn’t prove

        It does not prove who wrote the spec, that the stated units were correct, that the partner team received or read it, or who is responsible if the two sides used different units.

        A timestamp cannot establish correct units, a correct specification, receipt by the partner or technical safety.

        These are the bounds of a completed proof. The local tester does not establish any time. The chosen court, scheme or regulator decides what to accept.

        Questions, answered plainly.

        Your file stays on your device. During normal receipt creation, your device sends a randomized code made from its fingerprint, plus encrypted recovery data. It doesn't send the plain fingerprint or the random value that opens the code. Keep the original file and the complete receipt for checking. Privacy Policy.

        What should an interface control document state about units?

        For every field or value: the unit, the reference frame or convention, precision, allowed range, and the document version. The Mars Climate Orbiter board found a spec that required newton-seconds while delivered data was in pound-force seconds.

        Source summary as of October 30, 2026. Check the current source and its scope.

        Context for this answer
        How do I prove which version of the spec I sent?

        Keep the exact file and a time receipt for it. If any byte changes, the fingerprint no longer matches, so the receipt ties to that file only. Also keep the sent message or sign-off.

        Source summary as of October 30, 2026. Check the current source and its scope.

        Context for this answer
        Does a time receipt prove my units were right?

        A completed time receipt shows that the exact selected file existed by the independently witnessed time. You can check whether a later copy has the same bytes. It does not establish creation time, authorship, identity, event order, location or the truth of the contents.

        Does the partner team have to be involved?

        No. You fingerprint on your own device and share the receipt and file afterward. Their written acknowledgment, if you can get one, adds a separate record of receipt.

        Is my spec uploaded anywhere?

        Your file stays on your device. During normal receipt creation, your device sends a randomized code made from its fingerprint, plus encrypted recovery data. It doesn't send the plain fingerprint or the random value that opens the code. Keep the original file and the complete receipt for checking.

        Is a timestamp accepted as evidence?

        Electronic or nonqualified form alone is not a reason to deny a timestamp legal effect or admissibility. Other evidence requirements still apply. Article 41(2) addresses the qualified-timestamp presumption, and Article 42 its requirements; provider status alone is insufficient.

        Source summary as of October 30, 2026. Check the current source and its scope.

        Context for this answer
        What happened in the Gimli Glider case with units?

        A fuel density in pounds per litre was used as kilograms per litre, so the Boeing 767 loaded under half the fuel needed and glided to a landing after running out.

        Source summary as of October 30, 2026. Check the current source and its scope.

        Context for this answer
        Should I re-stamp when the spec changes?

        Yes. Each revision is a different file with a different fingerprint, so stamp each issued version and record the version number on it.

        The file tester runs on your device. It does not issue a timestamp or take a payment.

        Keep the records you already have.

        Keep your original files and any existing official records while the receipt service is being prepared.