DOCUMENT OPS

Sync risk register changes into the board deck risk appendix

When a risk item is created or its severity changes in Coda, updates the deck's risk appendix in Google Drive and pings the meeting owner if a high-severity risk was added close…

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCoda risk item created or severity changedCodaCoda
  • ActionRead full current risk register from CodaCodaCoda
  • LogicSort and filter risks by severity and status
  • ActionRewrite risk appendix in deckGoogle DriveGoogle Drive
  • LogicCheck for high-severity risk in freeze window
  • OutputNotify meeting owner of escalated riskSlack

What it does

Keeps the board deck's risk appendix in lockstep with the live risk register. Whenever a risk is added or re-scored in Coda, the workflow rewrites the appendix slide so the deck always reflects the current risk posture rather than a snapshot taken at deck-creation time.

When to use it

Use it for the window between deck assembly and the meeting, when risks surface or get re-rated. It is especially valuable for regulated or high-scrutiny boards where a newly escalated risk must appear in the pack.

How it works

  1. 1A Coda row event fires when a risk register item is created or its severity field changes.
  2. 2The workflow reads the full current risk register from Coda to rebuild the appendix accurately.
  3. 3A logic step sorts and filters items by severity and open status for the slide.
  4. 4It rewrites the risk appendix table in the Google Drive deck.
  5. 5A second logic check tests whether a high-severity risk was added within the pre-meeting freeze window.
  6. 6If so, it notifies the meeting owner in Slack so they can brief the chair before the deck circulates.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  2. 2
    Connect Google DriveDocs, sheets, slides, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.