RFP Description

The Vendor is required to provide the development and implementation of a website where the department can input requests on behalf of individuals and families for items and/or services needed, and registered members of faith-based communities and other charitable organizations can respond to said requests with their ability to provide such items and/or services.
- Provide community outreach services to register and promote the website.
- Navigation serves individuals, children, and families who may benefit from one-on-one (1:1) assistance in developing a service plan to meet their goals for stability, self-sufficiency, and health and safety.
- The website must, but is not limited to:
1. Be hosted on the contractor’s servers or be cloud-based.
2. Allow for up to two hundred (200) registered department originators to input requests.  
3. Include a request form for donations which includes the following:
• A system-generated request number;
• Fields for the originator’s optional input that must not be visible to responders:
i. Client’s name;
ii. Client’s address;
iii. Client’s phone number;
iv. Client’s case number; and
v. Client’s secondary reference/case number.
• Fields that must be visible to originators and responders:
i. Client’s county;
ii. Client’s city;
iii. Type of item requested, with the option to choose multiple items, including but not limited to: automotive; housewares; clothing; food; hygiene items; furniture; school supplies; cash assistance (rent); cash assistance (utilities); and cash assistance (other);
iv. Urgency indicator: crisis (needed within two [2] calendar days), urgent (needed within five [5] calendar days, and moderate (needed within ten [10] calendar days); and
v. A description text box of up to two thousand (2,000) characters.
4. Host up to one thousand (1,000) active requests; originators and responders must be able to sort requests by:
• Input date;
• County;
• City;
• Type of item requested;
• Urgency; and/or
• Estimated dollar amount/cost of request.
5. Send the email alert to responders when a request is entered and provide an option for them to respond to the request.   
• Responders must be able to choose which counties for which they receive alerts.
• The email alert must contain a link to the request, which must prompt the responder to log in to the website.
• The responder must be able to choose the option of answering the entire request or partial request, with a text box of at least two thousand (2,000) characters for an explanation of what they can offer.
• The responder’s answer must be emailed to the originator who input the request.
6. Show each request as a current need until marked as complete by an originator.
• Completed requests must be stored for at least one (1) year after completion and remain searchable by originators.
7. Allow for up to one thousand (1,000) community partners to register as responders; the responder’s registration form must contain:
• Responder’s name (personal or organization);
• If an organization – the person responsible for communication;
• City and county of residence;
• An option to choose alerts for requests from the entire state or specific counties;
• email address; and
• Cell phone.
8. Allow originators to pull reports in spreadsheet format, including:
• Active and closed requests per county;
• Active and closed requests by date range;
• Responses received per responder; and
• Case/client number.
- Recruiting and registering community partners; the contractor must:
1. Work with the department to develop marketing materials; all materials must be approved by the department before being disseminated.
2. Develop a plan to recruit community partners in ADA and canyon counties, and across the state in subsequent contract years to register as responders; the plan must include the contractor’s efforts to:
• Make contact with community partners including but not limited to:
i. Faith based organizations;
ii. Community groups; and
iii. Charitable organizations.
• Contact community partners through the following methods:
i. Phone calls;
ii. In person contact; and
iii. Media.
• Continuously recruit new community partners throughout the life of the contract.
• Train community partners in subjects including but not limited to:
i. Privacy;
ii. Customer service; and
iii. Working with the department.
- Contract Period/Term: 1 year
- Pre-Proposal Conference Date: March 28, 2025
- Questions/Inquires Deadline: April 04, 2025

Timeline

RFP Posted Date: Monday, 17 Mar, 2025
Proposal Meeting/
Conference Date:
Non-mandatory
Friday, 28 Mar, 2025
Deadline for
Questions/inquiries:
Friday, 04 Apr, 2025
Proposal Due Date: Friday, 25 Apr, 2025
Authority: Government
Acceptable: Only for USA Organization
Work of Performance: Offsite
Download Documents

Similar RFPs