Supporting evidence

These notes preserve source details and limits. Original internal files open in the private project repository and need access.

Who the draft personas describe

Source: NCSIM Personas, Confluence draft v4. Edited October 5, 2026 by Anthony Cala; exported October 25. This is first-pass PruTech material for BA review, explicitly not reviewed or approved by SUNY. All 22 pages were read, including the crosswalk, every profile, assumptions and source list. No images are embedded.

What we can use

E-006, source-derived profiles: the 21 profiles come from requirements, the RFP checklist and PruTech's response. They do not report interviews, observed behavior, sample sizes, or usage data. Their priority labels describe the draft's view, not demonstrated audience importance. Confidence is strong about the stated method and approval status. Treat goals and problems as requirements-based ideas to investigate. [Pages 1, 22.]

The six main roles describe access and responsibility: PUB public visitor, LRN signed-in learner, EPR employer/contract trainer, INS instructor, CAD campus administrator, NAD central administrator. Four campus subroles sit inside CAD through campus permission sets. These are not yet behavioral personas. [Page 1.]

The draft cites an October 2 FRD, while the supplied current FRD is October 22. Later decisions may have changed these descriptions. [Page 22; supplied file names.]

Crosswalk and detailed profiles

The draft's PRIMARY, SECONDARY and CANDIDATE labels are retained below so they can be checked later. They are not our recommendation.

Learners and visitors

Employers and other outside parties

Campus staff

Central SUNY roles

What this leaves us needing to learn

The draft provides a useful role and question inventory. It does not explain how common each need is, how people currently choose an offering, which tradeoffs matter, or where behavior differs within one role. Youth/guardians, providers and verifiers have especially explicit gaps. Campus differences and employer visibility could change whole journeys. Keep these distinctions when planning research; do not turn the 21 profiles into 21 confirmed design priorities.

The crosswalk uses Jira epics SUNY-84 through SUNY-93 for the ten modules. Its module links provide traceability, not proof every listed task has an accepted story. See onboarding notes for the later snapshot and RFP notes for the original requirements.

Coverage: PDF pages 1–22 read in full. Export says document-tracking and governance sections were omitted, and embedded Jira items became keys. Those omitted Confluence sections were not supplied or reviewed. Approval status and research-method limits are preserved here.

Related topics: cross-source findings.

Back to the prototype review