Proof (PDF + protocol) explained
Many people “have a PDF”. The real pain often comes later: which project does it belong to, which version applies, is it actually closed? LegitForm deliberately separates interim state (“received”) from closure (“finalized”). When you finalize, the exportable proof is created: PDF + protocol.
Why two files?
- PDF: the “document” you can file or hand off.
- Protocol: makes it traceable what was confirmed, when, and in which context.
- Together: calm, understandable documentation — without manual assembling later.
When is proof created?
Not automatically at the moment the person clicks — but when you consciously finalize inside the project. That makes it clear: collect first (interim state), then close (proof).
What this solves
- Find again: everything in the right project instead of chats/folders.
- Explain: timing + scope + context are documented cleanly.
- Hand-off: export (PDF + protocol) or bundle export (ZIP) for archive/hand-off.
Is this legal advice?
No. This is guidance for documentation/workflow. Check your specific case for your country and situation.
Why isn’t proof created automatically?
Because closure should be conscious: finalizing fixes the state. Before that, it’s an interim state (“received”).
What’s the difference between PDF and protocol?
The PDF is the document. The protocol explains context/scope/timing so it remains traceable later.
When can I export?
In LegitForm only after you finalize. Then PDF + protocol are created and exportable.
Is there a bundle export?
Yes. Per project you can export a ZIP — including finalized proofs (PDF + protocol + seal).