── ── Industry

CPA — Client Document Chase

Engagements rarely stall on technical difficulty. They stall on paperwork that never arrives, and then on follow-up that is polite, unstructured, and ignored.

Run CPA — Client Document Chase on a real problem

Bring something you're actually deciding — free, in the browser.

Run this on your problem →

How it works

1. Frame the engagement. Engagement type and year · entity types and jurisdictions · prior-year working papers available · hard deadline and whether extension exists · who actually holds the documents (often a bookkeeper or spouse, not the signer) · preferred channel and past response pattern · fee status. Mark anything unknown as UNKNOWN — an unknown here is itself a finding.

Gate: no prior-year file and no engagement letter → you are scoping, not chasing. Scope first.

2. Mine the prior year. Walk last year's return or working papers line by line: what document supported this, and do I have it yet? This finds what a generic checklist never will — the K-1 from a partnership the client forgot they hold, the state they moved out of mid-year.

When to use it

a tax or bookkeeping engagement is blocked on client paperwork
a client has gone quiet on a document request
drafting an initial PBC/document request
deciding whether to extend, deliver incomplete, or disengage
user says 'chase the client', 'missing documents', 'PBC list', 'client won't respond', 'what am I still waiting on?'

When not to use it

the documents are in hand and the question is technical treatment; the request is to prepare or review the return itself.

Worked example

CPA — Client Document Chase

Engagements rarely stall on technical difficulty. They stall on paperwork that never arrives, and then on follow-up that is polite, unstructured, and ignored.

Install this skill (free, MIT)

$npx skills add deciqAI/knowledge-skills

View CPA — Client Document Chase source on GitHub →

Useful? Star the repo — stars help other builders find it.