Spreadsheets, data organization, and analysis workflows.
Showing 25–33 of 33 guides
To resolve spreadsheet date ambiguity , establish what each original entry means before changing how it looks. Keep the recorded text, identify the source information that supports its interpretation, and leave unanswered questions visible. A date written with a month name and full year is easier to read, but that wording is trustworthy only if the interpretation behind it is supported.
To plan spreadsheet filtering , state which records should remain visible, identify the records that meet those conditions, and describe what the resulting view leaves out. Keep the complete source table separate from that description. A submission excluded by a filter still belongs to the source; a blank field still lacks information. Neither becomes a deleted record merely because the view answers a narrower question. For spreadsheet filtering , verify each step.
Before copying a formula, decide which inputs belong to the destination row and which belong to a shared location. Then predict the addresses the copied formula should contain. Checking spreadsheet formula references this way helps you catch a formula that produces a reasonable number while reading the wrong cells. The question is whether each reference still points to the input you intended.
To plan table joins , decide what each starting row represents, which field connects it to the other table, and what should happen when that field finds no match or several matches. Write those choices before combining anything. A credited name beside a submitted work is useful only when you can explain why that particular name belongs there.
To calculate percentage change , subtract the starting value from the ending value, divide that difference by the starting value, and multiply by 100. The starting value answers the question "Compared with what?" Choosing it correctly matters because reversing a comparison changes the denominator. An increase and its reversed decrease can have the same difference in counts but different percentages.
To check decision table logic , write down the conditions named in the instructions, lay out their possible combinations, and record only the outcomes the wording supports. A case with no applicable instruction is unanswered. A case with incompatible instructions is a conflict. Neither gives you permission to supply the answer you think the writer probably intended.
To find the average page count across two collections of books, add their total pages and divide by their combined number of books. When you have each collection's mean instead of its total, multiply that mean by the number of books it describes. The counts matter: a collection of eight books contributes more observations than a collection of two. Simply averaging their reported means gives both collections equal influence, which answers a different question. For weighted average calculations , verify each step.
A clear category comparison starts with a precise description of what the numbers count. Before drawing bars, establish the observation period, check whether every category uses the same counting rule, and distinguish a recorded zero from an unreported value. Then plan a common zero baseline, readable labels, and a caption that keeps the interpretation within those limits. For bar chart planning , verify each step.
A useful sort changes where a record appears while keeping its values together. Before spreadsheet sorting , define what one row represents, choose the field that should determine its position, and decide how to handle ties and unclear entries. That gives you a proposed order you can explain before touching any application controls.