Docs Features

Records

A spreadsheet of every bid in progress with your own columns, formulas and views. Agents read and write it, which makes it the place to run agent work across your pipeline.

View as Markdown Ask Claude Ask ChatGPT

Records is a spreadsheet with one row for every bid in progress. You add the columns you care about, such as "Quote sent", "Takeoff done" or "Hours", and save views as a table, board, timeline or calendar. Admins can publish a view so the whole company works in one live sheet.

Agents can read and write records too. That makes Records the shared checklist where you and your agents track work across many bids at once.

Where to find it

  • Your own records: My Hub > Records.
  • Shared records: Published Records in the sidebar (under Bidding).

Rows and columns

Rows are every opportunity that is Undecided, Accepted, Submitted, Needs Revision or Declined and not yet won or lost. You cannot add your own rows or other tables.

Click + Add column at the right of the grid:

TypeHolds
TextFree text
NumberNumbers, with a unit such as %, $ or sq ft
DropdownOne choice from a list, with colours
DateA date
FunctionA formula such as ={Hours}*150
Opportunity DataA live, read-only copy of a bid field, such as due date, assignee, client or estimate value

Formulas do arithmetic (+ - * / and brackets) on other columns in the same row, written as {Column Name}. They do not support functions like SUM or IF.

You can have up to 20 columns and 12 views.

Working in the grid

It works like a spreadsheet: click to select, type to edit, drag the corner to fill, Ctrl + C and Ctrl + V to copy and paste, Ctrl + Z to undo. Right-click a column header to rename, change type, sort, filter, set the alignment or show a sum in the footer.

Views

Click + above the grid to add a Table, Board, Timeline or Calendar view. Each view keeps its own grouping, sort and filters. On a board, drag a card to change a dropdown value or the bid's status.

Publish to the team

Open a view's menu and click Publish. Admins publish at once. Members send a request, and admins approve it from Published Records > Requests.

On a published record everyone can edit cells and sees the same data. Only admins change its columns. Members can sort and filter for themselves without changing it for others.

Records and agents

Records are how you point an agent at many bids at once and see what it did. A simple pattern:

  1. Add the columns that describe the work, for example a Spec check dropdown (To do, Done, Needs review), a Ceiling system text column and a Questions text column.
  2. Ask your agent: "For every Accepted bid where Spec check is To do, read the specs, write the ceiling tile and grid in Ceiling system, list anything unclear in Questions, and set Spec check to Needs review."
  3. The agent reads the record, works through the bids one by one and fills the cells. You review the board, then turn the questions into RFIs.

Because records work over MCP with no Tidy tab open, a connected assistant on a schedule can keep a record you published up to date for the whole team. This is how you build a small "agent factory": the record is the work queue, the columns are the inputs and outputs, and people check the results.

What the agent can do:

  • List and read your records and published ones.
  • Set cells in your own columns.
  • Add columns and change a column's name, type or options. Changing a type clears the column, so the agent asks first.

It cannot create or delete views, delete columns, publish records or approve requests. On a colleague's published record it can read but not edit.

Not available yet

No import or export, no custom tables or rows, no linked records between tables, and no automations that run when a cell changes.