How to use a Righthand with Google Sheets
Review a Google Sheets task register using exact ranges, stable row keys, typed values, proposed updates, and post-write reconciliation.
Treat the sheet as a record, not a paragraph
Use Righthand with Google Sheets to inspect a task register and prepare a decision list. The important identifiers are the spreadsheet, tab, header mapping, and stable record key. Row numbers alone can change when someone sorts the sheet.
Google's values reference describes ranges, major dimension, and returned values. Specify whether the workflow uses displayed values or another representation where the available tool supports that choice. A formatted date or currency should not be interpreted without its context.
Select a narrow read and update scope
Look up Google Sheets in integrations, identify the document, and inspect its exposed actions. For a first run, give the exact tab and range rather than asking the assistant to explore unrelated worksheets.
If no suitable direct action is available, provide an approved CSV with a header map and snapshot time. A CSV may omit formulas, formatting, and additional tabs; do not treat it as the full workbook.
An illustrative delivery register
A small team has columns Task ID, Owner, Status, Due date, and Dependency. Ask for tasks due next week that lack an owner or depend on unfinished work. These are example columns belonging to the team's sheet, not built-in Google Sheets fields.
Keep blank values distinct from zero and “not applicable.” When a dependency refers to an unknown Task ID, return an unmatched-reference exception. Do not invent the missing task or link it by a similar title.
A usable brief
On Friday at 2 PM America/Los_Angeles, read the approved Delivery tab and supplied header map. Review tasks due October 12-16. Produce a private exception list with Task ID, owner, status, due date, dependency, and source row reference. Draft corrections in a separate worksheet for my review. Do not overwrite formulas, sort the source, or update records yet. Reconcile row counts and unmatched Task IDs to the source. After approved supported writes, reread affected cells and compare with the authorized changes.
The example is illustrative. A proposed correction worksheet is an output for review, not proof that the source data has improved.
Sample result and reconciliation
An example line might say: “Task T-24; owner blank; due Tuesday; dependency T-19 not complete; lead assignment needed.” It should retain the source's date and status rather than infer a new delivery promise.
Before applying changes, match stable Task IDs again. A collaborator may insert rows between review and execution. If the record cannot be matched uniquely, pause that update and ask for a decision.
Failures to include in the report
A renamed header can break the map. A protected range can reject an update. A text date can sort differently from a true date. Report the specific mismatch and cells affected, and separate successful changes from rejected ones.
Keep currency and time-zone assumptions visible if the register includes budgets or timestamps. Repeat the job only after the first report is checked against the live sheet. See connection permissions for access setup and plans for ongoing review work.