Skip to content

Client Risk Scan

Use this page when the project already has multiple warning signals and you need a structured proceed / caution / stop decision before commitment.

This is not a sales page.

It is a lightweight decision frame for identifying whether the current project setup is stable enough to continue.

When to Use This Scan

Use this scan if:

  • the brief is still vague
  • pricing is being discussed before scope is defined
  • several stakeholders are already involved
  • urgency is being used to compress clarification
  • deposit or commitment signals are weak
  • revision expectations are already expanding

Core Inputs to Collect

A first version of the scan should collect:

  • project type
  • pricing model
  • brief clarity
  • scope definition
  • stakeholder count
  • decision-maker clarity
  • timeline pressure
  • deposit or upfront commitment
  • revision expectation
  • requirement stability
  • asset readiness
  • communication quality
  • special risk notes

Suggested Field Structure

Project Setup

  • What kind of project is this?
  • Is pricing fixed price, hourly, or milestone-based?
  • Is the brief clear, partial, or vague?

Scope and Stability

  • Is the scope defined, partially defined, or undefined?
  • Are requests stable, changing, or contradictory?
  • Are revision expectations bounded or already open-ended?

People and Authority

  • How many stakeholders are involved?
  • Is one decision-maker clearly identified?
  • Is feedback consolidated or fragmented?

Commitment Signals

  • Is there a deposit or equivalent commitment signal?
  • Is the timeline normal, urgent, or unrealistic?
  • Are the required assets ready?

Communication Quality

  • Are answers consistent?
  • Are critical questions answered directly?
  • Are major decisions being postponed while pressure to commit increases?

Output Logic

The scan should return:

  • Proceed
  • risk exists but is currently bounded
  • Proceed with constraints
  • only continue if scope, authority, payment, or revision boundaries are tightened first
  • Do not proceed under current terms
  • too many failure-path indicators are already active

Primary Failure Paths to Flag

A first version should identify the most likely dominant path:

  • vague scope -> fixed price loss
  • too many stakeholders -> approval drift
  • weak commitment -> unpaid discovery and churn
  • urgency plus ambiguity -> rushed commitment and rework
  • unlimited revisions -> open-ended scope creep

What Not to Do Next

Do not use the scan as permission to ignore obvious risk.

If the same red flags remain after the scan, the correct answer may still be to pause or decline.

Next Step

  • Return to Client Risk Precheck if you need to step back to the broader risk cluster.
  • Start with the Checklist if you still need a simpler review.
  • Move into the problem pages if one warning pattern is clearly dominating the risk.