| 13-03-2006, 10:49 | #1 |
|
Closed Account
|
Writing a brief for a web designer
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.
|
|
|
|
Advertisement
|
|
|
| 13-03-2006, 11:25 | #2 |
|
Registered User
![]() |
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/articl...ign-brief1.htm http://www.cleardesignuk.com/design-brief.html http://www.mda.org.uk/design.htm |
|
|
| 13-03-2006, 12:18 | #3 |
|
Moderator
![]() Join Date: Jun 2001
Location: The 2nd Circle of Hell
Posts: 14,677
|
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:
|
|
|