Why you need a Design Contract

Posted 01 Jul 2010 - 7 Gratefully received comments

A contract is a simple form of protection that any competent business person should have when starting a new project.

It’s an extension of the design brief in that it helps to inform both the client and the designer on what to expect of one another.

A simple design contract (I prefer the term agreement) will outline the basic non-design related elements of the project so everybody knows exactly what to expect for the duration.

This is the final stage of the ‘admin’ part of any project. So far we’ve met with the client, asked all the right questions, written and agreed a design brief. Now all that’s left to do is draw up and sign an agreement to cement the business relationship.

I must note that I’m not a solicitor so I have no idea if my agreement is legally binding, and I won’t vouch for it as such if you decided to use a version of it for yourself.

Rightly or wrongly, I work with clients on a basis of trust and I see the signing of a design brief and agreement as a way to make sure the lines of communication are completely clear. These are also very handy documents to refer back to during the course of a project if the expectations of the client or designer begin to change over time.

Below is my sample design agreement for a fictional client called The Swinging Penguins, a band looking for a new promotional identity.

Contact: Name: Dan Evans
Address: A Street, Ipswich, IP1 1IP
Telephone: 01473 444444
Email: dan@theswingingpenguins.com

Outline of design Brief:
Create a fun and memorable brand for ‘The Swinging Penguins’ a local band about to embark on a tour. This will entail:
• A logo/logotype
• Illustrative representations of each band member

Possible extensions:
• A simple tour website
• Tour posters/leaflets
• Merchandise T-shirts

A full copy of the brief can be provided on request.

Design Process/Timetable
Commencement date of project: 1/7/2010
A payment of 50% of the total quoted price is payable before work commences.

Stage 1 – Research
Using sources and leads provided by the client as well as any additional research deemed necessary the designer will gather
information that will aid in ideas generation.
Completion Date: 20/7/2010

Stage 2 – Ideas Generation & Development
With the aid of research the designer will begin sketching out
possible ideas and begin developing any promising leads. The agreed design brief will be the main guiding factor in this stage.
Completion Date: 30/7/2010

Stage 3 – Artworking
A maximum of three logo ideas will be artworked for presentation to the client.
The illustration element of the branding will be proofed to the client in the early stages to define the required illustrative style.
Completion Date: 30/7/2010

Stage 4 – Presentation & Client Feedback
Artworked samples will be presented to the client for critique and feedback.
First Client Meeting: 31/7/2010

Stage 5 – Revisions
This stage is quite fluid as there may be numerous meetings and feedback before a final design is agreed.
Subsequent Client Meetings between: 5/8/2010 – 26/8/2010

Stage 6 – Final Artwork – Supplying Files
Once a design has been agreed final artwork will be made and handed over to the client.
Completion Date: 1/9/2010
The outstanding balance must be paid before any of the original artwork files are given to the client. The final invoice will be generated once the final artwork proofs have been signed off.

Client Actions
The client agrees to:
• Sign off on progressive artwork profs to indicate that milestones have been achieved.
• Pay in a timely manner on receipt of invoice(s)
• Own all rights to the artwork that has been produced after final payment.
• Allow the designer to display the artwork in personal & business portfolios.

Designer Actions
The designer agrees to:
• Produce all artwork and products that have been agreed in the design brief.
• Finish the project within the timescale laid out in this agreement.
• Warn the client if the project might overrun the agreed timescale.
• Not disclose any information about the project until approved by the client.
• Work to the agreed budget.
• Warn the client if the budget runs the risk of being exceeded and seek permission before continuing.
• Send invoices at the appropriate times in the project.

Declaration:
At the end of the document make a provision for both the client and designer to sign it declaring that they agree to the terms of the agreement.

You can download a pdf version of this design agreement here, if you would like to see how I format it for the client.

This is what works for me, I believe the important bases are all covered:
It’s clear who the client is.
It’s clear what the designer is doing for the client (especially if it’s accompanied by a full brief.)
The design Process is explained.
The process is annotated by the expected timescales
The expected pay structure is explained
Finally I list any other details that might be expected of both parties.

I’d like to know how you handle design contracts. Do you use them? If not, why? If you do use contracts what is missing from mine?

If you enjoyed this post why not sign up to get automatic email updates whenever I post something new?
Subscribe to email updatesSubscribe to my RSS feed
Follow me on twitterJoin me on Facebook

- leave a comment!
 

7 Comments

  • Laura says:

    Hi Ken, your post is timely as always! I’ve been doing a bit of research myself on contracts, or agreements – I like the term, hope you don’t mind if I pinch it? It makes the whole process seem much more approachable.

    I’m definitely with you on needing a contract, even if its not completely legally binding, simply because it starts the whole project off on the right foot. The client knows what to expect from the designer, and also what their responsibilities are too. Often something clients forget about in my experience.

    One last point, you’ve made a little typo on point 3 of “Designer Actions” – “Warm” instead of “Warn”. Though I can’t say anything, I’m sure my comment is full of spelling and grammatical mistakes :)

    Cheers as always,
    Laura

    [Reply]

    Ken Reynolds Reply:

    Thanks for commenting Laura, I can’t claim ownership over the word agreement, so feel free to use it! :)

    I’ve amended the typo too.

    [Reply]

  • Johnny says:

    I think I’ve taken for granted the fact that designers have a different approach to organizing a project and creating a contract than developers do. Definitely a great example for designers here.

    As far as the legality of contracts, sure, it can be spruced up better with a lawyer. But since many freelancers work with clients from other countries, where enforcement may be difficult, building mutual trust and an agreement through a contract similar to yours is enough to keep any disputes at bay.

    Cheers,
    Johnny

    [Reply]

    Ken Reynolds Reply:

    Hi, and thanks for commenting.

    There certainly are a different range of issues to consider depending on the aims and outcomes of a prospective project. Personally I find the structure of this sot of document can be adapted quite well.

    You bring up an interesting subject on the legalities of a document changing, depending on the location of the client.

    [Reply]

  • Duncan Y. says:

    hmmm… The contract thing are always interested me. Let me share a little bit of insights of my experience in here.

    As in Malaysia, many customer especially SMEs often unwilling to sign any contracts as they would not want to legalize the commitment they should have. Most often(especially in smaller town area) they would just like to spend less than RM300(That’s less than USD$100) for a logo or identity for their new company and if possible, they’re expecting a pro bono service upon letterheads and name card as well!

    I think in our(Malysian) side, we need to sort out the possible legal problem arise upon intellectual property while dealing in contracts as most Malaysians are just started to aware of the importance of having contracts and still have little knowledge until what degree that we will be protected by the contracts as only those who works in Big city will be aware of the importance of it while town areas has really no ideas(may be most of them are like me – a non-proper-trained-self-taught-designer).

    [Reply]

  • Duncan Y. says:

    Hi, Ken. I have something feeling confused here. Should the designer add in another terms regarding the possibility of font purchasing if necessary and the licensing issue? I’m pretty new in this so umm…just asking.

    [Reply]

    Ken Reynolds Reply:

    Hi Duncan,

    Like I said in the article, I see this example as more of a written agreement between myself and the client. I can’t vouch for it’s legality. I use it as a device that sets boundaries and expectations for all parties concerned in a project.

    If you have an issue where the designer is expected to pick up certain overheads, like buying fonts etc, then this can be included in the document.

    I think this sort of format is loose enough to add and subtract certain guides and considerations as the arise. But I will reiterate, I cannot vouch for the legal protection that this document might provide.

    Hope this helps.

    [Reply]

Leave a Comment







© Ken Reynolds Design
footer navigation