Artwork for approval text to give a client

As part of the project work flow, getting approvals on artwork is essential. 

 

For the client, it triggers that the stage of concepts and revisions is finished, and the piece will go into production -- whether that be going to press for a print job, or publishing live for a web job. I find that it also encourages the client to proof the content to ensure all the content is what they need/want.

 

For the agency/designer, it documents that the client is happy and ready to move the project along. It's that most important word: "approved". It might even mean that the project can invoiced or closed-out. It also offers some protection if the client comes back and says they didn't approve it.

The following is the text that I use. 

 TIP: save this as a draft in your email, and copy/paste it when you need it.

WEB PROJECTS

 

For your approval:

While care is taken in the preparation of final files, it is essential that the web page/site be checked thoroughly by you or someone within your organization. [Your company Name] shall not be held responsible for any error or omittance not identified by the person providing final authorization.

 

Please choose one of the following and email your choice to [Your company Name]:

1. Approved. I understand that this is the last time I'll see the page/site before it is published. I have checked all functionality, content, information, including any numbers, addresses, spelling, illustrations, and have found them to be correct.
   
2. Approved with changes. Please make a correction to the page/site, and publish it. I do not need to see it again before it is published.
3. Not approved. Please make some revisions to the page/site.

PRINT

For your approval:

While care is taken in the preparation of final files, it is essential that the artwork be checked thoroughly by you or someone within your organization. [Your company Name] shall not be held responsible for any error or omittance not identified by the person providing final authorization.

 

Please choose one of the following and email your choice to [Your company Name]:

1. Approved. I understand that this is the last time I'll see the artwork before it is published. I have checked all functionality, content, information, including any numbers, addresses, spelling, illustrations, and have found them to be correct.
   
2. Approved with changes. Please make a correction to the artwork, and release the final files for the trade printer. I do not need to see it again before files are prepared and transferred.
3. Not approved. Please make some revisions to the artwork.

Photoshop and Fireworks: workflow

During the past two weeks, I finished up my Photoshop course, and started learning about Adobe Fireworks.

What is Adobe Fireworks, you ask? Simply put--it's a tool for getting client approval on website design. I have found that it's challenging for clients to visualize a finished project and it's important to get buy-in from the client at an early stage to make sure the work is headed in the right direction. Even with a creative brief, a creative department can interpret the direction in a way that the client was not intending. It's also important to keep the project on schedule, and on budget while avoiding project creep.

For my own work flow for web design, I see Adobe Photoshop and Adobe Fireworks fitting in as follows:

1. Receive project direction or creative brief (http://elise.com/web/tools/creativebrief.html) from the client or project manager
2. Plan project schedule
3. Research
4. Develop mood board http://www.webdesignerdepot.com/2008/12/why-mood-boards-matter/z
5. Rough out ideas and concepts 
6. Map-out site architecture diagram
7. Wireframe in Adobe Fireworks--ensures that all the elements and behaviours are in place
8. Receive client approval on the mood board, the site architecture diagram, and the wireframe
9. Build a prototype in Adobe Fireworks to develop concepts that a client can see/approve, using Adobe Photoshop, and Adobe Illustrator to develop graphics and images
10. Receive client approval before development begins 
11. Begin to build and code the website