Concepts · Planning

The planner

The planner is how an organization runs its week in os.esy.com. It keeps four kinds of record, from the long-term bet down to what’s on today, and Esy checks the ones that can be checked. Everything here is an api.esy.com record: the dashboard shows it, and agents read the same thing.

From the bet down to today

PlanThe bet, each brand’s engine, the score
GoalsA number and a date, with a pace
CommitmentsWhat must happen, with proof
TasksThe next things you do

Read it top to bottom. The Plan says where the business is going and what it’s measured by. Goals are that measure, with a line to stay on. Commitments are the few things that move a goal and must happen on time, every day, every week, or once. Tasks are everything else you’ll do, filed under the goal they serve.

Three kinds of record, two tones

KindExampleDone whenTone
CommitmentThree news posts a day by 9am; the newsletter every ThursdayEsy sees the proof by the deadline (or you tick a step Esy can’t see)Firm
Goal1,000 newsletter subscribers by April 30The measure reaches the targetPace, explained
TaskReply to the agency that asked about pricingYou check it offGentle

Firm means a miss stays at the top of Home until it’s done or excused with a reason, and a deadline never moves on its own. Gentle means Esy mentions a task, never chases it; a task that keeps rolling over gets one offer to make it smaller, give it a time, or drop it.

Where you see it

SectionWhat it shows
HomeThe score board (today’s ring, points, level, perfect days, six weeks, badges), each brand as a lane, and the navy rail: what’s left today, the next deadline with a countdown, the must-dos and tasks you can tick there, and this week’s dated steps.
TodayThe critical checklist as chains you don’t want to break, the Timeline (today’s deadlines and the tasks you gave a time, on one clock), then To do.
PlanThe hierarchy: the bet, the score, each engine, this week’s course, the next moves. In design; it takes Goals’ place.
GoalsYour goals by horizon, each measured one with its pace. Becomes part of Plan.
DaysThe record, day by day: what got done and what was planned and is still open.

Scope: the organization and its brands

Every record belongs to the organization or to one of its brands (a project). The scope picker in the bar narrows every section to one brand, or shows them all. A new record files under the brand in scope; a brand with no project yet gets one the first time something is filed for it.

Tasks in a sentence or two

A task has a title, an optional goal, an optional day (scheduledOn) and time (scheduledTime, which puts it on the Timeline), and an optional deadline (dueOn). A task planned for an earlier day and not done rolls over to today and says how many days late it is. Move sends it to today, tomorrow, next Monday, a date, a time, or no day; Drop keeps it in the record as dropped, never deleted. Reference: Planning API.

Your goals and a worker’s goals are separate
Goals and tasks can also be assigned to a worker, which steers its shifts (Assigned work). The planner shows only your own: a worker’s directives stay with the worker.
In short
  • Four records, top to bottom: the Plan, goals, commitments, tasks.
  • Commitments are firm and checked by Esy; tasks are gentle and checked by you; goals have a pace.
  • Home, Today and Days are views of the same records, and agents read them through the API.