How to write a technical task for a website correctly

What is a technical assignment and why is it needed?

Who draws up the technical specifications?

Brief

Contents of the TOR

Mistakes when drafting technical specifications

Conclusion

Developers, designers and others involved in creating a website are not visionaries. They cannot know what a potential customer wants. To do everything right, you need to create a technical task, which will clearly outline the stages of creating a website, changing details, writing text, etc. Such actions will help avoid misunderstandings between the customer and the contractor. This means that unnecessary expenses can be avoided. Therefore, it is important to create a technical task before starting work.

 

We will tell you why you need a technical specification, how to draw it up and what benefits it brings.

What is a technical assignment and why is it needed?

The technical task is a kind of clear instruction on what needs to be done.

 

Otherwise, the technical task (TT) can be called a document in which the development details are specified. According to what is specified in this document, the work will be carried out. The TT, described in detail, will not allow deviating from the execution of work in another direction.

 

In case of rejection, you will have to redo what you have done.

Who draws up the technical specifications?

The technical task is drawn up by the performer. The role of the performer can be played by a developer or a project manager. But the customer does not remain indifferent, since the task is created based on his wishes.

 

Customer's goal

 

The customer's goal is to get what they want. Therefore, it is necessary to discuss the stages before starting work.

The customer introduces the contractor to his business, goals, and tasks. The customer can also show examples of web resources that he liked as a guide for further work.

 

The performer's goal

 

The contractor’s goal is to complete a set of works as the customer wishes.

 

The contractor undertakes to complete the work on time, in accordance with the contract and technical specifications.

 

Of course, the main goal of the performer is to earn money. In view of this, the details and terms of work are discussed.

 

The benefit for each party is to understand what they have to work with, what volume of work to do, and also to insure themselves. For the customer, the insurance will be a quality check of the work performed, for the contractor - to reach the end of the path, due to certain types of clients who can stop work in the middle of the path.

Brief

A brief is a questionnaire in which the customer briefly describes:

 

  1. information about the company, its activities, values, and mission;
  2. Your competitors (strengths and weaknesses);
  3. Strengths and weaknesses of your organization;
  4. Using the desired colors when developing the resource;
  5. References of sites that you liked are indicated.

 

This is only part of what can be in a brief. In fact, this is also a document of sorts. It serves as a basis for further work. Briefs can be extended (with in-depth information). There is no clear standard. Each contractor creates such questionnaires at their own discretion, based on experience. They make further work easier.

 

After brief information in such a questionnaire, the contractor and the customer move on to the detailed analysis stage. Here the contractor will learn an expanded version of what was described.

 

The benefit of a brief is that it allows you to define the development concept and approximate cost at the start. A full budget calculation always occurs after a detailed discussion of the elements, work plans, their volume, and deadlines. At the initial stage, there may only be a preliminary price for services. This must be understood to avoid misunderstandings.

Contents of the TOR

Brief, later on, becomes the main task. The checklist for the technical task is as follows:

 

  1. Information about the company: name, goals, missions, date of foundation, services or products, achievements, certificates (if any);
  2. Target audience: gender, region of residence, age, interests, marital status, income;
  3. Website: visual part, website goals, content, mobile version;
  4. Design: colors, fonts, button sizes, etc. (a brand book comes to the rescue);
  5. Possibility of website administration;
  6. Integration of CRM systems, analytics;
  7. Additional comments and examples.

 

Below we will look at specific requirements in more detail.

 

Business requirements

 

Business requirements refer to detailed information about an organization.

 

Company information must contain the following:

 

  1. Name of the organization. This can be an individual entrepreneur, LLC, OJSC, or a brand name. For example, LLC "Flowers of Babylon";
  2. Products and/or services that the company offers. For example, selling flowers, gift wrapping;
  3. Contacts, opening hours, social media profiles;
  4. Achievement. Here you can add awards, certificates. For example, the brand won the competition for the best brand of the year, received an award;
  5. Competitors. Here you can highlight the most important competitors. About 5 - 6 is enough. Required for analysis.

 

The target audience is a very important indicator. It forms what and for whom it should be. When creating a website, it is necessary to focus on the target audience (TA), since there are many factors that influence conversion, increasing the time spent on the site, and other interactions.

 

For the target audience, the following is indicated:

 

  1. Gender, age, place of residence, marital status, income level;
  2. Hobbies, interests;
  3. What problem does your product solve?

 

For example, women from 18 to 35 years old, both married and unmarried, income level is average for the country (it is better to indicate the exact amount); are fond of creativity: embroidery, beadwork, etc. The problem that the product will solve: high-quality items for handicrafts, collected in one place: a wide range, different levels of the price segment.

 

It is worth paying special attention to the purpose of visiting the site. If sales are for clients, then the goals can be: leaving contacts for "warm" sales, sending out news, etc. For suppliers - collecting data for cooperation, sending out a product catalog with prices, etc.

 

Company goals

 

The main goal of any company is profit. Here it is worth thinking about possible promotions, promo codes, a well-built sales funnel. In the future, all functionality is subject to implementation on the site. A competent analysis of activities, external, internal factors will allow you to create the best Internet product to meet the needs of both the customer and the end user.

 

Non-functional requirements 

 

Analysis of the visual part of the Internet resource, development of pages, text is the main part of the work.

 

Approximate structure of the site and pages

 

It is good when there is a clear, ready-made structure of the site. This allows you to save time on further analysis. However, one way or another, the web resource will need improvements, changes in structure. This happens over time. Trends, search engine algorithms, user behavior change. Therefore, the approximate structure of the pages allows you to work with what you have at the initial stage, and then improve it.

 

As a rule, this includes:

 

  1. Home page;
  2. Additional pages: catalog, news, blog, contacts, promotions, questions and answers, vacancies.

 

It is better to work out the structure of internal pages carefully. Create the most convenient conditions for the user. For example, a search bar, a phone number, an e-mail subscription, a feedback form (fields), lists of sections, etc. (depending on the type of Internet resource).

Design requirements

 

They are formed, including from the brand book, corporate style. In such documents, acceptable fonts, colors are described, unfilled space, style are taken into account. For example, some companies prohibit the use of black when creating a website. Black can only be acceptable for the font, in other cases, each acceptable color is prescribed taking into account the tone, subtone by hex code, RGB, and so on.

 

Materials

 

Here you can include your favorite pictures, photographs, collages, acceptable for use in the design of the resource. You can attach links to your favorite references.

 

Functional requirements

 

Functional requirements are the capabilities that a web resource must have.

 

Sample set of modules for the user

 

This set includes a basket, filters (selection parameters), online ordering, callback, subscription to news, cost calculation, etc.

Administration

 

Are we talking about the admin panel or pre-prepared content management system (CMS), allowing you to edit, add, and delete information on the resource.

Example of admin panel

Questions

 

Be sure to ask additional questions about the operation of the Internet resource. For example, what server or hosting will be used, where the data will be stored, etc.

 

Lifehacks and templates

 

One of the life hacks: where to find a template? It is not difficult to find templates. They can be competitors' websites, ready-made templates on certain resources, any other resources.

 

The color scheme can be selected on the Internet: request for color selections, individual colors, color combinations.

 

Fonts can also be surfed. Google fonts are considered one of the most popular. There are quite a lot of them.

Mistakes when drafting technical specifications

Common mistakes:

 

  1. Deadlines. Deadlines are always agreed upon for each stage. If the deadline is delayed, you can agree to extend the deadline, stating compelling reasons;
  2. Access. Access is also provided to the customer. If the contractor has a failure (data deletion) or the developer deletes the data due to unnecessary use, the customer will provide it;
  3. Examples of what is desired. The concept of "beautiful" is different for everyone. Abstraction will only confuse, which will lead to disastrous results. Say right away what is needed, how it should be. For this, examples are attached;
  4. Specifics. We clearly describe, we outline the actions. Do not leave anything to the discretion of the performer. Vague phrases like "Make it a half-tone darker here", "Move the shape a little to the left" and the like are unacceptable.

 

Be careful when writing the technical specifications. Every mistake leads to an increase in deadlines and budget.

Conclusion

 

Website development is a responsible business. You need to approach it wisely and with interest, provide extended information to get what you want. That is why it is worth turning to professionals who will notice shortcomings in the brief, ask questions, and tell you in detail how the development process is going. Specialists will always prompt, offer solutions, which will significantly save time, budget, and nerves.

Leave a request

Feel free to submit your request right now! Our specialists will help you diagnose your accounts for free. We are always open to communication and ready to answer any questions.