This is your Unit 1 review session. You've built nine weeks of real work, so today is not a test — it's a chance to look back at what you've produced, confirm the skills you'll carry forward, and sharpen your troubleshooting instinct so small computer problems stop slowing you down. Everything you do today lands back in your Something Real project.
Think about your {{code:Digital_Portfolio}} folder for a moment. Which artifact in there are you most proud of right now? And which one would you most like the chance to redo? Don't write anything down — just notice which files jump to mind first. That instinct is data about what you've actually learned.
Unit 1 gave you the foundations. If a skill on this list still feels fuzzy, today is the right time to notice that so you can book yourself some practice before the next module leans on it.
| Concept | Why it matters | Example |
|---|---|---|
| File organisation in cloud storage — structured folders and consistent {{code:NN_topic}} filenames | A file you can't find is a file you can't use. | {{code:Digital_Portfolio}} holds every artifact from this unit. You can locate any one in seconds. |
| Source evaluation and AI verification — the CRAAP test, and checking AI answers against a primary source | Your name goes on the work. If a "fact" is wrong, you own the mistake. | Checking a PAYE rate an AI quoted against Revenue.ie before you put it in a proposal. |
| Online safety — spotting phishing, strong passwords, two-factor authentication | A stolen account means stolen work and possibly stolen identity. | An email "from your principal" asking you to verify your login. Real school systems never ask for passwords by email. |
| Word processing fundamentals — writing, formatting, spell-check, and saving professional documents | A typo-ridden document gets dismissed before it's read. | A Work Experience thank-you letter with your address, the employer's name spelled correctly, and a proper sign-off. |
| Troubleshooting mindset — check the obvious first, then narrow down | Employers value people who solve small problems before calling IT. | — |
Most common computer problems have the same two or three checks. The trick isn't memorising solutions — it's learning the order to check things. Below is the reference you'll use in the next activity. Read it through once before you start.
| Problem | What to check, in order |
|---|---|
| I can't find a file I saved yesterday | (1) Open {{code:Digital_Portfolio}} and scan for the filename. (2) Use the search box in OneDrive or Google Drive. (3) Check "Recent" in your cloud storage. (4) Confirm you're signed into the right account. School and personal accounts keep separate files. |
| I got an email that might be phishing | (1) Check the sender's full email address, not just the display name. (2) Do not open any link. (3) Hover over a link without opening it to see the real destination. (4) If unsure, open the real site by typing the address yourself. (5) Report the email and delete it. |
| An AI assistant gave me a "fact" I can't verify | (1) Treat the fact as unverified. (2) Search the web using 2-3 keywords from the claim. (3) Check a primary source such as Revenue.ie, Citizens Information, or the named organisation's own website. (4) If no independent source confirms it, leave it out. AI confidence is not accuracy. |
| My document opened but the formatting looks wrong | (1) Check it opened in the right app. A {{code:.docx}} opened in a plain-text editor loses formatting. (2) Close and reopen in Word Online or Google Docs. (3) Check the file downloaded fully. (4) Check your zoom level. |
| Cloud storage says "not synced" or my change isn't showing | (1) Check your internet connection. (2) Refresh the page. (3) Look at the save status. "Saved" means done, "Saving…" means wait. (4) Open the file in another tab to confirm your change is there. |
Keep this table to hand during the next activity — you'll refer back to it.
Open your {{code:Digital_Portfolio}} folder in your cloud storage and use the prompts below to notice what you've actually learned. Nothing here is graded — the point is to find the gap between what you think you know and what your portfolio can prove you know. Jot quick notes on paper if it helps; you'll use them in the next two activities.
For the next 15 minutes, work through the Troubleshooting Reference Guide above as a self-quiz. The goal isn't speed — it's being able to explain each solution clearly enough that you could talk someone else through it. This is exactly what solving your own computer problems at work looks like.
Pick any two of the five cases. For each one, write a single sentence explaining why the first check comes before the second. For example: "I check my internet connection before I refresh the page, because if the internet is down, refreshing won't help."
Writing the "because" is what proves you understand the logic, not just the list.
Think of one computer problem you've actually had recently that isn't on the list. Write it down, then write 2-3 check steps in the right order. Keep the paper with you — you may want to use it in your {{code:10_skills_review}} later.
Get ready to embark on an incredible learning journey! Get access to this lesson and hundreds more on our learning platform.
Chromebooks, laptops, and PCs are crucial tools for coding and digital skills education. Chromebooks are ideal for web-based applications and collaborative projects, while laptops and PCs support a wider range of programming environments and software for more intensive tasks like software development and data analysis.
