They Bought It, You "Owe" Half: The Unapproved Purchase

It arrives as a fait accompli

Bought. Delivered. Already in your child's hands, probably already loved. And half of it, apparently, is yours to pay — announced after the fact, in a message that treats the spending as something that simply happened to both of you.

Large shared purchases are exactly what advance-approval clauses exist for. Most agreements set a threshold — above this amount, both parents agree first — and this purchase sailed past it without a word. The pressure is real, because the item is for the kids, and refusing can feel, in the moment, like refusing them.

Hold the distinction steady, because everything in this post hangs on it: you are not refusing the item. You are refusing a process in which one parent spends and the other is billed. Paying this once, under protest, teaches that the process works.

The bait

Notice what the bait skips: any mention of the agreement, the threshold, or a conversation beforehand. The price is announced like weather. "They need it" does the moral work — who argues against a school laptop? And "send it this week" adds the standard deadline, so the whole thing feels like a bill that came due rather than a decision you were cut out of.

Send this

The reply reintroduces the missing step. It names the fact (no agreement), names the rule (advance approval above the threshold), and states the consequence (no reimbursement this time) — all without reviewing the purchase itself, the price, or the laptop's merits. Then it does the move that keeps the thread clean: it describes the working process, forward-looking and genuinely easy to use. Item and price first, confirmation in writing, then buy. Any parent reading that later sees a door standing open — with a doorbell.

One discipline on your side of it: the refusal is about the bill, never the item. Nothing in this script gets said anywhere near the child, and the laptop is never criticized, confiscated, or competed with. As far as the kids know, the laptop arrived and the adults handled it.

Never send this

Never send payment "for the kids' sake" alongside a furious paragraph. And never send a refusal that reviews their car, their holiday, and their spending in general.

Paying after protesting sets the precedent that buying first works — the protest gets forgotten and the payment becomes the policy. Next time it won't be a laptop you half-wanted to approve anyway; it will be something larger, announced the same way, with this thread quoted as the system working. The spending review fails from the other side: it starts the wider war this thread was designed to start, and it turns a clean rule — approve in advance — into an argument about two households' entire budgets, which nobody wins and everybody keeps.

If they escalate

Repeat the one line:

"Advance approval first, and I'll confirm my share in writing."

Then — this is the part that makes the rule real — use it yourself, visibly, the next time you buy something shared. Send the item, send the price, wait for the confirmation. A rule you follow yourself is far harder to paint as obstruction, and the thread will show a parent who asks first, every time, in both directions.

If the escalation includes a threat to take the item back or bill you through other channels, let it pass without a reply beyond the one line. The purchase stays where it is, the bill stays where it is, and your log notes the dates and amounts in case unapproved purchases become a pattern worth raising properly — with paperwork, in the right venue.

Why this works

Like every script in this series, this one is written for three audiences: your co-parent, you in six months, and the professional who may read the thread cold. To the third audience, the two messages side by side tell a complete story. One parent announced a $640 decision as a debt. The other named the approval rule, declined once, and described exactly how to do it properly next time. No insults, no budget audits, no child anywhere near it.

The rule is also the same one running under the rest of the money chapter: answer amounts, ignore verdicts, and keep money a system instead of a lever. It is why a bill with a threat attached gets exactly the same flat treatment, and why an enrollment sprung after the fact is refused the same way — the decision process is the thing being protected, because whoever controls the process controls every purchase after this one.

If your situation is slightly different

Your agreement has no approval threshold. The script's shape adapts: name the fact that there was no conversation, decline this one, and propose the threshold as the standing arrangement — "Let's treat anything over $100 as ask-first, both ways." Proposing the rule in writing, and then following it yourself, builds the custom even where the document is silent.

You'd honestly have approved it, and the money isn't the issue. You can still decline — the precedent is the issue — but if you choose to contribute, make it a chosen gift, not a reimbursement: pay it once, in writing, explicitly as a one-off that doesn't set the ask-first rule aside. Generosity chosen by you is a different thing from billing imposed on you, and the record can tell the difference.

The purchase is small but the pattern is constant. Twenty small fait accompli bills a month is the same process problem at a lower price. The rule scales down: batch the reply, name the process once, and log the amounts. Small numbers, stacked in a log, make the pattern visible without a single argument.

The principle

Decisions are shared before money is spent, or the spending belongs to the parent who decided. State it once, follow it yourself, and let every future purchase walk through the door you left open. This scenario is one of 55 worked in full in the book, alongside the rule for keeping child support out of logistics threads.