Task Management

How work is modeled in Based, and why it looks a little different from Linear, Notion, or Asana.

Three primitives

Based represents work with three primitives: entities (the data — tasks, projects), pages (places to put content and data views), and views (different ways to see the same entity collection — Table, Board, Calendar, Gantt).

A single Task can appear on a board grouped by status, on a calendar by target date, and on a gantt chart by start/end — it is always the same record underneath.

Why Based is different

Linear is opinionated about workflow. Notion is opinionated about pages. Based is opinionated about data portability: every entity lives as JSON in a bucket you control, and the views are just one consumer of that data.

That means you can start with the Project Management template, delete everything you don't like, and keep adding fields as your process evolves. The data stays yours.

The Project Management template

When you create a base and pick Project Management, Based provisions:

  • Initiatives — goal-oriented pushes with a target date
  • Workstreams — perpetual areas of work
  • Cycles — time-boxed sprints
  • Tasks — the actual units of work
Tasks can live under a project, a cycle, or another task. The hierarchy is up to you — Based doesn't force a single shape.

Further reading

Task Management — Based Docs