Skillnaija Start free

Your helpdesk morning: five tickets and one knowledge-base article

The capstone project for IT Support Fundamentals: Fix It, Log It, Explain It — a free Data & Tech course. Pass it and you earn a certificate anyone can verify.

Start the course free Download the project workbook

The project unlocks once you complete the lessons. The workbook is free to download now so you can see exactly what is expected.

What you will submit

One shared document link containing the setting, five ticket write-ups (one of them an escalation and one a security report with nothing opened or run), one knowledge-base article of 300 to 500 words with numbered steps and a last-reviewed date, and the reflection.

What to do, step by step

  1. Part 1. The setting (half a page). Describe a small organisation you support or could support: your own workplace, a family business, a school, a church office, or Swiftline itself if you have none. Say how many people, what devices they use (laptops, desktops, phones, printer, Wi-Fi), who approves spending, and who you escalate to when a fault is beyond you. Use made-up names for people: never put a real person's name, phone number, email address or password in your submission.
  2. Part 2. Five ticket write-ups. Take five faults, real or realistic, from different areas of the course (at least one laptop, one phone or account, one network or printer, and one security report). Write each as a ticket with these headings: Ticket ID; Who reported it (made-up name and role); Device; What the user said, in their own words; When it started and what changed; Priority (P1 to P4) with one sentence of reason; What you asked and observed; What you isolated (one device or all, one app or all, one account or all); The ONE change you made; How you verified the fix; Fix note (one or two plain sentences the user could read); Status. If a ticket was escalated, say to whom, why, and what you did before handing it over. At least one ticket must be an escalation, and the security ticket must show that no suspicious file was opened or run.
  3. Part 3. One knowledge-base article (300 to 500 words). Choose one fault from Part 2 that will happen again and write the article a non-technical colleague could follow on their own: a title that says the symptom in the user's words, who the article is for, what to check first, numbered steps with what the screen should show after each one, when to stop and call support, and a last-reviewed date. No product name may appear as required; if you name one, say it is an example.
  4. Part 4. Reflection (quarter of a page). Name one fault you would never attempt yourself and why (for example anything inside a power supply, a battery or an old CRT monitor), one request you would refuse and the exact words you would use (for example a manager asking for someone else's password), and one thing you would do differently next time.
  5. Put everything in one document (Google Doc, Word or PDF), set sharing to 'anyone with the link can view', and submit the link.

Files to work with

Project workbook (fill in, then submit)The whole brief, an evidence checklist, the grading rubric as a self-check and the link-sharing steps in one file. Opens in Word, Google Docs or WPS.Word · 7 KB

How it is graded

CriterionWeight
The five tickets are complete and specific: the user's words, when it started and what changed, a priority with a reason, what was isolated, one change at a time, a verification step and a plain fix note35%
The method shows: faults are isolated before anything is changed, only one thing is changed at a time, the escalation says to whom and why, and the security ticket opens or runs nothing suspicious25%
The knowledge-base article is 300 to 500 words, titled in the user's words, with numbered steps a non-technical colleague could follow, a stop-and-call line and a last-reviewed date, and names no vendor as required25%
The setting and reflection are honest and safe: made-up names only, no real credentials, a named never-attempt fault and a refusal in the writer's own words15%

You need 65% overall to pass. A failed submission comes back with feedback and can be revised and resubmitted once free; further attempts come with the All-Access Pass or as a paid retake.

Before you submit: make your link public

If your work lives in Google Drive or Google Docs, open Share → General access and change “Restricted” to “Anyone with the link” (Viewer). Then paste the link into a private browser window: if it opens without sign-in, you are ready. A private link cannot be graded — it is the single most common reason a good project fails.

Frequently asked questions

Do I have to finish IT Support Fundamentals: Fix It, Log It, Explain It before submitting the project?

Yes. The submission screen opens once every lesson in IT Support Fundamentals: Fix It, Log It, Explain It is marked complete. The lessons are where the methods, the local context and the worked examples the project depends on are taught.

How is the project graded?

An examiner scores each rubric criterion from 0 to 100 and weights them as shown on this page; you need 65% overall to pass. Most submissions are graded within minutes and you get written feedback on what was strong and what to improve.

Can I resubmit if I fail?

Yes. A failed project comes back with feedback; revise the weak parts and resubmit. A passed project is final — the certificate is issued and cannot be re-rolled.

What do I actually submit?

A write-up of what you did (under 5,000 characters) plus a public link to your work — a Google Drive folder, Google Doc, spreadsheet, GitHub repository or video. The link must open without sign-in; a private link cannot be graded. The free project workbook on this page walks you through all 5 steps.

Is the certificate real?

Yes. Passing this project issues a certificate with a unique verification code. Anyone — an employer, a client, a school — can open the verification page and see that the certificate is genuine and which project earned it.

More Data & Tech projects

Ready to earn this certificate?

IT Support Fundamentals: Fix It, Log It, Explain It is self-paced. Finish the lessons, complete this project, and the certificate is yours to share.

Start learning free