D
TOA Page & Flow Guide
PRIZM 4 · D Experience documentation framework
View all flows
← Back to AD (P&C) scenarios
Feedback 01 · Internship Requests card

Clarify placement fulfilment and declutter the card

Following the discussion with Marcie, distinguish placement fulfilment from the overall project request: all placements may be submitted while project actions are still pending.

01 · Move the “Fulfilled” badge

Place the badge beside “Total Placement Fulfilment” instead of the top-right corner. It describes the placement total, while Project Statuses continues to show pending actions.

02 · Remove red return-reason boxes

Remove the red “Returned for update” reason boxes from request cards. Retain the concise project-status counts; AD (P&C) can open the submission to read the reasons for return.

Original FigJam feedback · Eileen (Client team)

after discussion with marcie this afternoon, suggest not to put the 'fulfilled' status badge on the top right hand corner, put it somewhere nearer to the "Total Placement Fulfilment" instead. because it will look like it refers to the overarching project request, when actually only the placements are fulfilled, but there are still pending actions.

also, remove all the red "returned for update" boxes to declutter, since adpc will just click into it and will be able to see the reasons for return already.

BeforeOriginal card: status in the top-right corner and a red return-reason box.
Open before in FigJam ↗
Original card: status in the top-right corner and a red return-reason box.
  • 01Badge at request level. “Fulfilled” in the top-right corner can imply that the entire request is complete.
  • 02Return reason on the card. A large red reason box adds clutter below the project-status counts.
AfterUpdated page: Fulfilled beside the placement total; project-status counts retained without a red reason box.
Open after in FigJam ↗
Updated page: Fulfilled beside the placement total; project-status counts retained without a red reason box.
  • 01Badge moved beside Total Placement Fulfilment. Only the placements are fulfilled; project actions may still be pending.
  • 02Return-reason box removed. Project-status counts remain. Open the submission to read the reasons for return.

Red outlines and matching numbers identify the two changes; the dashed outline marks the simplified area after removal. Click a screenshot to view the original image at full size. Both references show the PC3 internship project request before and after the update.

Interactive anatomy

Internship Request Card

Placement fulfilment ≠ project approval. Select a scenario, then try the CTA.

1 PC3 : 2027 Internship Project Request

2 Tech UP1 Jan 2027 – 30 Jun 2027 · 1 Month
Polytechnic Scholar / Polytechnic Student1 March 2027 – 31 Aug 2027 · 2 Months
3 Total Placement Fulfilment
4 Project Statuses
  1. Project Request titleAuto-generation rule: Combine the request’s PC name, a colon, the internship year and the fixed suffix “Internship Project Request”.Format: {PC Name} : {Internship Year} Internship Project RequestExample: PC3 + 2027 → PC3 : 2027 Internship Project Request
  2. Category breakdownDates, duration and submitted / required placements.
  3. Request statusPending, Incomplete, Fulfilled or Expired. Fulfilled refers only to placements.
  4. Project status countsCount projects, not placements. Return reasons appear in details.
  5. Clickable CTAStart, edit or view the submission.
  6. DeadlineExpired requests are read-only.

Request states

Pending
No placements submitted.
Incomplete
Some placements outstanding.
Fulfilled
All required placements submitted.
Expired
Closed after the deadline.

Project states

Not submitted
Project has not been submitted.
Pending
Submitted; awaiting review.
Returned for update
Changes requested; update and resubmit.
Approved
Project review approved.

Interactive documentation example · Figma source ↗

Feedback 02 · Request states & CTAs

Four request states, with the right action

Compact card references. Red outlines highlight placement status and the submission action.

CTAWhen to show it
Start SubmissionBefore submitting anything.
Edit SubmissionOnce something has been submitted, while confirmation is still outstanding.
View SubmissionOnce everything has been confirmed.

Fulfilled describes placement fulfilment, not confirmation of the whole request. The Expired reference separately shows View Submission in Closed Requests.

Pending

FigJam ↗

0 / 6 placements submitted. No project yet.

CTA · Start Submission

Before submitting anything.

Reference correction: the screenshot still says Edit Submission; the updated CTA is Start Submission.

Incomplete

FigJam ↗

2 / 6 placements submitted. Some placements remain outstanding.

CTA · Edit Submission

Once something has been submitted.

Fulfilled

FigJam ↗

6 / 6 placements submitted. Project actions may still be pending.

CTA · Edit Submission → View Submission

Keep Edit Submission while actions remain; use View Submission once everything has been confirmed.

Expired

FigJam ↗

The reference appears under Closed Requests with an Expired badge.

CTA · View Submission

Review the expired submission, as shown in the reference.