D
TOA Page & Flow Guide
PRIZM 4 · D Experience documentation framework
View all flows

Mentor-first operating model

One record, several daily entry points

A Mentor may start from a project workload, an applicant card, the interview calendar, or a notification. Every entry opens the same applicant interview record and applies the same status, scheduling, document, history, and outcome rules.

Cross-role interview workflow

Mentor, Applicant and IO actions

Each lane shows who owns the next action from interview setup through the final outcome. Handoffs follow the FigJam flow for proceed to offer, talent pool, and rejection.

M

Mentor

A

Applicant

IO

Internship Officer

1 · Invite

Prepare and send interview setup

  • Review candidate and project context
  • Send one fixed slot or up to five shared slots
  • Monitor invitation and rescheduling status
Awaiting Interview → Invitation Sent

Review invitation

Choose an available 30- or 60-minute slot, or request another time with an optional comment.

Applicant response required
No action — shortlist has already been dispatched.
2 · Schedule

Resolve the schedule

When another time is requested, review the comment and send a replacement slot or record that scheduling will happen outside TOA.

Rescheduling Required

Confirm attendance

Accept the proposed time and use the confirmed start–end range for the interview.

Interview Scheduled
Track interview progress and exceptions.
3 · Interview

Conduct and complete the interview

  • Review CV, transcript and applicant context
  • Conduct the interview
  • Mark the interview complete
Interview Completed

Attend interview

Join using the agreed meeting details. No outcome or decision action is exposed to the applicant.

No decision until the Mentor submits an outcome.
4 · Outcome

Submit evidence and recommendation

Review transcript and AI-assisted summary, edit notes, then submit one recommendation.

Recommend for offerReferReject
Outcome Submitted
Wait for the formal IO decision.

Review and record the formal decision

Use the Mentor evidence and recommendation to choose the business outcome.

Proceed to offerMove to Talent PoolReject application
5 · Decision
Interview work is read-only after submission.

Respond when an offer is extended

Review the formal offer and accept or decline before the response deadline. Talent-pool and rejection outcomes are communicated without an offer action.

Offer Extended / Final outcome

Complete the outcome path

  • Proceed to offer: issue and track the offer
  • Talent Pool: preserve applicant context for future matching
  • Reject: close the application and retain the decision record

Where a Mentor starts

The choice of view changes how work is found, not how the interview record behaves.

01

My Projects

Review attention states within one assigned project, then manage its applicants.

02

Applicants

Scan applicants across projects by workflow stage and continue the next action.

03

Interviews

Use List, Week, or Month views to coordinate scheduled and proposed interview times.

04

Notification

Open a rescheduling request, reminder, or completed-interview task directly.

Six realistic Mentor scenarios

Each scenario identifies the trigger, the Mentor’s job, the system behaviour, and the next status.

Scenario 01

Applicant awaiting interview

Awaiting Interview
Trigger

The Internship Officer sends an applicant to an approved project.

Mentor action

Review project fit, transcript and CV, then decide how to arrange the interview.

System rule

No interview timeslot exists at this stage. The record only shows profile context and the setup action.

Awaiting Interview→Set up interview→Invitation Sent

Scenario 02

Invitation sent, awaiting response

Interview Invitation Sent
Trigger

The Mentor sends one fixed slot or up to five shared slots.

Mentor action

Monitor the sent setup and its history; no further action is required until the applicant responds.

System rule

Once a shared time is confirmed, it is removed from the remaining applicants’ available choices.

Invitation Sent→Applicant confirms→Interview Scheduled

Scenario 03

Applicant requests another time

Rescheduling Required
Trigger

The applicant states that the previously sent times do not work and may add a comment.

Mentor action

Review the previous setup and comment, then send one replacement slot or record that scheduling will happen outside TOA.

System rule

The previous slots remain in history. Shared slots are not available for this state.

Rescheduling Required→Replacement slot→Invitation Sent

Scenario 04

Interview day

Interview Scheduled
Trigger

The applicant confirms a 30- or 60-minute interview time.

Mentor action

Review the applicant context and meeting details, conduct the interview, then mark it complete.

System rule

Every interview displays a start–end range. Dragging a calendar item to another time requires confirmation.

Interview Scheduled→Conduct interview→Interview Completed

Scenario 05

Interview completed, outcome required

Interview Completed
Trigger

The interview has ended and the Mentor must record the evidence and recommendation.

Mentor action

Open the dedicated outcome page, review the transcript and AI-assisted summary, edit notes, then choose a recommendation.

System rule

Drafts remain private. Final submission requires a second confirmation and ends with a success toast.

Interview Completed→Save draft / review→Outcome Submitted

Scenario 06

Outcome submitted

Outcome Submitted
Trigger

The Mentor sends the final outcome to the Internship Officer.

Mentor action

Review the read-only history if needed; no further interview action is required.

System rule

The Internship Officer continues with the offer, rejection, or referral decision.

Outcome Submitted→Await IO decision

Status lifecycle

The same canonical status must appear consistently in Projects, Applicants, Interviews, side panels, history, and notifications.

Awaiting InterviewNo interview timeslot yet. Mentor setup is required.
Interview Invitation SentFixed or shared availability has been sent.
Interview ScheduledA 30- or 60-minute time is confirmed.
Interview CompletedThe Mentor must complete notes and recommendation.
Outcome SubmittedThe record waits for the Internship Officer’s decision.
Exception loop · Rescheduling Required
From Interview Invitation Sent or Interview Scheduled, an applicant may request another time. The Mentor reviews history and comments, sends one replacement slot, and returns the record to Interview Invitation Sent until the applicant confirms.

How a Mentor sets interview timeslots

Availability is selected by week. Unavailable times remain visible for context but are disabled.

A

One fixed slot

  1. Select a week.
  2. Select 30 or 60 minutes.
  3. Select an available date and start time.
  4. Review the full start–end range.
  5. Send to one applicant for confirmation.
B

Shared slots

  1. Select duration and week.
  2. Add available times across one or more dates.
  3. Review the selected-slots tray.
  4. Keep between 1 and 5 slots.
  5. Send to the selected applicant(s).
C

Replacement slot

  1. Review the original setup and applicant comment.
  2. Select one replacement time or skip portal setup.
  3. Confirm before sending.
  4. Do not offer Shared slots in this state.
Shared-slot behaviour
A confirmed time is removed from the selectable availability shown to other applicants. Do not show other applicants’ identities or an “occupied by” label.

Interview outcome flow

Outcome work is substantial enough to use a dedicated page rather than a dialog or side panel.

Open outcome prototype

Evidence and editable AI support

  • Applicant, project, interview date and time context
  • Interview transcript and evidence
  • Mentor interview notes
  • AI-assisted summary, clearly labelled and editable
  • Strengths, weaknesses and recommendation evidence

Mentor feedback

The final selection uses the agreed B3 wording:

Recommend for offerRejectRefer

Save draft remains available before submission. Sending the outcome requires final confirmation.

Mentor information architecture

Each page has a specific purpose while sharing one interview record model.

L1

My Projects

  • Active and closed projects
  • Mentor action status counts
  • Project-specific entry
L1

Applicants

  • Cross-project workflow board
  • Five stages in one row
  • Stage-specific detail panel
L1

Interviews

  • List, Week and Month
  • Scheduled and proposed ranges
  • Calendar coordination
L2/L3

Task pages

  • Interview setup
  • Applicant detail
  • Dedicated outcome page
Mentor questionBest entry pointWhy
Which of my projects needs attention?My ProjectsCompares project-level action states and counts.
What is the next action for this applicant?ApplicantsOrganises every applicant by current workflow stage.
What interviews are happening this week?InterviewsShows exact 30- or 60-minute time ranges across projects.
What changed for this interview?Applicant detail / historyShows the status-specific setup history and comments.