Task Work View

The Work view

Everything a task needs you to do, in one place - the day it is for, how far along it is, its instructions, the Knowledge procedures it follows, its checklists and the forms it needs, with one Complete button.

Asked for in #190: "open the task and complete that work in one place". Design: Task work view - design.

---

Where it is

Task window	The Work view is
Large window, tabs layout	the Work tab - and a task with work in it opens on it
Large window, two columns	the top of the wide column
Side panel	a section in line

It appears when at least one of Checklists on tasks, Forms on tasks or Procedures on tasks is switched on (Tasks → Settings → Checklists). A task with none of them looks exactly as before.

Open here on the Work tab decides whether tasks with work in them open on that tab. It is your own preference; untick it and tasks open on Details as usual.

---

What it shows

• The day it is for - for an occurrence of a repeating task, the date it was created for.
• Progress - 3 of 5 done, counting every checklist step and every required form.
• Complete - moves the task to your first closed status, asking the same questions as the status box: who else is on it, and whether required work is still outstanding. Once it is done, the head says so.
• Instructions - the task's description, read-only (tabs layout; in the other layouts it is already on screen).
• Procedures - Knowledge articles, read in place (below).
• Checklists - as before, and each step now shows its description from the checklist template.
• Forms - as in Forms on tasks, and Fill now opens the form in place, inside the Work view. Open in a new tab is still there if you want more room. Saving or submitting updates the task at once.

---

Procedures

With Procedures on tasks switched on, a task can reference Knowledge articles as its procedure: type in Add a Knowledge article as a procedure… and choose one. Each is shown in place, with its version and an Open link to Knowledge.

• Knowledge's own access applies. You can only add an article you can read. Someone who may not read it sees A procedure you do not have access to - not its title, not its text.
• Repeating tasks: every new occurrence follows the same procedures.
• The text is kept. When an occurrence is completed (or skipped), each article's title and text as they stood at that moment are kept with it, and the procedure says Completed against version 4. Editing the article afterwards never changes what an earlier occurrence was done against. This matters because an ordinary save in Knowledge changes an article in place - only save as a new version keeps the old text - so a version number alone could not promise the words.
• The same text is stored once, however many occurrences were done against it.

In the evidence report

Each occurrence lists its procedures and the version it was completed against. A Procedures used section at the end shows each kept text once, with a short fingerprint (sha256) - to anyone who can read Knowledge; to anyone else, it says the text is kept but not shown. The attachments and comments CSV lists each procedure with that fingerprint.

---

Follow-ups

When a check finds something to fix, Follow-ups in the Work view connects the fix to the check.

• Create a task or a ticket with a title. Follow up on a failed checklist step, or on a submitted form, fills in where it came from.
• Link an existing ticket (by its number) or task (TASK-number) instead.
• Each follow-up shows whether it is still open. One you cannot see is shown by number only.
• A follow-up ticket is raised by you as its requester - as when you raise one by hand - assigned to you, in the task's company. You need access to Tickets and an email address on your account.
• Pressing Create again after a dropped connection does not make a second one.

Completing the task while a follow-up is open is a setting, Tasks → Settings → Evidence → An open follow-up when the task is completed: allowed (the default - the check was done and recorded; the fix carries on), ask first, and record it, or refused until the follow-ups are closed.

Follow-ups are in the task's history and, for repeating tasks, in the evidence report and its CSV.

---

What a repeating check covers, and when it is due

Two settings on a repeat (in the task's Repeats section) describe a check rather than a chore:

Setting	Options
Each occurrence checks	Nothing in particular (default) · The day it is for · The day before (last night's backups, say) · Everything since the previous one
Each occurrence is due	On the day it is for (default) · Some days later · The next working day (Monday to Friday)

So a daily backup check, every day including weekends, set to check the day before and be due the next working day: Saturday's occurrence checks Friday night, and is due on Monday. The Work view says for Saturday · checks Friday.

In the evidence report that occurrence is on time if it is done on Monday and late if it is done on Tuesday - the report judges against the due date the occurrence was created with, so the weekend is not counted as rescheduling. Each row shows the period checked and that due date, and the occurrences CSV has both.

---

Answers that count as an exception

In the form designer, each option of a choice question (radio, dropdown, checkboxes) has an Exception tick. Tick Warning and Failure on a backup check's Result, and a task form answered that way is listed among that occurrence's exceptions in the evidence report - beside failed checklist steps, counted in the summary - and in the occurrences CSV. Someone who may not read the form's answers sees that an answer counts as an exception, not which.

Completing the task still means the check was done and recorded: a Failure stays a Failure.

---

Related

• Forms on tasks · Repeating task evidence · Checklists and SOPs
• Task work view - design (#190) · Developer guide