# How to use a Righthand with monday

Prepare a monday board review with item IDs, column mappings, subitem scope, and reconciled owner decisions.

By Righthand Team · 2026-10-09

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-monday

## Turn a monday board into a decision brief

Righthand can help review a monday board for owner decisions rather than compressing its colored columns into a generic status summary. Start with one board and a concrete question, such as which launch items need a confirmed date or explicit approval before next week's handoff.

monday's [items reference](https://developer.monday.com/api-reference/reference/items) distinguishes item identity and column values. A column's display label is not enough to establish its meaning or type. Provide the actual mapping used by the team and retain item IDs throughout the review.

## Define board, columns, and subitems

Specify the board identifier, included groups, relevant status labels, and subitem policy. For an illustrative launch board, give the columns Accountable owner, Launch date, Approval, and Dependency. Explain which approval values count under your team's policy.

Inspect the exposed tools through [integrations](/integrations). If the required board read is unavailable, provide an approved export or authorize a browser review of the selected groups. The provider's API describes possible operations; it does not establish which are native to your Righthand connection.

## A complete example brief

> At 1 PM America/Los_Angeles on Wednesday, review the approved launch board and specified subitems in the Delivery group. Produce a private decision queue with item ID, item URL, exact status label, owner, launch date, and approval value. Flag missing owners and inconsistent parent/subitem states using the supplied policy. Do not change columns or notify board members. Send to me for program-lead review. Reconcile the item count, included groups, pagination, and subitem coverage before delivering the brief.

The example is illustrative. A green status label may be a team's internal convention, not permission to make an external commitment.

## Present discrepancies without resolving them by guess

An example entry could say: “Launch checklist item marked Done; required subitem remains In progress; launch date present; owner decision needed.” The assistant should preserve that disagreement rather than replacing one state with the other.

If a people column contains several members, show them and explain that accountability is unclear under a single-owner policy. If a formula or mirrored value is present, identify it as derived information when the source exposes that distinction; do not propose writing into it like an ordinary editable field.

## Reconcile updates to the source

Match item IDs across runs and record changes in the same decision entry. Renaming an item or moving it to a different group should not create duplicate work. A board export taken before a launch-date change should remain labeled with its original snapshot time.

Permission changes can hide groups or columns. Report unavailable evidence rather than concluding that those items were removed. If the lead approves supported edits, target the exact items and columns, then retrieve the resulting values for comparison.

Define review authority through [Righthand's connection guide](https://docs.righthand.ai/guides/add-a-connection). Review [pricing](/pricing) for a recurring board responsibility and keep the program lead responsible for final launch decisions.