Helipass is preparing to roll out a major update to support UTC time conversions and localization across all tenant regions. These enhancements have already been successfully implemented in the Australia region, which operates on the + side of UTC, and will soon be merged into the core Helipass tenant used by all customers.

What Is Changing?

• System-wide updates to handle UTC time conversion accurately across all modules.
• Improved localization for tenants + UTC time zones.
• Merging of code forks to unify the platform and ensure consistent behavior.

What To Expect?

• Thorough testing is underway to ensure a smooth roll out early-mid November
• Some areas may still incorrectly show unexpected date shifts (e.g., data appearing a day early or late) depending on your region.
• Users are encouraged to monitor date and time displays closely after the update and report any anomalies.

Please check your Time Zone setting in your Helipass User Profile to ensure it reflects your actual location. This will help the system display and process time-sensitive data correctly once the update is live.

To check or update your time zone:

• Click your name in the top right corner of the screen
• Select “View Profile”
• Review your Time Zone
• If needed, select the correct time zone and click “Update Profile”

This is a critical enhancement that will improve accuracy and usability for all global users. The Helipass team is committed to resolving any issues quickly and ensuring a seamless transition.

____________________________________________________________________________________________

Manifest Users - Direct Linking of Web Check-Ins to Manifest Reservations
Helipass has streamlined the Web Check-In process by enabling automatic linking to manifest reservations. Before this update, users had to manually link checked-in passengers to their manifest entries, which added extra steps and increased the chance of errors. Now, the system intelligently matches passengers to their reservations based on the configured reservation window.

What's New?

• Web Check-In now searches for manifested passengers within the reservation window.
• Checked-in passengers are automatically linked to their manifest reservation.
• Checked-in weights and status update in real time on the manifest.

Why It Matters?
This update eliminates manual linking and ensures that passenger check-in data is immediately visible to operations teams. It improves transparency, reduces the risk of missed reservations, and speeds up the flight execution process. Teams can now rely on a more seamless and accurate check-in workflow.

____________________________________________________________________________________________

Schedule View Users - Disabling Edits for Historical Events on the Schedule
The Schedule View page has been updated to prevent accidental edits to historical events. Previously, users could modify or delete events that had already occurred, which led to confusion and data inconsistencies. The new guardrails ensure that only future events can be edited, while past events remain locked for reference. When an entire row is deleted or the passenger is swapped, only the future events that have not occurred yet will be adjusted and the historical events will remain the same.

What's New?

• Historical events can no longer be:
  • Deleted
  • Edited
  • Swapped to other passengers
• If the event has started but not yet ended:
  • Arrival date is locked
  • Other fields remain editable

Why It Matters?
By protecting historical data, this update helps maintain the integrity of scheduling records and prevents accidental changes that could disrupt planning. Users can now focus on managing upcoming events with confidence, knowing that past entries are preserved and accurate.

____________________________________________________________________________________________

TRF Users - Filter Travel Request Export by Arrival or Departure Date
TRF users now have more control over the Export feature on the Travel Forms page. Previously, exports were limited to submission date ranges, which made it difficult to isolate specific travel windows. With this update, users can now filter exports by Arrival or Departure date, giving them more precision when reviewing travel schedules.

What's New?

• Export options now include filters for:
  • Arrival Date
  • Departure Date
• Previously, users could only export by submission date range.

Why It Matters?
This enhancement helps users generate cleaner, more targeted reports that focus only on relevant travel requests. It reduces the need to manually sift through unrelated data and improves coordination with teams who rely on accurate travel schedules. TRF users can now share and analyze travel data more efficiently.

____________________________________________________________________________________________

TRF Users - Support Added for Linking Other Passengers and Dependents Under Passenger Profiles
TRF customers can now create and manage dependent profiles linked to primary passengers. These dependents, such as spouses or children, often travel with employees but don’t require full Helipass profiles. The new Linked Profile tab makes it easy to track these individuals without adding unnecessary complexity. This work is going to tie in new passenger profile types of Dependents as well.

What's New?

• A new Linked Profile tab has been added to the Passenger Profile.
• Dependents (e.g., spouse, children) can be created and linked to the main traveler.

Why It Matters?
This feature improves visibility into group travel and simplifies the management of non-compliant passengers. It supports better planning and coordination for families traveling together, and marks another milestone in the ongoing TRF improvements.

Keep your eyes open for more enhancements that are on the way!

____________________________________________________________________________________________

API Users - New Data Points Added to the API for Advanced Reporting
Helipass has expanded its API capabilities to support new features and improve downstream reporting. As tenants adopt new workflows and tools, the API must evolve to reflect the latest data structures. This month’s update adds several key data points to help customers build more powerful reports.

What's New?

• Added data points include:
  • Request/Reservation Data for Last Minute Changes (Australia region)
  • WebCat IDs (Australia region)
  • Cargo Reservation Types
  • Support for Passenger Travel Portal features

Why It Matters?
These additions give customers deeper insights into their operations and improve the accuracy of external reporting tools like Power BI. By keeping the API aligned with system enhancements, Helipass ensures that customers can make informed decisions using the most complete and current data available.

____________________________________________________________________________________________

Worksite Users - Edit Default Modal No Longer Pulling Null for Position and ICS Role
Worksite users reported that the Position and ICS Role fields were not appearing for passengers when searching them in the Edit Defaults modal, even for passengers with saved defaults. This led to blank fields and the risk of overwriting existing data with null values.

What Was Happening?

• Fields appeared blank, and saving would overwrite them with null values.
• This led to lost data and manual re-entry.

What Was Fixed?

• The modal now correctly loads saved defaults for these fields.

With this fix, users can confidently manage passenger defaults without worrying about data loss. The Edit Defaults modal now behaves as expected.

____________________________________________________________________________________________

Worksite Users - Arrival Presets Showing Passengers on Wrong Day (Australia Only)
Australian tenants encountered a bug where passengers were incorrectly appearing in the Arrival Presets section for the following day. This issue stemmed from time zone conversions, causing arrival times to shift and be misaligned with local schedules. The problem was particularly disruptive for teams assigning resources based on daily arrivals.

What Was Happening?

• Passengers arriving in Australia were showing up in the next day’s Arrival Presets.
• The system was converting local arrival times back to CST, causing date mismatches.

What Was Fixed?

• Time zone logic was corrected to respect local time for Australian tenants.
• Arrival Presets now display passengers on the correct day for assignment.

With this fix, scheduling and resource assignments are now accurate and aligned with local time zones. Teams in UTC+ regions can confidently rely on the Arrival Presets to reflect real-time passenger movements.

____________________________________________________________________________________________

Schedule View Users - Request Modal Load Time Improved
Users managing requests from the Schedule View page experienced long delays when opening the Arrival and Departure Request modal. The issue was especially noticeable when all passengers had already been assigned, causing the modal to sometimes take 30 or more seconds to load. This slowed down scheduling and created frustration.

What Was Happening?

• The modal could take 30+ seconds to load.
• This slowed down scheduling and request management.

What Was Fixed?

• The modal logic was optimized for faster performance.

With this fix, users can now open and manage requests quickly and efficiently. The Schedule View page is more responsive, improving the overall user experience.

____________________________________________________________________________________________

Manifest Users - Preventing Duplicate Passenger Adds to Manifest from the Manual Add Personnel Modal
A bug in the Manual Add Passenger modal allowed users to accidentally add the same passenger multiple times to a manifest. This occurred when the +Add button was clicked repeatedly before the system could process the first request. The resulting duplicates created confusion and required manual cleanup.

What Was Happening?

• Users could accidentally click the Add button multiple times.
• This led to duplicate entries on the manifest.

What Was Fixed?

• The button now changes to “Processing” and disables further clicks after the first selection.

This update improves the reliability of the manifest creation process and prevents unnecessary duplication. Users can now add passengers with confidence, knowing the system will handle their input correctly.

____________________________________________________________________________________________

Manifest Users - Trip Locking Settings No Longer Allowing Cargo to be Added to Trip
Helipass tenants use trip lock settings to prevent changes to manifests after a certain point in the flight preparation process. A bug was discovered that allowed cargo items to be added to locked trips, bypassing these safeguards. This posed a risk to operational accuracy and compliance.

What Was Happening?

• Cargo could be added to trips that were already locked.
• This undermined the integrity of finalized manifests.

What Was Fixed?

• The system now enforces lock settings for both passengers and cargo.

With this fix, trip manifests remain secure once locked, ensuring that no unauthorized changes can be made. This helps maintain consistency and safety across flight operations.

____________________________________________________________________________________________

Manifest Users - Error No Longer Appearing when Adding Passengers from Requests
A bug was causing error messages when users tried to add passengers to a manifest from a request. The issue was traced to conflicting notification settings, where certain combinations would trigger a system error. This blocked users from completing their manifests.

What Was Happening?

• If “Enable Mobile Notification Emails” was on but “Manually Enable Trip Passenger Notifications” was off, an error would appear.
• This blocked users from adding passengers.

What Was Fixed?

• The dependency between these two settings was removed.

This fix ensures that users can add passengers without encountering errors, regardless of their notification configuration. The manifest creation process is now more flexible and reliable.

____________________________________________________________________________________________

Manifest Users - Red Alerts for Unregistered Passengers on Manifest Restored
A bug was preventing Red Alerts from appearing on manifests when unregistered passengers were added. This issue affected tenants using the “Show unregistered passengers warnings” setting, which is designed to flag potential compliance risks.

What Was Happening?

• The manifest failed to flag unregistered passengers.
• This reduced visibility into potential compliance issues.

What Was Fixed?

• The alert logic was corrected to properly trigger warnings.

With this fix, manifests will once again display clear alerts for unregistered passengers. This helps ensure compliance and keeps operational teams informed during trip planning.

____________________________________________________________________________________________

TRF Users - BLM and LCM Approver Dropdown Lists Restored
TRF users rely on BLM and LCM Approver dropdowns to complete the travel request approval process. A bug caused these dropdowns to stop populating, preventing users from selecting approvers and saving their requests. This disrupted workflows and delayed approvals.

What Was Happening?

• Approver lists were blank, making it impossible to select required approvers.
• Users could not save or submit approvals.

What Was Fixed?

• The dropdown logic was corrected to properly load approver names.

With this fix, TRF users can once again complete approvals without interruption. The approval process is now smooth and fully functional.

____________________________________________________________________________________________

Helipass Users - Duplicate ID's No Longer Being Added to Passenger Profiles After Check-Ins
A bug was causing duplicate IDs to appear in passenger profiles when checking in at the kiosk. While it didn’t affect functionality, it cluttered the UI and created confusion for users reviewing passenger records.

What Was Happening?

• Multiple identical IDs were being saved to passenger profiles.
• This created visual clutter and potential reporting issues.

What Was Fixed?

• The kiosk logic was updated to prevent duplicate ID creation.

Passenger profiles will now remain clean and accurate, improving usability and reducing unnecessary data duplication. This helps maintain a more organized and professional system.