Nevada State Purchasing Division Department of Administration 515 E Musser St Ste 300 Carson City, NV 89701 purchasing.nv.gov nevadaepro.com

Request for proposals 05TO-S3607

Release Date 1/22/2026

Solicitation number 05TO-S3607

Single point of contact name Jennifer Thomas

Single point of contact email jennthomas@admin.nv.gov

Single point of contact phone 775-531-3311

Soliciting agency State of Nevada Purchasing Division

Contracting agency Office of the State Treasurer, Unclaimed Property Program

Solicitation title Unclaimed Property Software & Website Services

Deadline for submissions 3/12/2026

For deaf and hard of hearing, call 711 and ask the relay agency to dial the single point of contact phone number above.

This request for proposals is available at nevadaepro.com as a bid solicitation.

Table of Contents

Applicable regulations governing procurement

Statute and code. All applicable Nevada Revised Statutes (NRS) and Nevada Administrative Code (NAC) documentation can be found at: www.leg.state.nv.us/law1.cfm.

Single point of contact. Vendors and their representatives shall only contact the single point of contract or use the electronic procurement system regarding this solicitation until after a notice of award (NOA) has been issued. Failure to observe this restriction may result in disqualification of a response per NAC 333.155(3).

Ethics. Prospective vendors are advised to review Nevada’s ethical standards requirements, including but not limited to NRS 281A, NRS 333.800, and NAC 333.155.

Project overview

The State of Nevada Purchasing Division, on behalf of the Office of the State Treasurer, Unclaimed Property Program is seeking proposals from qualified vendors to provide software and support for the Nevada Unclaimed Property Program as described below and in the scope of work and attachments.

The State intends to award one contract in conjunction with this request for proposals (RFP), as determined in the best interests of the State. Office of the State Treasurer, Unclaimed Property Program shall administer contract(s) resulting from this solicitation. The resulting contract(s) are expected to be for a contract term of four years, with two (2) one (1) year extensions, which may be combined into a single extension, subject to Board of Examiners approval.

Contracting agency background

Office of the State Treasurer, Unclaimed Property Program is tasked with receiving abandoned financial assets, and acting as custodian of those assets until such time that the asset can be returned to its legal owner. The Administrator must comply with local, state, federal, and international laws and must ensure data integrity is maintained to accomplish these tasks. The Administrator serves as the head of a consumer protection agency.

Goals and objectives

This request for proposal is seeking vendors offering information systems and related services required to complete its tasks. This includes public and non-public facing interfaces, imaging systems, data protection, and more.

Scope of work

Vendor will be required to provide, as it relates to Technology standards and requests:

Encryption for data at all stages of use, including at rest. Encryption methods must meet required:

Applicable regulatory standards which may include HIPAA, DSS-PCI and banking standards.

Housing of servers, including back up and disaster recovery servers, which shall remain physically located in the United States.

Vendor Staff and Contractors that collect or process Nevada state data must be located within the continental United States.

Staff and Contractors that handle or process Nevada state data must provide evidence of a background check.

Vendor's employee and contractor access to Nevada state data must be documented or logged when handling or processing said data.

Any changes to the system must comply with NRS Chapter 603A and Federal standards where applicable.

Provide annual security audit reports and proof of certifications as they come available to the vendor (e.g.: SOC2 Type 2 reports, ISO27001 certification, any additional reports).

Provide monthly access security logs for the Nevada specific application logs.

Maintenance, upgrades, and patching of the server.

Provide IT data security reports upon request, based on audits conducted of State systems.

Vendor will not utilize any federal or state banned technologies regarding implementation, storage, or maintenance of Nevada state systems.

The state of Nevada, Office of the State Treasurer, reserves the right to audit all Nevada state data hosted on Vendor's servers.

The Nevada State Treasurer's office must be notified of security incidents, data leaks, or breach of systems that contain Nevada state data within 24 hours of discovery of the event.

Notification of the incident, leak or breach must contain at minimum:

Description of incident, including what data was impacted and the cause of the incident.

Date and time.

Any mitigation action taken.

Any preventative action recommendations.

Name, title, and date of the person completing the report.

Modifications and maintenance of the unclaimed property holder reporting and claims websites.

Allowing only data that has been approved by the State for publication to these websites and other publications.

Vendor will be required to facilitate:

Automation of data related to funds received, paid, or subsequent reversals of funds received or paid by the State's bank account into the system. This may be accomplished by uploading banking reports. The system is to reflect the payment information (electronic reference or check number) and the date of the action.

Allowing multiple receipts on the same batch of receipts.

Allowing the receipt type, amount, payor and memo line to be documented.

Allowing receipts to be split amongst reports and amongst general ledger accounts.

Ability to perform ACH payments and Check payments to claimants, allowing for AVS validation prior to making payment. If AVS validation fails, changing the payment type and possibly requiring the State to approve the change in payment method to ensure that the validation failure was not the result of a fraudulent claim.

Since the data is being collected on the Vendor's hosted website, the Vendor is still required to comply with National Automated Clearinghouse Association (“NACHA”) and other federal requirements, as necessary.

A change order may be required to implement AVS and ACH payments for additional development and transaction costs.

Automation of general ledger entries to demonstrate funds received based on the receipt and/or report type, requiring the system to be interfaced to the State's accounting system.

Automation of general ledger entries to demonstrate claims payment activities (including reversals), requiring the system to be connected to the State's accounting system. Where possible, the general ledger entries must break out the funds paid on a claim from individual properties’ fund sources. Cancels and reissues should be based on the date of the action and should reflect the fund sources in the same manner as the original issuance.

Automation of claimable properties being published to the national MissingMoney website.

Any changes to the requirements to publish claimable properties to MissingMoney website, changes to how it is delivered to or published on the MissingMoney website must be reviewed and approved by the State.

Statistical data published to the MissingMoney website must be reviewed and approved by the State.

Automatic importing of claims initiated on the MissingMoney website for claims in the State’s custody.

Software Functionality Requirements:

Holder Reporting and Remittance:

Ability to make payments by electronic formats supported by the State's banking partners and allow payments to be automatically tied to the reports they apply to.

Ability to automatically clear reports based on report and receipt information matching and the value of the report.

The ability to automatically attach receipts to reports, including the ability to split a payment amongst reports in a file when a payment for a file matches the value and FEIN of the payment information.

Automatic unclearing of reports when payment is rejected, to prevent payment of claims and prevent the report from locking for future handling.

Ability to search for holders, reports, and receipts based on holder ID, Report ID, Receipt ID, holder name, address, contact name, contact phone number, contact email address, FEIN, holder/payment/receipt type, etc.

Allow for new holders to be created internally by copying information from another holder.

Allow for new holders to be created based on importing of the Nation Association of Unclaimed Property Administrators (“NAUPA”) formatted Holder Report file. This can be implemented after the system is created. This includes the creation of foreign holders using foreign tax IDs.

Automated creation of new holders based on holder creation on the website. This includes the creation of foreign holders using foreign tax IDs.

Allow for customization of required fields in a NAUPA report and allow for errors or rejections when those fields are not populated or are populated incorrectly (e.g.: when a Social Security Number is in the name field, that should require an update on the report prior to submission) to take place prior to the report’s submission. This would require the website to perform preliminary analytics of the file to ensure that it is in a format that the system can read, is not a duplicate file, and meets standards established by the State and required for the system to process the report. The website should clearly indicate at that stage that the report upload was not successful.

Allow data on a screen to be exported to PDF/Excel format where appropriate, and data security requirements allow export of the data.

Allow for NAUPA III standards to be implemented once it is finalized.

Ability to allow for the State to process reports and claims in NAUPA II / NAUPA III formats.

If it is deemed appropriate by the State and vendor alike, converting specific information reported from NAUPA II to NAUPA III standards can be done in a manner that the State agrees to in writing. Specific conversions must be documented and available in a configuration report.

Allow certain State Government Holders (such as Courts and County Governments) to Report in Excel format, which can be uploaded to the system.

Allow for canned letters to be created and documented in the system with all letters sent to an individual holder to be accessed in one location.

Electronic sending letters from the system must allow for multiple recipients.

Communications sent must be able to be reproduced using the original date sent and the exact text of the communication.

Allow for automated modifiable penalty, interest and fee assessments; documenting assessments, waivers and payments.

Penalty and interest calculations should be based on the most recently received holder report payment and/or report received date, whichever is later. Calculations should not take into consideration payments for penalties, interest, fees, stock sales, or auction receipts.

Calculations should consider approved waiver and extension requests. (Thereby impacting report/remittance deadlines, applying waivers if estimated assessments prepayments were made, applying waivers if the property reported was all due during the reporting cycle for which the extension was granted, etc.), Allow for extensions to be documented prior to the report being submitted.

Allow for simple negative reporting.

Include simple, real time guides for holders to submit reports, including State specific inserts to ensure reporting is smooth for holders.

Allow multiple users at a holder to upload reports for the same holder.

Provide ability to provide a holder's reporting history on demand and delivered via email to an approved holder contact.

Tracking of original report data (including to the property and owner level of data), along with the details of any edits, the identity of the user who made the edits, when the edits were made, the information pre-edit and post edit, how the edit was made, etc.

Allow for reports and receipts to be classified by type.

Tracking of holder compliance, to include when reports/remittances were early, past due, failed to include required information, etc. Information should be indicated at the holder level.

Allow holder tracking based on the holder's FEIN, and to allow for the "holder name reported as" tracking to show at the property record.

Allow for reports/properties to disclose a remittance amount that varies from the report amount based on settlements, interest earned on certain property types, bankruptcies, etc. Each variance at the property level should be individually identified with an addition/deduction amount and type, with multiple additions/deductions allowable on each property and summarized at the report level.

Holder Related Website Features:

When a report is uploaded but prior to notifying the uploader, the file is analyzed to determine all associated holders. If the holders included in the file do not match records in the system, the system should require the holder to select holders associated with the information or create a new holder and provide a note as to why a new holder is necessary. This includes the creation of foreign holder using foreign tax IDs.

Require the holder to identify a reason that the “holder name reported” would vary from the holder’s information. For example: the holder is reporting on behalf of another entity, the holder is the successor company of the entity that originally held the obligation, etc.

Allow for holders to report on the website without requiring the report be encrypted prior to submission.

Website will only allow properly formatted NAUPA reports to be uploaded.

Allow the holder to identify the report type on the website.

Publish real time guidance and forms for holders.

The ability to determine and document a reported property owner’s identity.

The ability to send certain properties for periodic current owner address updates and document each update separately from the reported owner’s address. The information to be published shall be determined at a later date.

Publish instructions to make payment.

Ability to upload documentation to support reports and audits. Uploads should trigger notifications to Administrator’s staff to review the records.

Claims Related Requirements:

Allow for claims to be assigned to Administrator’s staff members.

Allow for multiple levels of review based on the value of the claim. This should include market value of stocks, stock cash received (including dividends and from stock sales) and safekeeping cashed out.

Allow for a percentage of properties to be paid to claimants based on ownership rights, not to exceed 100% of the cash value reported and remitted.

Allow for various statuses of claims and customizable information available to claimants when searching the status of their claim on line. For example, if a claim is under review for fraud, we would not want to claimant to be privy to that fact, only publishing that their claim is still in the process of being reviewed.

Allow for the State to automatically mark claims as potentially fraudulent and suppress claim forms based on email addresses, domain names, claimant names, address, IP Address, and other similar criteria.

Allow for the state to block website traffic from designated IP addresses.

Allow for looking up claims at a minimum by: Claim Number, claimant's e-mail address, claimant's address, claimant's SSN, reported owner name, claimant's FEIN/SSN, IP address, Finder name, payee name, check number, value, claimant name, claim status, claim source, CUSIP, number of stocks, and inventory items count.

Allow for editing claims information in the following fields: Claimant name, Address, Payee, Date of Birth, SSN/FEIN, Relation, Source, Email address, special handling, payment type, or other relevant information as deemed necessary by the Division.

Allow for adding property to claims from the property level inside the claims screen.

Allow for adding from property to claims from windows of property searches.

Allow for deleting properties from claim, and require notations of deletes.

Allow for switch first and last names at the payee level with a button.

Allow for toggle between FEIN and SSN.

Allow for splitting claims and bulk Splitting (adjusting percentages) and automatic recalculation of claim value.

Allow for manual and automated updating Claim Status.

Allow for adding notes, including documenting any edits made to a claim since its inception.

Allow for canned letters to be created and documented in the system with all letters sent to an individual claimant to be accessed on the claim.

Electronic sending letters from the system must allow for multiple recipients.

Communications sent must be able to be reproduced using the original date sent and the exact text of the communication.

Allow for manual edits of letters prior to being sent, and tie the sending of the letters to specific updates to the claim’s status based on the letter being sent.

When letters are sent to claimants, allow for attachments to be selected, such as the claim form, bond letters, general guidance, etc.

Initiating claims on the claims screen Inquiry results must show reported: Name, SSN, Address, Property ID, other claims on property, Check Number(s) Ability to search for property by Owner Name(s), SSN(s)/TaxId(s), Address, Property ID, Check Number reported, Account Number reported, Lexis Nexis ID, reported value (cash, shares, and inventory quantity), SK.ID, SK box number, Auction ID, Holder Name Reported, Holder Name, Holder FEIN, Property type code, Claimant Email, Claimant Phone Number, Claimant Name, IP address.

Ability to copy a claim or a claim and its properties to create a new claim with the same information Ability to see work history / claim activity Provide services that analyze a claim's likelihood to be fraudulent and allow various handlings based on criteria of likelihood.

Flag multiple claims on the same property, claims with IP addresses located in areas not supported by the information provided on a claim, claims with the same email address, claims with the same phone number, payee’s electronic banking information, etc. and provide all relevant claim IDs.

Allow for automated approval based on a variety of factors (to include at a minimum, value, number of properties, property types on a claim, claimant relationship type, etc.).

Document in the notes of the claim/property results of Lexis Nexis search, including the LexID®, that individual’s name(s), address history, Date of birth, tax ID, etc. Documenting the LexId alone does not guarantee the data can be requested and reproduced.

Provide details of success/failure of the individual criteria required to allow automated approval.

Allow for proactive claims payment issuances based on the system verifying reported information to information in Lexis Nexis, on recently paid claims, and other confirmation processes agreed upon by the vendor and the Administrator.

Ability to create reciprocal claims based on unpaid properties with different states reported as last known address.

Ability to add multiple properties to a claim at once Ability of the system to automatically add properties to a claim based on information provided by the claimant and/or owner information of other properties claimed.

Ability for the system to have various methods to automate claims approvals, including through proactive claims methods.

Claims Specific Website Functionality:

Allow constituents to create their own claim(s) online through the state’s website and/or through partnering websites (such as MissingMoney) if agreed to in writing by the Administrator.

All for constituents to search the status of their claim, upload documents directly to their claim, obtain a copy of their current claim form, and obtain a copy of the most recent system documented correspondence to the claimant through the website.

Provide a guide to creating a claim on the website.

Provide forms with guidance by claim type/circumstances on the website.

Do not allow properties on the website that are in an approval status of any level, that are marked as unpublishable or unclaimable, if the owner’s information is marked as private, or other criteria as determined by the Administrator are present.

Limit property and owner information published to the website to only those fields, presented in a manner determined appropriate by the Administrator.

Allow for a user friendly interface that guides the claimant at each step as to what’s required to complete the claim.

Safekeeping Ability to edit SKID Ability to customize information on property for bonds Ability to adding/delete SKID, without the assistance of the vendor, including but not limited to:

Creating Transactions Splitting Transactions Deleting transactions Creating appraisals Adding SKID to appraisal Deleting SKID from appraisal Creating Auction, without the assistance of the vendor, including but not limited to:

Adding SKID to auction Deleting SKID from auction Downloading appraisal and auction Uploading appraisal and auction from a spreadsheet, breaking out the values received by SKID.

Tying an auction to a receipt.

Closing auction when the receipt amount has no unapplied balance and every SKID has a value applied or a disposition applied.

Allowing images to be attached to SKIDs to keep Securities Ability to import reports from securities custodian or directly interface with securities custodian to ensure timely and accurate record keeping of stocks.

Ability to record Corporate Actions on stocks including, but not limited to: manually and automatically through uploaded spreadsheets or automatically from interface files information at the stock/CUSIP level including but not limited to: Dividends, Drips, Splits, Mergers, Interest/Principal Payments, Sales, Adjustments, Name Change.

Automatically apply actions taken at the stock/CUSIP level across properties with remaining shares.

Ability to undo/delete an action without the assistance of the vendor Ability to edit property and/or owner information, including but not limited to:

corporate actions on property Sell orders Proceeds imports Create stock Create custodian Merge Stock Custodian Reconciliation import, disclosing stocks that are out of balance, requiring further research by Administrator staff.

Stock Price import, updating the property Ability to have multiple dates for non-dividend corporate actions – the date of the change, the date the shares left the account, and the date the new shares came in Ability to have 2 dates for dividends - the record date and the settle date Ability to record the date the stocks transfer was initiated and the date it settled for newly reported properties.

Ability to obtain an exportable report from the holder report, an export of securities, with CUSIP, symbol, security name, stock transfer initiation and settle dates by property and owner.

Name change for stock Stock split with name change Auditing Allow for audits and other compliance efforts to be tracked in the system.

Provide an indication of a compliance effort on the holder's main page, to allow for report types to be evaluated Allow for uploads of Work in Progress reports from the website and/or importing from within the system.

Automated creation of audits based on uploads of audit proposal documentation and work in progress reports.

Ability to track statuses of audits, including lack of activity, where WIPS have required State intervention, etc.

Ability to track audit/compliance related reports.

Ability to track audit invoices.

Ability to image documents into the system.

Ability to import a Work in Progress report Allow for automatic notifications from the system when a holder's audit has not been included in a Work in Progress report for a specified period of time.

Ability to link audits of subsidiaries/affiliates to the parent company.

Reports of System Activity Allow for canned and customizable reports to demonstrate at a minimum:

Remittances received within a specified time period, disclosing the remittance amount, breakdown of how that remittance was applied, remittance method (e.g.: ACH Debit, Check, Wire, etc.), remittance type (e.g.: November cycle reports, audit reports, penalty and interest, etc.).

Claims initiated within a specified time frame (showing initial values, date initiated, status, payment amount and payment date).

Claims denied within a specified time frame.

Claims paid within a specified time frame (showing payment values, payment type, payment date, claimant name, etc.).

Claims cancelled/ reissued within a timeframe (based on the date of the action).

Properties available for claim at a given date based on the time frame a report was submitted, showing the breakdown of the owner's reported county of address, the value, the owner's name, and other fields required pursuant to NRS l 20A.580.

Property/Owner/Safekeeping/Stock Edits reports (showing properties edited by means other than the report deletion, by date the edit was made, who made the edit, what the values were prior to and subsequent to edits made, etc.).

Report Deletes/Rejections within a time frame (showing who deleted the report, when it was deleted, the value of the deleted report, etc.).

Data disclosing dates that images were uploaded on the claims website or otherwise scanned in by the State.

Data disclosing dates that images were uploaded on the holder/report/audit sections website or otherwise scanned in by the State.

Current information disclosing the State's received property values to date, properties paid to date, and the current balance of liability to the State.

Claims initiated and/or paid by type (owner claim, heirfinder claims, heir claims, business claims, etc.) for a specified date range.

Claims approved through Fast Track for a specified date range, along with those claims details (payee name, total cash value, total number of stocks transferred, total number of safekeeping inventory items returned, total estimated value, total number of properties, claim type, claim source, and if it was fast tracked.

Changes to State user access capabilities based on changes made within a specified time range.

Real time user access listings, along with detailed descriptions delineating what those accesses allow the user to do.

Reports received during a specified date range that have not been cleared. This should disclose the holder's FEIN Reports disclosing, at a minimum, claims paid through a settlement date, delineating if the claim was Fast Track, the claimant's name, the claim amount, number of properties on the claim, quantities of stocks and safekeeping and any subsequent proceeds from sales of stocks and safekeeping items.

Reports required for heirfinder discs (showing properties aged a specified amount of time, over a specified limit, showing each owner on the property, property type, the owner's address reported, the holder reporting the property, the general amount of the property, etc.).

Customizable, on-demand report functionality.

Other System Functionality Allow for users to be provided with accesses based on their job functions.

Ability to customize accesses and roles based on needs determined by the State.

Automated batch payments of approved claims based on the date the first claim documents were uploaded, automatically applying payment status to the claim.

The number of claims allowed in a payment batch must be customizable and editable by the Administrator without the need of the vendor’s assistance.

Ability to add alerts on reports, properties, and claims to prevent automated processes from taking place and to notify Administrator staff of an issue.

Ability to add notes and/or images to multiple properties, reports, holders, and claims at a time.

Ability to confirm share transfers Ability to confirm mailing of safekeeping Change orders are permitted when the State requests a change to the system. If a Change Order results in costs that are not included in the costs identified in Attachment BB, Exhibit E and Section 6 of the Contract, the vendor must provide a quote and receive approval of that quote prior to beginning the work. These quotes require amendments to the Contract and must follow the amendment process required by Section 31 of the Contract.

Maintaining the Administrator’s website for constituents to report and remit unclaimed property, filing claims, uploading documentation required to support reports.

Document retention: The system will retain and be able to pull from information previously reported or previously provided through the claims process. Document retention will, at a minimum, adhere to the state’s retention requirements for imaged documents.

Disposal of information will be performed in a manner agreed upon by the vendor and the Administrator.

Disposal and retention cycles should include considerations for back up and disaster recovery systems.

Attachments

Attachments for response. To be completed and returned.

Cost schedule Certification regarding lobbying Reference questionnaire

Attachments for review. To be read and not returned (unless redlining).

Standard form contract Insurance schedule

Attachments incorporated by reference. To be read and not returned.

Timeline

Questions. All questions regarding this solicitation shall be submitted using the bid Q&A feature at nevadaepro.com.

Timeline. The following represents the proposed timeline for this project.

All times stated are Pacific Time (PT).

These dates represent a tentative schedule of events.

The State reserves the right to modify these dates at any time.

The deadline for submissions is the nevadaepro.com bid opening date and time. Late quotes will not be accepted.

Evaluation

Evaluation and scoring are conducted in accordance with NRS 333.335 and NAC 333.160-333.165.

Responses shall be kept confidential until a contract is awarded.

In the event the solicitation is withdrawn prior to award, responses remain confidential.

The evaluation committee is an independent committee established to evaluate and score qualitative evaluation factors for the solicitation.

The State, at its option, may limit participation in cost scoring, presentations, or both to vendors above a natural break in relative scores.

Financial stability shall be scored on a pass or fail basis.

Responses shall be consistently evaluated and scored based upon the following factors and relative weights.

Cost factor. The cost factor score will be based on the following equation. The highest proposed cost from any vendor and the lowest proposed cost from any vendor will be added together to generate a combined total. For each vendor, that proposed cost will be subtracted from the previously combined total. This number is then divided by the highest proposed cost. The resulting number is multiplied by the cost factor weight to generate a weighted cost score.

Presentations. The State may require vendors to make a presentation. The State reserves the right to add additional criteria for presentations. The State reserves the right to forego presentations and select vendor(s) based on written responses submitted.

Best and final offers. Pursuant to NAC 333.165, the State reserves the right to permit revised responses or add criteria to obtain the best offers.

Nevada-based business preference

The State awards a five percent (5%) preference to Nevada-based businesses pursuant to NRS 333.3351 to 333.3356, inclusive.

Nevada-based business is defined in NRS 333.3352(1).

The term ‘principal place of business’ has the meaning outlined by the United States Supreme Court in Hertz Corp v. Friend, 559 U.S. 77 (2010), typically meaning a business’s corporate headquarters.

To claim this preference a vendor must indicate it on their vendor account and submitted quote in nevadaepro.com.

This preference cannot be combined with any other preference, granted for the award of a contract using federal funds, or granted for the award of a contract procured on a multi-state basis.

Inverse preference

The State applies an inverse preference to vendors that have a principal place of business in a state other than Nevada and that state applies an in-state preference not afforded to Nevada based vendors, pursuant to NRS 333.33695.

The amount of the inverse preference is correlated to the amount of preference applied in the other state.

Vendors who meet this criterion must indicated it on their submitted quote in nevadaepro.com.

This preference cannot be combined with any other preference, granted for the award of a contract using federal funds, or granted for the award of a contract procured on a multi-state basis.

Mandatory minimum requirements

Pursuant to NRS 333.311 a contract cannot be awarded to a response that does not comply with the requirements listed in this section. Response shall include confirmation of compliance with all mandatory minimum requirements.

Nevada Law and State indemnity. Pursuant to NRS 333.339, any contract that is entered into may not: (1) require the filing of any action or the arbitration of any dispute that arises from the contract to be instituted or heard in another state or nation; or (2) require the State to indemnify another party against liability for damages.

No Boycott of Israel. Pursuant to NRS 333.338, the State of Nevada cannot enter a contract with a company unless that company agrees for the duration of the contract not to engage in a boycott of Israel. By submitting a response, vendor agrees that if it is awarded a contract, it will not engage in a boycott of Israel as defined in NRS 333.338(3)(a).

nevadaepro.com vendor registration. Pursuant to NRS 333.313, vendor must be registered at nevadaepro.com to respond to the solicitation. Vendor information must match Nevada business license and sam.gov entity registration. Vendor information in nevadaepro.com will be used for contract formation. Email address(es) associated with general mailing address or default bid mailing address (if different from general mailing address) in nevadaepro.com will be used for formal notifications. If a vendor has a different contact name and email for negotiations, that should be indicated on the title page(s) of their response.

Nevada business license. Pursuant to NRS 353.007, prior to contract execution awarded vendor must hold a state business license pursuant to NRS chapter 76 unless exempted by NRS 76.100(7)(b). Business license must match nevadaepro.com vendor registration.

System for Award Management (sam.gov) Prior to contract award vendor must hold an active entity registration in sam.gov. Entity registration must match nevadaepro.com vendor registration.

Contract responsibility. Awarded vendor shall be the sole point of contract responsibility. The State shall look solely to the awarded vendor for the performance of all contractual obligations which may result from an award based on this solicitation, and the awarded vendor shall not be relieved for the non-performance of any or all subcontractors.

Data encryption and stateside data. State IT requires that data be encrypted in transit and in rest. State IT requires that State data assets must be maintained in the United States and data will not be held offshore.

Confidentiality and certification of indemnification

Submitted responses, which are marked confidential in their entirety, or those in which a significant portion of the submitted response is marked confidential shall not be accepted. Pursuant to NRS 333.333, only proprietary information may be labeled a trade secret as defined in NRS 600A.030(5). All proposals are confidential until the contract is awarded; at which time, both successful and unsuccessful vendor proposals become public information.

Vendors shall submit proprietary information and confidential business information in separate files, flagged as confidential in nevadaepro.com. The State shall not be responsible for any information contained within a response; responses shall be released as submitted.

By submitting a response vendor acknowledges its responsibility to act in protection of labeled information and agrees to defend and indemnify the State of Nevada for honoring such designation. Failure to so act shall constitute a complete waiver, and all submitted information shall become public information; additionally, failure to label any information that is released by the State shall constitute a complete waiver of any and all claims for damages caused by the release of the information.

Vendor certifications

Vendor understands and acknowledges that the representations within their response are material and important and shall be relied on by the State in evaluation of the response. Any vendor misrepresentations shall be treated as fraudulent concealment from the State of the true facts relating to the response.

Any and all prices that may be charged under the terms of the contract do not and shall not violate any existing federal, State, or municipal laws or regulations concerning discrimination or price fixing. Vendor agrees to indemnify, defend, and hold the State harmless from liability for any such violation.

All response terms, including prices, shall remain in effect for a minimum of 180 days after the response due date. In the case of the awarded vendor, all response terms, including prices, shall remain in effect throughout the contract term.

The price(s) and amount of this response have been arrived at independently and without consultation, communication, agreement or disclosure with or to any other contractor, vendor, or potential vendor. No attempt has been made at any time to induce any firm or person to refrain from proposing or to submit a response higher than this response, or to submit any intentionally high or noncompetitive response. All responses shall be made in good faith and without collusion.

The information included in this response has been arrived at independently and without non-public information obtained from State officials, staff, or their agents.

All employees and contractors assigned to the project are authorized to work in this country.

Vendor has a written equal opportunity policy that does not discriminate in employment practices with regard to race, color, national origin, physical condition, creed, religion, age, sex, marital status, sexual orientation, developmental disability or disability of another nature.

Vendor has a written policy regarding compliance for maintaining a drug-free workplace.

Critical items

In addition to the scope of work and attachments, the items listed in this section are critical to the success of the project. These items will be used in evaluating and scoring responses. Vendor response should address items in this section in enough detail to provide evaluators an accurate understanding of vendor capabilities. Responses that fail to sufficiently respond to these items may be considered non-responsive.

Standard form contract. The State strongly prefers vendors agree to the terms of the attached standard form contract as is. Ability to agree to contract terms is a high priority to the State. Vendors who cannot agree to the contract as is must include a redlined Word version of the attached standard form contract with their response, with comments justifying the benefit to the State for each requested change. To the extent a vendor has prior contractual dealings with the State, no assumption should be made that terms outside those provided herein have any influence on this project.

Indemnification. Required contract terms on Indemnification: "To the fullest extent permitted by law, Contractor shall indemnify, hold harmless and defend, not excluding the State’s right to participate, the State from and against all liability, claims, actions, damages, losses, and expenses, including, without limitation, reasonable attorneys’ fees and costs, arising out of any breach of the obligations of Contractor under this contract, or any alleged negligent or willful acts or omissions of Contractor, its officers, employees and agents. Contractor’s obligation to indemnify the State shall apply in all cases except for claims arising solely from the State’s own negligence or willful misconduct. Contractor waives any rights of subrogation against the State. Contractor’s duty to defend begins when the State requests defense of any claim arising from this Contract."

Limited liability. Required contract terms on Limited Liability: "The State will not waive and intends to assert available NRS Chapter 41 liability limitations in all cases. Contract liability of both parties shall not be subject to punitive damages. Damages for any State breach shall never exceed the amount of funds appropriated for payment under this Contract, but not yet paid to Contractor, for the Fiscal Year budget in existence at the time of the breach. Contractor’s tort liability shall not be limited."

Insurance schedule. The State strongly prefers vendors agree to the terms of the attached insurance schedule as is. Vendors who cannot agree must explain which areas are causing non-compliance and attach a redline if necessary. Awarded vendor shall maintain, for the duration of the contract, insurance coverages as set forth in the fully executed contract. Work on the contract shall not begin until after the awarded vendor has submitted acceptable evidence of required insurance. Failure to maintain any required insurance coverage or acceptable alternative method of insurance shall be deemed a breach of contract.

Vendor background

Provide a background, history, and why vendor is qualified to provide the services described in this solicitation. Background should include, at a minimum, the location(s) of the office(s) that would perform the work and the number of employees locally and in total. History should include, at a minimum, the number of years in business and company headquarters location. Provide a brief description of the length of time vendor has been providing services described in this solicitation to the public or private sector. If your company has worked with the State previously, include information about those engagements.

Key personnel. Provide a resume free of photos or overly stylized formatting for proposed key personnel, whether employed directly or through a subcontractor.

Current or former employees. If you employ (a) any person who is a current employee of an agency of the State of Nevada, or (b) any person who has been an employee of an agency of the State of Nevada within the past two (2) years, and if such person shall be performing or producing the services which you shall be contracted to provide under this contract, you shall disclose the identity of each such person in your response, and specify the services that each person shall be expected to perform.

Exclusions. All conditions and provisions of this solicitation are deemed to be accepted by the vendor and incorporated by reference in the response, except such conditions and provisions that the vendor expressly excludes in the response. Any exclusion shall be in writing and included in the response at the time of submission.

Subcontractors

Subcontractors are defined as a third party, not directly employed by the contractor, who shall provide services identified in this solicitation. This does not include third parties who provide support or incidental services to the contractor.

Vendor shall disclose all proposed subcontractors. Response should include a vendor information response form for each proposed subcontractor.

Vendor shall not allow any subcontractor to commence work until all insurance required of the subcontractor is provided to the vendor.

Vendor shall certify that subcontractors comply with mandatory minimum requirements except contract responsibility.

Vendor response shall identify specific requirements of the project for which each subcontractor shall perform services.

How the work of any subcontractor(s) shall be supervised How channels of communication shall be maintained How compliance with contracts terms and conditions will be assured Previous experience with subcontractor(s)

Confidential business information

The information requested in this section is designated as confidential business information by the Administrator pursuant to NRS 333.020(5)(b) and is not public information pursuant to NRS 333.333.

This information should be submitted as a separate attachment, flagged as confidential in nevadaepro.com.

Dun and Bradstreet number. Vendor shall provide their Dun and Bradstreet Number.

Financial information. Vendor shall provide the last two full years and current year interim (a) profit and loss statements and (b) balance statements.

Disclosure. Vendor shall provide complete disclosure of any alleged significant prior or ongoing contract failures, contract breaches, any civil or criminal litigation or investigations pending which involves the vendor or in which the vendor has been judged guilty or liable.

Conflict of interest. Vendor shall disclose any existing or potential conflict of interest relative to the performance of the contractual services resulting from this solicitation. Any such relationship that might be perceived or represented as a conflict shall be disclosed. By submitting a response in response to this solicitation, vendors affirm that they have not given, nor intend to give at any time hereafter, any economic opportunity, future employment, gift, loan, gratuity, special discount, trip, favor, or service to a public servant or any employee or representative of same, in connection with this procurement. Any attempt to intentionally or unintentionally conceal or obfuscate a conflict of interest shall result in disqualification of a vendor response. An award shall not be made where a conflict of interest exists. The State shall determine whether a conflict of interest exists and whether it may reflect negatively on State vendor selection. The State reserves the right to disqualify any vendor on the grounds of actual or apparent conflict of interest.

Client references

Vendor shall provide reference questionnaire attachment to client references from similar projects performed for private or public sector clients within the last five years.

The single point of contact must receive at least three complete reference questionnaire documents directly from the client references via email.

The purpose of these references is to document relevant experience and aid in the evaluation process.

Reference questionnaire will not be accepted directly from proposing vendors.

Client references shall not be requested from the contracting agency.

The State will not disclose client references, but may confirm if a reference questionnaire has been received.

The State reserves the right to contact client references during evaluation or negotiations.

Submission checklist

This section identifies documents that vendors shall submit to be considered responsive. Vendors are encouraged to review all requirements to ensure all requested information is included in their response.

Responses must be submitted as a quote through nevadaepro.com.

Vendors are encouraged to submit a single file attachment per section where possible.

Technical proposal information and cost proposal information shall not be included in the same attachment.

Cost proposal attachment shall not be flagged as confidential in nevadaepro.com.

Additional attachments may be included, but are discouraged and should be kept to a minimum.

Technical proposal

Title page Table of contents Signed certification regarding lobbying Response to mandatory minimum requirements Response to critical items Response to scope of work Other informational material

Proprietary information. If necessary. Attachment should be flagged confidential in nevadaepro.com.

Title page Table of contents Trade secret information, cross referenced to the technical proposal (alternatively, a redacted technical proposal and a full confidential technical proposal can be submitted)

Cost proposal

Confidential business information. Attachment should be flagged confidential in nevadaepro.com.

9.6 Contract Terms and References. Any and all references made in this Request for Proposals to “State,” “Treasurer’s Office,” or “Unclaimed Property Program” shall refer to the State of Nevada, the Nevada State Treasurer’s Office, and the Nevada Unclaimed Property Program respectively, unless context specifically ascribes a different meaning to those terms.

9.7. Other attachments. If necessary, not recommended.

9.8 Client references. Not submitted directly by vendor.

Revised 2024-10 Page 2 of 6

Page 1 of 1 Request for proposals 05TO-S3607 image1.png