timevolt
Opening soon. Receipts and payments aren't open yet.
Timevolt / Approval of a production change recorded before the deployment, with the approved package fingerprint
IT governance

Change approval log: preserve the existing decision, approved artifact fingerprint and separate deployment record.

Change approval log: preserve the existing decision, approved artifact fingerprint and separate deployment record. Keep your original source records together, then date the exact files. It does not establish who approved, their authority, approval time, successful deployment, matching production bytes, safety or compliance.

Try a file locally

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

EXAMPLE
Approval of a production change recorded before the deployment, with the approved package fingerprint
1 Nov 2026
Authority time: 14:02 UTC · example
Bitcoin block time: 14:10 UTC · example
Last checked: 15:02 UTC · example
✓ Dated◆ Permanent
Now keep it safe: three things
  1. Keep your photos and files unedited. The receipt only matches the originals. Put them in an album such as “My records”.
  2. Save this receipt to your camera roll.

    Keep the receipt file too. The image is a handy copy; checking needs the file.

  3. Email it to yourself.Email it to myself

    Your mail app opens a draft. Attach your receipt image and receipt file. Don’t attach your photos or documents. Timevolt does not send it or know whether it was sent.

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?

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.
      Approval of a production change recorded before the deployment, with the approved package fingerprint
      Approval of a production change recorded before the deployment, with the approved package fingerprint

      01 · Keep the exact files

      Keep the original files for approval of a production change recorded before the deployment, with the approved package fingerprint. Include any existing photos, signed records and source-system exports.

      Records to keep: Ticket approval record plus build artifact hash

      Approval of a production change recorded before the deployment, with the approved package fingerprint

      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.

      Approval of a production change recorded before the deployment, with the approved package fingerprint

      03 · Keep the evidence

      Keep the original files and complete receipt separately, alongside any existing venue, signature and workflow records.

      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 Kingdom; specified banks and Northern Ireland operations · 2014

      Keep complete records of changes and rollback tests

      Banks poorly tested rollback of a changed upgrade, with gaps in change records and risk controls. They settled early. The final notice imposed a fine.

      Summarized on Oct 29, 2026

      Read the source ›
      United Kingdom · 2022

      Record testing decisions and raise their risks

      A bank made a testing decision outside its rules, without recording it or raising the risks. It agreed to resolve the case. A final notice imposed a fine for wider system-move failures.

      Summarized on Oct 29, 2026

      Read the source ›

      Related cases

      United States federal · 2013

      Write down rollout checks and perform them

      Related: Software rollout controls

      A firm missed new code on one server and had no written rule for a second worker to review rollout. It agreed to penalties. It did not admit or deny the findings.

      Summarized on Oct 29, 2026

      Read the source ›

      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.

      Needs something else · United States federal guidance; selected organizational controls

      NIST SP 800-53 Revision 5 CM-3

      Review controlled changes, record decisions, implement approved changes and retain records for an organization-defined period.

      Base PDF includes December 2020 updates; official catalog flags August 2025 release 5.2.0. Selection and implementation remain organization-specific; no receipt approval.

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

      Read the source
      Needs something else · United States federal security-focused configuration guidance

      NIST SP 800-128, updated October 2019

      Archive change vetting by an authorized independent reviewer; procedures distinguish exempt, preapproved and exceptional changes.

      Federal-system guidance with voluntary nonfederal use; actual review, testing and rollout remain separate.

      Source summary as of 2026-10-29. 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.

      • GitHub environment protection rules

        Provides job approvals and configurable self-review prevention.

        Visit site

      • ServiceNow ITSM

        Provides change-management workflow product with risk assessment and approvals.

        Visit site

      • Atlassian Service Collection

        Includes Jira Service Management and configuration assets.

        Visit site

      Related workflows.

      Quarterly user access review: the reviewer list, decisions and removals frozen as submittedAccess or license request, manager approval and grantQuarterly user access review: the list shown to the reviewer, each keep/remove decision and proof removals happenedHuman-in-the-loop approval before an AI agent executes a high-impact action (refund, payment instruction, production change, customer message)Who was physically present at a members' or condo board meetingHuman-made process record

      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 establish who approved, their authority, approval time, successful deployment, matching production bytes, safety or compliance.

      It does not establish who approved, their authority, approval time, successful deployment, matching production bytes, safety or compliance.

      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.

      Does dating an approval file approve the release?

      No. NIST separates documented decisions from implementing approved changes; the receipt only dates the saved file.

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

      Context for this answer
      Must every change use the same approval route?

      NIST's guide distinguishes controlled changes, preapproved or exempt changes and exceptional procedures under organizational policy.

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

      Context for this answer
      Can a developer approve their own deployment?

      GitHub offers a setting preventing the initiating user from reviewing that deployment. Availability and bypass settings depend on the repository and plan.

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

      Context for this answer
      What belongs beside a change decision?

      NIST describes impact analysis, tests, rollback arrangements and checks of the implemented configuration.

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

      Context for this answer
      Is recording a decision enough to manage deployment risk?

      No. The bank notice concerns inadequate testing, change records and wider controls; a file date does not perform those activities.

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

      Context for this answer

      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.