Attachment 6.xlsx
XLSX spreadsheet 80 KB Posted
- Attached to
- FIND YOUR FUTURE PORTAL State and local contract opportunity
- Solicitation number
- 5400030161
- Issued by
- Richland County, South Carolina
About this file
Summary of CCWD FYF Portal Requirements Traceability Matrix
This document is a Requirements Traceability Matrix (RTM) for the Find Your Future (FYF) Portal, a comprehensive digital platform being procured by the State of South Carolina to support education-to-employment pathways. The RTM captures epic-level functional and technical requirements across multiple capability areas including accessibility support, analytics, assisted support, career pathways tools, personalized pathway experiences, client account management, employer support, job seeker support, and intelligent automation. The portal is designed to serve multiple user types including students, job seekers, employers, educators, advisors, and parents/guardians across K-12, postsecondary, and workforce development systems. Requirements are organized with phased implementation timelines, with releases designated as MVP (minimum viable product), R1.1 (Release 1.1), or future revisions. Offerors must complete the traceability matrix by specifying how each requirement will be met through product configuration, customization, future product releases, third-party integrations, or declining to propose functionality, along with detailed explanations and proposed revision placements based on implementation approach, dependencies, and funding considerations.
The RTM addresses critical functional areas including integration with South Carolina Workforce Online System (SCWOS) and other partner agency systems; support for multiple languages and WCAG accessibility standards; AI-assisted capabilities with human-in-the-loop oversight and responsible AI governance; secure data sharing with comprehensive privacy controls and consent management; credential and digital wallet functionality; cross-agency case management and service coordination; and comprehensive reporting and analytics for program evaluation and policy decision-making. The document emphasizes that the RTM represents living documentation that may evolve through discovery and implementation phases, with final release placement subject to refinement based on solution design, agency readiness, funding availability, and State approval. Offerors are required to address all 328+ requirements and demonstrate how their proposed solution will support the State's vision of creating an integrated, user-centered platform that removes barriers to education and employment while protecting privacy and maintaining agency autonomy over program determinations and systems of record.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| Attachment J.docx | DOCX document | |
| Exhibit B.xlsx | XLSX spreadsheet | |
| Attachment 5.xlsx | XLSX spreadsheet | |
| Attachment 1.xlsx | XLSX spreadsheet | |
| Schedule B.docx | DOCX document | |
| Attachment I.docx | DOCX document | |
| Schedule A.docx | DOCX document | |
| Attachment K.docx | DOCX document | |
| Attachment 2.xlsx | XLSX spreadsheet | |
| Attachment L.xlsx | XLSX spreadsheet | |
| Attachment 4.xlsx | XLSX spreadsheet | |
| Attachment E.docx | DOCX document | |
| Attachment 3.xlsx | XLSX spreadsheet | |
| Attachment C.docx | DOCX document | |
| Solicitation 5400030161.docx | DOCX document | |
| Exhibit A.docx | DOCX document | |
| Exhibit C.xlsx | XLSX spreadsheet |
Show all 17
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| Attachment 6 - CCWD FYF Portal Requirements Traceability Matrix |
| Offerors shall complete and submit this Requirements Matrix with their proposal response. Offerors must address all requirements included in this Requirements Matrix. This Requirements Traceability Matrix represents epic level requirements for this procurement and is a living document. Additional granular requirements may be added as the Program evolves and as insights from Partner Agencies and systems continue to develop. |
The “Release / Revision Designation” column on the Functional tab identifies CCWD’s current anticipated release phasing for requirements already prioritized for the initial implementation. Requirements marked MVP are expected to be included in the initial MVP or Release 1 launch. Requirements marked R1.1 are expected to follow in Release 1.1 after the MVP launch.
For any requirement not already marked MVP or R1.1, the Offeror shall propose an appropriate proposed future revision number in the "Release / Revision Designation” column and provide the rationale in the “Explanation or Comments” column. Proposed future revision designations should be based on the Offeror’s recommended implementation approach, solution design, sequencing experience, dependencies, level of effort, and the funding likely needed to execute that revision. The Offeror’s proposed designations should help CCWD understand how remaining requirements could be logically grouped, funded, and implemented after MVP and R1.1.
Offerors shall complete the “Requirement is met by” and “Explanation or Comments” columns for every requirement, regardless of whether the requirement is marked MVP, R1.1, or assigned a proposed future revision. Final release and revision placement may be refined during implementation based on discovery, solution design, dependencies, agency readiness, funding availability, and CCWD approval.
For each requirement on the Functional tab, the Offeror shall indicate which of the following five options will be primarily used to meet the requirement:
Product Configuration Select this option when the requirement is met by the proposed solution as part of its native functionality, either in its original unmodified state or through System Configurations. System Configurations are adjustments made through an administrator portal or other native tools that dictate system behavior, workflow, or feature display. Use of native scripting tools qualifies as customization and must be labeled as such.
Customization Select this option when the requirement is met through custom coding, development, or scripting that must be uniquely developed by a technical resource. Use of native scripting tools qualifies as customization. Offerors must provide comments elaborating on this selection.
Future Product Release Select this option when the requirement is not met by the proposed solution but will be met by a future system update or upgrade. Offerors must provide the version number and planned release date.
Integration with Third Party Product or Solution Select this option when the requirement can only be met through integration with a third-party product or solution and is not fulfilled by the main solution. Offerors must identify the third-party product or solution.
Not Proposed Select this option when the Offeror is declining to provide the functionality as part of the proposed response. Offerors may provide comments explaining this decision.
Functional CCWD FYF Portal Requirements Traceability Matrix The CCWD FYF Portal Requirements Traceability Matrix (RTM) captures epic-level requirements needed to help vendors design a high-level solution. The RTM is not intended to provide lower-level requirements in order to allow future solution vendors to determine how the functionality will be implemented at their discretion. Each requirement listed in the RTM is tied to a capability and a feature to group requirements based on the areas of functionality the requirement is associated with. Solution vendors will elaborate on the feature-level requirements to identify lower-level requirements that fit their solution and delivery methodology.
| ID | ||
| Abhinav Chawla: Unique ID number used to identify the item in the RTM. | Number. | ReqID |
| Lee, Jason: Unique identifier for each requirement, identifying which component it belongs to and the requirement number. | Requirement Type |
Lee, Jason:
| Identifies if the Requirement is Technical or Functional in nature | Category |
| Lee, Jason: Identifies application area in the solution. Includes Portal, Integrated Data Solution, and Customer 360. | Requirement |
Lee, Jason:
| Captures how a product, system, or service must behave to fulfill a specific customer need | Release / Revision Designation | Requirement is met by: | Explanation or Comments | ||||
| 103 | 1 | ACS - 1 | Functional | Accessibility Support | The system shall comply with all legislative and WCAG standards for accessibility | MVP | |
| 104 | 2 | ACS - 2 | Functional | Accessibility Support | The system shall be accessible to users with disabilities and shall present all content using plain language principles to ensure information is easy to understand, perceive, and operate for a broad range of users. | MVP | |
| 105 | 3 | ACS - 3 | Functional | Accessibility Support | The system shall comply with accessibility standards and support equitable access for employers of varying sizes and capacities. | MVP | |
| 106 | 4 | ACS - 4 | Functional | Accessibility Support | The system shall support language translation for event listings and calendar interfaces where available. | ||
| 107 | 5 | ACS - 5 | Functional | Accessibility Support | The system shall comply with all applicable federal, state, and local accessibility legislation. | MVP | |
| 108 | 6 | ACS - 6 | Functional | Accessibility Support | The system shall design and document additional functionalities, workflows, and automation scripts with custom reports. | ||
| 109 | 7 | ACS - 7 | Functional | Accessibility Support | The system shall support multilingual access by providing all user-visible text in a WCAG-compliant and fully translatable format and shall ensure full usability of all user-facing functionality for individuals with disabilities, including users of assistive technologies. | MVP | |
| 110 | 8 | ACS - 8 | Functional | Accessibility Support | The system shall provide native‑language translations for designated supported languages. | ||
| 111 | 9 | ACS - 9 | Functional | Accessibility Support | The system shall support translation of outgoing system‑generated communications into supported languages. | ||
| 112 | 10 | ACS - 10 | Functional | Accessibility Support | The system shall accept and process incoming user‑submitted text in supported languages. | ||
| 113 | 11 | ACS - 11 | Functional | Accessibility Support | The system shall generate documents in translated form for supported languages. | ||
| 114 | 12 | ACS - 12 | Functional | Accessibility Support | The system shall provide closed captioning for all video content. | ||
| 13 | ACS - 13 | Functional | Accessibility Support | The system shall ensure all user-facing text, system-generated communications, AI-assisted interactions, community features, mobile experiences, applet experiences, and user-generated community or mentorship content meet applicable WCAG accessibility requirements and plain-language principles. | MVP | ||
| 14 | ACS - 14 | Functional | Accessibility Support | The system shall support translation of user-facing portal content and communications into the State-designated supported languages, including English, Spanish, German, Chinese, French, Tagalog, Vietnamese, Russian, Portuguese, and Hindi. | R1.1 | ||
| 115 | 15 | AN - 1 | Functional | Analytics | The system shall collect and analyze user interaction and experience data within the portal, including click‑through rates, bounce rates, click‑path analysis, conversion analytics, and search/text insights (e.g., sentiment analysis). | MVP | |
| 116 | 16 | AN - 2 | Functional | Analytics | The system shall capture user experience via polls, surveys, interviews, and other methods. | ||
| 117 | 17 | AN - 3 | Functional | Analytics | The system shall support data standardization, validation, quality management, and auditability across data sources to enable accurate, consistent, and traceable statewide reporting | R1.1 | |
| AN-4 | Functional | Analytics | The system shall generate and use a non identifiable, pseudonymous analytics identifier that enables analysis of user interactions, pathway usage, search behavior, and other State approved analytics without exposing personal identity attributes. The identifier shall not be reversible and shall comply with all State approved privacy, consent, and data sharing rules. | R1.1 | |||
| 100 | 18 | AN - 5 | Functional | Analytics | The system shall support identification of factors associated with program completion, non‑completion, and successful employment outcomes. | R1.1 | |
| 19 | AN - 6 | Functional | Analytics | The system shall provide a comprehensive data quality management capability that supports the definition and enforcement of data ownership, validation rules, and data standards; maintains data lineage and refresh schedules; detects and manages duplicate records; and enables exception handling, stewardship workflows, and resolution of data quality issues through auditable processes. | R1.1 | ||
| 33 | 20 | AN - 7 | Functional | Analytics | The system shall provide embedded, in-context feedback and issue reporting capabilities that enable users to submit feedback and report issues at specific points within workflows, and shall support tracking, prioritization, and management of identified issues and usability improvements through a structured improvement backlog and resolution process. | ||
| 21 | AN - 8 | Functional | Analytics | The system shall provide analytics on AI usage, including frequency of AI-assisted form completion, AI-generated posting drafts, moderation automation events, user interactions with AI-generated content, and related audit or governance indicators. | |||
| 22 | AN - 9 | Functional | Analytics | The system shall support community engagement analytics, including participation trends, moderation activity, flagged content categories, mentor/mentee matching activity, community category utilization, and other State-approved indicators for safe and compliant operation. | |||
| 23 | AN - 10 | Functional | Analytics | The system shall support analytics and reporting for employer job posting distribution, including selected posting destinations, posting status, location coverage, rejection and resubmission status, duplicate detection, reconciliation results, and closure outcomes. | MVP | ||
| 24 | AN - 11 | Functional | Analytics | The system shall capture support service navigation feedback, issue reports, referral activity, service demand, resource utilization, task completion, and other State-approved information needed for continuous improvement. | R1.1 | ||
| 25 | AN-12 | Functional | Analytics | The system shall support the State’s use of de‑identified, anonymized, or pseudonymized data derived from user‑entered information and data stored in accordance with applicable consent, policy, and data‑sharing agreements, ensuring such data cannot be reasonably re‑identified and complies with all applicable privacy laws, DUAs/MOUs, and State‑approved governance rules. | R1.1 | ||
| 37 | 26 | AS - 4 | Functional | Assisted Support | The system shall provide AI‑assisted customer support through chatbots and generative AI that leverage the portal’s instructional and informational knowledge base, and shall integrate with augmented support channels to assist users before, during, or in place of human‑assisted support. | ||
| 34 | 27 | AS - 1 | Functional | Assisted Support | The system shall provide multi‑channel user assistance, including email, SMS/text messaging, and self‑service resources such as FAQs. | ||
| 35 | 28 | AS - 2 | Functional | Assisted Support | The system shall provide AI‑assisted customer support through chatbots and generative AI that leverage the portal’s instructional and informational knowledge base and shall integrate with augmented support channels to assist users before, during, or in place of human‑assisted support. | ||
| 38 | 29 | AS - 3 | Functional | Assisted Support | The system shall provide a secure, role‑based digital workspace that enables authorized advisors and professionals across agencies to collaborate on unified participant plans, manage case notes, communicate securely, and support participants subject to consent and data‑sharing agreements. | ||
| 39 | 30 | AS - 4 | Functional | Assisted Support | The system shall provide a unified participant view that integrates education history, training participation, support services, credentials, and employment outcomes with permission by the user. | ||
| 40 | 31 | AS - 5 | Functional | Assisted Support | The system shall support the evolution of a participant’s plan over time, allowing updates and additions as the user transitions from middle school through postsecondary education, workforce entry, and career advancement, with permission by the user. | ||
| 41 | 32 | AS - 5 | Functional | Assisted Support | The system shall provide a role‑based cross‑agency case view showing referrals, milestones, services accessed, and outcomes. | ||
| 42 | 33 | AS - 7 | Functional | Assisted Support | The system shall provide a user support capability that enables live assistance, escalation, and coordinated resolution through but not limited to, ticket tracking, callback or contact request options, and routing to relevant knowledge-based resources. | ||
| 43 | 34 | AS - 8 | Functional | Assisted Support | The system shall provide an appointment scheduling capability that enables users to book, reschedule, and manage appointments with advisors, case managers, career navigators, training providers, workforce centers, employer support staff, and other authorized representatives, based on real‑time availability, with integrated confirmations, reminders, and calendar synchronization. | ||
| 35 | AS - 9 | Functional | Assisted Support | The system shall provide a role-based counselor, navigator, advisor, and case manager workbench that allows authorized staff to view and manage assigned or authorized users subject to role-based access controls, consent rules, privacy requirements, and State-approved configuration. | R1.1 | ||
| 36 | AS - 10 | Functional | Assisted Support | The system shall support caseload management, user search, user status views, pathway review, milestone tracking, task assignment, appointment scheduling or tracking, referral initiation and follow-up, warm hand-off tracking, document request tracking, communications, alerts, reminders, and escalation workflows. | |||
| 37 | AS - 11 | Functional | Assisted Support | The system shall allow authorized support staff to record notes or interaction history where permitted and to help users understand recommended next steps, available supports, education and training options, employment opportunities, barriers to progress, and required actions without replacing authoritative systems of record. | |||
| 38 | AS - 12 | Functional | Assisted Support | The system shall allow the State to configure staff roles, permissions, visibility, supervisory access, confidentiality restrictions, program boundaries, regional boundaries, assignment rules, and reporting on caseloads, referrals, pathway progress, service coordination activity, response times, and outcomes. | |||
| 39 | AS-13 | Functional | Assisted Support | The system shall provide a Case Management Interoperability Framework that enables the portal to retrieve, interpret, normalize, and route case‑management information across multiple State‑approved case‑management systems only for cases where the user has been positively matched and authorized access has been confirmed by the case‑management system owner. | R1.1 | ||
| 40 | AS-14 | Functional | Assisted Support | The system shall support bi‑directional exchange of approved case‑management information with SCWOS and other State‑approved systems, including service‑plan elements, referral statuses, appointment information, milestone updates, and case‑note metadata, subject to role‑based access, consent rules, and data‑sharing agreements. | R1.1 | ||
| 41 | AS-15 | Functional | Assisted Support | The system shall support cross‑program case‑management coordination by enabling authorized staff to view interoperable referral workflows, service‑plan components, appointment information, and milestone tracking across participating programs and partner systems. | |||
| 42 | AS-16 | Functional | Assisted Support | The system shall allow the Workbench to retrieve approved case‑management information from SCWOS and other partner systems and to route authorized updates back to those systems in accordance with role‑based access, consent rules, and State‑approved configuration. | |||
| 43 | AS-17 | Functional | Assisted Support | The system shall enforce consent‑controlled interoperability so that case‑management information retrieved from external systems is displayed, routed, or updated only when permitted by user consent, role‑based access, data‑sharing agreements, and State‑approved privacy rules. | R1.1 | ||
| 44 | AS-18 | Functional | Assisted Support | The system shall support interoperable referral initiation, referral follow‑up, warm hand‑off tracking, and service‑coordination workflows that operate across SCWOS and other State‑approved case‑management systems without replacing authoritative systems of record. | |||
| 45 | AS-19 | Functional | Assisted Support | The system shall support interoperable appointment scheduling and appointment status exchange with SCWOS and other State‑approved systems, including booking, rescheduling, confirmations, reminders, and status updates, subject to partner system capabilities. | |||
| 46 | AS-20 | Functional | Assisted Support | The system shall support interoperable case‑note metadata exchange, including the ability to retrieve approved case‑note summaries or metadata from partner systems and to route authorized updates back to those systems without storing protected case‑note content unless expressly permitted. | |||
| 47 | AS-21 | Functional | Assisted Support | The system shall display approved case‑management information for a matched user, including upcoming appointments, assigned case manager information, open referrals, referral statuses, required tasks, case‑plan elements, milestones, program enrollment status, and case status, subject to partner system authorization. | |||
| 48 | AS-22 | Functional | Assisted Support | The system shall display case‑note metadata for a matched user when authorized by the case‑management system owner, without displaying protected case‑note content. | |||
| 49 | AS-23 | Functional | Assisted Support | The system shall allow counselors, educators, navigators, and other State-approved support users to search, view, print, export, or share State-approved career, education, training, support, and pathway information with students, families, job seekers, and adult learners without requiring access to an individual's protected record unless such access is authorized by role, consent, policy, and State-approved security controls. | MVP | ||
| 44 | 50 | CPT - 1 | Functional | Career Pathways tool | The system shall provide a career plan builder driven by user questionnaires that generates a personalized plan with milestones and supports ongoing tracking of progress toward user‑defined goals. | R1.1 | |
| 45 | 51 | CPT - 2 | Functional | Career Pathways tool | The system shall enable users to input or assess skills, credentials, job requirements/preferences and career interests (including aptitude assessments) and generate aligned career recommendations based on those attributes. | MVP | |
| 50 | 52 | CPT - 7 | Functional | Career Pathways tool | The system shall enable advisors to view mappings between courses, credentials, and career pathways. | R1.1 | |
| 51 | 53 | CPT - 8 | Functional | Career Pathways tool | The system shall automatically translate military occupational codes (e.g., MOS, AFSC, NEC) into equivalent civilian roles and map those roles to relevant civilian job titles, industries, and high‑demand occupations recognized in South Carolina. | R1.1 | |
| 52 | 54 | CPT - 9 | Functional | Career Pathways tool | The system shall identify education, training, and credential pathways aligned to translated military experience, including equivalency recognition, gap analysis against licensure requirements, recommended next steps to close gaps, and applicable waivers or expedited pathways for veterans. | MVP | |
| 54 | 55 | CPT - 11 | Functional | Career Pathways tool | The system shall identify and allow filtering of GI Bill‑eligible education and training programs aligned to users’ translated military career pathways. | R1.1 | |
| 55 | 56 | CPT - 12 | Functional | Career Pathways tool | The system shall provide employer‑facing explanations that translate military skills and experience into civilian, industry‑relevant language aligned with job qualifications and competency requirements | R1.1 | |
| 56 | 57 | CPT - 13 | Functional | Career Pathways tool | The system shall support accelerated navigation of pathways to reduce time‑to‑employment for veterans and military spouses. | ||
| 57 | 58 | CPT - 14 | Functional | Career Pathways tool | The system shall prioritize high‑demand occupations and regions when presenting translated civilian career pathways. | R1.1 | |
| 58 | 59 | CPT - 15 | Functional | Career Pathways tool | The system shall integrate with DoD, federal veteran, and South Carolina agency systems to maintain current pathway mappings, while complementing, not replacing, authoritative licensing, issuing, and employer systems, and without adjudicating licensure or hiring decisions. | R1.1 | |
| 59 | 60 | CPT - 16 | Functional | Career Pathways tool | The system shall keep pathway recommendations current as credentials, licensure rules, or labor‑market data change. | MVP | |
| 61 | PPR - 1 | Functional | Personalized Pathway / Roadmap User Experience | The system shall provide a personalized pathway, roadmap, timeline, journey, or similar user experience that helps each user understand current status, goals, milestones, recommended next steps, available resources, and progress over time. | MVP | ||
| 62 | PPR - 2 | Functional | Personalized Pathway / Roadmap User Experience | The system shall present recommended pathway steps based on relevant user information, including current circumstances, interests, skills, education level, employment status, location, family needs, transportation needs, financial situation, career goals, prior experience, barriers to success, completed milestones, and other information relevant to the user journey. | R1.1 | ||
| 63 | PPR - 3 | Functional | Personalized Pathway / Roadmap User Experience | The system shall explain why a recommended pathway step is relevant and, where available, present related costs, location, duration, requirements, eligibility considerations, and supports available to help the user complete the step. | MVP | ||
| 64 | PPR - 4 | Functional | Personalized Pathway / Roadmap User Experience | The system shall update the personalized pathway as users complete education, training, employment, or other milestones and shall present additional recommended next steps aligned to completed training, experience, skills, location, and long-term goals. | R1.1 | ||
| 65 | PPR - 5 | Functional | Personalized Pathway / Roadmap User Experience | The system shall allow users to view the personalized pathway in a graphical pathway, roadmap, timeline, journey, or similar visual view showing progression, milestones, sequencing, and next steps. | MVP | ||
| 66 | PPR - 6 | Functional | Personalized Pathway / Roadmap User Experience | The system shall allow users to view the same personalized pathway information in a structured list, table, checklist, hierarchy, or similar detailed view. | MVP | ||
| 67 | PPR - 7 | Functional | Personalized Pathway / Roadmap User Experience | The system shall allow users to switch between graphical and structured pathway views without duplicating data, losing context, or requiring separate manual entry, and both views shall reflect the same underlying goals, milestones, steps, status, due dates, locations, costs, eligibility requirements, resources, and progress. | MVP | ||
| 68 | PPR - 8 | Functional | Personalized Pathway / Roadmap User Experience | The system shall provide representative visual and structured pathway views during implementation review, including mobile-responsive views, accessibility behavior, plain-language labels, and examples showing how the same underlying data supports the graphical pathway and structured checklist/list/hierarchy views. | MVP | ||
| 69 | PPR-9 | Functional | Personalized Pathway / Roadmap User Experience | The system shall incorporate credential data stored in the Digital Wallet into pathway generation, eligibility determination, skills inference, and recommended next steps. | R1.1 | ||
| 70 | PPR-GUEST-01 | Functional | Personalized Pathway / Roadmap User Experience | The system shall allow users to enter information as a guest without creating an account and receive a personalized pathway based on the information provided. The guest pathway shall operate entirely within the portal’s stateless session model and shall not persist any data. Guest users shall be able to print, email, or text their generated pathway and may create an account at any time to save the information, parameters, and metadata used to generate the pathway. | MVP | ||
| 71 | PPR-SAVE-01 | Functional | Personalized Pathway / Roadmap User Experience | The system shall allow users to save multiple personalized pathways by storing only the user entered information, parameters, and metadata used to generate each pathway. Metadata shall include, at a minimum, the data source, as of timestamp, and pathway generation settings. The solution shall regenerate and redisplay each saved pathway by using the stored parameters and metadata. The solution shall not store pathway outputs as persistent data. User initiated exports such as PDF, printed copies, emailed copies, or texted copies shall be supported. | MVP | ||
| 60 | 72 | CAM - 1 | Functional | Client Account Management | The system shall allow users to manage and maintain profile information and preferences—including language, notifications, communications, contact details, account recovery, and the ability to view, edit, and export profile data. | R1.1 | |
| 61 | 73 | CAM - 2 | Functional | Client Account Management | The system shall support multiple user account types (e.g., personal, student, job seeker, employer, educator, advisor, and guardian) with role‑based access and consent-driven permission workflows, including support for guardian–learner relationships, age‑appropriate privacy controls, and secure, role-based data visibility and collaboration across users and authorized stakeholders. | R1.1 | |
| 62 | 74 | CAM - 3 | Functional | Client Account Management | The system shall enable users to save and access information across multiple portal applications and view progress across programs, services, and workflows. | R1.1 | |
| 63 | 75 | CAM - 4 | Functional | Client Account Management | The system shall allow users to create personalized dashboards, save searches, and view tailored content based on their preferences and activity. | R1.1 | |
| 64 | 76 | CAM - 5 | Functional | Client Account Management | The system shall enable users to track education credentials, certifications, and related records across participating agencies through a unified account view. | ||
| 65 | 77 | CAM - 6 | Functional | Client Account Management | The system shall provide the ability to capture user's consent to data sharing. | MVP | |
| 78 | CAM - 7 | Functional | Client Account Management | The system shall reuse existing client account data to pre‑populate screening fields, allow users to update or override information as needed, and minimize duplicate data entry across screening sessions. | |||
| 68 | 79 | CAM - 8 | Functional | Client Account Management | The system shall associate job postings and candidate interactions with the employer’s account. | ||
| 69 | 80 | CAM - 9 | Functional | Client Account Management | The system shall update educator professional profiles with completed learning activities and certifications. | ||
| 81 | CAM - 10 | Functional | Client Account Management | The system shall allow users to optionally connect their LinkedIn account using secure, standards-based authentication to import profile information into their portal account. | |||
| 82 | CAM - 11 | Functional | Client Account Management | The system shall support secure third-party profile connections using approved OAuth/OpenID Connect authentication, selective field import, user preview and edit controls, token protection, user disconnect capability, and prohibitions on password collection, profile scraping, or unofficial access methods. | |||
| 83 | CAM - 12 | Functional | Client Account Management | The system shall support State-approved consent persistence rules that allow the State to configure whether each individual data connection, profile import, or AI-assisted action requires a new approval, remains approved until revoked, or must be renewed after a defined period or condition. | |||
| 84 | CAM - 13 | Functional | Client Account Management | The system shall clearly document, display, and make revocable the user’s original consent when persistent approval is enabled and shall re-prompt users when required by State policy, data-sharing agreements, or applicable law without unnecessarily duplicating consent collection. | |||
| 85 | CAM-14 | Functional | Client Account Management | The system shall provide a secure Digital Wallet that enables users to store, manage, and selectively share credentials uploaded, imported, or pushed by partner systems, subject to consent and State‑approved privacy rules. | R1.1 | ||
| 86 | CAM-15 | Functional | Client Account Management | The system shall maintain credential provenance, issuer metadata, timestamps, and verification status for all credentials stored in the Digital Wallet. | R1.1 | ||
| 87 | CAM-16 | Functional | Client Account Management | The system shall support credential ingestion from partner systems through APIs, secure file transfer, or other approved methods, subject to user consent and applicable DUAs/MOUs. | R1.1 | ||
| 88 | CAM-17 | Functional | Client Account Management | The system shall support ingestion of credentials from third‑party credentialing platforms, credential issuers, and credential verification services approved by the State, using secure, standards‑based integration patterns and consent‑driven authorization. | R1.1 | ||
| 89 | CAM-18 | Functional | Client Account Management | The system shall interpret and normalize credential metadata received from external credential providers in accordance with State‑approved data governance and credential taxonomy standards. | R1.1 | ||
| 90 | PGPE - 1 | Functional | Parent and Guardian Portal Experience | The system shall support role-based parent and guardian accounts and workflows for users legally authorized to act on behalf of, support, or participate in the education, training, workforce, or service journey of a learner or dependent user. | MVP | ||
| 91 | PGPE - 2 | Functional | Parent and Guardian Portal Experience | The system shall support guardian-learner relationships, parental or guardian consent management, youth protection controls, age-based access rules, privacy controls, and role-based permissions that may vary by age, program, agency policy, legal authority, and State-approved configuration. | MVP | ||
| 92 | PGPE - 3 | Functional | Parent and Guardian Portal Experience | The system shall allow authorized parents and guardians to view, support, and, where permitted, act on relevant tasks, milestones, pathway steps, education or training activities, document requests, consent requests, appointment reminders, communications, referrals, and service coordination activities. | R1.1 | ||
| 93 | PGPE - 4 | Functional | Parent and Guardian Portal Experience | The system shall allow the State to configure what information a parent or guardian may view, submit, approve, decline, receive, or update, including differences between minor users and adult users. | R1.1 | ||
| 94 | PGPE - 5 | Functional | Parent and Guardian Portal Experience | The system shall not provide parents or guardians access to learner, job seeker, education, workforce, support service, or agency information unless authorized by applicable law, policy, consent, role-based access rules, data-sharing agreements, and State-approved security controls. | MVP | ||
| 95 | PGPE - 6 | Functional | Parent and Guardian Portal Experience | The system shall allow authorized parents and guardians, where applicable, to receive notifications, review and confirm information before submission, upload or reuse documents, support intake or program-related tasks, communicate with authorized staff, view recommended resources, and understand pathway and support impacts. | R1.1 | ||
| 96 | PGPE-7 | Functional | Parent and Guardian Portal Experience | The system shall provide a parent/guardian-facing discovery and guidance experience that allows parents and guardians to explore interests, careers, requirements, education and training options, affordability information, support resources, and next-step guidance for learners without requiring access to the learner's protected profile or record unless such access is authorized by law, policy, consent, role-based access rules, and State-approved security controls. | MVP | ||
| 70 | 97 | CEM - 1 | Functional | Client Experience Management | The system shall provide a consistent, intuitive experience across channels, endpoints, and devices using user‑centered design methodologies such as persona‑based modeling and journey mapping across the end‑user lifecycle. | MVP | |
| 72 | 98 | CEM - 2 | Functional | Client Experience Management | The system shall provide an interactive regional context map that displays jobs, education, and training opportunities, enhanced with data overlays and contextual “About This Area” summaries including transportation access, housing options, healthcare access, education institutions, and cost‑of‑living indicators. | ||
| 73 | 99 | CEM - 4 | Functional | Client Experience Management | The system shall estimate and display commute times and travel distances for opportunities based on a user-selected starting location. | ||
| 74 | 100 | CEM - 5 | Functional | Client Experience Management | The system shall present high‑level housing affordability indicators for the surrounding area to support relocation and planning decisions. | ||
| 75 | 101 | CEM - 6 | Functional | Client Experience Management | The system shall link opportunity locations to relevant relocation and support programs, including childcare assistance, veteran relocation resources, housing support, and community services, and shall enable users to access these resources directly from opportunity or regional context views. | ||
| 76 | 102 | CEM - 7 | Functional | Client Experience Management | The system shall surface workforce, education, and community events that support networking, onboarding, or community immersion. | ||
| 78 | 103 | CEM - 8 | Functional | Client Experience Management | The system shall allow parents or guardians to tailor the regional context view based on household needs and priorities. | ||
| 104 | CEM - 9 | Functional | Client Experience Management |
The system shall provide a moderated user community that enables eligible adult users to participate in topic-based or pathway-based discussions, share resources, and engage in peer-to-peer communication.
| 105 | CEM - 10 | Functional | Client Experience Management | The system shall provide non-browser-based digital access channels, including lightweight and mobile application experiences, that enable users to interact with core FYF portal functionality across supported devices and platforms. | ||
| 106 | CEM - 11 | Functional | Client Experience Management | The system shall provide interactive, map-based regional context tools that display local jobs, education opportunities, transportation access, cost-of-living indicators, support services, experiential learning opportunities, volunteer opportunities, and community resources alongside service recommendations. | R1.1 | |
| 107 | UXR-1 | Functional | User Research and Experience Validation | The Contractor shall develop and obtain State approval of a User Research and Usability Validation Plan and shall conduct State-authorized, iterative user research, co-design, and usability validation with representative users applicable to each release. Activities shall include, as appropriate, interviews, facilitated workshops, focus groups, contextual inquiry or workflow observation, persona and journey validation, co-design, prototype reviews, task-based usability testing, accessibility and assistive-technology testing, and plain-language or content-comprehension testing. The Contractor shall document participant categories, methods, findings, material issues, recommendations, design decisions, remediation actions, and traceability to requirements, design artifacts, backlog items, configurations, test cases, defects, and release decisions. Representative-user validation shall occur before final approval and acceptance of applicable priority-user journeys and release functionality. This requirement begins during MVP Release 1 discovery and continues for Release 1.1 and applicable later releases. | MVP | |
| 108 | MRE - 1 | Functional | Mobile-Responsive Experience, Mobile Application, and Desktop Applet Support | The system shall provide a mobile-responsive user experience accessible through State-approved browsers and devices. | MVP | |
| 109 | MRE - 2 | Functional | Mobile-Responsive Experience, Mobile Application, and Desktop Applet Support | The system shall ensure that any State-approved full mobile application or lightweight desktop applet uses approved APIs, secure sign-in, notifications, saved progress, and controls that prevent local storage of sensitive data. | ||
| 110 | MRE - 3 | Functional | Mobile-Responsive Experience, Mobile Application, and Desktop Applet Support | State-approved data integrations, APIs, interfaces, data feeds, link-outs, embedded handoffs, identity connections, partner connections, and source-system connections needed to deliver, operate, maintain, or sustain the solution shall not be treated as optional mobile, applet, or future-growth capabilities unless expressly identified as separately priced optional items in the awarded contract. | ||
| 79 | 111 | CCRT - 1 | Functional | College and Career Readiness tool | The system shall have a college readiness assessment that users can access. | MVP |
| 80 | 112 | CCRT - 2 | Functional | College and Career Readiness tool | The system shall have a career readiness assessment that users can access. | MVP |
| 81 | 113 | CCRT - 3 | Functional | College and Career Readiness tool | The system shall support secure, role‑based access for families, guardians, and caregivers—allowing multiple caregivers to be associated with a learner profile—while enforcing authentication, privacy, and consent controls appropriate for minors and adults. | MVP |
| 82 | 114 | CCRT - 4 | Functional | College and Career Readiness tool | The system shall display learner progress across education stages from early childhood through workforce readiness, including academic milestones, career exploration activities, credentials, certifications, and readiness indicators such as skills, interests, and goals. | |
| 83 | 115 | CCRT - 5 | Functional | College and Career Readiness tool | The system shall provide career pathway information across essential sectors, including, but not limited to: Technical trades, Healthcare, Logistics, Energy, Information Technology, Manufacturing. | MVP |
| 91 | 116 | CCRT - 6 | Functional | College and Career Readiness tool | The system shall normalize nontraditional or undervalued career paths through: Transparent data (wages, demand, training length), Real‑world career stories, Evidence‑based labor market messaging | MVP |
| 96 | 117 | CCRT - 7 | Functional | College and Career Readiness tool | The system shall allow users to compare multiple pathways side by side. | MVP |
| 98 | 118 | CCRT - 8 | Functional | College and Career Readiness tool | The system shall provide shared views, interactive conversation guides, and age‑ or stage‑appropriate checklists and prompts to support structured family discussions about education choices, career interests, financial considerations, and short‑ and long‑term planning. | |
| 119 | CCRT - 9 | Functional | College and Career Readiness tool | The system shall present education and training affordability information, including costs, financial aid types, and return‑on‑investment considerations relevant to pathway decisions. | MVP | |
| 120 | CCRT - 10 | Functional | College and Career Readiness tool | The system shall surface local and regional opportunities, including: Education and training programs, Work‑based learning, Internships, apprenticeships, or entry‑level jobs | MVP | |
| 121 | CCRT - 11 | Functional | College and Career Readiness tool | The system shall clearly communicate data sources when presenting labor‑market or outcome data to promote transparency and build trust with families and caregivers. | MVP | |
| 122 | CI - 1 | Functional | Common Intake | The system shall allow a verified third party to submit an application on user's behalf | ||
| 123 | CI - 2 | Functional | Common Intake | The system shall provide a structured common intake form that includes clearly labeled mandatory and optional sections for education, work experience, financial information, medical information, workforce goals, and supporting documentation. | ||
| 124 | CI - 3 | Functional | Common Intake | The solution shall allow users to submit or route common intake information to appropriate partner systems or workflows, subject to partner approval, integration capability, consent, and applicable data-sharing agreements. | ||
| 125 | CI - 4 | Functional | Common Intake | The system shall support paper‑based intake through accessible, user‑friendly application formats with document checklists, and enable agency staff to digitize paper applications and supporting documentation to populate the electronic common intake without manual re‑entry. | ||
| 126 | CI - 5 | Functional | Common Intake | The system shall enable a unified common intake experience that pre‑populates existing user data, allows core information to be entered once and reused across applications and referrals, and supports collaborative handoffs without requiring resubmission of intake data. | R1.1 | |
| 127 | CI - 6 | Functional | Common Intake | The system shall support legally binding electronic signatures within the common intake process. | ||
| 128 | CI - 7 | Functional | Common Intake | The system shall support dynamic, conditional intake forms that adjust questions and required fields based on user responses and program requirements. | ||
| 129 | CI - 8 | Functional | Common Intake | The system shall provide document upload checklists and validation to ensure required documents are submitted accurately and completely as part of the intake process. | ||
| 130 | CI - 9 | Functional | Common Intake | The system shall trigger rules‑based status notifications and support communication between users and application, intake, or request processors throughout the intake lifecycle. | ||
| 131 | CI - 10 | Functional | Common Intake | The solution shall provide clear explanations of intake status, next steps, required actions, or agency-provided outcomes based on submitted information. | ||
| 132 | CI - 11 | Functional | Common Intake | The system shall support saving intake progress and returning later to complete the process. | R1.1 | |
| 133 | CI - 12 | Functional | Common Intake | The system shall provide a unified electronic referral workflow that allows authorized users to refer individuals across programs and agencies, pre‑populates participant data, packages required documentation and consent, generates unique tracking identifiers, and preserves service context and data continuity. | R1.1 | |
| 134 | CI - 13 | Functional | Common Intake | The system shall enable bi‑directional status updates between referring and receiving agencies. | R1.1 | |
| 135 | CI - 14 | Functional | Common Intake | The system shall comply with FERPA, HIPAA, and applicable state data‑sharing agreements. | MVP | |
| 136 | CI - 15 | Functional | Common Intake | The system shall enable coordinated referrals to education, workforce, and wraparound support services such as: childcare, transportation, food assistance, and housing to reduce service gaps and delays. | R1.1 | |
| 137 | CI - 16 | Functional | Common Intake | The system shall provide summarized intake and referral performance views to administrators to support continuous process improvement. | R1.1 | |
| 138 | CI - 17 | Functional | Common Intake | The system shall support closed-loop AI-assisted profile, intake, questionnaire, resume, skill translation, opportunity posting, and pathway-support interactions that allow users and authorized staff to enter, update, clarify, validate, or correct information within defined workflows. | ||
| 139 | CI - 18 | Functional | Common Intake | The system shall require users to review, edit, confirm, or decline AI-suggested information before it is saved to the user profile or used to support pathway recommendations. | ||
| 140 | CI - 19 | Functional | Common Intake | The system shall maintain manual completion and non-AI alternatives for applicable intake, profile, form, resume, questionnaire, posting, and pathway workflows. | ||
| 141 | COMM - 1 | Functional | Communication and Notices | The system shall provide a shared notes feature for cross-agency staff communication | ||
| 142 | COMM - 2 | Functional | Communication and Notices | The system shall provide configurable, multi‑channel notification delivery (in‑portal, push, email, SMS, and external system integration) to notify users, advisors, and agencies of relevant actions, status changes, point‑in‑time alerts, and referral updates, with support for archiving and downstream system integration. | ||
| 143 | COMM - 3 | Functional | Communication and Notices | The system shall allow users to select, manage, and opt out of communication channels and notification types through profile‑based communication preferences. | ||
| 144 | COMM - 4 | Functional | Communication and Notices | The system shall provide each user with a consolidated, personalized view that displays announcements, current communications, upcoming activities, tasks, milestones, deadlines, status updates, and historical records across the portal. | ||
| 145 | COMM - 5 | Functional | Communication and Notices | The solution shall allow users to take action on pending tasks as outlined in notifications. | ||
| 146 | COMM - 6 | Functional | Communication and Notices | The system shall periodically prompt users to review and update personal information. | ||
| 147 | COMM - 7 | Functional | Communication and Notices | The solution shall allow users to select a preferred language for outgoing communications from among the State-supported languages. | ||
| 148 | COMM - 8 | Functional | Communication and Notices | The system shall display real‑time status indicators for service intake and processing activities, including current stage, required actions, and estimated time to completion. | ||
| 149 | COMM - 9 | Functional | Communication and Notices | The system shall trigger configurable notifications based on key events including application status updates, matched opportunities, upcoming events, credential or license expirations, renewal requirements, and status changes, using user‑selected delivery channels. | ||
| 150 | COMM-10 | Functional | Communication and Notices | The Contractor shall provide ninety (90) total days of paid digital advertising and media‑optimization services, including campaign design, execution, segmentation, optimization, and reporting. The State shall specify the start and stop dates for each paid campaign. The ninety (90) days may be used consecutively or divided into multiple campaigns throughout the contract term. All paid media costs, campaign operations, optimization activities, and reporting capabilities shall be included in the Contractor’s pricing for Release 1.1. The Contractor shall provide campaign analytics, attribution reporting, audience‑level performance metrics, and post‑campaign summaries for each paid campaign executed under this deliverable. | R1.1 | |
| 151 | CM - 1 | Functional | Content Management | The system shall provide a centralized Menu of Services that presents education, workforce, employment, veteran, and support services available across South Carolina in a single, navigable interface. | MVP | |
| 152 | CM - 2 | Functional | Content Management | The system shall organize services by user goal, life stage, and need (e.g., Explore Careers, Get Training, Find a Job, Support While You Train or Work) rather than by agency or program name. | MVP | |
| 153 | CM - 3 | Functional | Content Management | The system shall display plain‑language descriptions for each service that clearly explain what the service provides without agency‑specific jargon. | MVP | |
| 154 | CM - 4 | Functional | Content Management | The system shall include, for each service listing, a description, intended audience and eligibility signals, access method, and links to related portal tools. | MVP | |
| 155 | CM - 5 | Functional | Content Management | The system shall allow users to filter and search services based on eligibility indicators, location, population, and service category. | MVP | |
| 156 | CM - 6 | Functional | Content Management | The system shall provide contextual cross‑links from service listings to eligibility screening, referrals, case workspaces, and credential tools. | MVP | |
| 157 | CM - 7 | Functional | Content Management | The system shall provide an advisor‑specific view of the Menu of Services that supports consistent guidance through service comparison tools and scripting. | R1.1 | |
| 158 | CM - 8 | Functional | Content Management | The system shall support a full content‑management lifecycle for service and benefit content, including authoring, quality assurance, publishing, maintenance, version control, metadata management, search optimization, and workflows for authorized administrators to add, update, archive, or retire listings. | R1.1 | |
| 159 | CM - 9 | Functional | Content Management | The system shall provide policymakers and administrators with a consolidated view of how services across agencies support education‑to‑employment pathways. | ||
| 160 | CM - 10 | Functional | Content Management | The system shall function as the primary entry point to the portal by routing users from service discovery to deeper functionality such as screening, referrals, and applications. | MVP | |
| 161 | CM - 11 | Functional | Content Management | The system shall support consistent presentation and interpretation of services across agencies to reduce duplication and conflicting referrals. | MVP | |
| 162 | CM - 12 | Functional | Content Management | The system shall support multiple content types, including static articles, guides, and videos, as well as interactive content such as trainings, assessments, exams, and guided wizards. | ||
| 163 | CM - 13 | Functional | Content Management | The system shall present each workforce incentive using a standardized incentive profile—including program purpose, benefits, eligibility signals, timelines, funding limits, and administering agency—displayed in clear, plain language suitable for employers with varying levels of program familiarity. | R1.1 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .