Client Red Flag Checklist
Spot project risks before saying yes.
Spot bad-fit clients before you commit
The most expensive projects are the ones you should have declined. This checklist helps you surface the warning signs early — unclear scope, unrealistic timelines, payment hesitancy, disrespect for your process — before you say yes and get stuck.
Running a quick check turns a vague uneasy feeling into concrete, discussable points, which makes it easier to set boundaries, adjust terms, or walk away with a clear reason. Protecting your time upfront is cheaper than escaping a bad engagement later.
Spotting trouble early
Vague scope, rushed timelines, and haggling before value are cheapest to catch before you sign, not after. The checklist runs locally and nothing you note is uploaded.
Frequently asked questions
What red flags does it check?
Seven fit questions: whether the budget matches the outcome, the decision maker is involved, the timeline matches the scope, the feedback process is clear, past vendor problems are explained fairly, payment terms are acceptable, and communication feels workable.
What do the two short fields and the notes box do?
Enter the project type (for example "website redesign") and how the lead came in (such as "referral"). Put anything that worried you on the call in the notes box, one per line; it is listed under the checklist.
What should I do with a failed item?
Raise it before signing: a deposit for payment concerns, a written scope for timeline issues, or a named approver for feedback problems. If a flag cannot be fixed, it is a reason to decline.
Related tools
Free private browser tools for practical work.