Student pathwayCampus helpEmployability proof

Join the student pathway.

University and TAFE students can register interest for practical campus, community, referral, support, admin, marketing and project work when their course or skill area matches the type of help they want to offer. The app helps keep work clear through guidance, Team Up, job boards, skill tags, customer updates, official payment links, reviews and live resume proof.

Request student access Start as campus ambassador Ask for guidance

Guided student start

Choose one student helper path, see the proof you can build, then continue.

This guided start keeps the first step simple. Choose volunteer practice, resume proof, soft-skill practice, or a paid-work review request when you are ready.

VolunteerI want volunteer campus practiceStart with clearly tagged student-to-student help and build safe resume proof.Builds communication, organisation, customer care and tech confidence.Resume builderI want proof for my resumeChoose a mission that maps to job families and soft skills you can explain later.Shows Volunteer-tagged proof separately from paid job proof.PracticeI want study and soft-skill missionsPractise planning, communication, teamwork, management and digital business tools.Creates proof for admin, communication, planning and project support roles.Review firstI might be ready for paid workUse your campus proof to ask for manual paid-pathway review when ready.Paid readiness is reviewed manually and never auto-approved from Volunteer work.

My pathCampus helper

My tagVolunteer proof stays labelled

My skill proofTech + soft skills

My next stepReview before paid work

What happens next?

Pick a path, complete or request a safe campus mission, then turn the activity into Volunteer-tagged resume proof. Paid work stays separate and is checked first.

Start volunteer help Open resume proof Share helper card

Start Proof

Course match and manual review first.

To keep the pathway safe and useful, student helpers should be currently studying at a university or TAFE, with a course or skill area that matches the type of help they want to offer.

Technical pathways

IT, computer science, cybersecurity, networking, software, web or digital media can be considered for suitable technical or content tasks.

Business pathways

Business, management, marketing, accounting or administration can be considered for coordination, support, ambassador or business-help tasks.

Limited activation

Students are not activated automatically. The Fixers checks course, skills, location, privacy-safe evidence and task type before any work is matched. Students should not provide USI, student number, date of birth, banking, login, password, PIN or one-time code details.

Rule: registration is automatic, activation is manual, approval is limited by pathway, and matching only happens after approval.

How we review student evidence

We only ask for enough information to check whether the student pathway is suitable. Evidence helps The Fixers review current study status, institution, course area, skill fit, location and safe task type. It does not guarantee approval or work.

Evidence is used only to help review current study status, institution, course area, skill fit, location suitability and suitable pathway.
Students may cover unnecessary private details before sharing evidence. The Fixers does not need USI, student number, date of birth, banking, login, password, PIN, one-time code or private account details.
Evidence is reviewed manually by The Fixers. Submitting evidence does not guarantee approval, activation or paid work.
Admin review should record what type of evidence was checked, not sensitive identifier values from the evidence.
If evidence includes unnecessary private details, ask the student to resend a privacy-safe version or record only that private details were not stored.

Privacy rule: collect the minimum needed, cover unnecessary private details, review manually, and keep activation pathway-limited.

Safe task categories first.

Students should start with lower-risk work that matches their approved pathway, confidence and supervision level. Approval for one pathway is not approval for every tech job.

Good launch categories

Website content help
Basic setup guidance
Admin and support tasks
Ambassador and community tasks
Supervised remote help
Documentation and follow-up notes

Restricted until extra review

Passwords, PINs, one-time login codes, banking codes or remote-access approvals
Banking, payment systems or informal payment handling
Customer email accounts or private account access
Sensitive business systems or confidential data stores
High-risk cybersecurity incidents, breach response or scam recovery decisions
Unsupervised visits involving vulnerable customers or unclear safety risk
Broad approval for all tech jobs, all customer jobs or all provider work

Boundary rule

Manual approval must name the pathway and suitable task category. Students must not handle passwords, banking codes, sensitive accounts, high-risk cyber incidents or unsupervised vulnerable-customer visits unless separately reviewed.

Launch rule: low-risk first, pathway-limited, supervised where needed, and escalated when safety, privacy, payment or customer vulnerability is unclear.

Before your first student job

Approved students should start with clear, lower-risk work that matches their approved pathway. The safest first-job rule is simple: use normal words, do not overpromise, pause when unsure, and escalate anything involving safety, privacy, payment, customer vulnerability or sensitive account access.

How to work

Start with approved lower-risk task categories only. First jobs should match the student's approved pathway, confidence and supervision level.
Use normal words with customers. Explain what you can check, what you cannot promise, and what happens next.
Do not pretend to know. If the work is unclear, risky or outside your approved pathway, pause and ask The Fixers for help.
Never ask for passwords, PINs, one-time login codes, banking codes, remote-access approvals or private account information.

When to stop and ask

Escalate safety, payment, privacy, vulnerable-customer, provider concern or account-access issues before continuing.
Keep notes factual and customer-safe. Record what happened, what was checked, what was escalated and what the next step is.
Use official support, booking and payment pathways only. Do not move customers into informal side arrangements.
Treat the first job as a supervised learning step. Good judgement is knowing when to stop and ask for support.

Readiness rule

Students should not be matched to broad, unsupervised or sensitive work just because they are approved for one pathway. First jobs stay low-risk, pathway-limited and supported.

Safety reminder: ask for help early, do not guess, do not request private credentials or codes, and escalate privacy, payment or safety concerns before continuing.

When a reviewed student helper may assist

For suitable lower-risk work, The Fixers may involve a reviewed student helper. Student helpers are manually reviewed before activation, matched only to approved pathway categories, and expected to pause and escalate if the task becomes sensitive, unsafe or unclear.

Reviewed first

Student helpers are not activated automatically. Course fit, skill fit, privacy-safe evidence, location and task suitability are reviewed before limited activation.

Matched carefully

Students are considered only for suitable task types such as practical support, website content, setup guidance, admin/support, ambassador/community or supervised remote help.

The Fixers remains here

If a customer is unsure, concerned, unsafe or confused about next steps, The Fixers remains the support and escalation pathway.

Customer expectation rules

Some lower-risk tasks may be supported by reviewed student helpers when the task fits their approved pathway.
Student helpers are manually reviewed before activation and are not matched automatically just because they register interest.
Student helpers are matched only to suitable task types, approved pathways and safe task categories.
Students may help with practical support, website content, setup guidance, admin/support tasks, ambassador/community tasks or supervised remote help when suitable.
Students are not presented as senior technicians, broad providers or all-purpose technical experts.
The Fixers remains the support pathway if the customer is unsure, concerned, unsafe, confused about next steps or needs escalation.
Students must not ask for passwords, PINs, one-time login codes, banking codes, remote-access approvals or private account information.
If a task becomes sensitive, risky or outside the approved pathway, it should pause and escalate rather than continue informally.

Trust rule: describe reviewed student helpers honestly, do not imply senior technician status, and keep support, safety, privacy and payment concerns on official The Fixers pathways.

When a student helper should pause and escalate

Student helpers should only continue when the task is inside their approved pathway, low-risk enough for their approval level, and clear enough to explain in normal words. If the work becomes sensitive, unsafe, unclear or outside the approved category, the student should pause and escalate to The Fixers before continuing.

Approved pathway only

Students must not continue beyond the pathway or safe task category chosen by admin. Suggested pathways are guidance only and are not supervision approval.

Pause before sensitive access

Passwords, codes, banking, payment systems, email accounts, remote-access approvals, private accounts and sensitive business systems must be escalated rather than handled informally.

The Fixers escalation path

Safety, privacy, payment, vulnerable-customer, provider concern, scam pressure or unclear task suitability should move back to official The Fixers support and review pathways.

Escalation triggers

Task is outside the student's approved pathway or approved safe task category.
Customer asks the student to handle passwords, PINs, one-time login codes, banking codes, remote-access approvals or private account information.
The task involves a sensitive business system, payment account, email account, banking/payment system or private customer account.
The customer seems unsafe, distressed, vulnerable, pressured by a scammer, or unsure whether they should continue.
The job turns into high-risk cybersecurity, fraud, account recovery, data-loss, identity, legal, medical, financial or emergency advice.
The student is unsure, cannot explain the next step in normal words, or feels they may need to guess.
The customer asks for side arrangements, cash/payment changes, off-platform work, or contact outside official The Fixers pathways.
The student is asked to visit or continue with an unsupervised vulnerable-customer situation that was not separately reviewed.

Supervision levels

Self-guided lower-risk task inside approved pathway (self_guided_low_risk)
Check-in required before continuing (check_in_required)
The Fixers supervision or review required (supervised_required)
Pause and escalate before any further work (pause_and_escalate)

Escalation rule: when unsure, sensitive, unsafe, outside pathway or involving vulnerable customers, pause first and ask The Fixers before continuing. This is guidance only; it does not create a workflow engine or automatic matching system.

Student match eligibility display and safe filtering

This pass makes availability display safer: only students with approved_for_limited_tasks plus at least one manually approved pathway or safe task category should appear in eligible helper views. Suggested pathways remain visible as guidance only and must not make a student available.

Display state

Eligible for limited display

Status: approved_for_limited_tasks

Student may be shown only for the approved pathway and safe categories listed here.

Approved pathways

networking_setup

Manual approval only. These control eligibility display.

Suggested pathways

networking_setup, it_support

Guidance only. These must not make the student available.

Approved safe task categories

basic_setup_guidance, supervised_remote_help

Use these to keep work low-risk and inside the approved boundary.

Safe filtering rules

Only show students as available when student_application_status is approved_for_limited_tasks.
A student must have at least one manually approved pathway or approved safe task category before appearing in any eligible helper list.
Suggested pathways are display guidance only and must never be copied into available-student filtering as approval.
Pending, needs_more_information, student_status_checked, paused and declined students must stay hidden from customer-facing availability and match consideration lists.
Match display should show approved pathways, safe task categories, supervision level and escalation boundary in plain language.
Restricted categories such as passwords, banking systems, sensitive accounts, high-risk cyber work and unsupervised vulnerable-customer visits must not be treated as normal eligible work.
If a job category is not inside the approved pathways or approved safe task categories, the student is not eligible for that job and the task should pause or escalate.
Filtering guidance must remain lightweight. This pass does not create a matching engine, dashboard, CRM, support queue, workflow engine or automatic approval system.

Filter guidance: student_application_status = 'approved_for_limited_tasks' AND (student_approved_pathways IS NOT NULL OR student_approved_safe_task_categories IS NOT NULL)

What your application status means

Student application outcomes should be clear, calm and honest. A pending, paused, declined or more-information outcome should explain the next step without promising approval, paid work or broad task access.

Pending review

Thanks for registering interest. Your application is waiting for manual review. This means The Fixers still needs to check course fit, privacy-safe evidence, skill area, location and suitable task type before any work can be matched.

Next step: Wait for The Fixers to review the details, or provide more information if the team asks for it.

Needs more information

We may need a little more information before we can decide. This is not a rejection. It may simply mean the course, evidence, location, availability or preferred task type is not clear enough yet.

Status key: needs_more_information

Student status checked

Your study evidence may have been checked, but this does not mean you are activated for work yet. The Fixers still needs to confirm the suitable pathway and task boundary.

Status key: student_status_checked

Approved for limited tasks

You may be considered only for the approved pathways or safe task categories The Fixers has selected. This is limited activation, not broad approval for every tech job.

Status key: approved_for_limited_tasks

Declined for now

This application is not suitable right now. That may be because the course fit, task type, location, timing, evidence or safety boundary does not match the current student pathway. It does not mean you can never apply again.

Status key: declined

Paused

Your application or access is on hold. This may happen because timing, task suitability, safety review, location, availability or follow-up information needs another check.

Status key: paused

Messaging principles

Use calm wording for pending review, needs more information, declined and paused outcomes.
Explain that non-approval may be due to task fit, timing, location, missing evidence, unclear course match or safety boundaries.
Do not guarantee approval, activation, work, income, priority placement or future matching.
Do not make decline wording sound personal, final forever or punitive.
When asking for more information, request only privacy-safe details needed for course, evidence, skill, location or task suitability review.
Keep students off match and availability displays until they are approved_for_limited_tasks with approved pathways or safe categories.
Keep suggested pathways as guidance only and never as approval.
Remind students not to send USI, student number, date of birth, banking details, login details, passwords, PINs, one-time codes or private account information.

Boundary: reassurance messaging does not approve students, create a workflow engine or change matching logic. Manual review and pathway-limited activation still control access.

Student-to-student help

Start small on your campus.

Students can help other students on the same campus first. Volunteer practice is clearly marked with a Volunteer tag, so paid work and community practice stay separate.

VolunteerStart with campus volunteer helpHelp another student with a small, safe request on the same campus so you can build confidence and proof for your resume.Start this path Resume proof

VolunteerBuild resume proof firstUse clearly marked volunteer practice, thank-you notes, skill tags and outcomes as examples before paid work is considered.Start this path Resume proof

Paid pathwayI am ready for paid workAsk for manual review when you are ready for paid local tech help. Paid work is separate from volunteer-tagged campus practice.Start this path Resume proof

Volunteer-tagged tasks are optional and are for campus practice, confidence and resume proof. They are not a required unpaid step before paid work.

Level up safely

Build skills, proof and confidence before paid work.

Campus peer help should feel motivating without pressure. Students can start with clearly tagged Volunteer practice, learn across tech and business skills, then use the existing resume proof view when they are ready to show progress.

1Campus starterChoose a campus, select safe skill areas and ask for board access.

2Peer helperComplete a small Volunteer-tagged student-to-student help task.

3Reliable helperCollect thank-you notes, follow-up proof and safe outcome notes.

4Resume readyShow campus helper skill tags and resume proof from checked activity.

5Paid pathway reviewAsk for manual review before any paid local tech help is considered.

Tech supportWi-Fi, laptop setup, printing, email/login, software, phone setup and scam safety.

Business skillsCommunication, follow-up, customer care, clear notes, privacy and reliability.

Digital skillsMicrosoft 365, Google Workspace, Canva, websites, AI tools and safe online forms.

Open student resume proof Share campus helper link

Resume proof uses the existing profile skill tag view. It does not approve skills, publish private details, guarantee paid work or create a new resume engine.

Mission feed

Pick a useful campus mission, then turn it into proof.

The feed mixes real peer-help jobs with practice and resume-builder missions. Every mission links to a relevant job family and soft-skill proof so students can show what they are building.

VolunteerHelp a student connect to campus Wi-FiTech Support · Tech support assistantSoft skills: clear explanation, patience, problem solving, privacy awarenessStart this mission

VolunteerHelp a student set up Microsoft 365 for studyDigital Business Tools · Digital admin assistantSoft skills: organisation, communication, accuracy, follow-upStart this mission

PracticeHelp a student create a weekly study planStudy Support · Junior project coordinatorSoft skills: time management, organisation, communication, accountabilityStart this mission

PracticeSet up a simple task board for a group assignmentManagement and Organisation · Junior project coordinatorSoft skills: team coordination, planning, management, accountabilityStart this mission

Resume builderDraft a clear follow-up message after campus helpBusiness Communication · Customer supportSoft skills: professional communication, empathy, clarity, customer careStart this mission

PracticeCreate a simple Canva poster for student tech helpDigital Business Tools · Marketing/content assistantSoft skills: audience awareness, communication, design consistency, initiativeStart this mission

PracticeBuild a checklist for a small student club eventManagement and Organisation · Operations assistantSoft skills: organisation, planning, reliability, handover notesStart this mission

Review firstHelp a student understand a suspicious message safelyCyber Safety · Cyber safety assistantSoft skills: risk awareness, calm communication, privacy, escalationStart this mission

PracticeShow a student how to use AI tools for planning, not cheatingDigital Business Tools · Digital admin assistantSoft skills: judgement, explanation, ethics, communicationStart this mission

Generated missions are not fake paid jobs. Practice and volunteer missions are labelled, paid pathways stay review-first, and private details stay off public resume proof.

Soft-skill proof

Link small campus jobs to workplace skills students can prove.

Each mission produces privacy-safe proof across study, business, communication, management and organisation skills.

Tech support assistantproblem solving, clear explanation, customer care, privacy awareness

Digital admin assistantorganisation, document setup, accuracy, follow-up

Customer supportcommunication, patience, note-taking, expectation setting

Junior project coordinatorplanning, task breakdown, teamwork, deadline tracking

Marketing/content assistantsimple writing, design sense, audience awareness, consistency

Operations assistantprocess thinking, checklists, handover notes, reliability

Cyber safety assistantrisk awareness, calm communication, privacy, escalation

Open resume proof Share proof link

Progress record

Small Volunteer-tagged campus help can auto-credit private progress.

Small student-to-student campus help can count toward levels, skill tracks and resume proof drafts when it is clearly tagged Volunteer. Paid pathway access, public proof and anything sensitive still needs manual review.

Auto-creditVolunteer and practice tasks can privately add progress, badge and resume proof credit when they are small and safe.

Review gatePaid readiness, risky requests and public share cards stay review-first.

Share loopStudents can share resume proof or a campus helper invite through the existing share path.

Open resume proof Share campus helper link

This does not publish private details, approve paid work automatically, or create a separate job board.

Badges and skill tracks

Help peers, collect proof, then level up your resume.

Badges are earned from Volunteer-tagged campus activity. They are motivating proof, not a guarantee of paid work.

1First Campus HelpFirst small Volunteer-tagged campus peer help task.

23 Volunteer HelpsThree small campus peer help activities.

3Reliable Peer HelperRepeated safe peer support and follow-up proof.

4Resume ReadyEnough private proof to request resume/public review.

5Paid Review ReadyCan ask staff for paid pathway review.

View resume proof Share helper card

Completion loop

Post, help, thank, credit, share.

1Volunteer tagEvery volunteer task is labelled before a student starts.

2Small helpPeer help stays campus-first, low-risk and clearly scoped.

3Thank-you notePeer feedback becomes private proof first.

4Auto-creditSafe small tasks add private progress automatically.

5Review/sharePublic resume proof and paid pathway still need review.

Peer thank-you loop

Collect simple thank-you proof after help.

After a Volunteer-tagged campus task, a peer can leave a short thank-you or select safe endorsement tags. Public display stays privacy-reviewed and Volunteer-tagged.

Clear explanationPatient and helpfulGood communicationHelped me understandOrganised and reliableWould ask again

Thank-you notes support confidence, resume proof and admin review, but they must not include passwords, private documents, contact details or sensitive account information.

Safety and review

Small Volunteer tasks can auto-credit. Sensitive work needs review.

Auto-credit

Safe campus practice

Wi-Fi, Microsoft 365 setup, simple planning, follow-up writing and basic study organisation can privately credit progress when safe.

Review first

Sensitive support

Passwords, banking, payment, private documents, data recovery, security incidents, business/customer work and paid jobs require review.

Admin readiness

Paid pathway stays manual

Volunteer progress can support readiness, but it does not automatically approve paid work or public proof.

Upskill reflection

Every mission becomes a learning story.

After completion, students can capture what they helped with, what skill they practised, what they learned and what they would explain better next time.

What did I help with?

Connect the task to a mission, job family and soft-skill proof.

What did I learn?

Turn practical activity into interview-ready examples.

Add to resume proof?

Keep it private until reviewed, then show it with the correct Volunteer or Paid label.

Campus growth loop

Students can become campus connectors without a duplicate ambassador system.

The flow reuses the existing ambassador and referral/share routes. Students can share a helper card, invite classmates, support clubs, and bring more real campus requests into the mission feed.

Campus Starter

Complete profile and choose skill tracks.

Peer Helper

Complete Volunteer-tagged campus help.

Campus Connector

Share helper links and invite peers safely.

Student Tech Ambassador

Use existing ambassador review and referral pathways.

Start as campus ambassador · Share invite link

Campus insight

Use the same activity records to see what students need and what helpers are learning.

Staff can review campus demand, mission categories, practised skills, job families, Volunteer vs paid-review requests, thank-you notes, reflections and share activity from the existing thin record layer.

Demand

Most requested campus help and mission tracks.

Skills

Tech, business, study, management and digital skills practised.

Growth

Share activity, ambassador prompts and campuses with momentum.