The contract record
What a signature leaves behind, the audit-trail PDF only you can download, what Riffit will not tell you about it, and what happens to v1 when you revise.
3 min read · Video 1:02 · Updated 2026-10-10
A signature is the moment; the record is what you still have months later. This is what Riffit writes down, what it hands you, and what it deliberately will not claim.
Making a contract and getting it signed is the article before this one: Contracts and e-signing.
The record
Every step is timestamped as it happens: sent, opened, code sent, code verified, signed. Not a summary written afterwards, a line added at the moment.
That record is yours to take. Download audit trail gives you a PDF of the whole thing, from the kebab menu on the contract, not from your client’s page. It is a separate file from the signed contract, and only you can download it. Your client gets the signed PDF, with both signatures on it; you keep the audit-trail certificate.
What Riffit does not do is tell you what any of that is worth in a dispute. It keeps a detailed record and hands you the file. Whether that record does the job you need is a question for a lawyer, and any tool that answers it for you is guessing.
Sending it, and the code
A contract is sent from the dashboard, never from chat. When you send it you pick one channel for your client: email on every plan, or WhatsApp on Pro. The signing link and the six-digit code both go by that channel, so a contract sent by email is verified by email.
Reminders and the link
A contract that has not been signed can be nudged with Send Reminder, once a day. It goes by email, and on WhatsApp too if you sent the contract there on Pro. It carries the same signing link, so your client can sign straight from it.
The signing link has its own expiry, separate from the contract, and the page tells you when it is getting close. A reminder cannot bring back a link that has expired. For that, use Extend link: the link your client already has works again for the next 7, 14 or 30 days, and you can send it to them again in the same step. The extension goes on the record. Revise & resend is only for changing the terms: it makes a new version for you to sign.
Revising a signed contract
Same shape as a quote. Revising creates a fresh draft at the next version, which you edit and send.
The version that was signed does not disappear. It stays in the record, signature and all. That is the point: an amendment that quietly overwrote what was agreed would make the record useless.
Then billing it
A signed contract is billed from the dashboard, from a WhatsApp message like "bill the Rahul contract", or from the Create invoice button Riffit sends you on WhatsApp when the contract is signed. What it bills depends on the template.
- Project Contract and Freelance Service Agreement. One invoice for the fee. If you raised a deposit invoice first, the dashboard offers to invoice the balance. A contract that is fully billed stops offering an invoice.
- Retainer Agreement. One month at a time. Each invoice is for the next month and names it, for example November 2026, and you can raise it up to a month ahead. Riffit does not raise retainer invoices on its own and has no recurring invoices, so you raise each month yourself.
- Mutual NDA. Nothing to bill. The WhatsApp message you get when an NDA is signed has no Create invoice button.
In chat, Riffit stops you billing a Project Contract or Freelance Service Agreement twice. It matches on the original contract rather than the version number, so billing an amended contract from chat still counts as billing that job, and you are told which invoice already covers it. The balance after a deposit invoice is raised from the dashboard.
Was this helpful?
It is the only way I know which guides are working.