What "Cross-Block" Actually Means

In a spreadsheet, a cell reference is a coordinate inside one grid. A1 lives on the active sheet. Sheet2!A1 reaches another sheet, but you have already paid for it: separate tab, separate context, no spatial relationship to the formula that uses it.

GridDoc canvases are not built out of one grid. They are built out of blocks — independently positioned tables, formula cells, text panels, charts, drawings — that each have their own internal coordinate space. A cross-block reference is a formula in one block that points at a cell or range inside another block sitting somewhere else on the same canvas.

You can see this in the product pitch on griddocx.com: a "real calc engine with cross-block references — SUM, IF, VLOOKUP and more." That phrase is doing a lot of work. It is the reason a GridDoc page can hold a calculation report and the model behind it at the same time, instead of forcing you to maintain them in two files.

What It Looks Like in Practice

A typical engineering memo has three things on the same page: a table of inputs, an assumptions block, and a summary block that pulls a result out of those inputs.

In Word, those three things are decorative. The summary number is whatever you typed there last.

In a single Excel sheet, all three would be crammed into the same grid, with the assumptions section often demoted to a corner cell because there's nowhere else for it to live.

In GridDoc, each one is its own block — placed where it makes sense to the reader — and the summary block contains a formula like:

=SUM(LoadTable!D2:D12) * Assumptions!SafetyFactor

LoadTable and Assumptions are not other tabs. They are blocks on the same canvas, a few inches away on screen. The formula reads through the canvas and computes a live result. Update a load value or change the safety factor and the summary updates with it.

Why This Changes the Document

Cross-block references collapse the workflow that engineers, analysts, and technical writers spend most of their day on:

1. No more typed-in numbers. Anything that came out of a calculation can stay attached to the calculation. The summary sentence ("calculated stress is 142 MPa") can pull the value directly from the stress block instead of being a brittle copy.
2. Reference data lives next to the calculation. A material properties table, a rate schedule, a unit conversion list — each one becomes a block other formulas point at. The lookup target is on screen, in context, where a reviewer can actually check it.
3. Recalculation is global, not file-by-file. Edit a single input cell and every block that referenced it — the summary, the conditional language, the chart — updates in the same pass. No exporting, no re-pasting, no out-of-date appendix.
4. The audit trail is shorter. When a reviewer asks "where did this number come from?", a cross-block reference is the answer. The formula bar tells them the source block and the cell. That is harder to do when the answer lives in a different application.

How to Start Using Them

Anywhere you can type a formula in GridDoc — a formula cell, a table column, an inline result — you can use the standard BlockName!CellReference syntax. The functions you already know carry over: SUM, IF, VLOOKUP, and the rest of the library work across blocks the same way they work inside one. The only thing that changes is what the formula is allowed to see.

Once you have a calculation that reaches across the canvas, the rest of the document follows. The text block can quote the result. The chart can read the data. The conditional summary can rewrite itself when the inputs change. None of it has to be retyped.

That is what cross-block references are for.