Versions, in detail
A detail can be rejected three times before it's signed, and the old drawing keeps circulating. Here every upload of a document is a new version with its history kept, an approval is pinned to the version that was signed, and when revision C replaces revision B the sign-off on B stays exactly as it was.
Upload the revised file against the same document and it becomes current. The panel lists every version, who uploaded it and when, and the version badge on the row and in the header says which you are looking at.
A sign-off is pinned to the version that was signed. The record names the file and the version, carries that file inside, and prints its fingerprint, so the wrong revision can't be argued in later.
When the argument needs it, the earlier version is one click away in the panel, and the activity trail says who uploaded what and when.
The file name, the version they signed and whether it's still the current one, and the SHA-256 fingerprint of the exact bytes they saw. The original file is embedded in the record, so if the drawing on the server changes later, the record still holds the one that was signed and proves it.
See a real record, annotated →
Upload a new version, send it for sign-off, and one press compares it with the one they saw before. The reading names the old version by what they did with it, the version you rejected on the 7th, and says what moved. The client gets the same reading on their link, so the question "what's different?" is answered before it's asked.
A credit a press, from the monthly bundle every plan includes. AI can make mistakes: check it against the files before you act on it.
Versions are kept on every plan. Storage is what the plans are cut on; the limits are on the pricing page.
Set up in minutes and send a drawing for sign-off before lunch. Free for 14 days, no card, cancel any time.
