> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule fields and options

> Reference for AssetOps schedule list columns, filter criteria, creation wizard fields, and bulk edit fields

Look up the values that define a schedule in AssetOps. To create or manage schedules, see [Building schedules](/products/assetops/schedules/schedules-overview).

<h2 id="list-columns">
  List columns
</h2>

These columns appear on the building and [portfolio](/products/assetops/portfolio/schedules) schedule lists.

| Column         | Description                                                                                                                                          |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Title**      | Schedule name as a link, with schedule ID below (for example, `SCH-02235`). An external-link icon opens the linked Cloud BMS device when applicable. |
| **Work type**  | **Preventive maintenance** or **Inspection**                                                                                                         |
| **Recurrence** | How often work is generated (for example, **Weekly**, **On demand**)                                                                                 |
| **Status**     | **Active** or inactive                                                                                                                               |
| **Tasks**      | Number of tasks and total estimated time                                                                                                             |

<h2 id="filter-criteria">
  Filter criteria
</h2>

These criteria are available in the **Filters** panel on the schedule list.

| Filter              | Description                                       |
| ------------------- | ------------------------------------------------- |
| **Next run date**   | Date range for upcoming runs                      |
| **Work type**       | Preventive maintenance or Inspection              |
| **Inspection type** | Inspection category for inspection schedules      |
| **Assignee**        | User assigned to generated work orders            |
| **Team assigned**   | Team assigned to generated work orders            |
| **Frequency**       | Recurrence pattern (for example, monthly, weekly) |
| **Asset**           | Asset included on the schedule                    |

<h2 id="work-types">
  Work types
</h2>

| Work type                  | Description                                           |
| -------------------------- | ----------------------------------------------------- |
| **Preventive maintenance** | Recurring maintenance for building systems and assets |
| **Inspection**             | Routine site or asset walkthroughs to log findings    |

When you select **Inspection**, choose an inspection type.

| Inspection type | Description                              |
| --------------- | ---------------------------------------- |
| **Assets**      | Inspect individual assets                |
| **Area**        | Inspect rooms, floors, or common areas   |
| **General**     | Catch-all for miscellaneous observations |

<h2 id="wizard-steps">
  Wizard steps
</h2>

| Step             | Purpose                                                 |
| ---------------- | ------------------------------------------------------- |
| **General info** | Title, asset type, assignment, description, attachments |
| **Schedule**     | Timing, recurrence, due dates, and auto-fail            |
| **Assets**       | Assets included on the schedule                         |
| **Tasks**        | Task templates or task groups for generated work orders |
| **Overview**     | Review settings before you create the schedule          |

<h2 id="general-info-fields">
  General info fields
</h2>

<ParamField path="Title" type="Field" required>
  Name for the schedule.
</ParamField>

<ParamField path="Asset type" type="Dropdown" required>
  Asset types this schedule applies to.
</ParamField>

<ParamField path="Assignee" type="Dropdown">
  User assigned to work orders the schedule generates.
</ParamField>

<ParamField path="Assign team" type="Dropdown">
  Team assigned to work orders the schedule generates. Work orders assign to the entire team so members can assign work to themselves.
</ParamField>

<ParamField path="Description" type="Field">
  Notes about the schedule scope or procedure.
</ParamField>

<ParamField path="Attachments" type="Field">
  Files such as procedures or reference images. Select the upload area to add attachments.
</ParamField>

<h2 id="timing-fields">
  Timing and recurrence fields
</h2>

<ParamField path="Schedule type" type="Dropdown" required>
  **Just once**, **Recurrent**, or **On demand**. The fields below change based on your selection.
</ParamField>

<ParamField path="Start date and time" type="Date" required>
  When the schedule begins generating work.
</ParamField>

<ParamField path="End date and time" type="Date">
  Optional end date for the schedule window.
</ParamField>

<ParamField path="Due by days" type="Field" required>
  Number of days the assignee has to complete work after it is scheduled.
</ParamField>

<ParamField path="Frequency" type="Dropdown" required>
  Recurrence interval for recurrent schedules (for example, **Weekly**). Some frequencies support custom repeat options.
</ParamField>

For custom recurrence, set **Repeat on** (days of the week) and **On months** when those controls appear.

<h2 id="auto-fail-fields">
  Auto-fail fields
</h2>

<ParamField path="Auto-fail" type="Toggle">
  When enabled, work orders auto-fail if not completed by the configured threshold.
</ParamField>

<ParamField path="Days after due date" type="Field" required>
  Days after the due date before auto-fail applies (shown when **Auto-fail** is on).
</ParamField>

<h2 id="asset-addition-methods">
  Asset addition methods
</h2>

| Method                                 | Description                                                                                                  |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Add by asset type(s)** (recommended) | Includes all assets of the selected types. New assets of those types added later are included automatically. |
| **Add by asset list**                  | Select specific assets from a searchable table.                                                              |

<h2 id="bulk-edit-fields">
  Bulk edit fields
</h2>

Bulk edit updates only the fields you enable. Values apply to every selected schedule.

<ParamField path="Assignee" type="Dropdown">
  User assigned to work orders the selected schedules generate.
</ParamField>

<ParamField path="Team assigned" type="Dropdown">
  Team assigned to work orders the selected schedules generate.
</ParamField>

<ParamField path="Auto-fail" type="Dropdown">
  Auto-fail behavior for work orders created by the selected schedules.
</ParamField>

<ParamField path="Activation mode" type="Dropdown">
  Activate or deactivate the selected schedules.
</ParamField>

<ParamField path="Due-by days" type="Field">
  Number of days that set when generated work orders are due.
</ParamField>

<ParamField path="Next run date" type="Date">
  Date that triggers the next schedule run.
</ParamField>

<ParamField path="Auto-fill" type="Toggle">
  Force an immediate auto-fill across the selected schedules.
</ParamField>

<h2 id="detail-page-tabs">
  Detail page tabs
</h2>

| Tab             | Purpose                                            |
| --------------- | -------------------------------------------------- |
| **Details**     | General information, description, and timing       |
| **Attachments** | Files linked to the schedule                       |
| **Tasks**       | Task templates assigned to generated work orders   |
| **Assets**      | Building assets included on the schedule           |
| **Logs**        | History of work order batches the schedule created |

<h2 id="detail-page-fields">
  Detail page fields
</h2>

**General information** shows these values.

| Field               | Description                                        |
| ------------------- | -------------------------------------------------- |
| Title               | Schedule name                                      |
| Number              | Schedule ID (for example, `SCH-00091`)             |
| Status              | **Active** or inactive                             |
| Assignee            | User assigned to generated work orders             |
| Team assigned       | Team assigned to generated work orders             |
| Created by          | User who created the schedule                      |
| Created at          | Creation date                                      |
| Asset type          | Asset types on the schedule (for example, **AHU**) |
| Start date and time | When the schedule starts                           |

**Schedule** shows timing and recurrence.

| Field       | Description                                 |
| ----------- | ------------------------------------------- |
| Next run    | Next scheduled run date and time            |
| End by      | End date for the schedule window            |
| Recurrence  | Pattern (for example, weekly on Monday)     |
| Due by      | Days to complete work after it is scheduled |
| On month(s) | Months when recurrent runs apply            |
| Auto-fail   | Days after due when work auto-fails         |

## Related reference

<CardGroup cols={2}>
  <Card title="Task fields" icon="file-check" href="/products/assetops/reference/task-fields" arrow={true}>
    Template and group fields you assign during schedule setup.
  </Card>

  <Card title="Work order fields" icon="clipboard-list" href="/products/assetops/reference/work-order-fields" arrow={true}>
    Fields on the work orders a schedule generates.
  </Card>
</CardGroup>
