Tasks

Tasks lists every “task” the template hands out. For each one you say who does it by default, on which pages of a property or engagement it shows, and, if you want, when it applies. Every task of a published version is created in each new project at the starting stage, except a task that can repeat, as the section below explains.

In the template editor, select Tasks in the left menu. It comes after Fields.

Under Task list, one row per task. Under Add a task, a Name and Add task.

• A role: when a project starts, the task goes to every person who holds that role in the department and still works here.
• If nobody holds the role, or the row says Anyone (unassigned), the task starts with nobody on it. A manager puts someone on it from the project's page: Assign or reassign a task.

Tick Can repeat on a task that happens again and again in one project, such as a ticket for Tech / Development. A project does not get that task when it starts. Instead, a new task is made from it each time someone files one, and each of them is worked on its own: its stage, its people and its own values.

• A task that can repeat cannot wait for another task, and no task can wait for it. In Dependencies, Blocked by another task and Invalidated by another task refuse it, and the message at the bottom right names the task that can repeat.
• For the same reason, Can repeat cannot be ticked on a task that such a dependency already links to another task. The message names both tasks: remove the dependency first.
• Its other kinds of waiting, such as a document, a date or an approval, work as on any task.

A tag puts a task in a group with other tasks, such as all the appeal work. Select Tags on the task's row and pick tags from the company's list. A company administrator keeps that list on Task Tags.

• A tag belongs to the task in every version of the template, not to this version. So you can change the tags on a published version too, and a change reaches the work that is running now. On a published version, the line under Tasks ends with “this version is read-only, except task tags”.
• Revise keeps the tags of each task. A copy to a new template starts with no tags.
• Its tip says “Tags from the company's tag list. They belong to this task in every version of the template, so a change reaches running work at once, even on a published version.”

For each move, see Tag a template's tasks.

A task's departments are the departments that do it, and each one's numbers count the task. Select Departments on the task's row and pick from the company's departments. A department that is switched off shows (inactive) after its name, and can still be picked.

• A task can have more than one department, and it then counts for each. A task with none counts for the template's department, which the empty row names, followed by “(the template's department)”.
• Like a tag, a task's departments belong to it in every version of the template, so they can change on a published version too. A change reaches the work that is running now and the work that is finished. On a published version, a company administrator reads “this version is read-only, except task tags, departments and where tasks are done” under Tasks.
• Only a company administrator changes them. For anyone else, Departments is grayed out.
• Revise keeps the departments of each task. A copy to a new template starts with none.
• Its tip says “The departments that do this task. Each one's numbers count it; with none picked, it counts for this template's department. Company administrators choose them, for every version of the template at once.”

For each move, see Set the departments of a template's tasks.

Time on a task's row says how long the task takes, and where that time comes from. The Critical Path of a property, engagement or organization counts the days of its tasks with it. See The Workflow page of a record.

• The time comes from the first of three sources that has one: “measured in WarpCore (6 tasks)”, once at least five of these tasks finished in the last 90 days; “measured in FileMaker”, from the company's FileMaker records; or “an estimate”, from the company's study of its process. A task with none says No time yet.
• Nobody types a time. The company loads the times from FileMaker and the estimates, and WarpCore measures its own as tasks finish. A task carried over from FileMaker as done is not measured, even after it is reopened and finished again: it was finished before WarpCore.
• Like a tag, a task's time belongs to it in every version of the template. Revise keeps it. A copy to a new template starts with none.
• Its tip says “How long this task takes, as a record's Critical Path counts it: measured in WarpCore once five of these tasks finished in the last 90 days, else measured in FileMaker, else an estimate.”

Due date on a task's row says what the task's due date counts from, and how many days from it. Every running task of the version then shows its date on its card and in My Tasks. See The Work panel.

• Pick what the date counts from: Two-week notice, Closing date, First closing, Closing invoice, True-up invoice or Appeal deadline. None gives the task no due date.
• Appeal deadline is the state's, from the rule Legal enters for each state. A property in a state with no rule shows no due date. See Enter a state's appeal deadline.
• Type the days: a negative number is before that date, 0 is the day itself. The row then says the rule in words, for example “14 days before the closing date”.
• A due date belongs to the version, as a checklist does: you set it on a draft, and a published version shows it read-only.
• The date itself is worked out each time a screen shows the task, from the record's dates. A moved closing date moves the due date at once; a date the record does not hold yet gives no due date.
• A task counted from Closing invoice or True-up invoice is the client's payment: its due date is the invoice's terms. Once it has passed, the card adds the days past due, for those who see overdue invoices.
• A due date never stops anyone from moving the task.

A “condition” makes a task apply only when a project's values pass a test. Select Add a condition under the task, or Edit beside its count. The editor opens under the row:

A task whose tests fail is Not applicable on the project: see Why a task is “Not applicable”. When the version has no fields yet, the list says so once, with a link to Fields, and no task offers a condition.

A “checklist” lists the items to confirm while doing the task, one line each, in the order people read them. Each project's task shows the lines on its card, for the people on it to check one by one. Select Add a checklist under the task, or Edit beside its count. The editor opens under the row.

• Type a line, then press Enter or select somewhere else: it saves at once. Add a line adds one more, up to twenty. The arrows move a line up or down, and the trash icon removes it.
• A line cannot be empty, longer than 200 characters, or the same as another line of the task. The line says why under its box, and is not saved until it is fixed.
• The lines belong to this version, as the conditions do. You change them only on a draft. On a published version, Show opens them to read, and Hide closes them.
• Work that is running keeps the lines of the version it started from. A changed checklist reaches new work once a new version is published.
• A line that WarpCore's own record can answer shows where, in gray after its words: From and the place, for example From Cost approach. The ProperTax template load sets it; you cannot change it here. Move a line, or save the list with the same words, and the line keeps it. Reword the line and it is another line, with none.
• Revise and a copy to a new template both keep each task's lines, and where each is answered from.
• A checklist never stops a task: a line that is not checked holds nothing up.

Done on says where in WarpCore the task's work is done. Each running task of it shows that place behind Links on its card, as a link to the page on the task's record; My Route shows it on the task's stop. Choose one of these:

• Not set: the card shows no line. Nothing is guessed from the task's name.
• On the task card: everything the task asks is done on its card, such as Received or Approve. No line.
• On WarpCore pages: pick one or more pages, in the order the work goes. A property page is a module with one of its tabs, such as Assessments › Sale History, or a whole module, when the work spans its tabs. An engagement or organization page is named under its menu's heading, such as Engagement › Legal. Tick Done in Section Review when the task's sections are signed off in the review panel.
• Outside WarpCore: type the place in words, such as a call with the client. The card names it, with no link.
• Not in WarpCore yet: the work needs a screen WarpCore does not have yet. No line, until it does.

• Like a task's departments, its place belongs to it in every version of the template, so it can change on a published version too, and the change reaches the work that is running now. Revise keeps it; a copy to a new template starts with none.
• Only a company administrator changes it. For anyone else, Done on is grayed out.
• It is not Shows on. The line under the control says “Where this task’s work is done; its card links there. Shows on is where the card itself appears.”
• The pages carry the menus' own names, so a renamed tab reads the new way on every card at once. A page the menus no longer list shows under No longer in the menus, and the card leaves it out: pick its new place.
• On the ProperTax templates, the template loader sets each task's place from its own list, and a run puts back what that list says.

• Add a task: type its Name and select Add task. Set the rest after.
• Rename a task, describe it, choose who does it by default, and choose the pages it shows on.
• Tick Can repeat on a task that is filed again and again, such as a ticket.
• Tag a template's tasks, on any version.
• Set the departments of a template's tasks, on any version, if you are a company administrator.
• Say where each task's work is done, on any version, if you are a company administrator: Where a task's work is done.
• Make a task depend on a value.
• Give a task a checklist, on a draft: A task's checklist.
• Then say what each task waits for, in Dependencies, and where it sits on a board, in Task grid.

A department manager or a company administrator changes the tasks of a draft, and the tags of the tasks of any version. Only a company administrator changes the departments of the tasks, and where their work is done, on any version. Anyone with a role in the department can read them; for anyone else, Tags is grayed out, and Departments and Done on are grayed out for everyone but a company administrator. Everyone who can read the tasks sees each one's Time, and nobody changes it here. On a published or retired version, the rows are grayed out except Tags, Departments and Done on, Add a task is not shown, and a task with conditions shows Show in place of Edit.

• Two tasks of one version cannot share a name.
• Deleting a task asks first. It also takes away what the task grid holds for it. Projects already running keep the task: the change is to the draft only.
• Tasks are listed in the order they were added. They do not belong to a stage: every task starts at the starting stage and moves on from there.
• A task can have up to ten tests. When there are ten, the editor says “Ten conditions is the most one can have.”