How to write a deposit policy customers will actually read
A deposit policy is ignored for ordinary reasons: too long, too late on the page, too lawyerly. Four answers, two hundred words, three places.
It is not unread because people are careless
A deposit policy gets ignored for ordinary reasons. It sits at the bottom of a long document, in the smallest type on the page, and it arrives after the customer has decided to book and only wants to know where to sign. By the time the policy matters — a cancellation, a date moved, a payment that did not go through — nobody has read it. Often that includes whoever answers the email on your side.
So the job is not to write a firmer policy. It is to write one short enough to be read in a single pass and put it where somebody is still paying attention. Everything below serves that: fewer words, earlier, in the order the questions occur to the person reading.
Answer the four questions a customer really has
Strip a deposit policy down and it answers four things. How much do I pay today. What is the rest, and when does each part come out. What happens if I cancel. What happens if a payment does not go through. A policy that answers those four in plain order is complete, whatever else it leaves out.
Keep them in that order, because that is the order they are asked in. Anything that does not answer one of the four is usually housekeeping and belongs in the agreement rather than the policy: who to write to about moving a date, how a transfer to another person is treated, which name shows up on a card statement.
Give every answer a number and a date rather than a condition. Five hundred today, the balance in three payments on the first of each month, the last one fourteen days before the date: a customer can check that against a calendar. A deposit is required to secure your booking, with the balance due in advance of the event, is not a policy. It is a sentence about one.
Two hundred words, three places, four headings
Aim to stay under roughly two hundred words. That is enough for the four answers with a line of reasoning on the two that need one, and it is short enough to fit on a phone without scrolling. A policy that takes two screens gets skimmed to the next heading and abandoned halfway.
Put it in three places, in the same words each time: on the page where the booking is made, on the schedule the customer agrees to before the first payment comes out, and in the confirmation email. Identical wording matters more than it sounds. If your website says most deposits and your agreement says all deposits, the version quoted back to you will be whichever one helps them, and they will be right to.
Use headings, not prose. Four small headings with a line or two under each gets read; the same content as one paragraph does not. Nobody is reading this for pleasure. They are hunting for the answer to the one question they already have, and a heading lets them find it — and then, having found it, read the rest.
Write the firm parts in the voice you would use out loud
The firm clauses are where the writing usually goes wrong. Deposits are strictly non-refundable under any circumstances is the sound of somebody braced for a fight, and it invites one. Put the reason in the same sentence as the rule — the deposit stays with us because we book your caterer the week you confirm — and the rule stops reading as a threat and starts reading as arithmetic.
Say you and we. The client shall remit and the aforementioned sum are not more binding, they are only harder to read, and every clause a customer has to decode is one they will later say they did not understand. If a sentence would sound strange spoken across a table, it is the wrong sentence, even where the rule behind it is right.
Then write the unglamorous one. What happens when a card is declined on a payment date. Most policies go quiet here, which means the first time it happens you are inventing the rule in an email, annoyed, on a Friday. Decide it once in advance: we try again after three days, we write to you, the remaining dates do not move. It reassures the honest customer and it saves you from negotiating with yourself.
One test before you publish. Read it to somebody who has never seen your booking process, then ask them what they would pay today and what happens if they cancel next month. If they can answer both from memory, the policy is done. If they have to go back and look, it is still too long.