In project management literature, the term "activity" is technically more precise — it refers to a discrete piece of work with a defined start and end. However, "task" remains the common term in practice.
Pro tip: A project manager should be conversant in both terms. In Consequent, we use "task" in the interface, but you'll encounter "activity" in formal PM methodologies and certifications.
Clear Deliverable
A task should produce a concrete result. "Design header component" is better than "Work on design". You should be able to objectively determine when it's done.
Estimable Duration
If you can't estimate how long something takes, it's either too vague or involves too much uncertainty. Break it down or add research time first.
Single Responsibility
Each task should represent one logical piece of work. If a task naturally splits into phases, create separate tasks.
A clear, action-oriented description. Start with a verb when possible: "Install ceiling tiles", "Review contract terms", "Deploy to staging".
How long the work takes, expressed in days and hours. Consequent uses hours as the fundamental unit — no fractions, no minutes. A "2.5 day" task becomes "2 days, 4 hours".
Note: Duration is the estimated work time, not the calendar span. Working hours per day are defined at the project level.
An optional constraint. If set, the task won't be scheduled before this date, regardless of dependencies. By default, tasks start as soon as possible.
An optional deadline. If the calculated finish date exceeds this, Consequent flags the violation visually — it doesn't silently block you.
A percentage (0-100) indicating completion. Update this regularly as work proceeds.
Work with a duration. Most of your tasks will be this type.
Zero-duration markers representing an instant in time: "Permit issued", "Go-live approved". Milestones can have dependencies and constraints just like tasks.
Parent tasks that contain child tasks. Their dates are calculated from their children. In Consequent, summary tasks are structural only and cannot be predecessors or successors — link dependencies to leaf tasks or explicit gate milestones instead.
Clear task structure makes schedules auditable. Explicit wait tasks replace hidden lag, and milestones expose intent instead of burying it in metadata.
Consequent keeps duration and constraints explicit so anyone reviewing the plan can understand why a task starts and finishes when it does.
Tasks alone don't make a schedule. Learn how to connect them with dependencies to model the real-world sequences and constraints of your project.
Creating Dependencies