Issue Log — Definition & Commercial Strategy

Definition

An Issue Log is a dynamic repository used during the pre-sales and contracting phase to document, track, and assign accountability for project uncertainties, technical dependencies, or client-side bottlenecks. In B2B professional services, it transforms vague project risks into actionable line items that must be resolved or priced into the Statement of Work (SOW) before the contract is signed.

Explanation

Most B2B deals bleed margin because teams treat "unknowns" as "givens." When sales reps gloss over technical dependencies or client-side delays during the proposal phase, they aren't being optimistic—they are subsidizing the client’s project with their own margin.

An Issue Log is your primary weapon against "hope-based" pricing. It forces a collision between your delivery reality and the client’s expectations. By documenting every unresolved technical constraint or resource dependency, you remove the ambiguity that leads to scope creep. If an issue is identified but cannot be resolved before the SOW is locked, the Issue Log provides the audit trail required to create a "Risk Contingency" line item. Without this, you are effectively signing a blank check for your delivery team to honor, turning a profitable contract into a loss-leader within the first 30 days.

Examples (or Commercial Impact)

• Done Poorly: The proposal assumes "full API access" without verifying the client’s current infrastructure. Two weeks into the project, the delivery team discovers the legacy system is incompatible. You burn 100+ hours of engineering time on custom middleware—costing you $25k in margin—because you never logged the API dependency as a risk.
• Done Well: The Issue Log identifies "API Integration Complexity" as a high-risk item. You include a "Discovery Phase" in the SOW to audit the legacy system, and you price the implementation as a variable cost based on the audit findings. When the integration proves difficult, you have the contractual leverage to request a change order because the risk was identified, logged, and planned for during the proposal stage.

Commercial Checklist

1. Centralize the Log: Never rely on email threads. Use a shared Issue Log that is visible to both the pre-sales engineer and the account executive.
2. Assign Ownership: Every issue must have a status (Open, Pending, Resolved) and an owner (Client, Vendor, or Third-Party). If an issue sits with the "Client" for more than 48 hours, trigger an automated escalation.
3. Link to Pricing: If an issue is marked "High Impact," ensure that the financial model includes a contingency buffer (typically 10-15%) specifically tied to that risk.
4. The "Gatekeeper" Review: Before sending the final proposal, review the Issue Log. If an issue is still "Open," it must be explicitly mentioned in the SOW as an assumption or an exclusion.

Related Concepts

• [Margin Leakage](/glossary/margin-leakage)
• [Scope Creep](/glossary/scope-creep)
• [SOW (Statement of Work)](/glossary/sow)