Admin Dashboard §11: Engagement page

[oduwoleeyinojuoluwa44]

Backend for the Super Admin Dashboard's Engagement page (admin/super-admin only).

Scope: Phase A only — notification/resource engagement tables are explicitly out of scope until backend instrumentation exists.

• Stat cards (row of 4): minor assessment adoption rate %, minor assessment completion rate %, retake conversion rate %, avg time to retake after gate clears
• Chart 1: Retake Drop-off by Attempt Number (bar chart — candidates retaking after attempt 1/2/3), empty state "Not enough retake data yet."
• Chart 2: Minor Assessment Uptake by Type (bar chart — Language variants | Specialisation deep dives | Soft skill assessments), track filter dropdown, empty state "No minor assessment data yet."

Gate with @Roles(UserRole.ADMIN) + @AdminTiers(AdminTier.SUPER_ADMIN, AdminTier.ADMIN).

[zub-bee]

I'm confused about what "minor assessments" means. There's nothing like that in our backend system. I'm making an assumption that it means skill and advanced assessments, and that is what I used in my implementation. Is that okay? @oduwoleeyinojuoluwa44

[zub-bee]

I'm confused about what "minor assessments" means. There's nothing like that in our backend system. I'm making an assumption that it means skill and advanced assessments, and that is what I used in my implementation. Is that okay? @oduwoleeyinojuoluwa44

If we're checking the following: Language variants | Specialisation deep dives | Soft skill assessments. Where is that gotten from? This means skill and advanced assessments won't work and it has to work with the assessments in the Credlane database.

I think there's something I missed because there's nothing like minor assessments and I would like to know which assessment table in our database to use

[oduwoleeyinojuoluwa44]

Hey @zub-bee — good catch. Minor assessments (language variants, specialisation deep dives, soft skills) are a planned future feature that doesn't have a database entity yet. They are separate from and should not be mapped to the existing skill/advanced assessment tables.

The correct approach for now is to stub the minor-uptake chart and the two adoption/completion stat cards with empty/zero values and return a message like "No minor assessment data yet." The frontend can wire up the UI, but the data will stay empty until the entity is built.

For the engagement page this means:

• GET /admin/engagement/minor-uptake → return { buckets: [], empty: true, empty_message: "No minor assessment data yet." }
• minor_assessment_adoption_rate and minor_assessment_completion_rate stat cards → return { value: 0, trend: { direction: null, change_percent: null } }

Don't use the skill or advanced assessment tables for these — those are for the retake dropoff and retake conversion rate stats instead.