# Duty Rota card

> Canonical HTML: https://screenrig.ai/docs/cards/rota/

Weekly duties rotate through your team in order, with the next assignee shown alongside.

List people in rotation order and set an ISO anchor week. Duties advance one person each week, with offsets spreading assignments across the team. View the current week, a nearby week, or a single duty in a compact layout.

## Live card

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

Category: People. Tags: Schedules, Offices and workplaces.

## 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.

Names and duty assignments are supplied by the project; use an appropriate staff screen.

## 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 |
| --- | --- | --- | --- | --- |
| `anchorWeek` | string | `"2026-W01"` | maxLength: `8` |  |
| `rotationOffset` | integer | `0` | minimum: `-1000`; maximum: `1000` |  |
| `weekOffset` | integer | `0` | minimum: `-8`; maximum: `8` | 0 is this ISO week, 1 is next week, -1 is last week. |
| `perPage` | integer | `4` | minimum: `2`; maximum: `6` |  |
| `pageSeconds` | integer | `12` | minimum: `8`; maximum: `120` |  |
| `selectedDuty` | integer | `0` | minimum: `0`; maximum: `23` | Duty shown by the compact views. |

### Dynamic properties

| Name | Type | Default | Values and limits | Description |
| --- | --- | --- | --- | --- |
| `title` | string | `"This week’s duties"` | maxLength: `80` |  |
| `subtitle` | string | `""` | maxLength: `160` |  |
| `footnote` | string | `""` | maxLength: `240` |  |
| `people` | array | `[]` | maxItems: `40` | People in rotation order. Blank entries and exact duplicate names are ignored. |
| `duties` | array | `[]` | maxItems: `24` |  |
| `duties[].name` | string |  | minLength: `1`; maxLength: `60`; Required |  |
| `duties[].note` | string | `""` | maxLength: `120` |  |
| `duties[].offset` | integer |  | minimum: `-100`; maximum: `100` | Offset in the people list; defaults to this duty’s position. |

## 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": "rota",
  "primitive": "card",
  "card": "rota",
  "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": "This week’s duties",
  "subtitle": "",
  "footnote": "",
  "people": [],
  "duties": []
}
```

```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":"This week’s duties","subtitle":"","footnote":"","people":[],"duties":[]}}'
```