Technical pathways
IT, computer science, cybersecurity, networking, software, web or digital media can be considered for suitable technical or content tasks.
Request access
Students
Register student interest for manual course, skill, evidence and pathway review before any work is matched.
Course match and team check first.
To keep the pathway safe and useful, student support pages 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.
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 checked by our team by The Fixers. Submitting evidence does not guarantee approval, activation or paid work.
- Team 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 support page may assist
For suitable lower-risk work, The Fixers may involve a reviewed student support page. Student support pages are checked by our team 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 support pages 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 support pages when the task fits their approved pathway.
- Student support pages are checked by our team before activation and are not matched automatically just because they register interest.
- Student support pages 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 support pages honestly, do not imply senior technician status, and keep support, safety, privacy and payment concerns on official The Fixers pathways.
When a student support page should pause and escalate
Student support pages 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 process engine or automatic matching system.
Student match whether it qualifies 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 support page 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 whether it qualifies 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 support page 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, page, CRM, support queue, process 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 team check. 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 process engine or change matching logic. Team check and pathway-limited activation still control access.
Volunteer practice helps you start on campus
Choose this when you want student-to-student campus help first. Volunteer-tagged opportunities are for practice, confidence and resume proof, and they stay separate from paid work.
If there is immediate danger, call emergency services first
For suspicious messages, account access, remote access requests, banking/code pressure or unsafe behaviour concerns, pause and contact support before taking the next step.
You were referred by someone who wants to help
You can look around first. Starting Quick Help does not mean paid work starts immediately; we check the request and explain the next step.
1. Send the linkUse a normal message: “I thought this might help you.”
2. They decideYour friend can read it first, ask a question, or start Quick Help.
3. We check itIf their job goes ahead, we check whether a 5% thank-you applies.
Only share with people who may genuinely need help. To be counted, they should start through your referral link before booking.
Your referral link has been kept
You came through a referral link. You stay in control, and paid work does not start until the next step is clear.
Example: a AUD 300.00 job could mean AUD 15.00 as a thank-you after we check it.
Thank-yous are not guaranteed. To be counted, the person should start through your referral link before booking.
Thank-you guideSee what 5% can look like
Open this small guide only if you want example amounts. The person you refer still chooses whether to get help.
Example job amountPossible thank-you
AUD 100.00AUD 5.00
AUD 200.00AUD 10.00
AUD 300.00AUD 15.00
AUD 500.00AUD 25.00
AUD 1,000.00AUD 50.00
Keep it friendlyShare it as a helpful suggestion, not a sales pitch.
We check itIf the job goes ahead, we check the thank-you before confirming it.
No extra costThe referral thank-you does not add extra cost to the customer.
Example: a AUD 300.00 job could mean AUD 15.00 after we check it. It may not apply to cancelled, refunded, repeat, fake or self-made bookings. Simple sharing works best: “I thought this might help you.”
Fair sharingHow we keep referrals fair
You stay in control. Referrals are checked so the person who shared the link is only thanked when the rules allow it.
Do not refer yourselfA thank-you is for sending someone else to friendly tech help, not for your own booking.
One real request is enoughDo not create the same booking more than once or ask someone to submit fake details.
Only completed work can countA thank-you may not apply if the job is cancelled, refunded, unpaid, unsuitable or does not go ahead.
Use your link firstTo help us count it, the person should start through your referral link before booking.
No pressure: do not promise a guaranteed thank-you, create fake or repeat bookings, refer yourself, or pressure anyone to book.
Before you join
Before you join: The student pathway is designed to help students explore suitable campus, community, referral, support, admin, marketing, project and tech-related opportunities. It does not guarantee jobs, income, referrals, reviews, skill tags, ongoing work or future paid work. Students are not employees of thefixers.app or Your IT & Tech Mates unless a separate written employment agreement is made. Participation does not automatically create an employment, contractor, agency, partnership or franchise relationship. Students must only accept suitable tasks, follow safety and guidance rules, comply with campus or community requirements, and meet any age, tax, legal, consent or parent/guardian requirements that apply.
We received your request
The team will review it, check the safest next step, and contact you if more information is needed. Keep your job reference handy if one was shown.
We will review the safety concern carefully
The team checks the information, looks for the safest next step, and contacts you if more detail is needed. Keep screenshots or messages if safe.