Use the schedule

Use the schedule to create job events that repeat on a regular basis — daily standups, weekly retrospectives, nightly automation runs. You set up a job event once on a calendar, and Coord creates a real job each time the event runs.

Before you start

• To create or edit job events, you must be a member, admin, or owner of the workspace. Viewers can open the schedule and see existing job events but cannot make changes.
• To create job events that run agentic jobs, you must have a Coord Runner installed and online. See Set up a runner.
• To create job events that work on a GitHub repository, you must have GitHub integration set up for your workspace. See Set up GitHub integration.

Open the schedule

1. From the workspace sidebar, click Schedule. The schedule opens to a calendar showing the current month.
2. Switch between Month, Week, and Day views using the view buttons above the calendar.
3. Move forward or backward in time with the Previous and Next buttons. Click Today to jump back to the current date.

The current view and date are saved in the page's web address, so refreshing the page or sharing the link with a teammate keeps the same view.

A label above the calendar shows the time zone you are currently in (for example, "EDT (UTC-4)"). Every job event you see on the calendar is shown in this local time, even if the schedule itself is set to a different time zone.

Create a job event

1. Click Create Event in the top-right corner of the schedule.
2. Fill in the title and description, just like creating any other job.
3. By default, the event creates a user job — a person completes each one. To make the event run an agentic job instead, open the Agent tab in the dialog and select an agent. If you want the agent to work on a GitHub repository, also pick the account and repository here.
4. Open the Schedule tab in the dialog and set when and how often the event should repeat:
   • Start — the date and time of the first occurrence.
   • Timezone — the time zone the schedule uses. A schedule set for 9:00 a.m. in America/New_York stays at 9:00 a.m. local time even when daylight saving begins or ends.
   • Repeat — Never (one-off), Daily, Weekly, Monthly, or Yearly.
   • Every — for repeating schedules, how often the event repeats (every 1 week, every 2 weeks, etc.).
   • End — Never, After N occurrences, or On a date.
5. Optionally add attachments. Files you attach to the event are reused by every job it creates — you upload them once.
6. Click Create.

The job event appears on the calendar. Future occurrences show up as cards on the days they happen; click any of them to open the event in the detail panel.

Edit or delete a job event

To open a job event, click any of its cards on the calendar. The detail panel slides in from the right with Overview, Team, and Schedule tabs.

• Edit: click Edit at the top of the panel, or right-click an event card on the calendar and choose Edit. The same dialog you used to create the event opens with its current values.
• Delete: click Delete at the top of the panel, or right-click an event card and choose Delete, then confirm.

Deleting a job event stops Coord from creating new jobs from it. Jobs that were already created from the event are unaffected — they remain in your workspace and finish on their own.

Enable or disable a job event

The Enabled toggle at the top of the detail panel pauses a job event without deleting it. Disabled events stop creating new jobs but keep all their settings, attachments, team, and history. Flip the toggle back on to resume.

A job event that has reached its end (it has run its set number of times, or its end date has passed) shows an Ended badge. It stops creating new jobs automatically — there is nothing to disable.

What happens when a job event runs

Each time a job event runs, Coord creates a real job from it. The new job:

• Inherits the event's title, description, agent or user assignment, repository, team members, domains, and attachments.
• Lands in Ready, so it is good to go straight away — it skips the Backlog.
• Appears everywhere normal jobs do: the board, the explorer, the activity view. It runs, gets reviewed, and finishes through the standard job workflow.

The detail panel's Overview tab includes a Spawned Jobs section listing every job the event has created so far, with the most recent first. Click any of them to jump to that job.

Job event team and access

The detail panel's Team tab works the same way as a job team. Add team members with lead, editor, or viewer roles, and they will be added as team members on every job the event creates from that point forward.

Two access rules are worth knowing:

• Workspace viewers can open the schedule and see job events and their occurrences, but the Create Event, Edit, Delete, and Enabled controls are hidden.
• Among workspace members, only the event's creator, owner, event leads, and workspace admins or owners can edit, delete, enable, or disable a job event. Editors and other members can view it but not change it.

Rules and limits

• Edits apply to all future occurrences. You cannot change a single occurrence on its own.
• No drag-and-drop. You cannot move an event card by dragging it on the calendar. Use the edit dialog instead.
• Re-enabling does not flood your workspace. If a job event is disabled for more than an hour, only the most recent hour's missed occurrences run when you re-enable it — an event that has been off for a long time will not flood your workspace with backdated jobs.
• Created jobs land in Ready, not Backlog. Jobs from a scheduled event skip the Backlog review step and are ready to run straight away.
• Job events cannot have dependencies. A job event cannot depend on another, and the jobs it creates do not automatically pick up dependencies. Add dependencies to individual jobs after they are created if you need to sequence them.

Next steps

• Create your first job — a one-off job is a good first step before scheduling repeats.
• Use dependencies — sequence jobs after they are created.
• Manage job teams — control who can edit a job event and the jobs it creates.
• Set up a runner — required for job events that run agentic jobs.