Versions
Every proposal keeps a version history. Sending creates an immutable snapshot with a hash and a PDF. Edits after sending create a new draft version. The proposal's history shows every version, who changed it and whether it was approved, sent or accepted.
What the audit log records
| Event | Recorded |
|---|---|
| Send | Who sent, to whom, when, version hash |
| Approval or send-back | Approver, decision, note, version |
| Acceptance or decline | Client contact, when, version hash, certificate |
| Budget change | Who changed which target, old and new value |
| AI change accepted | Which page, what changed, who accepted |
| Revoke or expiry | Who revoked, or the expiry reached |
Why it matters
A firm can show that what the client accepted is what the partner approved, down to the version hash. That is the point of recording rather than trusting memory.
Still stuck? Email support@feebeaver.com. Professional plans get a reply within 1 business day; Firm plans get priority support.