The pricing PDF that should not have shipped

The wrong price is a symptom. The root causes are: no single source of truth, approvals conducted in email, ambiguous version names, no publish gate, broad write access, and no metadata linking an asset to its source and expiry. Eleven versions and three “final” labels mean the team cannot prove which file is current.

Design a linear workflow with gates:

1. Intake and draft. A brief states audience, channel, owner, and price or claim sources. The draft lives in one system, not as an email attachment. Every version gets a version number and date, never “final.”
2. Product review. Confirms the offer, price, and roadmap claims. Product approval is required whenever the asset contains a price, package, or availability claim.
3. Design and accessibility review. Checks brand, layout, alt text, tagged PDF, captions, and contrast.
4. Legal review. Confirms claims, disclaimers, and rights. For pricing assets, legal sign-off is mandatory and cannot be skipped because of deadline pressure.
5. Publish gate. A named publisher checks the approved version, channel, date, and expiry, then publishes. Freelancers can upload drafts but cannot publish.

Evidence: each gate records approver, timestamp, version, and comments. The published asset links to its approval record. If the price changes, the asset is unpublished or replaced, not left live. The publisher also sets a review date so outdated files expire.

Start with required capabilities, then map roles. The system needs version history, approval states, comments, role-based permissions, audit logs, metadata, expiring external links, and export controls. It should integrate with the team’s chat and project tools so approvals happen where people work, not in a separate inbox.

Role model:

• Staff owners: create, edit, submit for review, and view audit history for their assets.
• Approvers: product, legal, design, and accessibility reviewers can approve or reject at their gate but cannot publish unless separately authorized.
• Publisher: one or two staff can move an approved asset to live channels.
• Freelancers: upload-only access to a draft folder, with no publish rights and no access to legal or unpublished pricing files beyond their assignment. Use expiring links and watermarks for review copies.
• Sales: read-only access to the current published library, with old versions archived and clearly marked.

Criteria for the tool: SSO, granular permissions, version comparison, approval audit trail, metadata fields for price source and expiry, accessible PDF export, and a way to revoke external links. Avoid buying a heavy system if the team will not maintain metadata. A small pilot with one pricing asset and one case study will reveal whether the workflow is usable before a company-wide rollout.

First hour:

1. Unpublish or replace the post and the landing-page asset. If the platform does not allow a clean replacement, take the post down and publish a corrected version with a visible note if the error was material.
2. Preserve the evidence before deleting anything: the published file, URL, timestamp, screenshot, approval thread, and the version that was published.
3. Notify legal, sales, and the publisher. Give sales a short internal note with the correct price and what to say if a lead asks; do not let representatives improvise.
4. Contact the 14 inbound leads only if they may have acted on the wrong price. A brief correction is better than a silent error that becomes a contract dispute.
5. Check whether the same file was used on other channels and expire or replace those copies.

Log: who published, which version, which approval record was attached, when the asset went live, when it was removed, who was notified, and what correction was issued. Preserve the audit trail rather than editing it. Then run a short incident review: was the failure a missing gate, a permissions gap, an outdated source file, or deadline pressure? The fix should address that cause, not just add another email approval.