Tasks

What this screen is for

The Tasks page is the queue for every household’s commitments. It loads a summary row per household (open, completed, and whether any work has aged) and fetches a household’s tasks only when you expand its row.

The rail at the top counts households with aged work and reads “Needs attention” when there are any, then shows open, completed and the stale threshold in days.

Stale and aged

Age is measured from when a task was created, not from its due date. A task becomes stale after the firm’s threshold, which defaults to fourteen days and can be set between 1 and 365 in Task settings. A household’s badge reads “Stale work” when any open task is past the threshold and “Aged work” when any open task is between seven days old and the threshold.

The seven-day boundary is fixed in the query, but the legend above the list reads “Attention after N days” with N as half the threshold, so the two agree only while the threshold is fourteen. A task’s own Stale or Aged label is the server’s, computed the same way; where the server gives none, the page recomputes it from half the threshold.

Due dates are shown as Overdue once past, then Today, Tomorrow, or the date, and a completed task reads Completed.

Filters and sort

Status filters to Pending, Done or Stale; Stale keeps households with any stale or aged work and, inside them, tasks past the threshold. Kind filters to General, Review, Fee consent, Client upload, File note or External; Priority to High, Medium or Low; Household to one household. Sort by offers Newest, Oldest task, Due date and Household with ascending or descending order. Only the Household sort reorders the household list; the other three apply to the tasks inside each expanded household, and the list itself stays alphabetical. The filters and sort are written into the page address, so a filtered queue can be bookmarked or shared.

Adding, completing and deleting

Add task takes a household, a description, an optional due date, a priority (medium by default), a kind (general by default) and notes, and records the source as manual. The floating quick-task widget on every adviser page posts to the same place. The household workspace’s Add task on the client book takes only a description and a due date.

The checkbox completes a task or reopens it. Completing a task queues a Teams message for the household when the firm has a Teams destination configured. Delete removes the task outright, and there is no edit control: a task with the wrong wording or date is deleted and re-added.

Each task row shows its kind, priority, Stale or Aged label, due status and a source icon. A task generated by the implementation plan also carries an “Open advice” link to the household’s advice page; no other source has a link.

Upload file note

Upload file note reads a written file note (PDF, DOCX or TXT, up to 25 MB) and turns its action items into tasks in bulk, with no AI involved. The parser looks for a heading such as “Action items:” and takes the bullet, numbered or checkbox lines beneath it at high confidence, and otherwise matches list lines by pattern at lower confidence. A date within three lines of an item becomes its due-date hint. The household is suggested from the file name when it shares a distinctive word with a household name.

The preview table lets you include or drop each item, shows its confidence (green from 90 per cent, amber from 80), and asks for a household and a priority per item. Create tasks writes the included items that have a household as tasks of kind File note with source filenote; an item without a household is skipped.

This is a different path from the Meeting Copilot, which reads a transcript and proposes each task on its own with a supporting quote, as the Meeting Copilot guide describes.

Where tasks come from

Source shown	Created by	Kind
manual	Add task here, the quick-task widget, or the client book	as chosen
filenote	Upload file note	File note
desktop_widget, teams, outlook	An integration key of that type	as sent
implementation	The implementation plan’s nudges and portal implementation steps	General, or Client upload for a portal upload
staleness	The account staleness sweep	Review
pack_impact	Budget night, when a pack change is material for a household	Review, high priority
document_publication	Publishing a document	General
portal_advice	A client’s advice decision in the portal	General
vesper	A portal change request, or a follow-up confirmed in the Meeting Copilot	Review, or File note for a meeting task

Task settings and integration keys

Task settings holds the stale threshold and the firm’s integration keys. The integration-keys block is for advisers and principals only — a key authenticates as the firm, so issuing and revoking one is firm administration rather than task work, and a paraplanner login is shown neither the block nor the keys. A key has a name, a type (Desktop widget, Microsoft Teams or Outlook) and one or more households, and is shown once at creation. A key can read, create and complete tasks for its households only; it cannot edit or delete a task, and a task it creates carries the key’s type as its source, and Revoke stops the key.

What this page does not do

• Age a task by its due date; only creation age drives Stale and Aged.
• Edit a task after it is created.
• Reorder households by anything but name unless Household is the sort.
• Assign a task to a person from this page; the assignee is set only by whatever created the task.