Washington Construction Project Database | L&I Records

Washington Construction Project Data: How to Read L&I Records

Washington Labor & Industries publishes Intent Project Details records. It can be useful Washington construction project data for a supplier, subcontractor, or project team that already knows a prime company, awarding agency, or project ID. It is not evidence that a project is open for bidding, that a subcontract is available, that a business needs materials, or that a named person is an appropriate contact.

The usable research question is deliberately narrow: what did the official publisher retain for this specific public-works identity, and is the source context sufficient for the team's own independent research?

This Washington public-works filing research guide keeps that source boundary explicit: a filed record is useful for verifying a known research file, not for asserting a current opportunity.

Source receipt and review method — August 30, 2026

This guide was reviewed against the official Washington Labor & Industries Intent Project Details dataset, not a copied directory. The review checked the publisher label, the available role and date fields, and a bounded count/date query. At that review, the latest retained filing-received date was August 29, 2026; the publisher returned 239 filings received from August 28 through August 29. That observation is a dated source receipt for this guide—not a guarantee of future posting cadence, current project status, statewide completeness, or a service-level commitment.

PermitGrab's accompanying record check accepts one exact published prime-company name, awarding-agency name, or project ID and returns no more than 20 source rows for an active research account. It withholds obvious publisher date-format outliers rather than converting a malformed value into a project-timing claim. The method is intentionally small enough to audit: use the official dataset link, retain the publisher's role labels, and verify a consequential procurement question through the awarding agency.

What a construction project database can—and cannot—answer

The official L&I dataset identifies itself as Intent Project Details and, at the time of review, its publisher metadata describes a daily posting frequency. The public fields include a project or filing ID, awarding-agency label, prime-company label, project name, city, and several publisher-supplied date and amount fields. Those fields can make a known research file easier to verify against the official source.

They do not turn the source into a live bid board. The publisher may retain historical, amended, incomplete, or unusually dated rows; a field labelled “expected start” is still only the date the publisher retained for that field. For a current procurement or project-status question, use the relevant awarding agency’s own official process and project documents.

Start with one known identity

Use an exact prime-company name, awarding-agency name, or published project ID that your team already has. This keeps the workflow tied to a real research file rather than turning a public dataset into an unrestricted prospect directory.

The Washington public-works project research page explains the product boundary and links to the official L&I Intent Project Details dataset. PermitGrab's selected-record view is intentionally limited to one exact source identity at a time; it does not offer agency contacts, phone numbers, email, or an unrestricted directory.

Preserve the publisher's role labels

A public-works filing can name more than one organization. Those labels have to remain distinct:

Do not rewrite a source label to fit a sales workflow. If the source calls a party the filing company, retain that wording. If a field is blank, the correct answer is unavailable—not an inferred role from another database.

Read dates and amounts as published context

L&I filing-received, award, and expected-start dates can help a team understand how the publisher describes the filing. They do not prove a project's current schedule, active construction stage, procurement window, or purchase timing. Amounts, where published, are source fields—not a materials budget, contracted value, or forecast.

Before escalating a record for research, note:

1. The publisher and the exact identifier used to find the record.
2. The role labels shown by the publisher.
3. Which date field the team is reading and what that field represents.
4. Whether the record contains project location or scope text that is actually relevant to the team's territory.
5. The date the team reviewed the public source.

This creates a reviewable file without pretending that a historical filing answers a current procurement question.

Use the public record to decide whether more verification is warranted

A filing may justify additional work within a team's normal process: review the agency's procurement channel, confirm a project's current status, compare the named organization against an existing account, or decide that the record is too old or too sparse to pursue.

That is different from treating the row as a bid lead. Public filing data does not replace plans, addenda, a bidder list, qualification requirements, contract documents, procurement notices, or a team's own relationship and compliance checks.

For a team that needs an exact source view, open the selected Washington filing research tool. It remains a selected-record workflow by design; it does not make a general claim about statewide coverage, available opportunities, or delivery.

A five-step source-check workflow

1. Name the exact research question. Start with the agency, prime company, or project ID already in the team's file.
2. Open the official source context. Confirm that the record is from L&I's Intent Project Details dataset and retain the source date.
3. Keep roles and dates intact. Do not turn a publisher label into a decision-maker label or a date into a construction-status claim.
4. Verify through the appropriate official channel. Use the awarding agency's procurement process and normal qualification work for any current opportunity question.
5. Record the outcome. Mark whether the filed public information was sufficient for independent research, incomplete, historical, or outside the team's territory.

The benefit is modest but real: a team can reject unsupported assumptions early and spend its research time on the small number of public records whose source, role labels, and dates actually fit the question it is trying to answer.