What should be specified in the technical specifications for website development
Posted: Sun Feb 02, 2025 6:21 am
It is better to include the wording "anything not specified is left to the developer's discretion" at the end of the technical specifications, since at the very beginning of the document it will be perceived negatively. If the technical specifications are written correctly, no one will object to such a phrase.
The technical task for website development is a task from the client, even if it is prepared by the contractor. Therefore, it should contain instructions for the contractor on what and how to do. Sometimes in the technical task you can see phrases like "the project will include this and this". Beware of such wording, as they are more reminiscent of some kind of notifications, while the technical task assumes tasks.
State the tasks clearly and precisely. After all, the main goal of the TOR is to ensure that there is mutual understanding between the client and the contractor regarding the upcoming project.
Vague and abstract formulations will journalist email list not help matters. Here are some expressions to avoid:
"The web resource should please the client." But what if he is not in the mood?
"A web resource should be easy to use." What does "easy" mean in this case?
"A web resource should easily withstand a huge traffic of visitors." What numbers were meant here? 10,000 users? 20,000,000?
"Content from experts." Well, there's no need to comment here.
What should be specified in the technical specifications for website development
Source: PeopleImages.com - Yuri A/ shutterstock.com
Look for ambiguous wording in the texts. If you find any, rework them. All tasks should sound as specific as possible.
Instead of “fast resource loading,” write that all pages of the site should load at a speed of more than 80 points when checked through the Google PageSpeed Insights service.
Replace the phrase "Heavy load" with "60 thousand users simultaneously".
"The list of articles is displayed on the main page" should be reformulated as "6 new articles are displayed on the main page".
Instead of “laconic and user-friendly design,” write “the subscribe button should look like this” and accompany the task with a picture.
That's all about the wording in the TOR. Now let's look at its structure.
Please provide general information
Everyone involved in development should have a clear idea of what kind of business the client has and who the target audience is. Indicate this information at the beginning of the technical specification.
You also need to write down the purpose of the web resource, briefly outline its functionality. Otherwise, you risk getting a blog instead of an online store.
Explain complex terms
The main thing in the technical specification is to compose it in such a way that it is clear to everyone what the result should be. If you have to use terminology that is new to the customer, explain to him in plain language what you mean (just don’t send him to Wikipedia pages):
The technical task for website development is a task from the client, even if it is prepared by the contractor. Therefore, it should contain instructions for the contractor on what and how to do. Sometimes in the technical task you can see phrases like "the project will include this and this". Beware of such wording, as they are more reminiscent of some kind of notifications, while the technical task assumes tasks.
State the tasks clearly and precisely. After all, the main goal of the TOR is to ensure that there is mutual understanding between the client and the contractor regarding the upcoming project.
Vague and abstract formulations will journalist email list not help matters. Here are some expressions to avoid:
"The web resource should please the client." But what if he is not in the mood?
"A web resource should be easy to use." What does "easy" mean in this case?
"A web resource should easily withstand a huge traffic of visitors." What numbers were meant here? 10,000 users? 20,000,000?
"Content from experts." Well, there's no need to comment here.
What should be specified in the technical specifications for website development
Source: PeopleImages.com - Yuri A/ shutterstock.com
Look for ambiguous wording in the texts. If you find any, rework them. All tasks should sound as specific as possible.
Instead of “fast resource loading,” write that all pages of the site should load at a speed of more than 80 points when checked through the Google PageSpeed Insights service.
Replace the phrase "Heavy load" with "60 thousand users simultaneously".
"The list of articles is displayed on the main page" should be reformulated as "6 new articles are displayed on the main page".
Instead of “laconic and user-friendly design,” write “the subscribe button should look like this” and accompany the task with a picture.
That's all about the wording in the TOR. Now let's look at its structure.
Please provide general information
Everyone involved in development should have a clear idea of what kind of business the client has and who the target audience is. Indicate this information at the beginning of the technical specification.
You also need to write down the purpose of the web resource, briefly outline its functionality. Otherwise, you risk getting a blog instead of an online store.
Explain complex terms
The main thing in the technical specification is to compose it in such a way that it is clear to everyone what the result should be. If you have to use terminology that is new to the customer, explain to him in plain language what you mean (just don’t send him to Wikipedia pages):