Terms of reference for the designer

What is a Technical Assignment?

A technical task is a key document that outlines the requirements and process of creating a product or providing services. It serves as a guide for both the customer and the contractor, ensuring clear communication and successful project implementation.

A well-written technical task allows you to minimize misunderstandings between the task setter and the contractor, helping to achieve a predictable and effective result.

“Технічне завдання — це міст між уявою замовника та реальним продуктом. Без нього ризикуємо заблукати в морі можливостей та натрапляти на труднощі.” — коментує Ігор Степаненко, провідний проєктний аналітик.

Objectives of the Terms of Reference :

Unambiguous understanding of the project goal

The terms of reference help the customer and the developers to clearly define the goal and objectives of the website. It helps to avoid misunderstandings and provides a common vision of the end result.

Scope and functionality definition

The document precisely defines the scope of functionality that the site should provide. This helps to determine the necessary technical solutions and means to achieve the desired technical solutions and tools to achieve the goals.

Risk mitigation

The terms of reference help to identify possible risks and problems at the project planning stage. This allows you to prepare action plans to address them and avoid delays in development.

Improved communication

The document creates a common language for all project participants, including the client, designers, programmers, and testers. This facilitates better communication and a common understanding of tasks.

Quality Control

The technical task defines the criteria for assessing the quality of the project, which helps to determine whether they have been achieved. This is important for ensuring the high quality of the final product.

Budget and timeline planning

The terms of reference set the expected scope of work and timeline for the project. This allows developers and customers to control costs and avoid schedule delays.

Checklist of a competent SoW :

• A clear title. Put all the basic information in it: “who is the contractor”, ‘what is to be done’, ‘by what date it is to be done’.

• Name and surname of the contractor and his/her contacts. Specify a specific contractor.

• Description of the task. Make the most detailed description possible.

• Background information. Describe the product/service to be promoted, the target audience (the one for which the creative is created), and the expected result.

• Technical requirements. Give a clear list of technical properties of the creative and its placement: format, size, resolution, etc.

• General requirements. Add a list of all the necessary characteristics of the creative: colors, fonts, elements, etc.

• Quantity. Specify the exact number of creatives required. examples. Attach references to the file in the form of screenshots or links.

• Customer’s name and contact information. So that the contractor can clarify the task during the execution if necessary.

• Deadline for completion. Specify specific dates and times: the date of the task and the date of its completion.

Frequently asked questions about the terms of reference :

What is a technical specification and why is it needed?

A technical specification is a detailed plan listing all the requirements for a future project or product. Its purpose is to provide a clear understanding of the tasks and goals, as well as identify ways to implement them.

What are the main components of a technical task?

The main components of a technical specification include a general description of the project, detailed functional requirements, non-functional requirements, acceptance criteria, and an implementation plan.

What is the difference between a statement of work and a technical specification?

A statement of work is your navigator in the world of development, providing a general vision of the project and its goals, while a technical specification dives into the specific details of the implementation, describing the technical aspects of the product.

What mistakes should be avoided when writing a technical specification?

When creating a technical specification, it is critical to avoid unclear goals and lack of test scenarios. Providing detailed documentation and clear communication with the team is key to avoiding misunderstandings.

Conclusions :

The ToR does not so much show how to work on a project as it gives an understanding of what it should look like in the end. And this understanding is crystallized by both the contractor and the client. When forming an idea, you can miss the details. But when you start describing your wishes, you think about the little things and important nuances. This is how you can finalize the idea, revise goals, create a promotion strategy, and better study the market.

Even something that seems obvious is better to be written in the ToR. In doing so, you should follow the SMART model: all tasks should be specific, measurable, achievable, relevant, and time-bound. (Time-bound.) Then you will have clear criteria for successful implementation.

No vague wording - only numbers, diagrams, names of services, technologies, and tools. This is a technical document, so we avoid subjectivity.