The GNET Connect Workshop is a dynamic platform where GNET users can ask technical and general questions, brainstorm solutions, and discuss pertinent topics relevant to their businesses. Recently, a key discussion revolved around a new feature designed to expedite the affiliate vetting process: the Pre-Partnership Requirements checklist in the GNET Connect portal.
What is the Pre-Partnership Requirements Checklist? This new feature allows GNET members to create a customized checklist on their profile outlining the requirements for potential affiliate partners. Traditionally, companies might use forms or PDFs on their websites to list these requirements, but this new portal feature integrates them directly into the GNET Connect platform.
Key Functionalities of the Checklist:
• Define Requirements: Users can add specific items to their checklist, such as a Certificate of Insurance (COI), a drug test policy, or proof of a valid driver’s license.
• Required vs. Optional: Each requirement can be marked as either required or optional.
• Segment-Specific Application: A crucial aspect of this feature is the ability to apply requirements to specific partner segments. For instance, a requirement for a valid driver’s license might only be applicable to Independent Operators (IOs), while other requirements could apply to Corporate Operators or Distributors/Aggregators (like travel agencies). If no segment is defined, the requirement is visible to everyone.
• External Links: Users can include external links to forms or detailed checklists (e.g., a “pre-partnership checklist” form that needs to be filled, signed, and returned).
• Document Management Integration: If a user is a subscribed member with access to document management, prerequisite lists or completed forms can be uploaded directly to their document section.
How the Vetting Process is Expedited: When a company, for example, in Boise, Idaho, wants to partner with RMA (a demo company used in the workshop), they can search for RMA on the GNET Connect portal. Before sending a partnership request, they must go through RMA’s defined checklist. The system then background checks if the requesting company (like Mesa Limo, used in the example) already has the required documents uploaded to their GNET profile.
• If a document, such as an airport permit, is already uploaded and valid, it will show as “green” (compliant).
• If a document is missing or expired (e.g., a $10 million coverage COI), the system informs the user and provides an immediate opportunity to upload the necessary document directly from the portal. This eliminates the need to navigate to multiple screens.
This process significantly saves time and reduces redundancy, as documents only need to be uploaded once and remain accessible.
Beyond the Checklist: Real-World Requirements and Insights The workshop also delved into the diverse requirements companies have for partners, emphasizing that not all affiliates are “built exactly the same”.
• Legends (Paul’s company): Paul highlighted the need for Non-Disclosure Agreements (NDAs) and affiliate agreements as absolute requirements for VIP affiliates. He also checks for extra service charges (STC/VAT, early AM/late night pickups, airport fees) and requests details about a partner’s fleet. For new affiliates, a 30 to 90-day probation period with credit card charges after each transfer and weekly itemized invoices is standard before moving to weekly invoicing. Essential “givens” include drug testing, COI, airport permits, and special certifications needed for specific pick-up zones.
• Chicago Market (Paula’s perspective): Paula discussed strict vetting for Independent Operators (IOs), including road tests and ensuring full compliance with insurance requirements, especially federal limits, and workers’ compensation. She also noted the value of public portals in Chicago that allow operators to check the license status, violations, and suspensions of chauffeurs and vehicles. This capability is specific to Chicago but common in many major cities.
The Role of Independent Operators (IOs): The discussion included varying perspectives on working with IOs. Some large companies, like Legends, prefer not to work with IOs, citing concerns about control over vehicles and driver dedication. However, others, especially in different markets, vet IOs strictly and use them as an extension of their team for specific needs, such as during peak demand.
A key takeaway was the need for small operators and IOs to be as visible to the industry as they are to ride-share apps like Uber and Lyft. Tools like the Transco app and the GNET Connect portal’s ability to host documents can help achieve this visibility, allowing these operators to present themselves professionally and meet industry vetting standards. While some IOs may also drive for Uber Black or Lyft Black, it’s believed that they often prioritize calls from industry partners due to higher earning potential.
GNET Connect as a Business Tool: Attendees affirmed that GNET has been a significant source of new business and partnerships. Paul from Legends emphasized GNET as a “multi-layer tool” that makes his work life easier, allowing him to manage numerous affiliates and projects more efficiently. He noted personally gaining eight new affiliates through GNET who send him work.
Future Aspirations for GNET Connect: The workshop concluded with exciting suggestions for future enhancements:
• AI-powered matchmaking: A feature that would allow users to input specific requirements (e.g., “company in Florida with $1 million policy, 20 vehicles”) and receive a filtered list of GNET companies that meet those criteria.
• Industry standard terminology/tiers: Developing a standardized system for classifying operators (e.g., “Class A, B, C operator”) based on service level or attire, which could be displayed on GNET profiles.
The GNET Connect portal aims to be a comprehensive resource that helps members save money, do less work, and ultimately make more money by fostering better, more transparent partnerships.
Leave a Reply