# Order of Service card

> Canonical HTML: https://screenrig.ai/docs/cards/service-order/

Guide the room through hymns, readings and the order of service.

Display a supplied service order or hymn-number board, with reading references, notes and your chosen season label. Manual selection sets the current item; an optional change instant keeps screens together. Before-service and closing frames support the gathering, while the list follows the selected item or pages on the wall clock.

## Live card

This card is drawn in your browser by the same code the Players run, with sample data.

Category: Events. Tags: Events and venues, Schedules.

## Layouts

This fullscreen card fills the whole screen in landscape or portrait and is not placed as a corner, chip, or strip.

Layouts: full. Forms: landscape, portrait.

[Card layouts, themes and publishing](/docs/cards/). [Browse the cards](/apps/#cards).

## Data and privacy

This card uses its configured properties and live card data.

Use public service titles and references; private pastoral details are not needed.

## Properties

For theme, background, accent and position, see [Common properties](/docs/cards/#common-properties).

Set static properties in `params`. Bind `data` to a project card data key for live values; that document holds only dynamic properties. Without a data key, put the complete configuration in `params`. Nested rows describe the contents of their parent property.

### Static properties

| Name | Type | Default | Values and limits | Description |
| --- | --- | --- | --- | --- |
| `mode` | string | `"order"` | `"order"`, `"hymns"` |  |
| `followCurrent` | boolean | `true` |  |  |
| `perPage` | integer | `6` | minimum: `2`; maximum: `12` |  |
| `pageSeconds` | integer | `15` | minimum: `8`; maximum: `120` |  |

### Dynamic properties

| Name | Type | Default | Values and limits | Description |
| --- | --- | --- | --- | --- |
| `title` | string | `"Order of service"` | maxLength: `100` |  |
| `venue` | string | `""` | maxLength: `120` |  |
| `season` | string | `""` | maxLength: `80` |  |
| `serviceAt` | string | `""` | maxLength: `64` |  |
| `currentId` | string | `""` | maxLength: `48` |  |
| `previousId` | string | `""` | maxLength: `48` |  |
| `changedAt` | string | `""` | maxLength: `64` |  |
| `footnote` | string | `""` | maxLength: `240` |  |
| `phase` | string | `"before"` | `"before"`, `"live"`, `"complete"` |  |
| `items` | array | `[]` | maxItems: `40` |  |
| `items[].id` | string |  | minLength: `1`; maxLength: `48`; Required |  |
| `items[].title` | string |  | minLength: `1`; maxLength: `140`; Required |  |
| `items[].kind` | string | `"other"` | `"gathering"`, `"hymn"`, `"reading"`, `"prayer"`, `"music"`, `"sermon"`, `"response"`, `"communion"`, `"blessing"`, `"other"` |  |
| `items[].reference` | string | `""` | maxLength: `100` |  |
| `items[].hymnNumber` | string | `""` | maxLength: `20` |  |
| `items[].note` | string | `""` | maxLength: `180` |  |

## Canvas example

Add this item to a playlist page’s `primitives`. [Publish the playlist and assign a screen](/docs/cards/#publish-a-card-canvas).

```json
{
  "id": "service-order",
  "primitive": "card",
  "card": "service-order",
  "major": 1,
  "params": {
    "theme": "neomustard"
  },
  "rect": {
    "x": 0,
    "y": 0,
    "width": 1920,
    "height": 1080
  },
  "layer": 0,
  "content_fit": "fill",
  "data": "example-key"
}
```

## Write live data

The canvas example binds its `data` field to `example-key`. That value is a data key: a name this canvas item chooses, not the name of the card. Give each canvas item its own key when items should show different data, or share one key when they should show the same data. Keys are scoped to the project, follow the K/V key grammar, and cannot start with `feed:`.

Create this document before showing the card, then replace it to update the screen without republishing. Writes to a key that live canvas items bind are checked against each bound card’s dynamic properties. Use the same project as the playlist.

Save the document as `card-data.json`. The CLI reads the document itself, with no wrapper:

```json
{
  "title": "Order of service",
  "venue": "",
  "season": "",
  "serviceAt": "",
  "currentId": "",
  "previousId": "",
  "changedAt": "",
  "footnote": "",
  "phase": "before",
  "items": []
}
```

```console
screenrig card-data put example-key --file card-data.json
```

Or call the API directly. The API wraps the same document in a `document` field. An agent token already names its project, so no project header is sent; if you send `ScreenRig-Project`, it must match the token’s project. Supply your API authorization through the environment; see [API authentication](/docs/authentication/).

```console
curl --request PUT "https://api.screenrig.ai/api/card-data/example-key" \
  --header "Authorization: Bearer $SCREENRIG_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"document":{"title":"Order of service","venue":"","season":"","serviceAt":"","currentId":"","previousId":"","changedAt":"","footnote":"","phase":"before","items":[]}}'
```