What should be included in the TOR for website design?

Question

Design

Good afternoon.
I am writing a website for myself and the time has come to order a design. Before that, I have not personally encountered designers and have little idea how to work with them. I would like to avoid mistakes, so as not to overpay and not to wag the nerves of the designer.
I need not only to draw beautifully what is on the layout, but also to compose this layout. I have a general idea of ​​what should be on the page, what functions it should perform. But I can't say exactly where which elements should be. There is only a general concept. There is an approximate layout of how I see it. But, most likely, he will know better how to do it right.
Can you tell me what should be included? Here's what I see:
1. List of desired pages (with a brief description of the content)
2. Sitemap with a description of the navigation scheme
3. Description of user scenarios and goals to be achieved
4. List of entities used on the site and their description (for example: users, comments, articles and all their properties)
5. List of "similar" sites or their parts that I liked
6. The same list, but with sites that I didn't like
7. Sample layout. It is not mandatory to follow it, but it can be considered. It will show my design vision
8. Examples of content posted on the site: titles, texts, images. So that the designer can focus on their volume and size.
9. A list of what the designer cannot decide for himself (for example, the dimensions of product photos)
10. Description of the intended audience
11. If internationalization is needed, provide an approximate list of languages ​​that the system should support (English, Arabic, Japanese)
12. General information such as preferred color, etc.
Tell me what have I forgotten? What else needs to be specified?

Answer 1

habrahabr.ru/blogs/webdev/138749
habrahabr.ru/post/140574
habrahabr.ru/blogs/webdev/101464

Answer 2

Yes, I would kiss you with tears in my eyes for such detailed information. I'm exaggerating, of course, but in the low segment, designers usually get "well .. we need a site, something like this one, but different." By pulling out the information, it is possible to get the first, 5th, 10th and last point.
I think enough )

Answer 3

I am a designer. In your case, it is best to hire a contractor not only for design, but also for documentation. Unless, of course, the performer is capable of this, and the customer does not mind participating and paying for this work. Evaluation, drawing up technical specifications, prototyping are the same stages of work as drawing layouts.
In paragraphs 1-4, 7, 8, 10, 12 (and the rest) the designer can make a lot of suggestions and adjustments.

Answer 4

In general, documentation is a good thing, but difficult to digest, especially for designers. For a designer, the best thing is to create prototypes and decide on the location of the blocks yourself, or look for someone who makes prototypes. Of course, there are cool designers who combine both a designer and a usability specialist, but even in this case, he needs to first draw prototypes, solve all the little things with you, and then proceed to visualization. You will immediately start with the design of the page, ignoring the prototyping stage, you will probably miss many functional points due to the double focus on visual appearance and functionality

Answer 5

Agree with Trow_eu . Usually the customer says, make the site the same as this one and sends a link.

Answer 6

TK may be different. Simple, like a brief with information about the company. Or a detailed TOR in which there will be not only the site structure and a list of pages that need to be rendered, but also target actions for the main pages, the project audience is described, and much more.
Here it is described in great detail how the correct TK is compiled webdela.ru/blog/design/razrabotka-tekhnicheskogo-z...
True, we are talking about online stores, but this does not change the essence.