Plain Terms, Firm Boundaries: A Workable One-Page Contract for Independent US Designers

Independent designers in the United States seldom lose a project because they lacked a forty-page contract. More often, trouble begins with a proposal, an email thread, and a deposit that never quite defined what was included. A one-page client agreement will not resolve every legal question, and it is not a substitute for advice from a licensed attorney in the designer's state. It can, however, give both parties a shared operating document for scope, payment, ownership, and cancellation before work begins. For independent practices, that clarity is a professional-development issue as much as a legal one.

The case for a single page is practical. Clients read it. Designers actually use it. The document should be plain enough to discuss in a kickoff call and specific enough to settle the questions that routinely become disputes. The sections below outline provisions worth addressing, with sample language that should be adapted with counsel.

Make the scope sentence carry its weight

A one-page agreement lives or dies by its scope language. The document should name the deliverables, the project, and the limits of the engagement without relying on adjectives such as comprehensive or ongoing. A useful clause might read:

Designer will provide the deliverables described in Schedule A for the project described in Schedule A. The project includes up to two consolidated rounds of revision per deliverable. Work outside Schedule A, including additional concepts, new formats, or revisions after final approval, is out of scope and will be billed at $___ per hour or covered by a written change order.

Schedule A can be a short bulleted list attached to the page. The agreement should also state client responsibilities, such as providing source materials, naming one decision-maker, and returning feedback within a stated number of business days. Designers should treat vague phrases such as unlimited revisions, as needed, and final approval at client's sole discretion as red flags. So should any request for all working files without a separate discussion of ownership and compensation.

Convert revision limits into numbers

Revision language is where many otherwise sensible agreements become unstable. Words such as reasonable or minor invite disagreement because they depend on perspective. A stronger approach is to define the number of rounds, what counts as a round, and when a new scope begins. For example, two consolidated rounds per deliverable means the client gathers feedback from its team and returns one set of comments per round. Additional rounds can be billed at an hourly rate or handled through a change order.

The agreement should also distinguish between revisions and corrections. Correcting an error made by the designer is not the same as changing direction after approval. A short sentence can prevent a lengthy argument: Revisions requested after final approval constitute a new project scope. Designers should watch for contracts that promise unlimited revisions until satisfaction, because those terms make pricing impossible to defend.

Treat AI-generated assets as an explicit category

The use of generative AI in design work raises questions that older form agreements rarely address. A one-page contract should separate AI-assisted exploration from AI-generated final assets, require disclosure where material, and allocate responsibility for review. A sample provision might state:

Designer may use generative AI tools for internal exploration and drafting. Designer will disclose material AI use in final deliverables. Client is responsible for reviewing AI-assisted materials for accuracy and third-party rights before publication. Unless separately agreed in writing, Designer does not warrant that AI-generated elements are copyrightable or registrable, and Client accepts the allocation of risk described in this section.

That language is not a universal solution, and designers should consult counsel about insurance, indemnity, and client-specific requirements. It does, however, open a necessary conversation. Red flags include broad warranties that all output is original, demands for all prompts and intermediate outputs, and requests to feed confidential client material into AI tools without a data-handling agreement. The agreement should also confirm that the client owns final deliverables only after payment, while the designer retains ownership of tools, templates, and pre-existing materials.

Use kill fees to price uncertainty, not to punish

Cancellation clauses are often missing from informal proposals, which leaves both parties to negotiate from frustration. A kill fee, or cancellation fee, recognizes that a designer reserves capacity and may turn away other work. A sample clause could read:

If Client cancels before project kickoff, Client will pay a cancellation fee equal to 25% of the project fee. If Client cancels after kickoff, Client will pay for all work completed and noncancelable third-party commitments, plus a kill fee equal to 25% of the remaining project fee.

Designers should define kickoff, completed work, and noncancelable commitments. Red flags include refundable deposits with no definition of work performed, termination for convenience with no payment obligation, and clauses that allow cancellation after the designer has hired subcontractors or purchased licenses. The goal is not to penalize a client for changing course, but to make the cost of changing course predictable.

Tie payment to observable events

Payment terms should attach to events both parties can verify, not to optimistic assumptions. A deposit upon signature, a milestone payment upon approval of a defined stage, and a final payment upon delivery are easier to administer than a single invoice at the end. A sample provision might state:

Client will pay 50% of the project fee upon signature, 25% upon approval of the first round of concepts, and 25% upon final delivery. Invoices are due within 14 days. Late amounts accrue interest at 1.5% per month or the maximum rate permitted by law. Designer may pause work if an invoice is more than 14 days past due.

Designers should be cautious about net-60 or net-90 terms, pay-when-paid language, and approval gates controlled solely by the client. These terms shift cash-flow risk to the smallest party in the transaction. A one-page agreement can also include a simple pause clause, which is often more effective than an escalating collection dispute.

Keep change control and legal hygiene simple

Change orders do not need to be elaborate. A written email confirming additional work, fee, and schedule can suffice if both parties agree that email constitutes written approval. The agreement should also identify the governing state, confirm that the designer is an independent contractor, and state that it supersedes prior proposals and discussions. Designers should avoid broad indemnity clauses and assignments of intellectual property that take effect before full payment.

A one-page agreement is a starting point, not a guarantee. State law varies, and clients with procurement departments may require additional terms. Designers should review their template with a qualified attorney and update it as their practice changes. The larger point is professional: clear terms support better client relationships, and better client relationships support the kind of design work that independent practitioners want to keep doing.