How should you compose the technical task (TT)?

How should you compose the technical task (TT)?

If you want to create a specific web project, then it is necessary to attract an external contractor who is well versed in website building. But to make the final result successful and do not have to spend months on edits and adjustments, it is essential to approach the compilation of TT carefully.

Why do you need technical task?

Indeed, you can explain in words how the final web project should be, describe the essential components (location on the map, basket, directory, etc.). The usual, at first glance, project. But it is the views of authors and customers that can radically differ. As a result, this will not only lead to the need for revisions but can also significantly increase the time required for the project, as well as its cost.

So there is a conflict situation, while both sides are right: the customer did not get what he wanted, and the developer did everything according to the specified requirements. Regardless of whether the parties will make concessions or disagree, the losers will always be here.

It is to level out such disagreements, and a technical task is necessary. It is important to remember that the differences will remain (well, you can not put everything on the paper). That's only in case of good TT they will be very, very little. But do not be completely obsessed with the task, because its development also costs money. Finding the optimal balance is essential.

From what should the technical task consist?

As the terms of reference, we determine the document which regulates the list of necessary works. It is essential that each of the technical task points objectively assess for specific parameters (Is a particular section completed or not?).

As a result, in TT it is not necessary to specify the design, because here one will like, and the other will not. For example, if the task says that the sun will be in the background, two clouds and a tree, then the final result can be either ideal or frankly bad. But if you include a layout in those tasks, that's another matter.

In general, the task should be as if a dispute arose between the executor and the customer, and now everything is settled in the ship's order, based only on TT. No concepts like "convenient", "beautiful", "functional". Only clear requirements.

Besides, in each assignment, there should be a phrase that states that all unspecified items are according to the discretion of the performer. After all, the customer does not know and should not understand all the subtleties of the process.

Main sections

Structuring any technical task is essential. As a rule, it should contain the following sections.

Common Words

Here the executor is introduced into the course of the matter. In general, the work will be handled by programmers who do not have direct contact with the customer. As a result, it is important to prescribe the general direction of your web project, so that the performer does not have any hesitations. The section is in free form. The main thing is to answer the question: "What is the website about?"

Operational purpose

In fact, it means "how will the web page be profitable?". In the case of commercial projects, the benefit lies in profit. For online stores, the operational purpose consists of sales, discount web pages - link the seller and the buyer, information websites - advertising (that is, it is necessary to attract more visitors), and so on.

Functional purpose

Here it is necessary to provide a list of the means which obtain the profit. In the case of an online store here include:

  • the catalog;

  • guarantees;

  • basket and others.

The terms

This section ensures that both the customer and the performer understand each other. Here it is necessary to decipher concepts from the TT. In this case, the terms can be from both costs.

Features of data and lists

It is the most basic section of any technical task. If everything made right, the author would be able to understand what exactly the customer wants.

The data subsection contains a list of entities that will be using in the project. It is important to specify all the attributes of a particular object so that nothing goes unnoticed. For example, the news should contain not only the text but also the title, date, the author. Some attributes, such as the announcement, can be fine-tuned. But in the case of some others, this can cause difficulties.

Now on the lists. You want to see a list of recent announcements on the main page. But what are these recent posts? The last 10? Last for a day? By skipping this point, you can severely spoil your nerves.

Pages with descriptions

Everything is simple. What pages should be on the website, as well as what should be there? In this case, it is necessary to clarify not only what is displayed, but also in what way.

Reliability requirements

If you plan a high load on the web page, it is worth checking in advance. A good guarantee of reliability will be setting up backups.


The minimum is the content with which the customer can work with the website. Also, it is important to specify how many texts, photos, and videos you need to fill in, and also what quality they should be.

Delivery of the project

Here are described performance conditions of the calculation of work. At the same time, you can specify the point that even after full payment it is possible to edit minor bugs.

Of course, any terms of reference cannot cover all aspects of the project, but this useful task will solve many issues.

See also:

Get a quote

Please, fill the form


Get a callback

Please, fill the form

Thank's! We will get back to you a soon as possible.
Thank you for your interest to our company!
No problem:)