How to Request Live Staff Travel Loads

Asking "any loads on BA177 tonight?" in a Facebook group works until it doesn't. Posts get buried, answers are unverified, and half the group isn't even crew. This is how to ask smarter.

Post a load report when you've just traveled

The most valuable intel is fresh: staff standby count at check-in, passenger seats remaining, whether the list cleared early or went full. If you flew standby yesterday on LHR-JFK, that helps someone trying today.

Request with route, date, and airline

Vague posts get vague answers. Include origin and destination airport codes, travel date, operating airline, and whether you're on ID90 or ZED. Crew who've done the same sector can tell you if morning or evening flights tend to be lighter.

Share desk timing, not just yes/no

When the employee ticket desk opens relative to departure matters as much as the final load. Some airports want you three hours out; others won't list you until two. That detail saves someone a wasted trip to the airport.

Use verified crew channels

Load intel shared publicly can attract non-crew or create security issues on sensitive routes. Layvr Staff Travel is designed to keep reports inside a verified crew network - the same verification used for layover discovery. Guides are live now; in-app load requests are coming soon.