Often times the project brief doesn’t get the attention it deserves. To avoid miscommunication and conflict it’s best to iron out each and every knowable detail before work on a website build begins. The project brief (if done right) will be the most valuable reference for the organization’s management team and the design and development team you’re hiring to build-out your project. Never rush through this phase of the website quote process.
It may seem as though this process is time consuming and difficult, we can assure you, it’s worth every minute. This outline will help you communicate your hopes and needs. It will also allow your design and development team to catch missed items and possible conflicts while compiling a clear outline of requests, objects and goals.
In order to provide a guideline for discovery, bold items are essential to providing a brief to Spark Logix Studios. While ALL elements are useful, the bold text is highly important in gathering detail for the project build.
- The Purpose and Mission of the Organization
- The Purpose and Mission of the Website (What’s the website’s role/objective?)
- Services and Products Offered
- The History of the Business
- Are there branding guidelines to follow? Provide all branding documents in detail. Explain all requested branding guidelines to adhere to on the website. Include: logo, color schemes and all other notable branding detail.
- Where do your prospects live (geographical area)?
- How do your prospects currently find your product/service?
- Explain in detail your target audience.
- Who are the decision makers?
- How is a final decision made, approved and submitted?
- How frequently does the organization need updates on build progress?
- Will there be meetings requested by the organization? How frequent and in what format? What is expected?
- How are disputes to be handled?
- Will the decision maker &/or project manager be available for communication via Basecamp throughout the week?
- How many developers (teams) have worked on this particular project? Were there issues? What were those issues?
- Are there any third parties assisting in this development? Who? What will be their role and how will they communicate?
- How long has this project been active?
- Complete Sitemap (all pages)
- A list of all current pages
- A list of all newly requested pages
- Top Level Navigation (including all levels of dropdowns in list format)
- Are there 301 re-directs and newly requested URLs for existing pages? Please list all.
- (from Design Requests: label groups of pages that will include the same design layouts)
Pages (Written Content)
- Which pages will keep the exact content?
- Which pages will require modified content?
- Which pages will require completely new content?
- What content needs to be written? Include: each page requested, expected word count and if it’s (modified content, all newly written content) | Who will write it? Will they indicate the H1 and H2’s (and so on)?
- Will the Title Tags and Meta Descriptions need to be re-written? Who will write them?
- Which pages will keep all of the exact images?
- Which pages will require new images?
- Who will be providing the images?
- Define the exact functional elements of the website (If there are functionalities more so than a User reading text on a page it should be notated in vivid detail.)
- Define the User’s experience. Showcase typical User flow (sometimes visuals help). What happens? What’s accomplished? List each unique User experience and specify their exact functionality flow.
- Will content be provided via XML or CSV?
- Explain all integration needs with third parties and expected server compatibility.
- Are there specific forms to be used? How many? Where? What fields? Any conditional logic? Who receives correspondence or confirmation?
- Are there specific WordPress plugins to be used? What are they? What’s their purpose?
- Where will the site be hosted? What is the Developer’s responsibilities in relation to hosting?
The items included consist of the client’s use of websites they like and how they’d like to modify those designs to fit their vision. It’s important to highlight the design requests for the following sections of the site:
- Header/Preheader (Top of Page and Navigation Design and Function)
- Body Concept (Design and Function of Homepage)
- Footer / PreFooter (Bottom of Page Design and Function)
- Internal Page Concepts (Design and Function of Internal Pages) -How many internal page layouts will there be? List the needs of each and group together (as listed in the Content section).
- Color Palette/Scheme (as indicated in the Organization list).
eCommerce (if applicable)
- Explanation of products or services to be sold online.
- Product Content (manual data entry, CSV, XML, another source). Who is expected to load the products and all content related to products (written content, images, attributes, price variations, titles, meta, etc)?
- What configurations will be needed? Attributes, Variations, Shipping, Tax Scenarios, Payment Portals, etc.
- Explain the shop experience in detail. What is expected? Define the User flow in detail.
- Detail your plans for security including SSL or off site payment processing.
- What reporting methods are expected? Indicate reporting needs in detail.
- Include terms and conditions of purchase.
Testing and Revisions
- What is expected to be tested and under what conditions?
- In addition to the Development Firm, who else is expected to test functionality?
- When will testing take place and for how long?
- Changes and revisions in relation to testing: Who is responsible? How is it paid?
- Specify all deliverables and milestones for the Development Team.
- Specify all of your deliverables and milestones.