Glossary¶

These are the words dooer uses in its UI, emails, and docs. They are grouped by domain, not alphabetically — if you know the context (you're looking at the task board, or the feedback panel), scan that section first.

Tasks and projects¶

Task: The core unit of work in dooer. Every piece of work that needs to be tracked, assigned, and completed lives as a task.
Subtask: A task that belongs to a parent task. Subtasks inherit the parent's project. They have their own assignee, due date, and status.
Project: A named container that groups related tasks. Projects have their own statuses: PendingAcceptance, Planning, Active, OnHold, Blocked, and Completed.
Quick task: The short creation form. Requires only a title, an assignee, and a due date. Use it when the work is simple and well-understood.
Full Brief: The extended creation form. Adds a description, objectives, dependencies, and resource attachments. Use it when the work needs explanation before anyone starts.
Predecessor: A task that must be complete before the current task can begin. Set on the task's Details tab. dooer shows a warning if you try to start a task whose predecessor is not yet complete.
Dependency: The relationship between a task and its predecessor. When a task has an unresolved dependency, its status is Blocked.

Status and acceptance¶

NotStarted: The default status for a new task that has been accepted. The work has not begun yet. On the Kanban board this column is labelled "TO DO".
Working: Someone is actively working on the task right now. On the Kanban board this column is labelled "IN PROGRESS".
Paused: Work has started but stopped temporarily. The task is not abandoned — it will resume. Use this instead of Blocked when the reason is internal (the assignee is busy, not waiting on someone else).
Blocked: The task cannot proceed until something external is resolved — a predecessor is unfinished, or a Blocker feedback item is open. A blocked task sits in its own column on the board.
Complete: The assignee has marked the work done. If the task was a Full Brief, the assigner may still need to accept it.
Canceled: The task will not be done. It is kept in the system for history but removed from active views.
PendingAcceptance: A task lands here automatically when it is reassigned to a new person. The new person must explicitly accept it before it moves to NotStarted. Nothing lands silently on anyone's plate.
Acceptance: The act of the assignee confirming they take ownership of a task. Until acceptance happens, the task sits in the PendingAcceptance column.
Acceptance Signature: The timestamped record that the assignee accepted the task — stored on the task and visible in the Activity log.

Feedback¶

Bug: A feedback item that flags something broken or wrong with the deliverable. Raised inside a Full Brief task from the Feedback tab.
Clarification: A feedback item that asks a question about the deliverable. The work should not continue until the question is answered.
Blocker: A feedback item that stops the task from being completed. A Blocker must reference a dependency task ID. While any Blocker is Open or InProgress, the parent task's status is forced to Blocked.
Open: A feedback item that has been raised but not yet acted on.
InProgress: Someone is actively addressing the feedback item.
Resolved: The feedback item has been addressed and closed.
WontFix: The feedback item was reviewed and the team decided not to act on it. It is closed but kept for record.

People and roles¶

Assignee: The person responsible for completing a task. A task has exactly one assignee at a time.
Assigner: The person who created or delegated the task. On a Full Brief, the assigner is the one who accepts the completed work.
Owner: The person responsible for a project's outcome. Set when a project is created. Different from the assignees on individual tasks inside the project.
Sponsor: An optional stakeholder on a project — someone who has an interest in the outcome but is not doing the day-to-day work.
MEMBER: The default role for every new user. Members create and accept tasks, and can own projects.
MANAGER: Has direct reports. Can create users in their own team and view the Manager Reports screen for their direct reports.
DIRECTOR: Heads a department. Sees the full department tree in Manager Reports, can run bulk-import, and has access to the Audit Log.
HEAD: Top of the workspace. Sees every user, project, and report across the entire workspace. HEADs also approve invitation requests and manage trial accounts.

Scoring and priority¶

Impact: A number from 1 to 10 you assign when creating or editing a task. Higher means the task matters more to the outcome.
Criticality: A three-level label — Low, Medium, or High — that describes the urgency of a task. Combined with Impact, it determines where dooer places the task in the Priority Planner.
Q1 — DO NOW: Eisenhower quadrant 1. High impact, quick to complete. Do these today.
Q2 — SCHEDULE: Eisenhower quadrant 2. High impact, slow to complete. Block time for these — they drive long-term results but are easy to skip.
Q3 — QUICK WIN: Eisenhower quadrant 3. Lower impact, quick to complete. Do them if time allows after Q1 is clear.
Q4 — DEFER: Eisenhower quadrant 4. Lower impact, slow to complete. Defer, delegate, or cut.
5-day plan: The Priority Planner view that spreads your Q1 and Q2 tasks across the next five working days. dooer auto-places tasks based on Impact and Criticality. You can drag to reorder.

Workspace concepts¶

Workspace: Your organisation's top-level container in dooer. All users, tasks, projects, and notes live inside one workspace.
Department: A sub-group inside a workspace, managed by a DIRECTOR or higher. Departments set the reporting boundary for Manager Reports.
Area of Interest: A workspace-wide filter label you can attach to notes and tasks. Areas of Interest let you slice content across departments — they are not a hierarchy, just a tag.
Trial: A user account in probationary status. Trial users can use dooer normally, but a HEAD must approve them before they are considered full members. Managed from Settings → Invitations.
Sticky Note: A short, unstructured note you can pin to your Dashboard or attach to a project. Not a task — no assignee, no due date. The Dashboard widget that holds these is labelled Quick Notes.

Files¶

Brief Resources: Files attached at the project or Full Brief level to provide context before work starts — specs, design files, reference documents.
Files & Links: The section on a task's Details tab where you add attachments and URLs. Distinct from the Attachments tab, which shows every file attached to a task in one flat list.
Attachment: A file uploaded directly to a task. Limits: 25 MB per file, 100 MB total per task. Accepted formats: JPEG, PNG, WebP, GIF, PDF, plain text, CSV, XLS, and DOC.
OneDrive link: A URL pointing to a file in Microsoft OneDrive or SharePoint, stored on the task instead of uploaded. Useful for large files that would exceed attachment limits.

What's next¶

FAQ → Answers to the questions that come up most often.

Roles and permissions → The full permissions matrix — what each role can and cannot do.