Approvals
What Belongs in a Client Approval Record (and Why Verbal Approval Isn't Enough)
Verbal approval is fast, which is exactly why so many contractors, subcontractors, landlords, and property managers rely on it. The problem shows up later, when a client disputes a charge, a cost, or a scope of work, and there is nothing to point to except two different memories of the same conversation.
Why verbal approval isn't enough
Verbal approval leaves no timestamp, no record of exactly what was agreed to, and no way to prove it happened at all if the client later says otherwise. It puts the business in the position of arguing its own version of events instead of simply showing the record.
What a real approval record should show
- Exactly what was approved — not a general "yes"
- The cost or scope tied to that approval
- Who approved it, by name
- The exact date and time approval was given
- Whether and when the client actually viewed the request
An approval record that only says "approved" without showing what was approved is barely stronger than no record at all. The detail is what makes it dependable.
Approvals need to be tied to what they approve
A strong approval record connects directly to line items — the specific costs, materials, or scope changes being approved — rather than a single blanket approval covering an entire project. When a dispute is about one specific charge, a general approval doesn't answer the question. A line-item approval does.
Approval records protect everyone involved
A clear approval record does not just protect the business from disputes. It protects the client too, since it prevents them from being charged for anything they did not actually agree to. A dependable approval process benefits both sides of the relationship.
How Leeward helps
Leeward's approval requests are sent to clients through a secure share link, with delivery and view history tracked automatically. Once a client approves, the record — including line items, cost, and timestamp — locks in place and becomes part of the project's permanent, exportable history.