The Document That Has to Match the Numbers

Every technical document has the same hidden requirement: the words have to agree with the math. A stress report says "within allowable limits" only if the calculated stress is actually below the limit. A pricing memo says "qualifies for the volume discount" only if the volume threshold is met. A test report says "PASS" only if every measurement passed.

In a traditional workflow, that agreement is something you maintain by hand. You read the number, you decide which sentence to write, and you hope you never forget to update the sentence when the number changes.

GridDoc's IF formula moves that decision into the document itself. The same conditional you would write in a spreadsheet — IF(stress > allowable, "EXCEEDS", "OK") — works on any block on the canvas, and the result is a live value that other blocks can read.

How IF Works on the Canvas

Drop a formula block, point at a value somewhere else on the canvas, and write the condition. Because every block has an address, an IF formula on page four can reference a calculated stress on page two and a tabulated allowable in a lookup block on page one. There is no separate worksheet to keep open. The decision is part of the document.

The output of an IF can be a number, a string, a status code, or a reference to another value. That single rule covers most of the conditional patterns engineers actually use.

Three Patterns That Earn Their Keep

Threshold checks with named outcomes. Place IF(deflection_max <= L/360, "PASS", "FAIL") next to your deflection summary. The PASS/FAIL is computed, not typed. When the input loads change and the deflection updates, the verdict updates with it.

Conditional warnings. Use a callout block that only renders content when a condition is true. IF(temp_rise > 40, "Thermal margin warning: derating required.", ""). If the design stays cool, the warning is invisible. If it doesn't, the warning appears in the right spot, with the right number, automatically.

Branching content. Nested IFs choose between several pre-written paragraphs. A compliance block can pull "Meets IBC 2021 Sec 1604.5" or "Refer to alternate path per Sec 1604.6" depending on a risk-category lookup. The document carries every variant; the formula picks the one that applies.

Why This Matters More in a Document Than in a Spreadsheet

In a spreadsheet, an IF result lives in a cell that nobody outside your team will ever read. In a document, that result is the prose your reader sees. That changes the stakes of getting it wrong, and it changes the value of getting it right automatically.

It also changes the review cycle. A reviewer who finds a number they disagree with can change the input and watch the conclusion update — the verdict, the warnings, the compliance language, and any downstream calculations — without anyone manually rewriting the document. The narrative tracks the math because the narrative is the math.

A Note on Composition

IF is rarely interesting on its own. It earns its place when combined with the rest of the formula engine — SUM rolling up a table, VLOOKUP fetching a code value, cross-block references chaining inputs to outputs. The condition is just the last step: a small piece of logic that decides what the document says about the result.

That is the broader pattern in GridDoc. The blocks hold the data, the formulas connect them, and the IFs decide what the document concludes. The page reads like a normal report. Underneath, every claim it makes is checkable.

---

GridDoc is free to try — get started at griddocx.com and build your first conditional document today.