Technical specification — order compilation of a TS for website | Price

Author: Анатолий Ситников

  • Help
  • Layout corresponds to your ToR
  • Design and function discussion
  • Do a prototype to demonstrate
  • Advanced company brandbook
  • Solve all tasks in time
  • Get the exact price — fill in ↓
FROM 6000$

 Price per TR (from)6000 $8000 $10000 $
 Site prototype   
 Development design  
 Description of functionality
 Client selection of CMS  
 Website structure development  

Fill out the form  — get the exact price:

4000 characters left
If you have a technical task — attach (formats: docx, odt, txt, pdf, zip, doc, rtf):
Add files

Since 2013, we have been helping our clients to develop their business on the Internet.

Technical task for the site — order the preparation of TOR for the site

Space-site experts have prepared recommendations and detailed instructions for you on how to make a well thought-out technical specification for the site. We will understand and answer the most common questions: who creates the ToR, what should be included in it, who needs it and much more.

Why do you want to make a TOR for the site?

Promoting the successful development of a site of any orientation — it is a clear and detailed terms of reference. If there is detailed documentation, both the customer and the contractor can be sure that they understand what they want and what they need to do. That is, they are united in the desired result. We have prepared arguments for you, both for the customer and for the executor in favor of drawing up the ToR.

Use for the customer

Begin with the customer, because it is primarily interesting to him that what he has planned, the performer has brought to life. Among the main arguments:

  • TK — protection for the customer. If we had to deal with an unscrupulous contractor, and there are enough of them, the ToR will be an annex to the main contract. And it will be the main argument about the quality of services provided.
  • Structuring an idea. Often the customer does not understand himself that he wants to and has only a very vague vision, some thoughts and vague formulations. When the ToR says what exactly should happen, it is easier to arrange one's own desires and preferences "on the shelves".
  • Budget savings. If the terms of reference have been thought out, then problems in the process of its implementation are excluded. This means that it will be possible to avoid unnecessary spending.

Artist uses

Artist, as well as the customer, and even more importantly the task. At the coordination stage, it helps to solve a lot of disputable questions, and at the same time it helps to save time and nerves. Main arguments:

  • Artist protection. If you understand, all the performer needs to do is to fulfill the items of the ToR and its requirements. If the customer demands something that is not available in the initial conditions, you can always pay attention to it and refuse or ask for additional payment.
  • TK are clear instructions. If it is very detailed, it describes all the important points for the customer. This speeds up development by several times, while reducing questions and discussions.

Who makes up the TK?

The answer to this question is sought by both stakeholders, and at different stages. In short, it may be said that the terms of reference should be the customer's, because he is the one who knows all the information about his project, in any case, more than the performer.

If there are problems with the creation of TORs, the future artist can help. And he does it at his discretion free of charge or for a fee. We in Space-site, depending on the scope of work, sometimes we allocate the compilation of TOR in a separate service. Thus, the analysis and preparation of the document is carried out. After that, the customer himself decides to continue cooperation with us or to apply with a ready detailed ToR to another studio.

Major sections

To answer the question: "What should be in the ToR?" you need to understand the phased plan for its creation. It is the question of what to include in it that we are asked very often. So, we offer details on the content of the technical assignment.

Project information

No matter if we are going to work with you in the future, at this stage it is necessary to describe the project, submit as much information about it as possible. You should also define the main tasks. The following points should be described in detail:

  • Business direction.
  • Predictable target audience.
  • CA needs.
  • Present the problems of the current site, if any.
  • Tasks to be solved by the new resource.

Technical features of the project

It is likely that many of the following points may cause difficulties, but it is information about the technical features of the site that will help to understand the project. And only with their description will you be able to develop a site that meets your needs. Here are some of the most important technical aspects:

  • Adaptability. Does your resource need to be displayed correctly on PCs and mobile devices screens?
  • Cross-browser. Determine which minimum browser versions the site should display. Old browsers, such as Internet Explorer 7, significantly reduce the possibilities for the developer. At the same time, they do not use more than 1% of those who visit the Internet all over the world.
  • Management system. If you have not yet decided which CMS to choose, specify it in the ToR.

Site structure

It is necessary to describe the basic elements of the pages using a hierarchical or tree-like model. This will help define the basic modules of the site and the links between them.

Through elements

Through elements are blocks and constructs that appear in some form on all pages of the resource. These include 4 basic:

  • Site cap. This is the top part of the resource, which includes important visual tools — company logo, contact information, page navigation, some additional elements.
  • Basement site. This is the lower part, which is the same for any page of the resource. Often it duplicates the information from the header of the site or only part of it.
  • Side panels or sidebars. Vertical columns, they include a specific set of widgets. These function blocks can be side panels that include filters, fast navigation through categories, etc.
  • Floating windows, forms. They appear after clicking on the button or at another action that the customer will define.

Unique pages

In general, the scope of work for the designer, developer — are unique pages, sections. On their basis is built the entire site. That's why each page that needs a unique design and structure, you need to describe in the terms of reference for the site.

Unique pages — these are the layouts that will be the basis for each page of the site. They will have similar characteristics. Each such page will still require time spent on development by the developer.

To make things clearer, we've prepared a few examples of a brief description of such unique pages. And don't forget that you will still need to use more detailed formulations.

So the news page in the blog:

  • It has through elements — a hat and a basement.
  • Additional blocks in the form of: news title, brief description, photo cover, publication date, news text and comments block.

If you need a product page in the directory, you must have:

  • Through elements — hat and basement.
  • Supplementary blocks: side column with goods filters by set parameters, list of goods in each category, block of personal offers.

Based on the example of unique pages, all other pages will be based on them, but only after integration with the control system. And this process will be automated.

Other pages

Customers often lose sight of the requirements for additional functional pages when drafting the ToR. Below we offer a brief list of things to include in the structure of any site:

  • Typical text page. On its basis, new pages are created, which cannot be attributed to the type of unique. At this stage, you should lay down the following elements: headings, paragraphs, lists, tables, embedded videos, images, etc.
  • Error pages. These are small pages that the visitor sees on the site if something went wrong. Often these pages are underestimated — and this is a big mistake. If you implement them creatively, the result will surprise you and visitors to the site.
  • Search results page. This is a very important functional page. Conversion and sale depends on the convenience of providing the search results.
  • Access and registration page. If the resource is supposed to be authorized, the forms for this must be extremely convenient.

Emportant moments of the ToR for the site

There are moments that are no less important than the description of the structure of the pages in the ToR. In the document, it is worth pointing out the points that determine the logic of the site.

Along description of entities

For a clear understanding of the structure, in the process of developing the site it is customary to highlight the essence. These are certain types of material that have their own characteristics and properties. To make it clearer, let's show you an example:

  1. You create a business card site that has only a few pages. The essence of this is a "page", each with a title, and a number of other options.
  2. If you need to add a news section, you will need another "news" entity. In addition to the title and content, you can add the date of publication, the name of the author.
  3. Interestingly, "author" is also the essence. Each of them has its own name, a unique photo. In this case, the entities can communicate. For example, the news and its author.

If we talk in general, the essence — a kind of elements that are in the structure of the site. On their basis similar elements are created.

Functional features

All functional features of the future site, which cannot be attributed to any of the proposed pages, should be grouped into a separate block. In this case, each of them should also be described. For example, a popular feature on most sites — a commentary module. If it is necessary, then the creation of TOR requires a detailed description of the process of publishing comments, their moderation by the administrator.

We also recommend to describe in the ToR the process of site interaction with third-party sites. It concerns the button of social networks, integration with CRM, sending a notification to the mail and everything that goes beyond the standard functionality, but should be fixed in the documentation.


However our material turned out to be quite voluminous, not all aspects of the terms of reference were covered. Remember that the more thought through the ToR is, the less disagreement and disagreement will arise. Here you can apply the well-known Murphy's Law:

If you don't describe any feature of the site in the TOR, it will be implemented incorrectly.

Of course, this is not true for every project, but still having a detailed and clearly defined terms of reference, the budget preservation will vary within 5-20%. And if you can minimize errors, why not do it?

Technical requirements for the site — Price 2021

Technical specifications price for the site Price, $
Basic from 6000 $
Standard from 8000 $
Full from 10000 $