Working with the Schedule Editor
The schedule editor opens the live schedule in BeOnTime in the working area — next to the chat. It is not an image or a copy: it is a plan editor fully compatible with MS Project — you open and edit your MS Project plan, and the agent works in the same schedule under your control.
Distinguish two things: /plan gantt creates a planning document (see Schedule planning); the schedule editor is the live plan you manage day to day.
How to open a schedule
Tell the agent which project and which schedule — it will find the available options and open the one you need in the working area. If a schedule is already open, the agent continues with it.
On the schedule you can see: tasks (and summary rows for groups), durations, date constraints, dependencies, and assigned resources.
What the agent can do
| Action | What it looks like |
|---|---|
| Read the plan | Answers questions about dates, dependencies, and load — from the current state |
| Change durations and dates | Edits tasks, including constraints ("start no earlier than", "finish exactly on a date") |
| Add and restructure tasks | New tasks, nesting, ordering; dependencies between tasks |
| Work with resources | Assign and unassign people, change allocations, maintain the project's resource catalog |
| Show a snapshot | A PNG snapshot of the schedule — into the chat or into documents |
How the review works: "apply first, then verify"
The schedule is the one surface where the mechanics are reversed: the agent applies the edit to the live schedule immediately, and you decide whether to keep it or revert it.
- The edit appears on the schedule at once: recalculated bars and dependencies.
- Each edit is marked with a mark on the task row (or resource row):
- Accept — the edit is locked in as yours;
- Revert — the value returns to the previous one (an added task is removed);
- Accept/revert all — a batch decision for all open marks.
- While marks are open, you keep working with the schedule as usual: your edits are never restricted.
- Marks live with the plan: close the working area — they are saved and wait for your decision.
This is deliberate: a schedule is a fast-recalculating model, and a "proposal without applying" would be useless (you could not see how the edit affects the finish date). You see the real effect and then decide.
Resources
- The project's resource catalog is visible on the schedule; the agent maintains it: adds, renames, reorders.
- Assignment — to a task, with an allocation: 100% means the task is entirely on one person.
- Summary rows (task groups) can carry their own assignments — that is extra work over the whole block (e.g., PM supervision), not a replacement for task-level assignments. The same people on a summary row and on the tasks is a double count of work.
- A resource's load is visible on the schedule: the agent can show overcommitment and propose a shift.
Date constraints and progress
- Constraints: "as soon as possible", "start no earlier / no later than", "finish no earlier / no later than", "exactly on a date" — with the date.
- Dates are precise, to the minute; the agent works with them without rounding.
- A task's progress (percent complete) is updated by the agent on actuals; after the update, verify visually that the bar shading on the schedule matches.
Collaboration and security
- Work runs in your account: the agent acts with your permissions and does not bypass organizational limits.
- Sharing: schedules can be shared with colleagues in the organization — access is controlled by your system.
- The document of record is your schedule database: everything applied and accepted lives where you manage schedules.
Typical scenarios
- Recalculation after a deadline change: "The contract shifted the finish by two weeks — recalculate the plan and show what breaks."
- Staffing: "Assign the developers to the release tasks so nobody is overloaded."
- Preparing for a status meeting: "Prepare a recalculation for tomorrow's meeting — I will review and accept."
- Day-to-day upkeep: "Close the finished tasks, move X, refresh the dependencies."
Where to continue
- Schedule planning — how the plan is built from tickets and estimates.
- Daily operations: walkthroughs and meetings — the daily walk with the plan in mind.
- Status snapshots and change analysis — monitoring against the baseline.