A practical brief is a paragraph; a checklist is the same paragraph broken into single actions in the order you will do them. You meet this skill in every practical task in ICT, and a good checklist also becomes part of your evidence.
It opens practical workflow and software versions because every later skill in the module depends on knowing exactly what you are about to do.
How do you turn a brief into a checklist?
Read the brief once without touching the computer. Then work through these steps.
- Underline every verb. Each action word is a candidate step: open, add, sort, format, save, export.
- Attach an object and a value. “Format” becomes “format column D as currency with two decimal places”.
- Find dependencies. Ask “what must already exist?” before each step.
- Put the steps in order, then add a check after any step that changes data.
- Finish with the outputs. The last lines name the files you must produce and their exact filenames.
Worked example
Invented brief for Harbour Bakes (a fictional shop):
“Open
sales.csv. Add a Total column showing quantity multiplied by unit price. Format Total as currency with two decimal places. Sort so the largest Total is first. Save your work assales_total.xlsxand also export a PDF calledsales_total.pdf.”
Underlined verbs: open, add, format, sort, save, export.
Checklist:
| # | Action | Check |
|---|---|---|
| 1 | Open sales.csv from 01_source and save a copy in 02_working | Original untouched |
| 2 | Add header Total in D1 | Header spelled as brief |
| 3 | Enter =B2*C2 in D2 and copy down to the last row | Row count matches data |
| 4 | Format D2 to the last row as currency, two decimals | Shows two decimals |
| 5 | Sort all rows by Total, largest first | Rows stayed together |
| 6 | Save as sales_total.xlsx in 03_output | Filename exact |
| 7 | Export PDF sales_total.pdf to 03_output | Reopen it |
With quantities 12, 8, 5 and prices 1.50, 2.25, 4.00, the totals are 18.00, 18.00 and 20.00. Check: 12 × 1.5 = 18, 8 × 2.25 = 18, 5 × 4 = 20. After sorting, 20.00 comes first.
The mistake to watch for
A common slip is a vague step that hides several actions.
Mistaken checklist: 1. Open file. 2. Do totals. 3. Make it look right. 4. Save.
“Do totals” does not say which column, which formula or where. “Make it look right” does not say what to format. The student then forgets the PDF export because the checklist never mentioned it.
The correction is to copy each requirement from the brief into its own line, with the exact name, value or location. If a line cannot be ticked as done or not done, it is too vague.
Check yourself
1. Brief: “Add a column called Discount, calculated as 10% of Price, and save the file as price_list_v2.csv.” Write a three-step checklist.
Show answer
- Add header
Discountin the next free column. 2. Enter a formula such as=B2*0.1in row 2 (if Price is in B) and copy it down. 3. Save as CSV with the filenameprice_list_v2.csv. A check line after step 2 is a good addition.
2. Which step must come first: “copy the formula down” or “enter the formula in the first row”? Why?
Show answer
Enter the formula in the first row. Copying down repeats an existing formula, so it cannot happen before one exists.
3. Rewrite “tidy the table” as an action that can be ticked.
Show answer
For example: “Set column widths so all text is visible and align the headers to the centre.” Any version with a specific action and an observable result is acceptable.
Where this leads next
Once the checklist is written, you need to find each action in your own program. That is locating an equivalent feature in your actual software.
To test the whole module, try the practical workflow practice set. The ICT practical task and evidence checker offers short original briefs for turning into checklists.
If you can follow a plan but find it hard to build one, online one-to-one ICT tuition lets a teacher watch you do exactly that and give feedback on the spot.