# How to use a Righthand with Smartsheet

Prepare a Smartsheet exception worksheet with sheet, row, and column IDs, preserving raw values and derived-cell boundaries.

By Righthand Team · 2026-10-09

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

## Review exceptions at the cell level

Use Righthand with Smartsheet to prepare an exception worksheet for an approved sheet. The report should identify which row needs a decision and which exact cells support it. A row number can change after sorting, so it should not be the only reference used for a proposed update.

Smartsheet's [sheet structure guide](https://developers.smartsheet.com/api/smartsheet/guides/basics/sheets-rows-columns-and-cells) describes sheets, rows, columns, and cells. A cell is identified through its row and column context. Retain those identities when reconciling a report with the source.

## Supply the column mapping

Give the sheet ID, included rows or filter, and relevant column IDs and types. For an illustrative vendor-readiness sheet, map Vendor, Accountable owner, Required date, Approval state, and Source reference. Explain which values require review under the team's policy.

Inspect Smartsheet's actual tools in [integrations](/integrations). If cell reads are unavailable, provide an approved export with stable row references or permit a browser inspection. An exported spreadsheet may flatten formulas, links, or contact values; state what remains available.

## A complete example brief

> At 1 PM America/Los_Angeles on Tuesday, review the approved vendor-readiness sheet using the attached column mapping. Produce a private exception worksheet with sheet and row ID, vendor, exact approval value, owner, required date, and the source cells behind each question. Separate missing values from unavailable data. Do not edit cells, change sharing, or contact vendors. Send to me for operations review. Reconcile the included row count and preserve raw and displayed values where the source exposes both.

This example is illustrative. A formatted monetary or date display can differ from its underlying value. The owner should decide which representation belongs in the final report.

## Define the expected worksheet

An example item might read: “Vendor row; approval cell Pending; required date present; owner contact absent; operations lead must confirm accountability.” The assistant should not select an owner from another row simply because the vendor name looks similar.

Keep linked or calculated cells distinct from ordinary editable inputs. A proposal to change a displayed result may require changing a source cell elsewhere, and that source could be outside the approved scope. Flag the relationship rather than modifying it by guess.

## Reconcile changes and row movement

Match stable row identities across runs instead of their visual order. If a column is renamed, use its mapped identity and refresh the displayed label. If the column itself is replaced, ask for a new mapping before treating it as equivalent.

Missing rows can reflect filters, permissions, or deletion. Report incomplete coverage and avoid a false “all vendors ready” conclusion. If approved cell updates are supported, reread the specific row and column values afterward and compare them with the approved worksheet.

Use [Righthand connection permissions](https://docs.righthand.ai/guides/add-a-connection) for the sheet and reviewer. Check [pricing](/pricing) for an ongoing vendor-readiness responsibility.