• Reading the Job Performance Tab: Plan, Actual, Drift

  The Job Performance tab reads Plan, Actual, and Remaining, then breaks the Job down by Deliverable drift and by service type, in effort and never in money.Few readers

• Plan Stepper: How to Build a Job Plan Step by Step

  The Plan Stepper builds a Job one step at a time, four steps for a Project and three for a Retainer, auto-saving as you go until you are ready to activate.Few readers

• Job Tasks: Assignees, Allocations, and Statuses

  Job Tasks sit inside Deliverables, and each person on a task gets their own allocation, so one task can hold several service types and one shared due date.Few readers

• Projects vs Retainers: Choosing the Right Job Type

  A Project is finite work with a Timeline and a Retainer is ongoing work in monthly cycles, and the Job type you choose shapes every planning step after it.Few readers

• Running Retainers: Monthly Cycles, Tasks, and Actuals

  A Retainer runs in monthly cycles, and each cycle is its own window with its own effort pools, tasks, and actuals, so looking at March shows only March.Few readers

• Activating a Job: What Happens When the Plan Locks

  Activating a Job opens time logging, unlocks the execution tabs, starts billing, and freezes your plan as the Original Plan you will be measured against.Few readers

• Deliverables: Status, Due Dates, and Confidence Explained

  A Deliverable carries a status, a due date, and a Confidence call, plus effort pools by service type that are budgets to watch, never hard ceilings.Few readers

• Job Lifecycle: Pending, Active, Completed, Archived

  A Job's lifecycle has four statuses: Pending plans for free, Active starts work and billing, Completed takes cleanup time, and Archived stops the bill.Few readers

• Change Orders: How to Add Scope to a Locked Job Plan

  A Change Order is the only way to add scope to an Active Job, layering hours on top of the frozen Original Plan instead of quietly rewriting it.Few readers

• Moving a Task Without Losing Its Time or History

  Move task sends a Job Task to another Deliverable or Job, and every hour ever logged against it moves too, so no history is lost and no total changes.Few readers