Dust hazard analysis cost: a sourced, itemized planning guide

A dust hazard analysis is not one standardized parcel of labor. One proposal may cover a documented process in one building; another may cover several materials, interconnected systems, missing drawings, new testing, workshops, calculations, and a detailed action register. Calling both projects a “DHA” does not make their scope equivalent.

The published vendor span is retained as a dated market anchor, not promoted as survey truth. Buyers should use it to ask better scope questions rather than to force every proposal inside a universal number.

List buildings and process areas, process units, materials and operating states, collection systems, current records, prior analyses, required field time, sample and test assumptions, workshops, calculations, draft review, final deliverable, travel, and optional implementation work. Ask each bidder to mark included, excluded, conditional, or owner-supplied.

A comparable matrix exposes whether a commercial difference comes from price, technical team, effort, missing inputs, or a different deliverable. The lowest total and the broadest scope both need evidence.

The linked $9,000–$85,000 overall span is a vendor-published source claim. The calculator's base, per-process, per-sample, per-collector, and travel amounts are explicit DustDHA model assumptions. NFPA, OSHA, or laboratory context links do not turn those allowances into published fees.

The result displays that distinction beside every line. It is a budgeting aid and scope prompt, not a quote, appraisal, or claim about what a particular provider must charge.

The public market anchor used here is a vendor-published span of $9,000 to $85,000, verified from its source on July 21, 2026. It supports one narrow statement: that the vendor publicly described a broad overall range. It does not prove an industry average, a guaranteed minimum or maximum, a price for a particular facility, or independent survey data. DustDHA labels the source as a vendor source for that reason.

The range is useful because it exposes how misleading a single universal price would be. The calculator uses explicit DustDHA model allowances to explore scope; those allowances are assumptions, not prices extracted from NFPA, OSHA, a laboratory, or a provider rate sheet. A real proposal must replace the model once a provider has reviewed the site and deliverable.

Proposal totals can reflect different numbers of buildings, rooms, processes, materials, operating modes, collectors, connected systems, and scenarios. They can also include different amounts of document reconstruction, field time, staff workshops, sampling, laboratory work, calculations, draft review, travel, and implementation engineering. Even reports with similar titles can therefore describe unlike deliverables.

Build a scope matrix before comparing price. For every proposal, mark each area and activity included, excluded, optional, or owner-supplied. Ask what happens if drawings are stale, tests are not representative, or an additional material is found. This converts price comparison from guesswork into a review of equivalent work.

Current process descriptions, drawings, equipment information, material evidence, prior DHAs, closure records, and change history can reduce the unknowns a provider must price. Missing records can require field verification, document development, additional interviews, or assumptions. Old records still have value when their date and facility condition are clear; unlabeled or contradictory records create review work.

Give bidders an indexed document list rather than a claim that records are complete. Let them identify gaps and state who is responsible for resolving each one. Better information can improve proposal comparability and project control, but DustDHA does not promise that it will lower the fee.

Testing should answer a defined engineering or hazard-information question. The project team may need to establish whether existing data represents the material as processed, identify characteristics relevant to hazard analysis or protection design, or resolve a changed material condition. The exact tests, samples, preparation, and laboratory scope should be defined by qualified people.

Ask proposals to separate laboratory charges, sampling or preparation, shipping, consultant coordination, interpretation, and possible retesting. A menu of tests is not itself a justified program. DustDHA's calculator includes a labeled per-sample planning allowance so the input is visible, but it does not claim that allowance is a published lab price.

Request the number and purpose of site days, assumed team size, travel-time treatment, reimbursable policy, mileage or airfare treatment, lodging assumptions, and conditions for an additional visit. Clarify whether production must run, equipment must be opened, or shutdown access is needed. Remote document review and workshops may reduce some travel but cannot automatically replace field verification.

The calculator's travel line is a planning assumption, not a provider policy. Obtain actual written terms. Compare the field outcome promised, not only the trip cost: a lower travel amount paired with insufficient access can create later scope changes or a weaker evidence record.

A project may end with a high-level screening record, an equipment-focused review, a site-wide DHA, a revalidation, a standards crosswalk, or a package that also includes calculations and corrective-action design. Draft workshops, recommendation detail, drawing markups, action registers, executive summaries, and implementation support add different work. Define what technical decisions the deliverable must support.

Ask who reviews and approves it, how factual comments are handled, what files are delivered, and whether future revisions are included. A low price for an undefined report is not necessarily economical. A higher price is not evidence of quality. Scope and team evidence must explain the difference.

Separate the base scope from conditional work. Examples include additional process areas, new materials, laboratory testing, drawing development, protection-system calculations, implementation design, extra site visits, expedited work, and travel changes. Each option should identify its trigger, price basis or quotation process, schedule effect, and approval authority.

Avoid a large unexplained contingency that obscures what is included, but also avoid assuming every unknown can be priced exactly before records and field conditions are reviewed. A written change process lets the facility control additions and preserves an audit trail. DustDHA's planning output should be attached as context, never represented as a cap the provider must fit.

Use the result to inspect sensitivity and prepare questions. Save the chosen facility size band, process-unit count, sample count, collection-system count, travel choice, model method, source anchor, and verification date. If the total moves sharply when one input changes, verify that count and ask providers how they scope the same item.

Do not enter fewer units to force a preferred budget or present the output as a competitive quote. Send the same factual scope to up to three providers and compare their inclusions, assumptions, team, schedule, and terms. Once real proposals arrive, archive the model as planning history and use the validated proposal scope for decisions.

Present the business need, facility and process boundary, known evidence gaps, requested deliverable, timing, model inputs, published source anchor, and uncertainty. Separate the initial analysis budget from possible testing, design, equipment, or corrective-action implementation. State that competitive provider scopes will replace the planning assumptions.

This gives approvers a decision record without pretending the calculator is a quotation. If funding must be staged, identify which early work defines the remaining scope and who will approve later phases. Do not use an arbitrary low figure that cannot support the requested deliverable or a broad contingency with no trigger.