Prevailing Wage Determination Processing Time

Compare an initial, redetermination, or Center Director Review request with the matching DOL processing date and source freshness.

Current official PWD queues

PWD official update: June 30, 2026 · Updated Aug 13, 2026

OEWS
April 2026
Non-OEWS
March 2026
Redetermination
April 2026
Center Director Review
May 2026

Remaining Requests

  • Dec 2511
  • Jan 2663
  • Feb 26106
  • Mar 26627
  • Apr 2614,386
  • May 2618,310
  • Jun 2616,797

Read the queue correctly

How to interpret PWD processing time

A PWD queue month is program-level context. It identifies the receipt month DOL reports working on for a particular request type; it is not a promise that every request from that month is complete, and it is not an estimated decision date for one case. Start by matching both the request stage and, for an initial request, the wage source selected on the ETA-9141.

Choose OEWS or Non-OEWS for an initial request

Use the OEWS row when the prevailing wage request relies on Occupational Employment and Wage Statistics data. Use Non-OEWS when the request relies on another acceptable wage source, such as an employer-provided survey. The two queues can move at different rates, so choosing by whichever month looks faster produces the wrong comparison. If the wage source is unclear, review the filed ETA-9141 or ask the employer or representative who prepared it before interpreting the result.

Use the request date for the review now pending

A redetermination and a Center Director Review have separate queue rows because they begin after an initial determination. Compare a redetermination with the date that redetermination was requested. Compare a Center Director Review with the date that review was requested. Keep the original PWD filing date as background, but do not substitute it for the later review request date; doing so mixes different agency clocks and can make the queue gap look much larger than it is.

What the published month can and cannot tell you

When your applicable request date is earlier than the published queue month, the request may deserve a closer status check, but the comparison still cannot show whether DOL has opened it, whether additional review is occurring, or when a decision will arrive. When the request date is later, the published queue has not yet reached that month in the broad program view. Workloads, case complexity, data corrections, and uneven movement inside a month prevent this table from functioning as a personal countdown.

Connect PWD timing to the rest of the PERM process

PWD is only the first major timing segment. Recruitment normally follows the wage determination, and the PERM filing and review clocks begin later. Use the PERM Timeline to place the PWD request, recruitment steps, ETA-9089 filing, Analyst Review, possible Audit Review, and a potential I-140 filing in order. Review Data Sources and Methodology when you need the exact freshness rules, labels, calculation boundaries, disclosure-data filters, or reasons a historical result may be unavailable.

Repeat a PWD comparison after an official update

Use the same request stage, wage source, and controlling request date when comparing two official publications. Record each publication's official date and matching queue month before deciding what changed. A later PWD processing time queue can show movement in the program-level table, but it does not confirm activity on one request. If the request enters redetermination or Center Director Review, begin a separate comparison with that review's request date instead of carrying forward the initial-request gap.

A practical PWD processing time pre-check

Before relying on a PWD processing time comparison, collect four facts from the request record: the exact receipt date, the request stage, the wage source used for an initial request, and the date on the latest official DOL table. Use the receipt date shown on the filed or acknowledged request rather than the day drafting began, a recruitment date, or a later email date. If the request is in redetermination or Center Director Review, keep both the original receipt date and the later review-request date, then compare the later date with the matching review row. If any fact is uncertain, label the comparison incomplete instead of selecting the row that produces the shortest apparent wait.

Next, preserve the evidence behind the reading. Note whether the table says OEWS, Non-OEWS, redetermination, or Center Director Review; copy the official reporting date; and keep the source link with your private case records. When the site labels data stale or unavailable, confirm the current table directly before taking action. A queue month earlier than your request month usually means the broad workload marker has not reached that month. The same month means only that both dates share a calendar month. A queue month later than your request can justify checking the official status, but it does not prove that the request was skipped, lost, or ready for decision.

Finally, decide what question the evidence can answer. Current PWD processing time data can help with planning conversations, document follow-up, and the order of later PERM steps. Completed-request history can show how prior groups varied, but pending requests are absent from those distributions. Neither source reveals an adjudicator's activity, the number of requests ahead, an approval probability, or a personal completion date. Use the official FLAG status tools for case-specific information available to the filer or representative. Confirm response deadlines, procedural choices, and legal consequences from the actual notice and qualified counsel. Recheck the source after a new DOL publication, record what changed, and avoid treating one month's movement as a stable forecast.

A reproducible PWD processing time record

  1. Name the current PWD processing time request stage.
  2. Confirm the controlling PWD processing time request date.
  3. Separate initial PWD processing time from later review.
  4. Identify the initial PWD processing time wage source.
  5. Match PWD processing time to the exact FLAG row.
  6. Copy the PWD processing time receipt month exactly.
  7. Record the official PWD processing time source date.
  8. Record when the PWD processing time source was retrieved.
  9. Read the PWD processing time gap as calendar position.
  10. Keep PWD processing time counts separate from case status.
  11. Recheck PWD processing time when the source becomes stale.
  12. Never turn PWD processing time into a guaranteed date.
  13. Never infer PWD processing time from another wage-source row.
  14. Preserve corrected PWD processing time values as later observations.
  15. Compare PWD processing time only within the same stage.
  16. Keep PWD processing time correspondence with private records.
  17. Verify a PWD processing time deadline from the notice.
  18. Cite the official PWD processing time table when sharing.
  19. Label PWD processing time evidence as official or calculated.
  20. Keep PWD processing time history separate from current queues.
  21. Check the PWD processing time program scope before comparing.
  22. Use PWD processing time OEWS data only when applicable.
  23. Use PWD processing time non-OEWS data only when applicable.
  24. Anchor redetermination PWD processing time to its request date.
  25. Anchor Director Review PWD processing time to its request date.
  26. Treat PWD processing time remaining counts as aggregate context.
  27. Treat PWD processing time history as completed-request context.
  28. Do not use PWD processing time to infer approval probability.
  29. Do not use PWD processing time as a personal queue rank.
  30. Do not use PWD processing time as an agency deadline.
  31. Revisit PWD processing time after an official publication.
  32. Retain the prior PWD processing time source for comparison.
  33. Discuss case-specific PWD processing time concerns with the representative.
  34. Keep the PWD processing time limitation beside the result.

Completed PWD request history

Initial PWD processing time

Filters · 3 selected

Latest complete year· FY2025

150 days

20 days shorter than FY2024

119190 days

Half finished in this range

Over 202 days

Slower 10%

209,428

Completed cases studied

Six-year processing-time trend

The dot is the typical time, the band is the middle half, and the open circle marks the slower 10% threshold.

Typical timeMiddle halfSlower 10%
FY2026
134121
FY2025
202150
FY2024
194170
FY2023
218189
FY2022
210183
FY2021
161145
days
0100200300

Historical evidence · monthly

How processing time changed during FY2025

Monthly results show when the wait began to rise or ease.

Completed cases · Initial PWD processing time · All decisions

Typical completed time by month

  • Oct 2024183 daysHalf finished in this range: 177189 days
  • Nov 2024198 daysHalf finished in this range: 194200 days
  • Dec 2024199 daysHalf finished in this range: 197201 days
  • Jan 2025204 daysHalf finished in this range: 203207 days
  • Feb 2025190 daysHalf finished in this range: 183196 days
  • Mar 2025163 daysHalf finished in this range: 155170 days
  • Apr 2025143 daysHalf finished in this range: 138148 days
  • May 2025125 daysHalf finished in this range: 120131 days
  • Jun 2025118 daysHalf finished in this range: 118119 days
  • Jul 2025119 daysHalf finished in this range: 118122 days
  • Aug 2025112 daysHalf finished in this range: 109114 days
  • Sep 2025103 daysHalf finished in this range: 101105 days

More historical evidence

Evidence, sources & methodology

Official case records studied each year

Every available DOL year is included. Outlined bars are older records that support case counts but not processing-time calculations.

Current queue data comes from U.S. Department of Labor FLAG Processing Times. Historical completed-case data comes from official OFLC disclosure data. This independent website interprets the official data and is not affiliated with or endorsed by the U.S. Department of Labor.

How the numbers are built

PWD time runs from the initial DOL receipt date to the decision date for the selected request path. Annual and monthly percentiles are recalculated from exact processing-day histograms; stored medians are never averaged.

What these numbers cannot tell you

Public queue dates and completed-case history are program-level context. They are not pending inventory, cases ahead of an application, an approval probability, or a personal decision-date forecast.

Data quality funnel

Raw records

2,712,290

Valid durations

1,781,684

Used in statistics

1,775,593

Only completed PERM-class PWD records with usable receipt and decision dates are included. Small cohorts are omitted.