Building a Proof-of-Work Portfolio When You Have No Professional Network or GitHub History
Ultra-low-effort artefacts you can finish in a weekend using free tools
You can create a usable proof-of-work portfolio in one weekend even if your only experience is classroom projects or NYSC. Focus on four non-code artefacts—process maps, annotated screenshots of tools, short screen-walkthrough recordings, and before/after process notes—made with free browser tools. These items show how you think and work, which is what many entry-level and career-change employers actually examine when formal job titles are missing.
Why these artefacts work for graduates and career changers
A traditional portfolio often assumes design files, code repositories or client deliverables. Most Nigerian graduates and career changers do not have those. What you do have is the ability to observe a process, improve a small part of it, and record the steps. Process maps, annotated screenshots, short walkthroughs and before/after notes turn that observation into evidence anyone can open in a browser or PDF.
These artefacts are useful for roles in operations, administration, customer support, project coordination, data entry, HR support, marketing coordination, teaching support and many graduate-trainee schemes. They do not require coding knowledge or a professional network.
The four artefacts you can finish in a weekend
1. A simple process map
Choose any routine you already know from school, NYSC or a personal task—attendance recording, filing, report preparation, student registration, inventory counting, or even how you organise your own weekly study schedule. Draw the current steps as boxes connected by arrows.
Free tool: diagrams.net (also called draw.io). It runs in the browser, needs no account for basic use, and exports to PNG or PDF. Google Drawings or the free tier of Canva also work for simple flowcharts.
What to include on the map:
- Start and end points
- Every decision point (yes/no or choice)
- Who performs each step (you, supervisor, student, customer)
- One or two notes on pain points (delays, missing information, repeated work)
Spend 60–90 minutes. Export the finished diagram as a clear PNG or PDF. Name the file something specific such as “Attendance-Process-Map-NYSC-School.pdf”.
2. Annotated screenshots of tools you already use
Open any tool you used during school or service—Google Sheets, Microsoft Excel, WhatsApp Business, Canva, a school portal, or even the calculator and notes apps. Take three to five screenshots that show real work: a filled attendance sheet, a sorted list, a simple formula, a labelled folder structure, or a completed form.
Add short annotations (arrows, text boxes, numbers) that explain what the viewer is looking at and why the arrangement matters. Free tools for annotation: the built-in markup on most phones, Google Drawings, or Canva’s free editor.
Example set for an administrative support role:
- Screenshot of a Google Sheet with attendance data, annotated to show how late submissions were flagged
- Screenshot of a shared Drive folder structure, annotated to show naming rules that reduced search time
- Screenshot of a simple summary table you created for a supervisor
Keep the annotations short and factual. Avoid claims such as “increased efficiency by 40 %” unless you have a record you can defend.
3. A short Loom-style walkthrough (2–4 minutes)
Record your screen while you walk through one of the artefacts above. Explain the problem, the steps you took, and the result in plain language. Free options: Loom free tier (limited video length), the built-in screen recorder on most laptops, or a phone screen-recording app.
Script outline (write it first, then speak):
- One sentence: what process or problem you chose
- Thirty seconds: the original situation
- Sixty to ninety seconds: the steps you followed (point at the map or screenshots)
- Thirty seconds: what changed and what you would improve next
Upload the video to Google Drive or YouTube as unlisted and keep the link. The recording proves you can explain your work clearly—an ability many employers test in interviews.
4. Before/after process notes (one page)
Write a single A4 page in Google Docs or any word processor. Use three headings only:
- Before – two or three short sentences describing the original way of working and the main difficulty
- What I changed – the concrete steps you took (the process map and screenshots support this section)
- After – what is different now, written in observable language (“files are retrieved the same day”, “incomplete forms are returned immediately”, “attendance is entered before 10 a.m.”)
Add a final line that states the tools used (Google Sheets, diagrams.net, phone camera, etc.). Export as PDF. This one-page note becomes the cover document that ties the other three artefacts together.
How to package everything so it is easy to share
Create one Google Drive or OneDrive folder named “Portfolio – [Your Name] – [Target Role]”. Inside it place:
- The one-page before/after notes (PDF)
- The process map (PNG or PDF)
- The annotated screenshots (combined into one PDF or left as separate images)
- A short text file or Google Doc that contains the link to the walkthrough video and a two-sentence description of each item
Set the folder permission to “Anyone with the link can view”. Copy the shareable link. On your CV, under a Projects or Selected Work Samples heading, write one line such as: “Process-improvement sample (attendance recording system) – view folder: [link]”. The free CV Builder on AlertNaija247 can help you place that line cleanly under Education or a short Projects section without complicated formatting.
If you already converted NYSC or classroom duties using the Duty–Result–Skill framework, the same language can appear both on the CV bullets and inside the before/after notes so the two documents reinforce each other.
Common mistakes that weaken these artefacts
- Choosing a process that is too large or vague (“how the school runs”). Pick one narrow, repeatable task you controlled.
- Adding invented numbers or “efficiency gains” you cannot explain if asked.
- Recording a walkthrough that is longer than four minutes or full of filler words. Write the script first.
- Using decorative fonts, heavy colours or multi-column layouts that make the PDFs hard to read on a phone.
- Leaving the Drive folder set to “Restricted” so the employer cannot open the link.
- Treating the artefacts as secret. Share the link only when it is relevant to the role, but do not hide the work.
Questions readers often ask
1. Will employers actually open a Google Drive folder?
Many do, especially when the CV already contains a short, relevant description of what is inside. Keep the folder tidy and the first file the one-page notes so the viewer sees value immediately. If the application system only accepts PDF uploads, combine the notes, map and screenshots into a single short PDF and upload that instead.
2. What if my NYSC or classroom work involved almost no tools?
Use paper-based processes. Photograph the physical register, the filing cabinet labels, or the handwritten summary you prepared. Annotate the photos the same way you would annotate screenshots. The principle is the same: show the steps and the improvement.
3. Can I use these artefacts for more than one type of job?
Yes, provided the process is relevant. An attendance-process map can support applications for administrative, teaching-support, data-entry and operations roles. Rewrite the one-page notes to emphasise the skills the particular job description mentions (accuracy, record-keeping, training others, etc.).
4. How many artefacts do I need before I start applying?
One complete set (map + screenshots + walkthrough + notes) is enough to begin. Add a second set later if you want variety. Quality and clarity matter more than quantity.
5. Do I need a personal website or GitHub account?
No. A well-organised Drive or OneDrive folder with clear file names and a shareable link is sufficient for the roles these artefacts target. A website can come later if you move into design, development or content roles that expect one.
Practical weekend schedule
Saturday morning (2 hours): Choose the process, sketch the current steps on paper, open diagrams.net and produce the process map.
Saturday afternoon (2 hours): Take and annotate the screenshots. Write the before/after notes.
Sunday morning (1.5 hours): Record the walkthrough, upload it, create the Drive folder, set permissions and write the short description document.
Sunday afternoon (30–45 minutes): Add the portfolio link to your CV and prepare one STAR story that uses the same example for interviews.
The goal is not a perfect design portfolio. The goal is a small, honest set of documents that let an employer see how you approach a real task. That is the definition of proof of work when formal experience and professional networks are still limited.
This guide is informational only. It does not list vacancies, guarantee interviews or claim that any employer has verified the method.