Last updated: May 30, 2026
Tasks are the workhorse of Focal Point. They live either as personal tasks (just yours, no project) or attached to a project (your own or one you've been invited to). The Planner rolls everything into daily / weekly / monthly views; the Tasks tab gives you list and Kanban views per project.
Tasks created without a project go into your personal task list and are visible only to you. Tasks attached to a project follow that project's sharing — collaborators see them with you.
Every task in a project gets a stable, human-readable task key like SCB-29 or QAS-2:
Task keys appear in comments, the activity log, mentions, and links — they're how to refer to a task without paste-bombing an internal id. Type "QAS-2" anywhere it'll auto-link in the relevant surfaces.
Four levels: none, low, medium, high. Defaults to "none." Priority drives sort order in some Planner views and surfaces as a coloured chip on the task card.
Priority is independent from due date. A "high" task with no due date doesn't show up on today's view; a "none" task due tomorrow does. They're complementary, not redundant.
Due dates can be a calendar day ("due Friday") or a specific time ("due Friday at 3 PM"):
If you don't need the time, leave it off — calendar-day dates are clearer for everyone.
Tags are coloured labels you can attach to tasks for filtering and visual grouping. Two scopes:
Create a tag from the tag picker on any task. Tags can be assigned a colour at creation — the picker shows colour swatches.
A task can have any number of tags, mixed scope (one global + two project tags is fine).
Tasks can reference one another through typed relations:
Focal Point refuses to create a relation cycle (A blocks B, B blocks A) — it returns a clear error pointing at the offending chain so you can untangle it. Relations are scoped to tasks you have access to; you can't link to tasks in projects you're not a member of.
Every task has a comment thread. Comments are plain-text, attributed to whoever wrote them, and show up in the activity log + on the task card. When you reference another task by its key (e.g., "see QAS-2") in a comment, the key auto-links.
On shared projects, comments by collaborators show their avatar and name. The order is creation-time ascending — oldest at the top.
Every task keeps an activity timeline — a running log of what happened to it and when. Open a task and scroll to the Activity section to see it. The log captures the kinds of changes that matter for a shared workflow:
On a shared project each entry is attributed to the person who made the change, so the history reads as "who did what, when" — useful for catching up on a task other people have been working.
Open the Planner view (daily / weekly / monthly) or the Tasks tab and choose a sort:
Filters orthogonal to sort: Open (default), Completed, or All. Plus the per-project filter pills along the top.
If a task is in a shared project, you can assign it to any project member from the task detail. The assignee gets a notification (per their notification preferences). Re-assignment is fine; the activity log captures the change.
Personal tasks (not in a project) can't be assigned — there's no one else to assign them to.
The search bar at the top of any planner view searches tasks, notes, and projects. Tasks come back ranked by title and description match. Each result row shows the task key, project name, and tags so you can disambiguate without opening the task.
You can scope search by project via the filter pill below the search bar — useful when one project has many similar-sounding tasks.
That instant search is keyword-based — it matches the words you type (a task key like QAS-2 jumps straight to that task). Premium adds AI semantic search, which ranks by meaning rather than exact words — so "somewhere to stay in Rome" can surface a note titled "Trastevere apartment" even with no shared keywords. Reach for keyword search when you know roughly what it's called, and semantic search when you only remember the gist.
Open the task detail and tap the three-dot menu → Delete. The action is confirmation-gated and moves the task (plus its comments) to Trash. You have 30 days to restore it from Settings → Trash; after that the nightly cleanup hard-deletes it.
If you delete the parent project instead, every task inside it dies in the cascade automatically — you don't need to delete tasks one by one first. See Delete a single project.
null in places where a key would be. Edit one of those tasks once and it'll be assigned a key on next save.Was this helpful? Email support@milehighsoftwaresolutions.com with feedback, corrections, or questions we should add here.