Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Writing a brief for a web designer

  • 13-03-2006 10:49am
    #1
    BrianD
    Closed Accounts Posts: 7,221 ✭✭✭


    Any pointers on writing a brief for a web designer? I would like to put the design of a web site out to "tender" and need to have what we require documented. I know what we require from a user point of view but what about the 'back end'. Suggestions welcome and/or links to examples.


Comments

  • #2
    Seth Brundle
    Moderators, Politics Moderators Posts: 41,235 Mod ✭✭✭✭Seth Brundle


    What will be required - static brochure site, database driven site, etc?
    What will be supplied by you (text, pictures, etc.)?
    Who is the target market?


    Have a look at these...
    http://www.designspring.co.uk/articles/web-design-brief1.htm
    http://www.cleardesignuk.com/design-brief.html
    http://www.mda.org.uk/design.htm


  • #3
    The Corinthian
    Closed Accounts Posts: 19,777 ✭✭✭✭The Corinthian


    This is not specific to design, but to any Web site or application.

    The level of detail in a RFT should be looking for is very much related to the budget involved. If the project is a high-end complex application worth a six-figure sum, then your replies should be detailed and complex - as such your RFT should seek that level of detail. If you’re looking for a €1,000 brochureware site, on the other hand, don’t expect anyone to spend that long on the bid; thus you should write your RFT in such a way that it cuts to the chase of what you’re looking for.

    I’ve seen RFT’s that have sought 30-page (plus) replies, yet the tenders themselves have a budgets of under €5,000. These are RFT’s that either get few replies or very bad ones (cut ‘n past tenders from companies who are not going to write a detailed reply specifically for such a small project).

    Either way, whether it’s a one-page document or a 60-page RFT, your principle three parts should be as follows:
    1. Executive Summery. Both an introduction to the project and an overall explication of what the application is meant for and will actually do. Background information and the general feel sought of the application should be put here.
    2. Deliverables. These are listed (with description) the actual deliverable functionality of the application. Using a numbering system for the deliverables is advisable as this is how they should be referenced in any bid and potentially in any future agreed deliverables contract.
    3. Other Business Considerations. Proposed credit terms, deadlines, accreditations sought, taxation or legal issues, T&C or anything else that would be not be directly related to the application.


Advertisement