8
Published — awaiting MJ takeup
↑ 2 from last week
5
Taken by MJ (active)
This month
2
At risk — no taker < 2 BD
⚠ Needs action
3
Cancelled this month
May 2026
21
Completed this month
May 2026
Training & OJT Status
Business rules — Training & OJT (§4.3)
OJT = Completed is the eligibility gate. Training Completed alone is not sufficient. Both must be done before an MJ can receive job listings for a role.
System blocks assignment if OJT ≠ Completed for the target role and displays an error message to staff.
Status values (Training and OJT): NA / Pending / Scheduled / In Progress / Completed.
Schema is role-agnostic: (MJ_ID, Role_Code, Training_Type_Code, Status) — extensible for future roles.
Open questions — Training (§4.3)
[H4 — High] Training role list is incomplete and overdue. 4 roles confirmed, 5+ unnamed additional roles exist. OJT data model and eligibility engine cannot be finalised. Escalate to Maisarah.
[M10 — Medium] Withdrawn/Terminated exit requires offline acknowledgement — but there is no system field to record or audit this. Audit risk if disputed.
Owner: AAC / Maisarah · Target: URG sign-off 8 Jun 2026
| Service role | Pending | Scheduled | In progress | Training completed | OJT completed | Eligible MJs |
|---|---|---|---|---|---|---|
| 🤝 Chaperone | 3 | 2 | 1 | ✓ 15 | ||
| 💬 Befriending | 5 | 3 | 2 | ✓ 10 | ||
| 🏠 Home Assessment | 8 | 4 | 0 | ⚠ 5 | ||
| 🏛 Centre Assistant | 2 | 1 | 1 | ✓ 20 |
⚠ [H4] Training role list pending finalisation from Maisarah — counts above are based on 4 confirmed roles only.
Job Listing & Assignment
Business rules — Publishing & Matching (§5.2–5.3)
Lead time: ≥ 3 business days minimum. < 3 BD = system blocks publication. Public holidays excluded from BD count.
Urgent flag: Published 3–5 BD before job date = "Urgent" badge shown on C4Me listing.
Matching (all criteria must be met): OJT = Completed, language, gender, service boundary, required skills.
Slots: Chaperone/Befriending = 1 confirmed + 4 waitlist. Home Assessment = 2 confirmed + 4 waitlist.
No-taker alert: 2 BD before — SCC Nurse, AE, and all AAC Staff notified. Client informed of risk.
Auto-cancel: No confirmed MJ 1 BD before job → auto-cancelled. SCC Nurse assigns SCC staff or cancels appointment.
Open questions — Jobs (§5–6)
[H1 — High] Waitlist model conflict: sequential 12h-per-person chain vs open simultaneous grab. Open grab is working assumption. Not formally confirmed — core state machine logic.
[H2 — High] Home Assessment partial cancel: if 1 of 2 confirmed MJs cancels < 1 BD, does the whole job cancel or just re-open the slot?
[H3 — High] MJ fee table entirely absent. Payment module cannot be designed. Overdue from Finance.
[M4 — Medium] Service boundary: postal code exact match vs district range? Two different semantics — cannot build engine until resolved.
[M6 — Medium] Urgent flag — does it attract a higher MJ pay rate? If yes, must be in fee table before notification engine is built.
Can published task be editable? If yes, what fields can be edited?
ANSWER:
Owner: AAC / Maisarah · Target: URG sign-off 8 Jun 2026
| Job ID | Type | Facility | Date | Time slot | Client | Status | MJ assigned | Waitlist | Urgency | Actions |
|---|
⚠️ At-risk jobs
MJ-2026-001 · Chaperone
SCC — Queenstown · 20 May 14:00
0 takers · Auto-cancel: Tue 19 May
MJ-2026-005 · Centre Assistant
SCC — Bishan · 23 May 13:00
0 takers · Auto-cancel: Thu 21 May
⚙️ Business rules
System
OJT gate — eligibility
MJ must have OJT = Completed for the specific role. Assignment blocked if not met.
Waitlist
Open grab model (working assumption)
Slot opens → any waitlisted MJ can grab. First committed write wins. Sequential 12h model removed.
Deadline
Auto-cancel at 1 BD
No confirmed MJ 1 BD before job → auto-cancelled. SCC Nurse assigns SCC staff or cancels client.
Alert
No-taker alert at 2 BD
SCC Nurse, AE and all AAC Staff notified. SCC informs client of risk. Staff must intervene.
Slots
Home Assessment — 2 confirmed required
Confirmed MJ names shown on listing. If 1 cancels <1 BD, whole job status TBC (pending H2 resolution).
❓ Open questions
H1 — High
Waitlist model not formally confirmed
Open grab vs sequential — must be voted at URG. Core state machine logic.
H2 — High
Home Assessment partial cancel undefined
If 1 of 2 MJs cancels within 1 BD — whole job cancel or re-open slot? Blocks cancel logic.
H3 — High
MJ fee table absent
No confirmed rates per role. Payment module cannot be designed. Overdue from Finance.
M1 — Medium
Waitlist race condition
Simultaneous grab by 2 MJs → requires db-level optimistic locking or atomic slot claim.
M4 — Medium
Service boundary logic undefined
Postal code exact match vs district range — different semantics. Cannot build matching engine.