HPD Builder governance that keeps you in control

Start with ownership, not logins

The HPD record is a long-lived disclosure that supports sales and specs. The account that owns an HPD should sit with the manufacturer. Consultants can help prepare or verify. Ownership is what survives staff changes, mergers, or vendor switches.

Memberships, tokens, and who pays

HPD Builder use is unlimited for HPDC members, with General membership at $2,500 and Affiliate at $995 per year, both including Builder access (HPDC Support, 2025). Non‑members can publish using a three HPD bundle pack (HPD Builder, 2025). Budgeting these items with the manufacturer prevents mid‑project stalls.

Why governance matters commercially

Over 14,000 HPDs are now published by almost 1,000 manufacturers, which signals buyers that disclosures are a market norm, not a novelty (HPDC Summer Newsletter, 2025). Repository additions average roughly 250 new HPDs each month, so competition does not wait (HPD Public Repository, 2025). Good goverance means products are discoverable faster.

Two ways to let outsiders help

Approved Preparers are consulting firms recognized by HPDC for HPD preparation expertise. They guide data entry, screening, and formatting to the Standard. Teams also use direct logins under the manufacturer’s account when a trusted service provider is doing day‑to‑day data work. Both models can be safe with the right guardrails.

Access pattern that works at scale

Set the manufacturer as account owner. Create named user access for internal staff and any external preparer. Use a single shared email only for the Owner of Record, controlled by IT. Keep publishing rights with a product or sustainability lead. Store credentials in an enterprise password manager and rotate on vendor off‑boarding.

Boundaries for preparers and verifiers

Preparers can draft content, upload evidence, and run hazard screening. A manufacturer reviewer approves content, checks claims against BOM and SDS, and presses publish. Third‑party verifiers, when engaged, review the finished HPD. This separation reduces errors and shortens rework time.

When experience criteria are still in progress

If a consultant has not yet met HPDC’s experience expectations to be an Approved Preparer, use direct login with tight boundaries. Limit what can be changed without review. Require a change log in the project workspace. Make hand‑off back to the manufacturer part of the statement of work.

Hand‑back plan from day one

Write down who owns the Builder account, who pays membership or bundles, who can publish, and how to reclaim access if people leave. Add a checklist for closeout that includes credential rotation, document storage, and naming conventions so the next HPD version is faster.

Common pitfalls and quick fixes

• Consultant holds the only login. Fix by assigning a manufacturer owner account and adding consultants as named users.
• Tokens bought by a vendor. Fix by purchasing through the manufacturer and granting access.
• No audit trail of edits. Fix by keeping a change log and storing source files with version dates.

The real speed move

Publishing quickly is not about clicking faster. It is about clear roles, predictable reviews, and ownership that never drifts. Set the structure once, then let experts do the heavy lifting while the manufacturer keeps the keys.