NFPA 660 deadline and DHA revalidation tracker

Track the prior DHA completion date and the standard edition used, then calculate the applicable periodic review checkpoint. Alongside that date, keep a live screen for material, process, equipment, throughput, dust collection, building, procedure, or safeguard changes. A date-only register misses the changes that can make an analysis stale before the calendar checkpoint.

If there is no prior DHA, the planning question is not “when does the old report expire?” It is how to establish scope and complete the first defensible analysis for the affected processes.

OSHA jurisdiction differs between federal states, full State Plans, and public-sector-only State Plans. Fire-code adoption can also differ by locality. The tracker uses state information as routing context; it does not infer a local code edition or an enforcement decision without a current primary-source record for the exact authority.

Confirm the responsible OSHA or State Plan office, local fire marshal or authority having jurisdiction, permit conditions, insurer requirements, and contractual commitments before treating a planning date as mandatory.

First validate the inputs: prior report date and scope, materials, process changes, current equipment, and standard edition. Assemble drawings, dust-collection information, representative test records, prior findings, closure evidence, and management-of-change records. Ask a qualified reviewer to define the missing work.

The optional RFQ uses the same facility profile so a provider can respond to a structured scope. DustDHA shares a qualified request with no more than three matched firms and does not perform or certify the engineering work.

No single date on this site can establish every facility's legal deadline. NFPA publishes a consensus standard, while a site's obligations can also involve adopted codes, an authority having jurisdiction, OSHA or a State Plan, permits, insurer conditions, and contracts. Those paths differ by jurisdiction and facility. DustDHA therefore avoids the unsupported claim that every U.S. facility became enforceable on one date.

The tracker answers a narrower planning question. It records whether a prior DHA exists, calculates a visible periodic-review checkpoint from the entered year, identifies the selected state's OSHA jurisdiction context, and highlights earlier changes that may make the existing analysis stale. The result tells the user what to verify next; it is not a legal deadline notice or a finding that a site complies.

Where the five-year cycle is the appropriate planning baseline, the arithmetic is the prior DHA completion year plus five. The result is only as reliable as the input: a cover date does not prove which processes were included, whether recommendations were closed, or whether later changes were evaluated. The tracker displays the entered year and resulting checkpoint so the assumption is visible rather than hidden in a score.

Before using the date for scheduling, verify the actual completion or approval date, edition and scope of the old analysis, current NFPA 660 requirements, and any applicable authority or contractual requirement. A report already outside the planning interval deserves prompt review, but an apparently future checkpoint does not override a material change, incident, invalidated test, or omitted process.

A change can make an earlier review appropriate when it affects a fact or safeguard on which the analysis relied. Examples include a different particulate or formulation, finer material, recycled content, changed moisture, higher throughput, new or relocated equipment, collector or duct modifications, altered ventilation, building changes, revised controls, or a different operating or cleaning practice. Incidents, near misses, inspections, and new test results can also expose an assumption that needs attention.

Use a change register to connect the event with the relevant DHA section, affected equipment and material, reviewer, evidence considered, and decision. That approach avoids both extremes: ignoring a meaningful change until the calendar turns, or commissioning a full revalidation for every routine replacement without examining equivalence.

The state field identifies whether private-sector workplace safety is generally under federal OSHA or an OSHA-approved State Plan, using OSHA's current public State Plan source. Some plans cover private and public workers; others cover only state and local government workers. The label helps route the next jurisdiction question but does not resolve local fire-code adoption, permit conditions, or a particular inspection decision.

A facility should record the responsible OSHA or State Plan office and separately identify the local fire marshal or other authority having jurisdiction. Check current official sources for the exact location and facility type. DustDHA does not infer missing fire-code data or present a statewide label as a complete legal map, because local adoption and amendments can change the answer.

A useful register links the date to the analysis it represents. Include the report title and revision, completion and approval dates, covered buildings and processes, material set, standard edition, open recommendations, last change screen, responsible owner, planned review lead time, and evidence location. Add fields for incidents, inspections, material changes, and projects that could trigger an earlier review.

The owner should be able to explain why the record remains current, not merely point to a future year. Schedule procurement early enough for document collection, provider selection, site access, testing, workshops, draft review, and decisions. The tracker cannot estimate that full project schedule from six answers, so the on-screen result is the start of planning rather than a promised completion date.

Treat missing evidence as an unresolved scope question, not as proof that no work was ever done. Search controlled document systems, engineering archives, insurer files, project records, and predecessor reports. Interview long-tenured staff carefully, but distinguish recollection from a retrievable analysis. Create an inventory of affected materials, areas, and systems while the record search continues.

If a complete applicable DHA cannot be established, ask a qualified provider to define the initial analysis scope and immediate information needs. Do not invent a historical date to make the tracker produce a status. The tool supports an explicit no-prior-DHA path so the facility can preserve uncertainty and move toward a defensible first analysis.

Work backward from the facility's verified need date rather than from an assumed universal deadline. Allow time for comparable proposals, confidentiality steps, records collection, fieldwork, representative sampling and laboratory work if required, analysis workshops, draft review, and resolution of factual comments. Site outages, seasonal production, travel, and access constraints can affect the plan.

Ask providers for dependencies and the difference between start date, field visit, draft delivery, and final issue. A fast proposal is not the same as a complete project schedule. If a deadline is near or uncertain, document interim responsibilities with qualified advisers instead of treating an RFQ submission as risk control. DustDHA routes introductions; it does not reserve provider capacity or manage the engineering schedule.

Keep the snapshot with the inputs and source date that produced it: industry selection, dust status, prior-DHA answer and year, state, facility size band, and user role. Add the supporting report, scope, current standard source, jurisdiction checks, and change register outside the tool. If an input changes, generate a new snapshot rather than silently editing the old conclusion.

The emailed PDF is a convenience copy of planning information and carries the same limitations as the on-screen result. It is not a signed engineering document, an inspection record, or proof of compliance. Its value is traceability: it helps the facility and prospective provider see the same initial facts and the same unresolved questions.

The right reviewers depend on the decision. Operations and maintenance can verify how the process runs; engineering can verify equipment and drawings; EHS can coordinate records, procedures, incidents, and jurisdiction questions; management can assign resources; and qualified external specialists can define or perform technical analysis. Legal counsel or the authority having jurisdiction may be needed for a legal interpretation.

Give reviewers the inputs and source links, not only the status label. Ask which assumptions are confirmed, which need evidence, and which changes affect timing. Record the decision owner and next action. The tracker deliberately avoids naming a facility safe, unsafe, compliant, or noncompliant because those conclusions require evidence and professional judgment beyond its inputs.