Sari la conținutul principal
FreeThree checks for your projectUptime, accessibility, SEO and cookie checks for your project
Toate articolele

Running a website5 noiembrie 20265 min de citit

One place for every request about your website

Valentin ZsigmondFounder & Lead Engineer

The opening hours on your contact page are wrong. Someone notices on Monday and mentions it in the team chat. On Wednesday a colleague emails the developer about it, with slightly different hours. By the next week the chat has scrolled on, the email is one of many, and the page still shows the old hours.

Everyone meant well, and the request still had nowhere to live. This article is about what a request needs in order to get done, and how to give every request about your website one place.

Where requests go missing

Each of the usual channels loses requests in its own way.

  • Email keeps the request in one person's inbox. When that person is away, the request is away too.
  • Chat is quick, and by the next morning the message is three screens up.
  • A phone call or a meeting leaves no record at all. Two people remember two versions.
  • A shared spreadsheet is at least a list. The discussion about each line still happens somewhere else.

The signs are familiar. Nobody is sure who has the job. Two people do it, or nobody does. Someone writes "any news on this?" every few days. The change goes live and turns out to be wrong on a phone. A year later, nobody remembers why the page was changed.

What a request needs to be done well

Five things. None of them is technical.

One owner

A request with two owners has none. Others can help, and others can follow along, but one person is in charge and everyone knows who.

A tester

The person who made the change is the worst person to check it. They know what they meant to do, and they see that. Name someone else to look at the result before it is called done.

A test plan

A test plan is a short list of steps to try, with what should happen at each. It replaces "looks fine to me". For the opening hours it might be:

  1. Open the contact page. It should show weekdays 9 to 17.
  2. Open it on a phone. The hours should fit on the screen.
  3. Check Saturday. It should show 10 to 14.

Three steps, a minute's work. If the page shows "closed" for Saturday, step three fails, and the tester writes down what the page showed instead. The person in charge now knows exactly what is left.

A deadline

A request without a date gives way to every request that has one. Any date will do, even a distant one.

The history

Questions get asked and answered along the way: should the form go above the footer links, or below? If the answer lives in a chat, it is gone when you need it. Kept with the request, it is there for the colleague who joins next month, and for you a year later.

How Flow holds that

Flow is the Tilizy product for this. It keeps every request about a website in one list, from the first message to the finished change.

A request is a short message in your own words: what is wrong, or what you would like. You say whether it is a fix, something new or a question. No technical words are needed.

Every request has a state, so nobody has to ask for news. You see what is open, what is being worked on, what is waiting for your answer and what is done.

The five needs each have a place:

What the request needsWhere it lives in Flow
One ownerEvery request has one person in charge. Others can share the work or follow it. Followers get every reply, and someone you mention follows too.
A testerA tester can be named on the request to check the result.
A test planThe request carries the steps and what should happen at each. The tester marks every step as passed or failed. A failed step needs a note on what happened instead.
A deadlineA date on the request, with a warning a day before it passes, and a priority from low to urgent.
The historyReplies and decisions stay on the request. Every change is listed with who made it and when.

Every request belongs to a project, such as one of your websites. If you work for others, it belongs to a customer too. Projects and customers come with your Tilizy account, so Flow needs no other product.

What goes into the list is up to you: a fault a visitor reported, an idea from a meeting, or a finding from a scan of your website, which we describe in what one scan of your website tells you.

What the free plan includes

The whole tracker is free for one project and up to 3 people. That covers everything described above, and more:

  • a person in charge, followers and a tester;
  • test plans with passed or failed steps;
  • checklists, and requests grouped into bigger ones;
  • labels, deadlines and reminders;
  • a board or a list, with filters and search;
  • time tracking on every request;
  • links to the code changes and deployments behind a request, with where the change is live;
  • 1 GB of files.

There is one limit you should know about before you rely on it. The change history, the list of who changed what and when, is kept for 30 days on the free plan and then deleted. Your requests and replies always stay.

The Team plan costs €9 a month per project, excluding VAT, and includes 10 people across your organisation. It adds what matters once a customer depends on you: change history kept for good, 10 GB of files per website, internal notes your customer cannot see, answer-time targets, and compulsory testing, where a request cannot be resolved until every step of its test plan passes. Team can also be joined by Resolve, our AI, which does the work on a request and leaves the approval to you. We describe it in Hand the small jobs to an AI, and keep the last word.

Where the tool's job ends

Flow keeps the request. The work is still done by whoever looks after your website: your own team, your developer or your agency.

And a list only helps if requests go into it. The habit matters more than the tool. Agree on one rule with everyone who touches the website: if it is not in the list, it has not been asked. The first time someone answers a chat message with "put it in the list, please", it feels fussy. A month later nobody is asking for news any more.

Everything Flow does, and the two plans, are on the Flow page.

Scris de

Valentin Zsigmond

Founder & Lead Engineer

Now check your own project.

Add your project and see what it needs. The first three checks are free.