Assessment Protocols & Intake Strategy

Situation: A new client, Jamie, has just completed the ESQ-R self-report. Their scores show significant deficits in Task Initiation and Time Management, but relatively strong Working Memory. During the intake call, Jamie says: "I know exactly what I need to do — I just can't make myself start."

What is your priority as the intake coach?

Strong intake move.

Asking for a specific recent example grounds the conversation in observable behavior rather than abstract patterns. This is consistent with the Goodness of Fit principle — you're collecting concrete, context-specific data before making coaching decisions.

Jamie describes: "Last Tuesday I had a work report due. I sat at my desk for 90 minutes, reorganized my desktop, made coffee twice — never typed a word."

What do you do next?

Excellent. Context-fit assessment in action.

Probing environment, time-of-day, and competing stimuli gives you the data needed to design a context-specific initiation protocol — not a generic to-do list. Jamie's strong Working Memory means the plan can be more complex; the initiation barrier is the leverage point.

Outcome: You identify that Jamie performs best in a cleared workspace in the morning. You design a two-step "desk clear + timer on" startup protocol. Jamie reports success 4 of 5 days in week one.

Scenario complete. Key takeaway: specific behavioral examples + context probing = interventions that actually transfer.

Partial miss — context skipped.

"Break it into smaller steps" is generic advice that ignores the context data you just collected. Jamie knows how to do the report; the barrier is initiation, not task complexity. Generic advice here risks the knowledge–performance trap: Jamie will understand the strategy but not apply it because the environmental triggers aren't addressed.

Outcome: Jamie tries breaking the report into steps, gets stuck on the first item, and emails you two days later saying "the strategy didn't work." You've now lost trust and will need to re-intake.

Useful but premature.

Psychoeducation about the knowledge–performance gap is valuable — but offering it before collecting behavioral data puts the theory before the evidence. You don't yet know which specific contexts trigger Jamie's initiation failures, so the explanation has no anchor to Jamie's actual experience.

Better approach: collect the specific example first (Choice A), then introduce the framing once you have concrete behavior to attach it to.

Scope and priority risk.

Exploring developmental history can be contextually useful — but as a first move in intake it signals a clinical/therapeutic orientation that is outside EF coaching scope. EF coaches focus on current functional patterns and forward-looking behavior change, not developmental etiology. Starting here delays the functional assessment and may confuse the coaching role.

Reserve developmental history questions for cases where there is a clear functional reason to ask — and frame them in terms of current patterns, not root causes.