Review a calculation chain in a fictional spreadsheet

A plausible spreadsheet total can conceal an omitted row or a copied formula that points to the wrong group. Trace how the number is produced before debating its meaning. This exercise uses invented effort values and a stated rounding convention. Its artifact is a formula-lineage note, not a claim about real project hours or a Kiguri spreadsheet integration.

Map the output back to its source cells

Create a synthetic sheet with five task-hour values in B2 through B6. Each contains 0.335 hours. C2 contains ROUND(B2,2), with equivalent row references through C6. D2 contains SUM(C2:C5). Write every dependency in the lineage note: input cell, unit, intermediate formula, and final range.

This reveals that D2 excludes row six even though the fictional task group includes it. Also mark any manually copied value as a value rather than a live formula. A displayed number equal to yesterday's subtotal does not establish that it will respond to a changed input. Inspect the actual expression or record that it is unavailable.

State where rounding happens

For the manual fixture, round decimal halves upward to two places. Each 0.335 becomes 0.34. Summing all five rounded rows gives 1.70 hours. Summing the five unrounded inputs gives 1.675, which rounds once at the end to 1.68. These totals differ because rounding happens at different stages.

The current D2 formula sums only four rounded rows, producing 1.36. Its problem is not the same as the 1.70 versus 1.68 policy choice. Identify the omitted row separately from the agreed rounding order. A software calculation may have additional numeric representation details; label these arithmetic values as the manual convention, not an executed spreadsheet result.

Inspect copied ranges and units

Suppose another fictional group uses C8, C9, and C10 with rounded values 0.50, 0.75, and 0.25 hours. Its intended subtotal is 1.50. If a copied subtotal formula still reads SUM(C2:C5), it reports the first group's 1.36 instead. Correct-looking formatting can hide the wrong dependency.

Compare the range endpoints with the actual group membership, including rows inserted later. Confirm every quantity uses hours before adding it. Do not turn a day value into hours without an agreed interpretation. The lineage note should identify an excluded row or inconsistent unit explicitly rather than simply describing the final total as inaccurate.

Change one synthetic input and predict the response

Change B6 from 0.335 to 0.535 in the manual exercise. Its rounded C6 becomes 0.54. The existing D2 range still excludes it, so D2 should remain 1.36. A corrected SUM(C2:C6) should increase from 1.70 to 1.90.

Record that prediction before checking a sheet. If the actual observation differs, inspect references, manual values, and rounding behavior. Distinguish a formula inspection from running the fixture. A final number matching by coincidence is insufficient when its lineage still points to the wrong cells.

Reconcile the note and the accepted rule

Have the relevant owner establish whether row rounding or final rounding is intended. Update the fixture expectations accordingly, and repeat the omitted-row and copied-group checks. Keep unresolved differences visible rather than choosing whichever total looks familiar.

Ask a second reader to explain why changing B6 affects the corrected first subtotal but not the separate second group. If the lineage cannot support that explanation, the review remains incomplete. Finish with source references, intermediate values, range boundaries, rounding policy, and observed or unexecuted checks clearly distinguished.