The client says that was never in the deliverable.
Scope disputes are about what was agreed and what was delivered. By the time one starts, both files have been edited ten times.
A payment dispute is the same argument with an invoice attached.
WITHOUT A RECORD
It is your sent folder against their memory.
WHAT YOU DO
STEP 1
Seal the scope when it is agreed
The signed proposal or statement of work, as it stood that day. Seal a document.
STEP 2
Seal the deliverable at handover
The report, the designs, the code archive. One seal can cover several files.
STEP 3
Put the seal link on the invoice
The client can check their copy against it at any time, with no account. Check a file.
STEP 4
Seal revisions as versions
Each one names the one before, so the history reads in order.
WHAT YOU GET
FREE
The seal and its page
Your declaration and the fingerprints of your files, on a hash-chained record that an outside authority timestamps each night. Free at the desk for a person. The Seal.
FREE
The check
Anyone holding a copy drops it on the check page. It is the sealed file or it is not. No account. Check a file.
PAID · AUD 49 a pack
The Seal Evidence Pack
One document from the seal’s record for a client or a dispute: the declaration, the hashes, the dates and the chain, frozen and recomputed every time it is opened. See it on the pricing page.
WHAT IT WILL NOT DO
- A seal shows the file existed by the date it was recorded and has not changed since. It does not show the client received it or accepted it.
- Not a contract and not a signature.
- APIR never holds your files. Keep them: a seal can only be checked against the file itself.
Start with the free step.
No card and no call. Every price is on the pricing page, and what APIR holds and does not hold is on the trust page.
NOT QUITE YOU?See every door