01
Basic Operations
Counting how much every cell-level decision moves the number and whether it can be read back from the sheet: the difference relative and absolute references produce when copied and how many cells a wrong reference spreads to, a count function giving three different results for a blank cell, a zero and a number written as text, the records a boundary comparison sends to the wrong tier in nested conditions, the record blocked from matching by an invisible space and a difference in letter case, a day-counting decision giving two durations, the vertical lookup that breaks when a column is inserted and the match-index pair that does not.
- 01 Worksheet Structure A single amount formula is copied to 60 rows, and when the reference decision changes the total drops from 13,427.16 fee units to 3,354.98: the relative reference spreads wrongly to 59 cells, 52 of them zero and 7 a wrong number that reads like an amount. The third version, written with an embedded literal, gives the same total, but when the unit rate rises from 8.4 to 9.1 it follows in 0 cells instead of 60. Of the 8 parameters on the sheet, 6 enter no formula.
- 02 Basic Functions Four counting functions are applied to a single 60-cell range and four different numbers come out: 53 filled cells, 39 numbers, 29 values above zero, 7 blank cells. The total of the same column is 708.5 m³; because 14 numbers written as text are silently skipped, the real total is 967.2 m³, a difference of 26.7%. The denominator of the mean swings between 11.81 and 24.43 across four defensible decisions, a factor of 2.07; in 1 of six formulas the denominator is not visible at all, in 3 the decision is an embedded literal, and in only 1 is there a reference to a parameter cell.
- 03 Logical Functions The same nested condition is applied to the 10/25/40 m³ tariff tiers in three versions: when the boundary comparison is `<` instead of `<=`, 4 records change tier; when the order of the conditions is broken, 20 records fall into the wrong tier and the first tier empties completely. The boundary decision moves the amount total from 26,219.52 to 26,698.32 fee units, that is 1.83%, but it moves a single bill by 35.5%. Of the three versions that produce the same total, only one has the tier written in a cell; in the others the decision sits inside a 3-layer condition and in no cell.
- 04 Text Functions 48 field visit records are matched to a 60-subscriber list on the subscriber code, and in raw form only 8 of them match. Trimming raises that to 24, trimming plus uppercase conversion to 32, and removing every kind of whitespace to 48; the consumption reported for the visits swings between 232.1 m³ and 1204.8 m³ across these decisions. A fifth decision that rebuilds the code yields the same 48 while silently attaching a record that arrives with a different prefix to the wrong subscriber. A locale-insensitive case conversion misses 15 of the technician names, and of three versions that produce the same result, only one leaves the 40 correction decisions readable back cell by cell.
- 05 Date Functions The mean resolution time of the same 54 support requests comes out as 6.33, 7.33, and 5.20 days under three day-counting decisions; with the endpoints excluded, 6 requests appear to have taken zero days, and in the workday count two requests that took two days on the calendar show zero workdays. What one month later means at month end diverges for 6 of the 60 subscribers: the clamp rule collapses three subscribers onto the same day and produces three periods of 28, 29, and 30 days, while the overflow rule gives every one of them 31 days but shifts the February reading into March. When written as text, 19 of the 54 opening dates can be read as two different days, and the largest deviation is 323 days.
- 06 Lookup Functions The same lookup is built in four versions, and when a column is inserted in the middle of the table only one of them breaks: the vertical lookup with an embedded column number returns the wrong value in 48 of 48 records, raises an error in none, and shows a total of 1084.6 m³ instead of 1204.8 m³. Had the inserted column carried an unreasonable number, the same breakage would have shown up as 201081.0 m³. When the table is re-sorted by region, approximate match silently changes 34 records, and the only thing that carries that decision is a zero in the formula.