5. Adapting a Defended Message to One Contractor's Situation

One contractor, one penalty letter

The Ledgerlane Marketing project in Claude now holds a lot of checked work. It has the product-facts register, the brand guide, the six-element audience-and-offer brief, the tagged evidence file and the tested FAQ answer. This chapter adds no new foundation. It uses that foundation for one real-looking person and checks that nothing slips while it does.

The question this chapter answers is narrow. When one customer's situation arrives, how do you change a defended message for them without losing what made it defensible? Adapting a message does not mean rewriting it. You choose which parts of the brief to bring forward for this situation, and you leave the rest alone. Then you prove two things. Every changed line still points to a named source. And no new promise has crept in.

Here is the situation. It is illustrative, like every Ledgerlane fact. A contractor with one van got a late-filing penalty letter from HMRC, the UK tax authority, this week. They have no bookkeeper. They sent a short message through the Ledgerlane website. It says, in their words: "Got a penalty letter on Tuesday for my tax return. One van, no bookkeeper, never really kept on top of it. Can you help and what does it cost?"

That is the whole input. Four facts are in it. They got a penalty letter. It is about their tax return. They run one van. They have no bookkeeper. Everything else we might want to say has to come from the brief, the register or the evidence file. If it comes from none of them, it does not go in.

What the brief already covers

Start by reading the brief against the message, before Ida writes a word. This takes about five minutes. It saves an argument with the draft later.

The brief's audience element already describes this person. Its observed trigger is a penalty or a large year-end bill, and it rests on lines one, two and five of the evidence file. Those three lines come from independent sources, so the trigger has strong support. This contractor arrived in exactly that state. So the reply does not need to explain why someone in their position might want help. They already know. The brief told us they would.

The positioning element names the real competitor. It is not another bookkeeping firm. It is the accountant they see once a year, plus inertia, the habit of leaving things until the letter comes. That matters for the reply. The useful difference Ledgerlane offers is about when the work happens: every month, not once a year in a rush. A reply that makes that point is on solid ground. A reply that says Ledgerlane is better than accountants is not, because nothing in the brief supports it.

The price row covers them too. One van is a hundred and eighty pounds a month, from the price list, owned by the founder, current. The register also holds the four inclusions and three exclusions, and onboarding of about two weeks from signing.

What the brief does not cover

Now the gaps. There are three, and each one is a place where a fluent assistant will want to fill in something plausible.

First, the penalty itself. We do not know how much it is, which stage it is at, or which tax year it covers. The contractor did not say.

Second, VAT. VAT is value added tax, the sales tax a business charges once its turnover passes a set level. We do not know if this contractor is VAT-registered. And the register's VAT row is still open. It is assigned to the founder to confirm. So we cannot say whether the price includes VAT, and we cannot say quarterly VAT prep is relevant to this person.

Third, their deadlines. We do not know what they owe or when.

These gaps lead to an important decision. Some facts about penalties and deadlines are general. They are the same for every sole trader. Those can be checked once and put in the register. Other facts are about this one person. Those can only come from the person.

Putting the penalty and deadline facts in the register

Ida could recite UK tax deadlines from what she says she knows. Do not let her. A model's training has a date, rules change, and a register row has a source and a checked date where a model's memory has neither. The rule from the last chapter still holds: never state a fact that is not a row.

So before drafting, add the time-sensitive facts as rows. Take each one from HMRC's own published Self Assessment guidance. Self Assessment is the system sole traders use to report income and pay tax each year. Each row gets the same columns as before: claim, value, source, owner, date last checked, status. The checked date is the day you read the HMRC page yourself. The owner should be someone who will look again. The founder is the obvious choice.

Here are the rows, said the way you would say them. The tax year ends on the fifth of April. An online return is due by midnight on the thirty-first of January after that tax year ends. A paper return is due by the thirty-first of October. The tax owed for the year, called the balancing payment, is due on the thirty-first of January too. So is the first payment on account for the next year. A payment on account is an advance toward next year's bill. The second payment on account is due on the thirty-first of July.

The penalty rows come next, and they need their conditions kept inside the value. A return up to three months late gets a fixed hundred-pound penalty. That applies even if no tax is due, or if the tax was paid on time. Between three and six months late, ten pounds a day is added, for up to ninety days. That can come to nine hundred pounds. At six months, a further three hundred pounds or five percent of the tax due is added, whichever is higher. At twelve months, the same again. Late payment is separate. Five percent of the unpaid tax is added at thirty days, again at six months and again at twelve months. Interest also builds up every day on overdue tax, at the Bank of England base rate plus two and a half percent.

Notice how much the conditions matter. "The penalty is a hundred pounds" is false for many people who get a letter. "A return up to three months late gets a fixed hundred-pound penalty" is true. The first version is the kind of line a draft produces when it drops a qualifier. The register stops that by holding the condition in the same cell as the number.

One more row belongs here. It is Making Tax Digital for Income Tax. This is HMRC's newer system, where some sole traders keep digital records in software HMRC accepts and send four quarterly updates a year. They still file a final declaration by the thirty-first of January. Since the sixth of April twenty twenty-six, it has applied to sole traders with gross business or property income over fifty thousand pounds. From April twenty twenty-seven the line drops to over thirty thousand. From April twenty twenty-eight it drops to over twenty thousand.

Ledgerlane's audience earns sixty to two hundred thousand a year. On paper, that means most of them are already inside Making Tax Digital. But look at what we do not know. "Earning" in the audience paragraph is a rough description, not a measured gross income for this contractor. So the row goes in, with its threshold and dates. The reply may mention that the rules exist. It may not tell this person the rules apply to them.

Mark every one of these rows with a monthly next check, like the rest of the register. Tax figures and thresholds are exactly the kind of fact that goes stale between campaigns.

The rules a penalty reply has to live inside

Two sets of limits shape this reply, and both were already in the project.

The brief recorded the advertising code's limit on guarantees. In the UK, the Advertising Standards Authority enforces the CAP Code, the rulebook for non-broadcast ads. A business's own website and marketing emails fall under it. For a service near tax penalties, the code allows plain statements of what you do. It does not allow a guarantee, or anything that sounds like one, that a penalty will be cancelled or reduced. Only HMRC and the tax tribunals decide that. The code also counts it as misleading to leave out something material. One example: if someone appeals a penalty, interest on late tax keeps building up while the appeal is pending. A reply that suggests an appeal stops the clock would be leaving out that fact.

There is a related point that matters even more for Ledgerlane. Look at the register's four inclusions. Receipt photo capture, monthly bank reconciliation, quarterly VAT prep and tax-ready year-end accounts. Penalty appeals are not on the list. HMRC does allow appeals, usually within thirty days, and it accepts a "reasonable excuse" such as serious illness. But Ledgerlane has no row saying it handles them. So the reply cannot offer to appeal the penalty. It can say, honestly, that the penalty letter itself explains how to appeal. That is a fact about HMRC's letters, not a Ledgerlane service.

The brand guide adds its own rule: no compliments or reassurance in place of information. A worried person does not need to be told it will be fine. They need to know what Ledgerlane does, what it costs, what it does not do, and what to do next.

Asking Ida for the adaptation

With the rows in place, open a new chat inside the Ledgerlane Marketing project. Paste the contractor's message, then the request. Here is the request, as typed:

"Below is a website inquiry from a contractor. Draft two things: a reply email to them, and a short section for the offer page aimed at contractors in the same situation. Start from the audience-and-offer brief. Change only what this situation needs. Do not add benefits, services or claims that are not already in the brief, the product-facts register or the evidence file. After each sentence you changed or added, put in brackets the evidence line number or register row it comes from. Use only facts the contractor wrote in their message when you refer to them personally. Do not guess their penalty amount, tax year, income, VAT status or deadlines. At the end, list anything you would need to know to make the reply more useful but do not know, and list the register rows you used with their checked dates."

Each part of that request has a job. "Change only what this situation needs" keeps the brief's tested wording where it already works. The bracket tags make the audit possible, because you can check a tag in seconds and you cannot check an untagged sentence at all. The line about the contractor's own facts separates situation from person, which we will come back to in a moment. And the final list turns Ida's gaps into questions you can see, not guesses she quietly fills.

Reading the first draft line by line

Ida's first draft reads well. That is the risk. Here are the faults it shows, illustrative but typical.

The reply opens: "Sorry to hear about the penalty, don't worry, we'll sort it out for you." The tag says audience trigger, lines one, two and five. Check it. Those lines say contractors get penalties and then look for help. None of them says Ledgerlane sorts out penalties. The sentence borrowed a true citation to carry an untrue promise. It is also a guarantee in tone. "We'll sort it out" sounds like the penalty will go away. Under the advertising code, that is the kind of implied promise you cannot make. Under the brand guide, it is reassurance in place of information. Cut it.

The second fault sits in the pricing line: "One van is a hundred and eighty pounds a month, including VAT." The price has a row. The VAT part does not. The VAT row is still open. This is the same fault the FAQ test caught last chapter, and it came back. That is worth noting. A fixed fault in one saved asset does not stop the model making it again in a new one. Only the open row and the audit catch it. Cut "including VAT."

The third fault is a deadline with no date: "We'll get your books ready well before your next deadline." Which deadline? Ida does not know. Neither do we. The sentence also promises a timing outcome that depends on when they sign and what state their records are in. The register says onboarding is about two weeks from signing. That is all we can say about timing.

There is a smaller fault in the offer-page section. It says, "If you've been fined a hundred pounds." The register row is a hundred pounds for a return up to three months late. Dropping the condition makes it wrong for anyone further along. Put the condition back, or leave the number out of the offer page entirely.

Then read the gap list Ida added. It asks for the penalty amount, the tax year, whether the contractor is VAT-registered, and whether their income is above the Making Tax Digital threshold. Those are the right questions. Three of them should go to the contractor. The VAT price question goes to the founder, because it is the open row.

One revision

Tell Ida what to fix, in one message: "Remove the sentence promising to sort out the penalty. Remove 'including VAT'. Remove the deadline promise. In the offer-page section, either keep the penalty figure with its condition or drop it. Turn the unknowns about this contractor into two or three short questions in the reply. Keep the tags."

The revised reply runs about like this, in Ledgerlane's plain voice. Thanks for getting in touch. Ledgerlane does monthly bookkeeping for one- and two-van trade contractors. One van is a hundred and eighty pounds a month. That covers receipt photo capture, monthly bank reconciliation, quarterly VAT prep and tax-ready year-end accounts. It does not cover payroll, chasing invoices or advice on becoming a limited company. We do not handle penalty appeals. Your letter from HMRC explains how to appeal and the time limit for doing it. Setup takes about two weeks from signing. To tell you what we would do first, can you tell us three things? Which tax year is the letter about? Have you filed that return yet? Are you registered for VAT? Reply here, or book a short call.

Each sentence about Ledgerlane carries a tag in the working copy: the price row, the four inclusion rows, the three exclusion rows, the onboarding row. The questions carry no tag because they claim nothing. The line about the letter is general and safe. The diagnostic call to action comes straight from the brief's call-to-action element.

Now audit the revision for new claims, the same way as before. Read each sentence and ask what it says Ledgerlane does, costs or promises. Find the row. If there is no row, the sentence goes. This one passes.

Situation versus person

This draft shows the line between two things that are easy to blur.

Adapting to a situation means using what the brief already knows about everyone in that situation. Contractors who just got a penalty letter are in a hurry and want facts. The one-van price applies. The when-not-how-good difference applies. You can write that once, for an offer-page section, and it fits every contractor with a penalty letter.

Personalizing means using facts about this one recipient. Here the rule is strict. You may use only what they told you. This contractor said one van, no bookkeeper, a penalty letter about their tax return. So the reply can quote the one-van price, and it can skip explaining what a bookkeeper does. It cannot say "your hundred-pound penalty," because they did not give an amount. It cannot say "now that you're in Making Tax Digital," because they did not give their income. A guess that turns out right still teaches the reader you invent things. A guess that turns out wrong does worse.

So the offer-page section and the reply differ in a clear way. The section speaks to the situation, with penalty stages and their conditions as general proof. The reply speaks to the person, using only their own four facts plus Ledgerlane's register, and asks for the rest.

Checking the voice

Last, compare the reply to the brand guide's accepted examples, the onboarding email and the corrected hero section. Put them side by side.

The onboarding email uses short sentences. It names what is excluded. It gives a next step. It never says "don't worry." The revised reply does all four. It has no "stress-free" or "hassle-free". It does not praise the contractor for reaching out. The brief's benefit wording comes from customer lines, not from Ida. On voice, it passes.

Saving the work and the method

File three things together in the project. First, the revised reply and offer-page section. Second, the request that produced them. Third, a short fault note: guarantee-like reassurance removed, unsupported "including VAT" removed again, undated deadline promise removed, penalty figure given back its condition.

Then save the method itself as a reusable project instruction called situation adaptation. It says, in plain terms: when adapting the brief to a customer situation, change only what the situation requires. Tag each changed sentence to an evidence line or current register row. Use only facts the recipient supplied. Never promise an outcome that depends on HMRC or on information you do not have. Do not offer services that are not inclusion rows. End with a list of unknowns, split into questions for the customer and questions for the owner, and the rows used with their checked dates.

That instruction is what makes the next adaptation faster. You will not have to retype the rules. You will still have to read the draft.

Here is one to try. A two-van contractor writes in. They got their year-end figures and the tax bill is far bigger than they expected. Start with the same steps. Read the brief against the message. Which parts of the trigger apply? The two-van price row is two hundred and sixty pounds a month. Then look at the register. The thirty-first of January and thirty-first of July payment-on-account rows matter here, because a large first bill is often followed by advance payments toward next year. But you do not know if that is what happened to this person. Watch for a draft that promises to "reduce your tax bill." Ledgerlane has no row for that. It is a promise about an outcome, and it cannot be in the reply.

The reply and section from this chapter are defended against their evidence and fitted to one real situation. That completes the message you can defend. The next build is the offer page itself, where this section becomes one part of a path a customer can actually click through.

That instruction is new, and an instruction is only worth something if it behaves the same way in every chat that uses it. A recent change to Claude Projects makes that worth checking now.

A Projects change that spreads your saved instructions

On the seventeenth of September twenty twenty-six, Anthropic changed how Claude Projects run work. A project no longer has to run as one linear thread over a folder of files. A coordinator can now send work out to several parallel threads at once. Each parallel thread inherits the project instructions and reference files when it starts.

For Ledgerlane, the effect is direct. The situation adaptation instruction, the facts passage, the register and the brand guide now travel into every thread a coordinator starts. That is good when they are right. It also means one stale file or one loose instruction reaches every thread at once. The rule from the last chapter, one current register and delete the old file before uploading the new one, now protects more work. The threads pick up files when they start, so update the register before you begin a job, not halfway through.

The smallest useful action takes about ten minutes. Open a fresh chat in the project. Paste the two-van inquiry and a one-line request: adapt the brief to this situation using the situation adaptation instruction. Then check four things. Does every changed sentence carry a tag? Is there any VAT claim, even though the row is still open? Does the reply refer only to facts the contractor wrote? Does it end with the unknowns split between customer and owner, and the rows used with their checked dates?

If all four hold, the instruction works on its own, without the history of this chapter's chat behind it. That matters, because parallel threads will not have that history either. If one fails, fix the instruction's wording, not the draft, and run the fresh chat again. A fix to the draft only repairs that one reply. A fix to the instruction reaches every future thread that starts from it.