Move selected issues from the report into a single working list. Each row should include a URL, a specific problem, an assignee, and the next step. Otherwise, old findings can get lost when a new audit comes in.
You can keep the list in a regular spreadsheet or your task management system. reChecker provides check results; you organize assignees and deadlines yourself. There’s no need to copy the entire report into the spreadsheet—start with the work your team actually plans to do.
Record selected tasks with their sources
Below is a sample of three rows. It shows different work statuses:
| Task and source | Who takes action | Next step | How to complete it |
|---|---|---|---|
| The menu links to an old returns policy, audit 04.10 | Developer | Replace the URL after approval | Open the new page from the menu |
| The price on /services is outdated, owner’s check | Manager | Confirm the new price with the editor | Compare the published text with the decision |
| Card headings changed 03.10 | Website owner | Check two card variants | Confirm the correct values on both URLs |
Add the exact URLs and links to the reports for your tasks. An issue type without a URL is a reason to ask for clarification, not a complete task assignment. If the problem affects a group of pages, save several examples and note how they differ.
Verify a finding before creating a task. You can follow the steps for verifying an audit finding. If the result is unclear, record it as “needs investigation” rather than presenting an assumption as a defect.
Explain the order of work in one sentence
Write why one task should be done before another: “the returns policy can’t be opened from the main menu” or “the price needs to be updated before the ad campaign launches.” A priority number without an explanation is easy to forget.
Color-coding every row the same way won’t help with prioritization. Unavailability of an important page should be addressed right away; plan the remaining work based on its impact and the team’s capacity. See the article on audit priorities for general guidelines.
The assignee estimates the time required. A seemingly small item may involve changing a shared template and checking different variants. If investigation is needed first, set a deadline for its results; agree on a deadline for the fix afterward.
Specify what you’re waiting for and from whom
Replace “waiting for the client” with “Maria needs to confirm the price by October 6.” Replace “pending” with “the change is published; Sergey is checking two URLs.” Then the next person can see how to proceed.
If access is missing, name the person who controls it and specify what access is needed. If a task is deliberately postponed, record the decision and the reason. Don’t call this an exception a fix: the problem may remain even though the team has decided not to change it for now.
For a published task, assign a separate verification step. A new technical audit should include the relevant URLs and be run after publication. The automated audit covers up to 100 pages; the absence of an error elsewhere on the site does not confirm that the original page has been fixed.
Review the list by finishing work already in progress
At the weekly review, first look at changes that have been published but not checked. Next, review requests that are blocking further work. Then choose new tasks.
Check three rows: a new one, one waiting for a response, and a closed one. The new row should state a clear fact; the waiting row should name a person and the decision needed; the closed row should include the date and the result after publication. If everything is explained only in a long message thread, add the missing details to the list.
Example of a closed task: “06.10, /returns opens from the menu on the homepage and the card page; checked by Anna.” If the issue returns, add a new case and link it to this verification. The earlier result will be useful for comparison; there’s no need to delete it from the history.