Simple Contracts for Small Jobs: What to Put in Writing

Nobody wants to send a 14 page contract for a $600 job. So most small jobs run on a handshake, and most of the time that works, right up until the one time it doesn't: the client remembers a different price, the finish date was apparently promised, and suddenly you're arguing about a conversation from six weeks ago that neither of you can quote. The answer isn't legal theater. It's a page of plain writing that both sides saw before the work started.

You Need Less Paper Than You Think

A contract's job on a small project is mostly to prevent honest misremembering, not to win lawsuits. Memory is terrible and money makes it worse. That means the document can be short, friendly, and written like a human: an agreement summary, a scope, a price, and a few ground rules. One page. If your work carries real physical or financial risk, think roofing, electrical, anything with permits or big liability, spend the money on a lawyer-drafted template once and reuse it for years. For everyone else, plain language you actually send beats perfect language you keep avoiding.

The Terms That Earn Their Space

• Scope: what you're doing, with numbers attached, plus one line on what's not included
• Price and payment schedule: total, deposit, when the balance is due, and accepted payment methods
• Timeline: start date and either a finish date or an honest estimate labeled as one
• Change process: extra work gets priced in writing before it happens
• Client responsibilities: content, access, approvals, decisions by a named role, and what delays cost
• Revisions or punch list: how many rounds, or how post-job fixes get handled and for how long
• Cancellation: what happens to the deposit and to work already completed if either side walks
• Late payment: the due date and what happens after it, even if that's just a modest monthly charge

That list covers maybe 95% of the disagreements small service businesses actually have. Notice what's not on it: intellectual property warfare, indemnification chains, jurisdiction clauses. Add those when the job size justifies them.

A One Page Outline You Can Copy

When an Email Thread Is Enough

For small jobs with established clients, a confirmation email genuinely can do the job, and courts in many places treat a clear written exchange as an agreement. The trick is writing it like a contract wearing casual clothes: state the scope, price, timeline, and deposit in one message and ask for a reply confirming. “Confirming before I book you in: three cleans monthly at $140 each, first visit May 2, cancellations need 48 hours notice. Reply yes and you're on the calendar.” What doesn't count is a vibe spread across nine messages, two texts, and a phone call. If the terms aren't in one findable place, you don't have terms, you have archaeology.

Connect the Paper to the Money

The agreement and the invoice should tell the same story. Same scope wording, same price, same schedule. When you send the deposit invoice from the invoice generator, reference the agreement date on it; when you collect the final payment, the line items should match the scope the client signed off on, plus any change orders they approved along the way. If a dispute ever does happen, that tidy chain of agreement, invoices, and payment terms is what turns a shouting match into a five minute lookup.