1.1Users a. Self-service password reset functionality for users to unlock their account or change their password utilizing two-factor or multi-factor authentication. Passwords have complexity and length requirements. b. Users are automatically logged out after a period of inactivity. c. Ability for users to communicate within the software via notifications and direct messaging. (Desired) 1.2Data Entry a. Robust client record search functionality to help prevent the creation of duplicate records. b. Intuitive workflows to streamline process for users. c. Functionally to create bed reservations within the HMIS software. d. Capability for users to securely upload documents and files directly to client records. e. Auto exit and default end date functionality. f. Pause data entry workflow and the ability to return to the same place at a future session. (Desired) g. Integrated ID card functionality for individuals to use for check-in, which will create enrollments and/or services, and can be generated from the HMIS software and printed. (Desired) h. Ability to track real-time reservations, occupancy, and the availability of beds and units. (Desired) i. Ability to batch import data from agencies who do not use HMIS. (Desired) 1.3 Case Management a. User-friendly interface for recording case management information, including but not limited to: setting reminders, case notes, developing case plans, and uploading external documents. b. Track referral data. 1.4Coordinated Entry a. Real time by-name list, priority list and Youth by-name list. b. Capacity to host a prioritization tool and automated forms associated. c. Ability to record information needed to match to housing projects, including client preferences, in a “housing assessment” d. Real-time eligibility calculations, client choice in Coordinated Entry. e. Capacity to distinguish between a request for housing and a request for transfer from one housing project to another. f. Ability to manually and automatically update housing assessment statues. g. Mechanism for submitting and tracking project vacancies (“matches”) that can take into account client preference, and automatic as well as manual updates to match statues. h. Ability for stakeholders to record data used in project eligibility calculations. i. Capacity to track start/end dates for participants matched to non-CoC housing projects. j. Automated deliverables, such as email notifications, to advise of match status changes. k. Automated system to calculate chronic homelessness and update in real-time (Desired) 1.5Fund Management a. Ability to create funding sources. b. Ability to link services to funding sources. c. Allow users to enter dollar amount for services provided.