01.CRITICAL PATH SCHEDULING

The schedule that
keeps itself honest

Tensara plans work on a real critical-path engine and keeps the plan current with updates from the people doing the work — reviewed, approved, and applied by the person who owns the date. Every date is computed. Every change is accounted for.

02.THE SYSTEM

Purpose-built for project controls. Tensara treats the schedule as a live working record — computed on CPM logic, updated at the source, reviewed by the people accountable for the date.

Computed, not curated

Forward pass, backward pass, total float, driving logic. The critical path is calculated on every change — never drawn by hand, never out of date.

Updated at the source

Progress arrives as tickets from the people doing the work. Review, approve, and the plan recalculates on the spot. Nothing changes silently.

Accountable by default

Every movement of the finish date traces to a decision — with a name, a reason, and a timestamp attached.

03.PLAN

Start with an AI draft, then prove it with CPM

Don't start from a blank grid. Seed activities, WBS, durations, and draft logic from the project context, then let Tensara's critical-path engine compute the path that actually drives the finish. AI accelerates the first pass; CPM keeps the plan honest.

  • AI-seeded first-pass schedules
  • WBS, calendars, lags, constraints, and reviewable logic
  • Float and driving path computed on every change
ACTIVITY NETWORK TF 0 = DRIVING

04.UPDATE

Progress is a paper trail

Field updates arrive as tickets against specific activities — remaining duration, percent complete, actual dates. The planner reviews and approves; approved changes recalculate the schedule immediately. The update cycle is measured in minutes, not meetings.

  • Propose, review, approve — in one queue
  • Bulk actions for update day
  • Author, reason, and timestamp on every change

05.STEER

Use AI to interrogate the schedule

AI schedule analysis reads the computed plan and turns it into a focused risk review: bottlenecks, fragile logic, duration concerns, and parallelism opportunities. The cockpit still ranks the finish-date drivers, so course corrections happen while they're still cheap, not at the month-end lookback.

  • AI findings tied back to affected activities
  • Risk drivers ranked by finish impact
  • Float fragility and logic risks surfaced before review meetings

06.IN THE BOX

6.1

Interactive Gantt

Drag, link, and inspect the plan with the driving path always in view.

6.2

Ticket workflow

Propose, review, approve — with bulk actions when the updates pile up.

6.3

Execution cockpit

Schedule health and risk drivers, ranked and readable at a glance.

6.4

WBS & calendars

Structure the work and model working time the way the job actually runs.

6.5

Budget overview

Cost alongside schedule, in the same record — not a separate spreadsheet.

6.6

Workbook import

Bring an existing plan in from a spreadsheet and keep moving.

07.START

One schedule.
Everyone on it.

Start from zero or import a workbook. Either way, the critical path is computed before your first coffee refill.