Plan the retrieval across agreed sources
Produces a concrete retrieval checklist mapping each agreed input to its source location, pull order, and target filename before any downloading begins.
In / outAgreed input list + source access details → retrieval checklist (item, source location, pull order, working filename)
You might say…
“I used to just start downloading things — then I'd find I'd grabbed the wrong version from the wrong folder and had to start over.”
What it does
Given the engagement's agreed input list and the sources the client has granted access to, produce a concrete retrieval checklist: which files/exports/responses to pull from which location, in what order, and what each will be named in the working location. Used at the start of gathering, before any downloading begins, to make the consolidation systematic rather than ad hoc.
Trigger: Use when you have a confirmed input list and source access, before touching any client file or system.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation