RFP DV-25-556 Short Term Rental Tech Solution.pptx

PPTX presentation 7 MB Posted

Attached to
Short-Term Rental Tech Solution
Solicitation number
DV-25-556
Issued by
Los Angeles County, California

About this file

This is a Request for Proposal (RFP) for the City of Long Beach, California, seeking technological solutions to support administration of the Short-Term Rental (STR) program. The RFP encompasses four primary solution components: an online portal for registration and renewals, address identification and reporting capabilities, tax collection functionality, and a 24/7/365 call service hotline for handling neighbor complaints. The City intends to procure a single integrated solution containing all components, though consideration may be given to awarding individual components based on feasibility. Questions from prospective bidders are due by 11:00 AM (PST) on July 24, 2025, with the City posting responses by August 7, 2025. Proposals must be submitted by 11:00 AM (PST) on August 21, 2025. The evaluation period follows in fall 2025, with demonstrations estimated for October 2025, negotiation and contract selection anticipated for November 2025, and estimated spring 2025 implementation.

The RFP specifies comprehensive system requirements including PCI compliance, SOC 2 certification, full data encryption in transit and at rest, Single Sign-On for City users, and multi-factor authentication for business customers. The solution must provide continuous data backup across multiple geographic server locations and support robust reporting and ad hoc customization capabilities. The selected contractor must provide customer support with human representatives available within two automated voice prompts for public users and designate a single point of contact for City users who responds within one business day. No pricing information, set-asides, incumbent contractor details, or specific contract term lengths are provided in this RFP agenda document.

View the file

Other files

Show all 12

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

RFP DV-25-556: Short-Term Rental Tech Solution

Agenda

Introductions

RFP Instructions and Timeline

Summary & Goals

Scope of Work

RFP Evaluation Criteria

Proposal Content

Questions

RFP Instructions and Timeline

Questions Due to the City11:00 AM (PST) July 24, 2025
Posting Q & AAugust 07,2025
Proposals Due11:00 AM (PST) August 21, 2025
Evaluation PeriodSpring 2025 (Estimated)
DemosOctober 2025 (Estimated)
Negotiation & Contract SelectionNovember 2025

Summary & Goals

Reduction of Customer inquiries regarding simple details of their registration.

Shortened registration review times.

Attaining a 100% accuracy in calls forwarded from the program-required hotline reaching the emergency contact.

Increased availability of tracking mechanisms that assist the City to review registration statuses.

Reduction of the steps and clicks required to update the City’s public facing website on current registration counts and locations.

The City of Long Beach (City) is seeking proposals from qualified firms to provide technological solutions that assist with the administration of the Short-Term Rental program. This includes address identification and data reporting, compliance monitoring, enforcement, and tax collection support

Scope of Work (Section 2.1)

Solution Component #1: Online Portal, Registration, and Renewals This solution component shall:

Include a self-service online portal to allow the public to register and renew (annually) their short-term rental(s).

Enable City users to independently update accounts and correct applicant errors, ensuring the City does not need to rely on Contractor for assistance with basic administrative functions.

Allow the City to manually and/or preemptively disallow the submittal of a renewal application for any given individual registration.

Disallow the submittal of new applications without consent/approval from the City.

Send automated emails/notifications to short-term rental registrants when submitting payments or applications to the City, as well as when any City approvals or denials are made.

Include the ability for the public to submit information, documentation, and payment necessary to obtain a registration.

Solution Component #1: Online Portal, Registration, and Renewals (continued)

The solution component should:

Include the ability for the public to have multiple sets of contact information for individual registrations, including owner, tenant, property manager, etc.

Include the ability for the public to export reports for information relevant to their account including, but not limited to, their tax payments.

Include the ability for the public to access general information about the status of their application or approved registration, including expiration date and registration number.

Provide a module wherein the City may view all registration records and may filter or change the view of these records without leaving the page.

Provide the ability for the City to securely enter the account of a portal user to assist/troubleshoot issues.

Provide a registration process which may be modified directly by the City, upon request by the City to the Contractor, or both.

Provide the ability to automatically withhold a renewal application submittal if the account is delinquent and to notify the registrant.

Provide for changes to registration statues to be instantaneously reflected across all the affected solution components, including reporting.

Solution Component #1: Online Portal, Registration, and Renewals (continued)

The solution component should:

Disallow the ability for an individual person to be registered for more than one non-primary registration and more than one primary registration. Likewise, an applicant applying as a business entity shall only obtain one non-primary registration.

Provide the ability to link multiple registrations to a single account.

Allow portal users the ability to modify details on their new or renewal application prior to City approval, including changing the application type (if application fees are equal in cost).

Allow portal users and the City to communicate directly within the solution.

Allow the City to create ad hoc e-mail notifications.

Allow the City to change automated email notifications upon request.

Provide the ability to add smart fields/labels to registrations both pre- and post-go live with the solution.

Provide a waitlist mechanism for when the City reaches a registration cap at a property, group of properties, or on a citywide basis.

Solution Component #2: Address Identification and Reporting

Provide the ability to correctly match online short-term rental listings to existing properties, with human verification of each listing identified and justification of matching criteria used.

Scrape/scan STR platforms at regular or randomized intervals, including new platform sites discovered post go-live, and take high resolution screen shots of all listings as well as determine their minimum night stay.

Include an automated updated live dashboard displaying property totals and listing counts, listing compliance breakdown, and STR location map.

Include a robust record management system that can export reports in Excel or CSV format.

Be able to identify, record and report advertised property details including, but not limited to, the number of bedrooms, host information, maximum occupancy, minimum night stay, property type, type of rental (entire home vs. room rental), nightly rate, etc.

Be able to document, categorize, and store history related to a property unit, including the advertisements, registrations, City notes, etc.

Solution Component #2: Address Identification and Reporting (continued) This solution component should:

Allow the City full access and editing rights to maintain a list of properties/parcels should such a list be incorporated into the solution.

The City should have an indefinite number of ways to label individual, or groups of properties/parcels and those labels should be contextualized on a map.

Provide the City the ability to customize compliance statuses or labels as required to meet the City's unique regulations on STR.

Be able to identify and distinguish between different property types such as condominiums, single-family dwellings, duplex, apartment homes (4+ units), etc.

Provide ad hoc reporting features.

Be able to identify potential

Solution Component #3: Tax Collection

Allow the City to create, edit and schedule email reminders for monthly tax reporting.

Auto-calculate taxes based on which hosting platform was used and collect payment.

Provide the ability to waive penalty and interest fees, either for individual accounts, individual registrations or entire taxable periods.

Solution Component #3: Tax Collection (continued)

Provide the ability for registrants to remit taxes for all properties/units they manage in a single upload.

Allow the tax rates to be updated as needed without the need to engage a development team.

Provide the ability to automatically request support documentation for an exemption taken on a tax return.

Provide the ability to write off fees and maintain why the action was done.

Continue to calculate interest on outstanding tax due resulting from an underpayment.

Provide the ability to process and track overpayments and underpayments.

Provide the ability for a taxpayer to remit the remaining amount due as a result of an underpayment or amended return online.

Provide the ability for a taxpayer to use a credit resulting from an overpayment or amended return online to reduce another filing amount.

Process amended returns and reflect revenue in the correct reporting periods.

Provide the ability to create a “payment plan” for payment agreements wherein users are able to remit payment according to the specified schedule and amount due online and the City able to track and report on the payment plan balance.

Solution Component #4: 24/7/365 Call Service Hotline

Provide a 24/7/365 (including holidays) live hotline to address neighbor complaints and issues concerning property rentals.

Allow the caller to speak with a live person before the call is over.

Record each incoming call to the hotline, notify all incoming callers that they will be recorded, and make all recordings available to the City.

Create a custom script for each call (developed jointly by the selected firm and the City) and any options, if applicable, as a call progresses onto the next steps.

Solution Component #4: 24/7/365 Call Service Hotline (continued)

Provide call center agents whom shall cross reference the address given by the hotline caller with all registered short-term rentals with the City and call the emergency contact immediately after completing the hotline call in order to instruct the emergency contact about their requirements to resolve the issue.

If the call attempts are successful, the emergency contact shall be provided an option to input resolution notes which will be accessible to the City.

If the calls are unsuccessful, a voicemail shall be left and a text shall be sent, both providing a summary of the issue(s), City requirements to resolve the issue, and an option to provide resolution notes which will be accessible to the City.

Provide the following information for each hotline call which will be made available for review in the system by the City:

Date and time of the call Unique complaint ID Recording of call Type of Complaint: noise, trash, unregistered rental, exceeding occupancy, etc.

Reporting party name (if provided) Reporting party address (if provided) Reporting party phone number STR address as reported Confirmed property address STR account number (if available) Note if the reporting party wants a callback Emergency contact name(s) and phone number(s) (provided by the City or the via registration portal) Details, including timestamps, for each attempt made by Contractor to contact Emergency contact Emergency contact resolution notes (if provided)

Provide a field for each call for the City to assign/edit a compliancy status.

Provide a field for each call for the City to enter notes.

Provide the City with the ability to directly update emergency contact names and numbers without solution provider assistance.

Provide the complaining party and the emergency contact the ability to submit photos/videos as ‘evidence’.

Customer Support The Contractor shall:

Provide customer support for public and City users of the solution.

Ensure that public users who are attempting to reach a representative of the Contractor be able to speak with a human customer support representative within two automated voice prompts.

The Contractor should:

Designate a single point of contact for City-users for the life of the contract who must respond to all City-inquiries within one business day.

It is the intent of the Department to procure a single solution that will contain all the above components. However, consideration may be given to award certain components individually depending on feasibility.

The following requested services apply to the entirety of any proposed solution, whether in whole or in part:

System Security The solution system shall:

Provide full encryption and audit logs on every action.

Be Payment Card Industry PCI compliant.

Be System & Organization Controls Two (SOC 2) compliant and provide certification documentation.

Encrypt all data while in transit and at rest (e.g. credit cards information, personal information and documentation, etc.).

Provide Single Sign On (SSO) for City users.

Not store any private or sensitive data in the error logs.

Not store database connection information, passwords, and any other sensitive credentials in plain text.

Use HTTPS standard encryption for web-based traffic.

The solution system should:

Provide multi-factor authentication for business/portal customers.

Continuously back up data to minimize recovery windows and stored in multiple server physical locations for redundancy (i.e., data centers located on the east and west coast).

Support scanning of files for viruses and malware.

Provide the ability to display the last date and time the user logged onto the system.

Expire the session after user walks away for a certain period of time.

RFP Evaluation Criteria (Section 3.2)

Proposal Content (Section 4.2)

Questions?

Thank you image2.jpeg image3.png image4.png image5.png image6.png image1.png

File details come from the government source that posted it. Updated .