How Jot works.

Create an account, then start a project three ways: from scratch, by importing a plan (CSV or Excel), or by describing it in a sentence and letting Jot draft the structure for you.

Then jot your first action — a title and a due date is all it takes. Everything else (numbering, scheduling, linking) the platform fills in around you.

Every project is a work-breakdown structure: numbered rows (1, 1.1, 1.2…) that nest into phases. Milestones are zero-duration markers shown as a diamond on the timeline.

View the same plan four ways — Table for editing, Gantt for the two-tone timeline, Split for both at once, and Board for a status-grouped Kanban. Pick whichever fits the moment; they share one selection.

Actions are the unit of work under each WBS row. Capture is two fields; add criticality, a checklist of "needs", estimates, and dependencies when you have them — never before.

Link actions as predecessors and Jot computes the critical path and warns you before a date slips. An action moves open → in progress → done; on the Board you can drag it across columns.

Each person carries a load index that blends how much is in flight, how heavy it is, and how fragmented across projects it is. It reads on a calm-to-overloaded band, shown as a gradient ring.

The Effort page breaks your own load down and shows it per project. Managers see team capacity on the Team page — everyone’s ring at a glance, so overload is obvious before it bites.

Open a teammate and ask a plain question — "What is Lily doing this week?", "How busy is Lily?" — and Jot answers from their live workload in a sentence or two, instead of handing you a calendar to decode.

Answers are grounded in the projects you share with that person; nothing outside your reach is ever used.

Three roles per project: Member, Group Leader, and Manager. Members own and run their own work; Group Leaders and Managers gain oversight — team rollups, cross-department alerts, and approvals.

Permissions are enforced in the API and the database, not just the interface, so the tenant boundary and role checks hold no matter how a request arrives.

Bring an existing plan in from CSV or Excel — Jot maps rows to the WBS, preserves numbering, and flags anything it could not place so you can fix it in one pass.

Start free on the Solo plan. Team adds unlimited projects, roles, OBEYA rooms, predictive warnings, and integrations; Enterprise adds SSO, on-premises options, and a security review.

See current pricing on the pricing page. Billing is per user, monthly or annual.