List of discussion points for KLP 1. KLP to provide a list of deliverables and a list of exclusions 2.

The designs should be provided in prototype format showing basic page structure and order(Fireworks HTML, Flash catalyst, or PDF). 3. Example user journeys will need to be defined before wireframes can be signed off 4. Copydeck to be provided showing size of copy areas and in what locations on the wireframes the copy will go 5. Defined standard for any video content original and user generated (resolution, format etc) 6. How are the assets (images and videos etc) to be created? Use of licensed/stock assets to be considered where appropriate 7. Audio what are the audio requirements? Is there any original music or v/o required? Who is doing audio post, if any? 8. Is there a need for any 3D rendering? Animation? 9. What video post is planned? Grading is generally not required for online, although if there are multiple videos there needs to be a process to match a visual standard. Are there resizing requirments or will this be automated? 10. Timing plan with milestones is required. Gantt chart or equivalent. 11. Durations and hours work needed, not just a list of milestones 12. Project controls the number and the timing of reviews and approvals (agency CD, client etc) plus number of amends 13. Legal signoffs, reviews and approvals to be defined 14. When will a prototype and/or first build review be delivered? Define what will be completed by this stage 15. Testing process. Testing scripts and/or process needs to be defined. 16. When will the site be completed? 17. When will the work go-live? (There should be a gap between these two to allow for problems and last minute changes). Launch should not happen before a non-working day.
Page 1 of 2

18. What level of fine-tuning (as opposed to bug-fixing) is planned? What level of changes can be made within the scope? Define the tolerances before out-of-scope is triggered. 19. Source files and assets to be delivered to Britvic. These need to be packaged so they can be re-delivered if required as one file/directory structure with versioning. 20. What are the target OSs and browsers? 21. What is the build platform? 22. How are reviews going to be delivered? Designs/wireframes etc should be in PDFs with page numbers and versioning. 23. Copy to be distributed in a reviewable format that allows comment without destroying the layout, hence not a word processor file. PDF or spreadsheet, dependent upon prior agreement. If PDF, then Britvic will need to confirm they are able to add comments and strikeouts etc. 24. Are there any software requirements for Britvic to review? (Acrobat, Excel etc). What are the plans for sharing files? Email Ok to use for formal notifications but deliverables (designs, etc) need to be uploaded to a central location and a link sent. Versioning and page numbers required in all delivered filenames and folders. 25. What is planned for hosting? 26. What is planned for SEO? 27. Who is supporting the site once it goes live? KPIs? 28. More complete Statement of Work/Project Initiation Doc/deliverables list etc required 29. Define the team who will be contacting Britvic contact details plus roles and responsibilities. Provide this in a format that can be referenced (Google sites, FTP server or as a PDF etc) 30. What debriefing is planned?

Page 2 of 2