ICDL Spreadsheets (ICDL) common mistakes
ICDL Spreadsheets · Understand the traps and how to avoid them.
Typing a value into a cell and pressing Enter, then later overwriting a neighbouring cell that was actually referenced by a formula, without noticing the dependent formula now returns an error or a different total.
Candidates build a sheet top-down and treat each entry as isolated, so they do not track which cells feed formulas and do not check the recalculated result after an edit.
What to do instead
Before editing, select the target cell and use Trace Dependents/Precedents or Ctrl+[ to jump to referenced cells; after any edit, re-check the affected totals and confirm no error values appeared.
Entering a formula that omits the equals sign (e.g. typing SUM(A1:A5) or A1+B1), so the text is stored as a label and no calculation occurs.
Candidates think of the formula as a description of what they want rather than a syntax with a mandatory leading operator, and they do not verify the cell shows a result.
What to do instead
Always start with = (or +), then confirm the cell displays a computed value and that the formula bar shows the full expression rather than plain text.
Dragging or copying a formula that uses relative references into a new row/column and getting wrong results because the references shifted, or the reverse: hard-coding $ on every reference so a fill-down never updates.
Candidates do not distinguish relative from absolute referencing, and they copy formulas without inspecting the formula bar in the destination cell.
What to do instead
Decide the intent first: use $A$1 to lock a constant (e.g. a tax rate), plain A1 for values that should shift per row. After filling, click two or three copied cells and read the formula bar to confirm the references moved as intended.
Selecting a range for a function but leaving the wrong argument order or missing a required argument, e.g. =IF(A1>50) with no value-if-true/false, or =VLOOKUP with the lookup column not leftmost, producing #N/A or a logic error.
Candidates memorise function names but not argument structure, and they accept a result without sanity-checking it against a known case.
What to do instead
Use the function dialog/argument tooltip to see each argument's role and whether it is required; test the formula on one row where you already know the expected answer before filling it down.
Copying a worksheet or moving it and assuming formulas and references follow, when relative references to other sheets or an absolute range now point at the wrong sheet or a stale range.
Candidates treat sheet operations as cosmetic and do not re-verify cross-sheet formulas after duplicating, renaming, or reordering tabs.
What to do instead
After any copy/move/rename, check formulas that reference other sheets; rename sheets via the tab (not by retyping in cells) so references update automatically, and re-point any broken references manually.
Formatting numbers by retyping them (adding a currency symbol or percent sign as text) instead of applying a number format, so the values become text and stop summing.
Candidates confuse appearance with data type and reach for the keyboard rather than the Format Cells dialog or ribbon number group.
What to do instead
Keep the underlying number clean; apply currency, percentage, or decimal places through Format Cells > Number (or the ribbon). Verify by checking the value is right-aligned and still participates in a SUM.
Building a chart from the whole sheet or from the wrong range, so series include totals, blank rows, or labels, and the chart is unreadable; or leaving the default chart type that misrepresents the data.
Candidates insert a chart first and then try to fix it, rather than selecting a clean data range (labels plus values, no totals) and choosing a type suited to the comparison.
What to do instead
Select only the header row plus data rows (exclude totals), insert the chart, then use Select Data to confirm series and category labels; switch chart type to match the message (column for comparison, line for trend, pie for parts of a whole).
Printing or exporting without setting the print area, orientation, scaling, or repeating header rows, so columns spill onto extra pages and headers appear only on page one.
Candidates preview on screen and assume the printed output matches, skipping Page Setup and Print Preview.
What to do instead
Set the print area, choose portrait/landscape and fit-to-width scaling in Page Setup, set rows to repeat at top for multi-page tables, then check Print Preview before confirming.
Sorting a single column or a selection that excludes adjacent columns, so rows become mismatched (names separated from their values).
Candidates highlight just the column they want ordered, and the sort dialog's 'expand selection' prompt is dismissed without reading it.
What to do instead
Select the entire data block (or click one cell inside it) and use Sort so whole rows move together; if prompted to expand the selection, accept it, and verify a couple of rows afterwards.
Leaving the active cell or selection in an unintended place, or saving in the wrong file format/location, so the submitted file opens showing a stray cell or loses formulas as values.
Candidates finish the task content and close the file without a final check of cursor position, sheet order, and Save As type.
What to do instead
Before saving, click A1 (or the expected start cell), confirm the correct sheet is active, use Save As with the required format and filename, then reopen the file to confirm content and formulas survived.