ProsFair

Career Transition · Free, self-guided support

Your experience can help you take the next step.

Lost a job, facing changes from AI, or ready for another direction? Understand what you can carry forward, explore realistic options, and build something you can use to pursue work.

Explore before registering. Sign in to save. No course purchase or AI subscription needed.

A practical path forward

  1. 01

    Recognise what you bring

    Translate real responsibilities and decisions into useful experience.

  2. 02

    Try a possible direction

    Work through a realistic case with examples and review notes.

  3. 03

    Show what you can do

    Build private evidence, then pursue employment or paid projects.

Start where you are

A plan that fits what you need now.

Three directions to investigate

Explore the work before choosing the path.

These are starting points, not predictions of demand, pay, or hiring. Your saved workspace can compare current ProsFair opportunities; employers set their own requirements.

Customer onboarding and support operations

Help customers get started, coordinate handovers, and handle exceptions with care.

  • Clarify what a customer needs
  • Track setup dependencies and ownership
  • Explain delays and escalate unresolved blockers

Practise a clear customer update and a dependency checklist. Allow about 30–45 minutes; pause whenever needed.

See this pathway’s exercise →

Knowledge and process operations

Turn scattered working knowledge into procedures people can follow and maintain.

  • Gather and check source instructions
  • Write steps and exception handling
  • Assign a document owner and review trigger

Practise a short procedure with an exception and a review checklist. Allow about 30–45 minutes.

See this pathway’s exercise →

Operations coordination and reporting

Organise operational records, explain uncertainty, and coordinate useful follow-up.

  • Check records for duplicates and missing values
  • Summarise performance with a stated method
  • Assign follow-up actions and explain limitations

Practise a small weekly report in the editor or a spreadsheet you already have. Allow about 30–45 minutes.

See this pathway’s exercise →

See what you will make

Realistic practice. Something useful to show.

Open a case to see its source facts, starting template, worked example, and AI review exercise. In your private workspace, write your response and turn it into a portfolio sample.

Customer onboarding and support operations

Fictional practice · about 30–45 minutes

Customer onboarding and support operations

You coordinate onboarding for fictional company Cedar Studio. A customer expects to start on Friday, but an account import is blocked. Produce a checklist, customer update, and escalation plan.

  • The import needs approval from Cedar’s account owner, Sam.
  • Sam has not approved access. Engineering can estimate timing only after approval.
  • The customer asks for an update by Thursday at 14:00 UTC.
  • No refund or completion date has been approved. Never request a password.
Open a starting template
SETUP CHECKLIST
Task | Owner | Dependency | Status | Next update

CUSTOMER UPDATE
What we know:
What remains uncertain:
Our next update:

ESCALATION PLAN
Trigger:
Owner:
Information needed:
See a worked example

Checklist: Sam approves import access → engineering estimates completion → coordinator confirms the revised plan. Customer update: Your import is awaiting account-owner approval. We cannot confirm Friday yet. I will update you by Thursday, 14:00 UTC, even if approval is still pending. Escalation: Contact the account owner now; if approval remains missing by the update deadline, escalate to the onboarding lead with the blocker, impact, and action taken. Limitation: This plan cannot establish engineering capacity or authorise a refund.

One possible approach. Write and explain your own response.

Review an AI-style draft

This intentionally flawed training draft needs your judgment. No AI account or paid tool is needed.

Great news! Engineering has confirmed your import will finish Friday. Send us your admin password to speed things up. If we miss Friday, you will receive a full refund. There is no need for another update.
Compare with review notes
  • Engineering has not confirmed a completion date
  • Passwords must never be requested
  • A refund was not authorised
  • The promised Thursday update still needs an owner

Self-review checklist

  • Every blocked task has an owner and dependency
  • The update separates known facts from estimates
  • A next-update time and escalation trigger are explicit
  • No passwords, invented promises, or unapproved refunds
Optional supporting resourceWriting clear procedures

Use the guidance on ordered steps to improve your setup checklist.

Free to read; no purchase required. Reviewed 2026-11-04. The exercise works without this link.

Knowledge and process operations

Fictional practice · about 30–45 minutes

Knowledge and process operations

A fictional support team needs a procedure for duplicate invoice reports. Turn the source notes into a one-page procedure with an exception route and maintenance notes.

  • Agents can compare invoice IDs and dates in a read-only billing view.
  • Only the billing lead can approve a credit or change an invoice.
  • If invoice IDs differ, send both IDs to the billing lead through the approved internal channel.
  • Customer-facing examples must use fictional identifiers; do not copy payment details.
Open a starting template
PURPOSE AND AUDIENCE

BEFORE YOU START

NUMBERED STEPS
1.
2.
3.

EXCEPTIONS AND ESCALATION

DOCUMENT OWNER AND REVIEW TRIGGER

SOURCE LIMITATIONS
See a worked example

Purpose: Help support agents investigate a possible duplicate invoice. 1. Open the approved read-only billing view. 2. Compare invoice IDs and dates. 3. For different IDs, send both fictional example IDs and the issue summary to the billing lead through the internal channel. Exception: If access or records are missing, stop and ask the billing lead. Do not approve a credit. Owner: Billing lead. Review after a billing-process change. Limitation: The notes do not establish refund eligibility or a response deadline.

One possible approach. Write and explain your own response.

Review an AI-style draft

This intentionally flawed training draft needs your judgment. No AI account or paid tool is needed.

Resolve duplicates by editing the invoice directly. Promise every customer a credit within 24 hours. Paste their full card details into the public knowledge base so other agents can compare records.
Compare with review notes
  • Agents have read-only access and cannot edit invoices
  • Neither credit eligibility nor a 24-hour promise is established
  • Payment details must not appear in public documentation
  • The billing lead must handle approval and exceptions

Self-review checklist

  • Steps are ordered and usable by the stated audience
  • Approval boundaries match the source notes
  • Missing information and exceptions have a route
  • An owner and review trigger are included
Optional supporting resourceWriting clear procedures

Check the order, wording, and exception handling of your procedure.

Free to read; no purchase required. Reviewed 2026-11-04. The exercise works without this link.

Operations coordination and reporting

Fictional practice · about 30–45 minutes

Operations coordination and reporting

Prepare a weekly fulfilment report using only the fictional records below. Identify data issues, calculate an on-time rate with an explicit denominator, and propose two follow-ups.

  • Order A | due Monday | delivered Monday | owner Lee
  • Order B | due Tuesday | delivered Wednesday | owner Jo
  • Order B | due Tuesday | delivered Wednesday | owner Jo (duplicate)
  • Order C | due Wednesday | delivery date missing | owner Lee
  • Order D | due Thursday | delivered Thursday | owner Jo
  • The reporting cutoff is Friday. A missing date does not establish whether delivery happened.
Open a starting template
DATA CHECKS

SUMMARY
Unique orders:
On-time rate and denominator:
Unknown status:

FOLLOW-UPS
Action | Owner | Next check

LIMITATIONS
See a worked example

Remove one duplicate B record: four unique orders remain. A and D were on time, B was late, and C has unknown status. Among the three orders with a known delivery date, 2/3 (66.7%) were on time. Across all four orders, 2/4 (50%) are confirmed on time; C remains unknown. Follow-ups: Lee checks C’s delivery status; Jo reviews the cause of B’s delay. Agree check-in times with each owner. Limitation: This small, incomplete sample does not establish a trend or explain the cause of a delay.

One possible approach. Write and explain your own response.

Review an AI-style draft

This intentionally flawed training draft needs your judgment. No AI account or paid tool is needed.

All five orders were delivered. The on-time rate is 80%, proving a strong improvement this month. Order C was late because Lee was careless. No follow-up is needed.
Compare with review notes
  • There are four unique orders, not five
  • Order C’s delivery status is unknown
  • The 80% calculation has no supported basis
  • There is no comparison period or evidence about blame; follow-ups are needed

Self-review checklist

  • The duplicate is handled explicitly
  • Calculations state the denominator and cutoff
  • Missing data stays unknown
  • Follow-ups name owners without inventing causes or trends
Optional supporting resourceCreate and format spreadsheet tables

Optional help organising the fictional records. The text editor is enough to complete this exercise.

Help page is free to read; Excel licensing may vary. No purchase required. Reviewed 2026-11-04. The exercise works without this link.

Leave with a next action and work you can explain.

Keep your notes and samples private, save and return at your own pace, and choose what to share. You can apply immediately, change direction, or use your evidence outside ProsFair. Productive employer work should be paid.

Start your saved plan →