Signed before it leaves the yard

They get a link. Opening it shows the agreement in a browser — no account, no app, no login. A one-time code is sent to their email, and once it is verified they sign either by drawing with a finger or by typing their name. It works on a phone at the kerb, which is the point: the signature happens before the equipment leaves, not in an email thread afterwards.

Yes, and it happens first. A member of your team counter-signs in the app, and that is what releases the agreement to be sent to the customer. The finished PDF carries both signatures with their timestamps.

The signature itself — a drawn image or the typed name — plus the time, the IP address and the device the signature came from, and the fact that the one-time code was verified. All of it sits on an audit trail alongside every other event on that agreement: created, counter-signed, sent, opened, signed or declined.

No, and this is deliberate. The clause text is copied onto the agreement at the moment it is raised, so it is a snapshot rather than a live reference. Editing a template or a clause afterwards changes future agreements only — it can never alter what somebody already put their name to.

We would rather be precise than reassuring here. A SHA-256 hash of the agreement and its signature metadata is recorded at the moment of signing, which is genuine tamper evidence — if the content were altered, it would no longer match. But nothing in the product re-validates that hash automatically today, so treat it as a record you can point to, not a lock that prevents change.

We do not claim certification under eIDAS, the US ESIGN Act, UETA or any equivalent, and you should not take this page as legal advice. What Rentablez gives you is the evidence such regimes generally care about: a verified one-time code to the signer, the signature itself, the time, the IP address and device, an event-by-event audit trail, and a content hash. Whether that is sufficient for your jurisdiction and your contract values is a question for your own lawyer.

Yes — that is the normal case. Clauses are yours to write, in a rich-text editor, and you assemble them into templates in whatever order you want. There is a set of system clauses to start from, but nothing obliges you to use them.

Yes. An agreement is either a master agreement held at customer level or an order contract attached to a specific hire, so a long-standing account can sign once rather than every time.

They can decline from the signing page and give a reason, which is captured on the audit trail. The agreement moves to declined and can be revised and re-sent. Note that no notification is pushed to your team when this happens today, so declines are something you check rather than something that chases you.

No. There is no automated reminder schedule. You can resend a signature request whenever you choose, and the signing link carries its own expiry — seven days by default — but the chasing is a decision your team makes rather than something the system does on a timer.

Yes. Agreements can be laid out to leave the first page clear for stamp paper, or every page, which matters in markets where a physical stamped instrument is expected alongside the electronic record. A witness block can also be printed, though witnesses sign on paper rather than electronically.

Those are hand-over documents — proof that goods left the yard, with their own numbering and layout. The contract is the only document in Rentablez that carries e-signature, one-time-code verification, an audit trail and a content hash. If you need to prove what was agreed rather than what was handed over, it is the contract that does it.

No. Contracts and e-signature are a separate module rather than part of the base product, so it depends on your plan. Ask on the demo and we will tell you plainly where it sits.