Purpose:
This document outlines the process for Cabo/Cabotage users to request new features or enhancements to existing functionality within the application.
What Qualifies as a New Feature Request
Considered a New Feature:
- A new capability or workflow not currently available in the system
- Enhancements or improvements to existing features (additional fields, automation, reporting, usability improvements, etc.)
- Requests that change how a current feature behaves by design (not due to a defect)
NOT Considered a New Feature:
- Bugs or system defects (see Bug Submission SOP)
- Errors, crashes, or incorrect system behavior
- How-to questions or training requests
- Process or operational questions
Steps to Submit a New Feature Request
1. Clearly Define the Request
When identifying a new feature or enhancement, be prepared to describe:
- What problem you are trying to solve
- Why the current functionality is insufficient
- Feature expectation if the feature is implemented
Helpful context to include (if applicable):
- Business impact (time saved, risk reduced, revenue impact, etc.)
- Any deadlines
2. Provide Supporting Details
Include as much relevant information as possible to help evaluate the request:
- Screenshots or screen recordings
- Example workflows or mockups (if available)
- Current workaround being used (if any)
3. Submit the Feature Request
- Submit to the Business Owner of that area for review and approval
- Omar Alami – All front-end LTL
- Matt Watson – All front-end Truckload
- Eric Dyson – Accounts Receivable
- Rodney Hayhurst – Accounts Payable
- Will Sison – Contracts
- Alan McClanahan - Cabotage
- Zach Miller – Customer Success/CS-CRM
- Peyton Berry and Josh Sagar - Inside Sales/IS-CRM
- Tiffany Letson – Truckload Accounts Payable
- The Business Owner will submit the request to the PM at john.redam@priority1.com
- Use a clear and concise subject line, for example:
- Feature Request: Add Status Filter to Shipment View
In the email, include:
- A detailed description of the requested feature
- The business problem it addresses
- Any supporting screenshots, videos, or documentation
- Timeline/priority expectation
4. Review Process
- The PM will review the request to ensure it is properly categorized as a feature request and contains clear details, instructions, examples, etc.
- If additional clarification is needed, the PM will ask for further details and the request will be on hold until clearly defined
- Approved requests will be logged and reviewed by Development
5. Prioritization and Planning
- Feature requests are prioritized based on:
- Business impact
- Users affected
- Strategic alignment
- Development effort and sprint capacity
- Submission of a request does not guarantee immediate development or inclusion in an upcoming sprint
6. Communication and Updates
- If approved for development, the feature will be scheduled into a future sprint
- Status updates will be shared as the request progresses through the development cycle
- Once development has been completed, the feature will be available for Business Owner testing in the sandbox environment and will require approval by the Business Owner.
- 2 business days (prior to the sprint release) for general features
- 5 business days (prior to the sprint release) for large features
- Once released, you will be notified as part of an application update or release communication
Effective Feature Requests are:
- Outcome-Focused: Explain the problem and desired result, not just the solution
- Clear: Well-defined requests are easier to evaluate and prioritize
- Patience: Feature requests are balanced against existing roadmap priorities and sprint capacity
Comments
2 comments
Cabo/Cabotage Feature Request (SOP)
Vendor user - hide the shipping and handling fee for Harbor Freight Vendor show a total including shipping and handling fee.
also for these customers that use a vendor user-
Highways & Skyways Transportation - Gastonia
|308427-P1
ROAD SCHOLAR TRANSPORTATION
|310889-P1
My Director Shannon Crim.
Please sign in to leave a comment.