One Excel workbook per project, kept in step with the board both ways

When a deal reaches the right pipeline stage, a scenario creates the project's SharePoint folder, pauses so the folder exists before anything is written to it, and copies in three templates: the calibration-audit file, with content generated by Gemini, the project workbook and a third working file. It writes the links back to the board, seeds the workbook with a worksheet and a first row, and records which workbook belongs to which project in a data store.

When a column changes on the board, a second scenario finds the item's workbook and row in the data store, and a router sends the change down one of four routes by kind of column: numbers, linked records, dates or statuses. Each route writes the value into its cell, and every Excel write has a Skip or Ignore handler, so one locked workbook doesn't stop the next change.

About every twenty minutes a third scenario reads the workbooks' rows through SharePoint's API, finds each matching monday item by column value and writes back the rows that pass its filter, so calculations done in Excel reach the pipeline without anyone retyping them. Its Excel and monday branches fail soft as well.

When a property moves to report preparation, a fourth scenario pulls its files from SharePoint, asks Make's AI web search for the local water and utility rates, writes them into the workbook, sets the item's status and emails the team to say it is done. Its modules are named in business language, so the scenario reads as the job it does.