Project Management
A project represents an outcome that takes multiple steps, such as “Move into the new home” or “Launch the new website.” It keeps related work under one result and adds order, status, dates, and review.
Projects, Folders, Categories, and Sections
| Structure | Purpose | Can contain |
|---|---|---|
| Project | An outcome to advance and eventually finish | Sections, tasks, subprojects |
| Folder | A non-actionable organization container | Folders and projects |
| Category | A top-level area and display grouping | Folders and projects; descendants inherit it |
| Section | A stage divider inside one project | Tasks |
Example: Work (category) → Client A (folder) → Launch Website (project) → Launch Prep (section) → Configure DNS (task).
Projects and folders can form a hierarchy. A section must sit directly inside a project. Use a task—not a section—for something you need to check off as work.
Create a Project
Start with an outcome title that can eventually be judged complete. Add only the fields you need:
- Notes, category, and parent folder
- Project type
- Status, flag, or star
- Due date and review interval
- Tags, defer date, or duration where the platform editor exposes them
Then add one concrete next action. An outcome without an actionable step is likely to stall between reviews.
Project Types and Availability
Parallel
Direct tasks do not block one another, so several can be available together.
Sequential
Work advances in list order. Locus exposes the first task or descendant that can actually be performed; later siblings remain blocked.
Single Action List
A collection of related, independent actions that share a project container without forming a strict outcome sequence.
The project type applies to direct contents. A section or task can independently make its own direct children parallel or sequential. Locus calculates First Available through the entire hierarchy.
Project Status
- Active: participates normally in lists, Schedule, and review.
- Paused: temporarily not advancing; project contents become unavailable.
- Completed: the desired result has been achieved.
- Canceled: you no longer intend to pursue the result.
Completing a project completes its active tasks. Tasks that were already paused or canceled preserve that meaning. A cancellation or status cascade can affect a whole project tree, so read the confirmation first.
Dates and Hierarchy Constraints
Project dates form boundaries for descendants:
- Child plan and due dates cannot be later than corresponding parent dates.
- Child defer dates cannot be earlier than a parent defer date.
- Moving an item applies the new parent’s constraints.
If a child needs a different boundary, adjust the parent or change the hierarchy.
Starred Projects
Starring pins a frequently used or important project to quick navigation. It does not change priority, status, or availability. A flag is a separate property used to highlight an item itself.
Project Review
Each project can have a review interval. Active, non-folder projects whose review date has arrived enter Review Projects, with the oldest due review first.
During a review, ask:
- Is the outcome still valid and clearly stated?
- Is there at least one truly executable next action?
- Should any task be removed, paused, or marked Waiting For?
- Are project type and task order correct?
- Are dates, tags, and notes still trustworthy?
Completing the review advances the next review date. See Review & Logbook.
Duplicate a Project
Duplication is useful for templates and complex recurring processes. Choose a date strategy:
- Reset dates: create the structure without the original dates.
- Keep dates: copy dates unchanged.
- Smart offset: preserve relative spacing while shifting the whole structure to a new time base.
Review status, dates, action lists, and reminders on the copy before treating it as committed work.
Design Guidance
- Name a result: “Publish the Help Center,” not “Help Center.”
- If a project repeatedly has no next action, add one, pause it, or cancel it.
- Use a category or folder for an ongoing area that never completes.
- Use a section for project stages and a subproject for a work package with its own result and review cycle.