“What are the agents running on Thursday?”
Work for agents sits in a backlog with no days on it. Nobody can say what runs when, or what lands on the same morning.
Scheduled AI agents: Plan what your agents execute, and when.
A ConvOps week and month board for what your scheduled AI agents execute, sized to what your workspace actually finishes. Spread work before its deadlines, plan next week in one pass, and let each item start itself on its day.
capacity = points done per week, last 4 weeks · no history: unknown, never 0
to plan · 2 items with no day
Mon 26 Oct
4 / 10
- Reconcile vendor accounts
- Pull access-review evidence
Tue 27 Oct
8 / 10
- Refresh outerwear pages
Wed 28 Oct
4 / 10
- Draft market brief
- Account research: renewals
Thu 29 Oct
3 / 10
- Article: pricing explainer
Fri 30 Oct
0 / 10
to plan · 2
0 · unknown
- Variance notes for close
- Translate onboarding guide
in short
How do you plan what scheduled AI agents execute?
ConvOps Plan is a week and month board where a team decides what its agents execute and when, sized to workspace capacity, and can start work on its planned day.
ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.
key facts · october 2026
- The week board shows days in lanes: by project, by executor, or one flat lane. The month view links each day to its week.
- A tray holds the Now and Next work that has no day yet. Drag an item onto a day, or place it from the keyboard.
- Capacity is the average number of points your workspace finished per week over the last four weeks, with S, M and L worth 1, 3 and 8. With no history it reads unknown, never zero.
- Spread puts each item of a batch on the least-loaded working day on or before its deadline. Preview it as a dry run, which shows each day's points and warns when the week goes over capacity. It is all or nothing: if any item is refused, the whole spread is refused and nothing moves.
- A planned task can start on its own on its day, at the time you set, in the task's time zone, on the executor you name.
- Schedules fire on a cadence (once, every few minutes or hours, daily, weekdays, weekly, monthly) or a custom recurrence rule, each in its own time zone, and show their next five fires before you save.
- Upcoming schedule fires appear on the board next to the planned work.
best for
- Teams whose agents carry a week of work and need to decide what runs on which day.
- Audit preparation, due diligence and launch work with deadlines, spread over the week against real capacity.
- Teams across regions that want each run at a local hour.
not for
- Rostering people. Plan schedules the work your agents execute.
- A Gantt chart with dependencies between items. The board places work by day.
updated
the problem
Nothing shows what runs on Thursday, or whether it fits.
Work for agents waits in a backlog with no days on it. The overload shows up on the deadline, and a schedule that drifted an hour leaves no trace.
“Will all of this fit before the deadline?”
The plan assumes a week the team has never finished. The overrun shows up on the deadline, not on the Monday before it.
“Why did the 08:00 run start at 07:00?”
A schedule kept in UTC drifts an hour when the clocks change, and a run that could not start leaves no trace.
board
A week board with a tray of unplanned work.
Days by lanes, grouped by project, by executor or flat. Work with no day waits in the tray until you drag it onto one.
Mon 26 Oct08:00 market brief
6 / 10
- Article: pricing explainer
- Reconcile vendor accounts
Tue 27 Oct08:00 market brief
9 / 10
- Account research: renewals
- Refresh category pages
Wed 28 Oct08:00 market brief12:00 stock check+1
3 / 10
- Article: onboarding guide
Thu 29 Oct08:00 market brief
4 / 10
- Pull access-review evidence
- Variance notes for close
Fri 30 Oct08:00 market brief
11 / 10over by 1
- Draft analyst brief
- Article: release recap
to plan · 3
0 · unknown
- Translate holiday FAQ
- Audit supplier contracts
- Tag support themes
- Week and monthThe week shows days by lanes: by project, by executor or flat. The month counts each day's work, and each day opens its week.
- A tray for work with no dayOpen tasks and bugs from Now and Next, up to 500 shown with the true count. Drag one onto a day, or use Place here from the keyboard.
- Slipped work is flaggedSlipped and late items are marked on the board. Upcoming schedule runs show on each day: two, then a count.
- Unplan cancels the runTake an item off its day and its auto-run is cancelled with it.
example · content
A content calendar the agents work from
Each article sits on its publish day in a lane per publication, and starts itself at 07:00 on that day.
week board · lanes by project · auto-run
example · financeenterprise
Quarter-end close on the month view
Reconciliations, accruals and variance notes are dated up to close day. The month counts each day, and slipped items are flagged before the close.
month view · planned days · slipped flags
example · agencyenterprise
Client work by executor
Lanes by executor show what each executor carries each day, and the recurring client reports sit on the same days as chips.
lanes by executor · schedule chips
example · data operationsenterprise
A 40-batch records migration
Forty migration batches wait in the tray with no day. The tray shows the true count, and each batch gets a day when someone places it or a spread does.
tray · Now and Next · place or spread
example · software delivery
Release prep without a stale run
Drag a fix onto Thursday and it moves to Now. Take it off again and its auto-run is cancelled with it.
placement · Now cap · unplan cancels auto-run
Work that comes in phases fits the board as it is: the ConvOps implementation plan template turns an approved plan into one child task per phase, and each phase task can go on its own day.
capacity and spread
Capacity from what you actually finished.
Capacity is what your workspace completed per week over the last four weeks. Spread work onto the least-loaded days before each deadline, and see the overrun before you commit.
6 items to spread · size first
Mon 2 Nov
1 / 10
- Tag new arrivals
Tue 3 Nov
4 / 10
- Store hours update
- Fix feed errors
Wed 4 Nov
0 / 10
Thu 5 Nov
4 / 10
- Supplier FAQ refresh
- Banner copy check
Fri 6 Nov
3 / 10
- Weekly trading notes
to plan · 6
0 · unknown
- Refresh outerwear pages
- Rewrite gift-guide copy
- Audit discontinued SKUs
- Update size charts
- Regenerate alt text
- Check promo banner dates
- Measured, not estimatedThe average points completed per week over the last four weeks. S, M and L count 1, 3 and 8; unsized counts as M.
- Unknown, never zeroWith no history, capacity says unknown. Weekend days count at a quarter of a weekday.
- Least-loaded day firstA spread fills the least-loaded working day on or before each deadline, biggest items or earliest deadlines first.
- All or nothingPreview it first. If any item is refused, the whole spread is refused and nothing moves.
example · data operationsenterprise
Forty batches over two weeks
A dry-run spread places the forty migration batches on the least-loaded days before cutover, shows each day's points and warns when a week goes over capacity, before anything is committed.
spread · dry run · week over capacity
example · legalenterprise
Due diligence that lands whole
A hundred and twenty document reviews across legal, financial and IT lanes, with over capacity set to refuse. An overbooked spread is refused whole, so no workstream is half planned.
lanes by project · over capacity: deny · all or nothing
example · healthcareenterprise
A new revenue-cycle team
With no finished weeks yet, capacity reads unknown instead of zero, so the first plan is not told it has no room. Weekend days count at a quarter.
capacity · unknown, never 0 · weekend factor
plan next week
Plan next week in one pass.
Review what slipped, choose against capacity, confirm. Three steps and one commit, and the dry run says what it found before anything is written.
reviewslipped: carry or tray
chooseagainst the meter
confirmdry run, then commit
- Slipped work firstEach slipped item carries over to next week or goes back to the tray.
- A meter while you choosePoints chosen against next week's capacity, with over by a number shown before you commit.
- A dry run, then one commitThe dry run reports over capacity, the Now cap and deadlines before the week. A refusal stays in the dialog with its reason.
example · complianceenterprise
A Friday review for audit prep
Each Friday the audit lead plans next week's evidence collection: slipped requests first, picks against the meter, a dry run with spread order set to deadline first, one commit. Each item then starts at 06:00 Europe/Berlin on its day.
Plan next week · capacity meter · deadline-first spread · auto-run
example · sales
Account research before the pipeline review
Sales operations picks next week's account research against capacity, so every brief has a day before the review it feeds.
Plan next week · deadlines · spread
auto-run
Work that starts itself on its day.
Give a planned item a start time and an executor. On its planned day, at that time in the task's time zone, ConvOps dispatches it.
000306091215182107:0009:3007:0007:00
22:30sun · Europe/Madridnight window
schedulesEurope/Madrid
- 07:00Article: pricing explainerplanned Mon · 07:00 · cloud-contentnot today
- 09:30Account research: renewalsplanned Tue · 09:30 · cloud-researchnot today
- 07:00Article: onboarding guideplanned Wed · 07:00 · cloud-contentnot today
- 07:00Article: release recapplanned Fri · 07:00 · cloud-contentnot today
next: Article: pricing explainer in 8h 30m
- A day, then a timeA planned day is a date. Auto-run adds the start time, in the task's time zone.
- On the executor you nameThe executor is always set explicitly. Custom-runner executors are refused for auto-run.
- Finished work stays finishedIf the task is done before its time comes, nothing is dispatched.
- Inside a run, it countsAn auto-run set from inside a run counts against that run's dispatch limit.
schedules
Schedules that keep local time.
Repeat work every few minutes, hourly, daily, on weekdays, weekly, monthly, or with a repeat rule. Each schedule has its own time zone and a preview of its next runs.
example · treasury · a market-open briefing per desk
000306091215182108:00
22:30sun · Asia/Tokyonight window
schedulesAsia/Tokyo
- 08:00Market-open briefingWeekdays at 08:00 · Asia/Tokyonot today
next: Market-open briefing in 9h 30m
08:00 local = 23:00 UTC, the day before
000306091215182108:00
22:30sun · America/New_Yorknight window
schedulesAmerica/New_York
- 08:00Market-open briefingWeekdays at 08:00 · America/New_Yorknot today
next: Market-open briefing in 9h 30m
08:00 local = 12:00 UTC, 13:00 from 1 Nov
Every Mon at 07:00America/Chicago
next 5 runs
- Mon 26 Oct 07:0012:00 UTC · -05:00
- Mon 2 Nov 07:0013:00 UTC · -06:00clocks changed 1 Nov
- Mon 9 Nov 07:0013:00 UTC · -06:00
- Mon 16 Nov 07:0013:00 UTC · -06:00
- Mon 23 Nov 07:0013:00 UTC · -06:00
recent
Mon 19 Oct 07:00refused: executor missing · logged as a blocked activity · schedule still enabled
- Cadence in plain EnglishEvery 1 to 59 minutes or 1 to 23 hours, daily, weekdays, weekly on chosen days, monthly on day 1 to 31, once, or a custom RRULE. Each builder cadence is described back in words; a custom RRULE is shown as written.
- A zone per scheduleEach schedule has its own IANA time zone and keeps local time across daylight-saving changes.
- The next five, before you saveThe preview lists the next five runs in local time and UTC. A rule with no future run is refused.
- Refused, logged, still enabledA run that cannot start is logged with its reason as a blocked activity. The schedule stays on, and its issue links to the fix.
example · financeenterprise
A management report on day 1
A monthly schedule on day 1 at 08:00 Europe/London creates a fresh report task each month, so every month keeps its own record.
monthly · day 1 · new task per run
example · vendor riskenterprise
One quarterly review, one history
A custom repeat rule wakes the same vendor-review task every quarter, so its notes and runs stay on one record. A daily schedule creates a new sanctions-list check each morning.
custom RRULE · wake · daily new task
example · supportenterprise
Triage that follows the sun
Three weekday schedules at 08:00 in Singapore, Dublin and Chicago run one triage workflow, each on its own local morning.
weekdays · a zone per schedule
example · data operations
A one-off cutover at 02:00
A once schedule starts the cutover at 02:00. If it has not started 15 minutes later, the Schedules page flags it overdue.
once · overdue after 15 minutes
under the hood
How the board decides.
Capacity, the spread, auto-run and schedules are plain rules over workspace settings, readable from the app, REST and an AI client.
Capacity is arithmetic
Capacity is the average points completed per week over the configured weeks. Points come from size, unsized items count as M, and a week is 5.5 units: five weekdays and two weekend days at a quarter each. It is one figure for the whole workspace.
payload
plan.capacity_weeks 4
plan.points_s|m|l 1 / 3 / 8
plan.unsized_as M
plan.week_units 5.5
plan.weekend_factor 0.25A spread is all or nothing
Each item goes to the least-loaded working day on or before its deadline, in the configured order. A dry run returns where each item would land without writing. If any item cannot be placed, the whole spread is refused. The over-capacity setting decides whether an overbooked spread is allowed, warned about or refused.
payload
POST /api/v1/plan/spread dry run or commit
plan_manage commit_spread the same from an AI client
plan.spread_order size_first | deadline_first
plan.spread_weekends false
plan.spread_over_capacity allow | warn | denyAuto-run is one deferred dispatch
A planned day is a date. Auto-run adds a time, and ConvOps dispatches the task at that day and time in the task's time zone through one deferred dispatch. The executor is named explicitly and custom-runner executors are refused. A task already finished by then is not dispatched, and the reason is auto_run_stale.
payload
PUT /api/v1/plan/auto-run/{task_id}
DELETE /api/v1/plan/auto-run/{task_id}
plan_manage set_auto_run | clear_auto_runSchedules: a rule, a zone, a record
A cadence kind is described back in plain English, a custom RRULE is shown as written, and runs are expanded in the schedule's IANA zone, so daylight-saving gaps and overlaps are handled. A rule with no future run is refused at create. A refused run creates nothing and writes one blocked activity per occurrence. Run now does not advance the cadence.
payload
schedules_read get | summary | upcoming | runs | preview
schedule_create | schedule_attach | schedule_update
schedule_list | schedule_delete | schedule_trigger
POST /api/v1/schedules/preview next 5 runs, UTC and localquestions
Plan and schedule questions, answered.
What is Plan in ConvOps?
Plan is the ConvOps week and month board where a team decides what its agents execute and when. Tasks with no day wait in a tray until someone places them on a day. Capacity comes from what the workspace completed over the last four weeks, a spread fills the least-loaded days before each deadline, and a planned item can start itself at a set time on its day, on the executor you choose.
How do I schedule an AI agent to run automatically?
Open Schedules in ConvOps and create a schedule: choose whether each run creates a new task or wakes an existing one, then set the cadence, the time zone and the executor. Cadences run from every few minutes to monthly, or a custom repeat rule. ConvOps previews the next five runs before you save. For one-off work, place the task on a day on the Plan board and turn on auto-run with a start time.
Who is ConvOps Plan for?
ConvOps Plan is for teams that hand recurring or deadline-bound work to AI agents and need to decide what runs on which day: operations, finance, compliance, content, research and engineering teams. It fits when the work is bigger than one chat, such as a quarter-end close, an audit evidence list or a content calendar, and when the team wants to see a full week before committing to it.
How does ConvOps know how much work fits in a week?
ConvOps measures capacity from what your workspace completed: the average points done per week over the last four weeks. Sizes S, M and L count 1, 3 and 8 points, unsized items count as M, and weekend days count at a quarter of a weekday. Capacity is workspace-wide. With no history yet it says unknown, never zero, so a new team is not told it has no room.
Is there an AI tool that can create schedules?
Yes. An AI client connected to ConvOps can create, update, list and trigger schedules with the schedule tools, and read previews and upcoming runs with schedules_read. The same rules apply as in the app: every schedule has a cadence and its own time zone, and a rule with no future run is refused. Inside an isolated run, creating or changing schedules stays off unless that environment grants it.
What happens when a scheduled run cannot start?
ConvOps refuses the run, logs it with the reason and keeps the schedule enabled. A run is refused when its project is archived or unknown, its program is inactive, its executor is missing, or its auto-run is stale. No run is created, one blocked activity is written for each occurrence, and the Schedules page shows the issue with a link to the fix.
Do ConvOps schedules handle time zones and daylight saving?
Yes. Every ConvOps schedule has its own IANA time zone, UTC by default, and its runs keep local time across daylight-saving changes. A weekly 07:00 run in Chicago stays at 07:00 local when the clocks change, and only its UTC time moves, from 12:00 to 13:00. The preview shows the next five runs in local time and in UTC before you save.
What repetitive tasks can AI agents do on a schedule?
With ConvOps, any work your agents already run through a workflow can repeat on a schedule: a daily reconciliation check, a weekly compliance evidence pull, a monthly report on day 1, a morning briefing per region. Each run follows the same workflow steps as a manual one, approval gates included, and a run that cannot start is logged with its reason instead of vanishing.