Fly date Nepal, mobilisation explained

The fly date is the calendar entry that matters most to a project manager planning a Nepal crew arrival, and it is the one date the corridor manages backwards from rather than forward to. The fly date does not get scheduled at the start of the file, it surfaces when five upstream gates have closed in sequence, and the variance on each of those gates is what decides whether a 95-day corridor lands at day 95 or drifts to day 120. This guide explains what sets the fly date, what moves it, and what an employer can do to bring it forward without breaking the corridor.

For the broader corridor mechanics, see How to hire Nepali workers for Croatia, complete 2026 guide. For the DOFE-side detail that drives the first three gates, see DOFE permit, complete employer guide.

What the fly date actually is

The fly date is the airline ticket booking, Kathmandu Tribhuvan International to a destination airport, one-way under the Free Visa Free Ticket reform of May 2024 for in-scope destinations. Booking happens after DOFE has printed the individual labour permit, after the destination-country visa is stamped in the passport, and after the airport reception is confirmed at destination. The booking window from confirmed-can-fly to actual-fly runs 3-7 days at the median, airlines have inventory on the Kathmandu hubs but the worker file needs all artefacts in physical hand before the ticket commits.

What the fly date is not: a date negotiable from the demand letter. The corridor regulator is DOFE; the destination regulator is the immigration ministry of the destination country. Neither responds to project deadlines. The fly date is the output of regulator timing, not an input to it.

The five gates that move the fly date

Werklist tracks the file against five named gates from Day 0 (signed demand letter) to fly date. Each gate has a normal window and a peak window; the file's actual landing date is the sum of the windows it experiences, not the median of the normal range.

Gate 1: DOFE Job Order verification. Submitted at Maharajgunj after the attestation chain closes; verified in 14-28 days normal, 35-45 days at the September-October Gulf-mobilisation peak. This is the single critical-path gate of the entire corridor, nothing downstream moves without it.

Gate 2: Destination-side permit issuance. For Croatia, the HZZ labour-market test (8-15 working days for named-shortage trades) plus the MUP jedinstvena dozvola (25-40 days at PU Zagreb or PU Split). For Saudi Arabia, the Musaned authorisation against the E-Wakala. For Malaysia, the Labour Office pre-approval (7 working days) plus calling visa. Run in parallel with the DOFE-side processing where the regulator allows it; the destination gate often closes before or after Gate 1 depending on which corridor.

Gate 3: Medical and pre-departure. Medical fit-test at a DOFE-approved Kathmandu centre (the Patan testing centre is the most common), police clearance, biometrics, foreign employment insurance purchase. Combined 10-15 days; runs in parallel with Gates 1 and 2 once the candidate is shortlisted.

Gate 4: Visa-D stamping. For Croatia, the New Delhi Croatian Embassy, Nepal's nearest Croatian consular representation. Stamping window runs 15-25 working days, decided by appointment availability and consular workload. For Gulf and Malaysia, stamping at the resident Kathmandu embassy runs 7-15 days. This is the gate that most often slips the fly date by a week.

Gate 5: DOFE labour permit issuance and ticket booking. Once Gates 1-4 are closed and the PDOS certificate is on file, DOFE prints the per-worker labour permit. Werklist's Kathmandu team books the flight, confirms airport reception at destination, and notifies the worker. The 3-7 day buffer between permit issuance and actual fly date allows for last-minute medical re-checks where the original certificate is approaching the 90-day validity edge.

What moves the fly date earlier, without breaking the corridor

Three operator levers compress the fly date inside the lawful corridor. Werklist applies all three where the brief allows.

The standby roster. If the named trade and destination match an existing Werklist standby roster of pre-DOFE-permitted workers held against an anchor employer's annual demand, the corridor can collapse Gates 1 and 3, the workers already carry the permit, the medical, the PDOS certificate, and the insurance. Fly date in 50-70 days is feasible against the standby roster, where it is 95-120 days from fresh sourcing. The standby roster works only where the trade and destination are both pre-vetted, it is not a generic shortcut.

Submission timing outside peak. DOFE's verification queue compresses 30-60 percent during the September-October Gulf-winter mobilisation backlog. Files submitted in November or January clear faster than files submitted in late September. Where the employer's project start date allows, Werklist times the submission to land outside peak.

Parallel-tracked attestation. The Chamber of Commerce attestation, destination MFA stamp, and Nepal Embassy verification can be run in parallel against pre-drafted templates rather than sequentially. The Werklist pre-submission checklist closes this in 5-7 days where ad-hoc preparation would run 10-14.

What moves the fly date later, and how Werklist reads it

Three failure modes account for most of the corridor slips we see on Nepal files. First, employer-side document errors, unattested demand letters, mismatched headcount between demand letter and contract, missing destination MFA stamp on Gulf files. Each return adds 7-10 days at the DOFE Maharajgunj review. Second, embassy queue compression at New Delhi during Schengen-state visa peaks, March and September push the visa-D window to the 25-day end of the range. Third, medical certificate expiry, files attested against an optimistic fly date that then slip 30 days fail the 90-day medical validity check, requiring a re-test that adds 5-7 days.

The Werklist Kathmandu team reads each of these against the file weekly. The corridor-fit assessment Branimir's team sends on the scoping call names which of the three is most likely to apply to the employer's specific brief.

What the fly date confirms at Tribhuvan

The flight is booked from Kathmandu Tribhuvan International, TIA. The worker travels with the DOFE labour permit, the destination visa, the bilingual employment contract, the medical certificate, the PDOS completion certificate, the Welfare Fund receipt, and the foreign employment insurance policy. Tribhuvan immigration checks the labour permit against the passport, the visa, and the airline manifest at departure. The Werklist destination partner meets the worker at the destination airport, Zagreb, Split, Dubai, Riyadh, and walks the residence registration that most destinations require within 8 days of arrival. The fly date is the bridge between the Kathmandu file and the destination shift.

The Kathmandu branch, where the fly date is actually decided

Werklist's Kathmandu branch tracks every file weekly against the five gates, holds the standby roster relationships that compress the corridor where they apply, walks the Maharajgunj submission and the Patan testing centre relationship, and books the flights when the permit is in hand. The branch lead, the photographed team, and the licence number with renewal date live on the Kathmandu branch page.

If you are scoping a Nepal corridor and need a realistic fly date against a specific target start date, send a brief. We reply within one business day with the corridor fit, whether you sign with us or not.