When a client-workflow problem is visible but its cause is unclear, this checklist sorts it into a category and points to a first resource. It is a routing aid, not a validated diagnostic instrument. Base the result on current project records rather than memory or a numerical score.
If you already know the specific symptom, use the Problem-to-page guide instead. If the entire lifecycle is unclear, read Freelance client workflow system: inquiry to final payment before classifying one part.
Record the observed problem
Write down:
- the project stage where the issue appears;
- the input, decision, or event that should move the stage;
- the person who owns the next action;
- the record that shows current status;
- the effect on delivery, approval, billing, or closeout.
Use the applicable agreement or project authorization when the issue concerns start conditions, approval, billing, payment, or closure.
Match the evidence to a category
| Category | Choose it when the current record shows | First resource |
|---|---|---|
| Workflow sequence | Stages happen out of order, a handoff lacks an entry or exit condition, or work starts without the authorization required for that project | Freelance client workflow system |
| Approval or delivery | The approval owner, review state, acceptance evidence, or route for conflicting feedback is missing | FAQ: what counts as client approval? |
| Billing or payment status | The agreement’s invoice trigger is unclear, payment status has no authoritative record, or follow-up relies on memory | Invoice and payment workflow setup |
| Tool or system of record | Two records conflict, ownership between tools is unclear, or current client status requires checking several places | CRM vs project management for client workflows |
| Execution consistency | The rule is defined, but comparable projects use different checklists, records, or messages at the same trigger | Workflow starter pack |
| Narrow question | The surrounding workflow is clear and one term or bounded situation blocks the next action | Problem-to-page guide |
Check the candidate category
Before choosing a category, confirm each statement that applies:
- The issue appears in a current record, not only in a general impression.
- The category names the earliest missing input, owner, decision, or transition you can identify.
- Correcting that item would affect the later symptoms you observed.
- The issue is not better explained by an obligation or trigger in the applicable agreement.
If two categories remain plausible, do not use table order as a tie-breaker. Inspect the earlier lifecycle stage and choose only when the record supports it. If the evidence still does not separate them, use the Client workflow health check to compare the areas without assigning a score.
Pause software evaluation when the rule is missing
Clarify the process before comparing software when:
- the stage sequence is unclear;
- the approval owner is unnamed;
- billing is not tied to the event stated in the agreement;
- the record does not show what changes when a deal closes;
- the system center is still disputed.
Continue from the result
- After a clear category, open its first resource and correct the missing rule or record.
- After an unclear result, gather the missing project evidence or compare the workflow areas with the Client workflow health check.
- After the rule is corrected, choose a matching template or checklist from Templates and checklists.
Record the category, the evidence that supports it, the next action, and the action owner. Revisit the classification if new evidence changes the earliest identified failure point.
