Consulting Practice
Bound client intake context
Discovery notes and prior proposals may contain other clients’ confidential information; a shared assistant must retrieve only the active engagement.
Context systems
Free Canadian small business workbook
Context Boundary Mapper
Decide what an AI system can see, retrieve, remember, and produce before live data is connected.
7 pages · PDF workbook · No email required
Preview the complete PDF All 7 pages · Free to explore
Scroll through the full workbook below. Download the PDF for selectable text, printing and your own working copy.
What’s inside
A working guide
for a real decision.
Decide what an AI system can see, retrieve, remember, and produce before live data is connected. Use this guide to make the operating choice explicit, test it with evidence, and record who owns the next decision.
Who this is for
Workflows that connect AI to documents, CRM records, inboxes, or internal knowledge.
Bring the people who own the work
Include the workflow owner, a person who performs the work, a reviewer with authority to approve or stop it, and the relevant data or tool owner.
Includes an explainer, working worksheet, three illustrative examples and practical considerations. This is a planning PDF, not prebuilt automation software.
Use it with your own work
Five questions
to work through.
Choose one workflow. Record enough context to support a decision, then use the worksheet to name the owner, evidence and next review.
Scope
What is in and out of scope for context boundary mapper?
Information
Which approved sources and permissions are required?
Authority
Who can review, approve, override, or stop this work?
Failure
What happens when evidence, quality, tools, or ownership fail?
Proof
What result would justify continuing or expanding?
Illustrative examples from the workbook
Where this becomes practical.
Independent Retailer
Separate store and customer records
A stock assistant needs product and supplier data, but must not absorb payment details or unrelated customer messages.
Accounting Practice
Protect matter-level records
A client summary tool must not mix files, staff notes, or permissions across engagements.
- AI-supported role
- Classify permitted source material and flag requests that cross a documented context boundary.
- Human authority
- The data owner approves access, checks exclusions, and signs off before live records are connected.
- What to measure
- Count unauthorized retrievals, missing-source flags, access corrections, and time to resolve exceptions.
Illustrative scenarios, not client results or a promise of performance. The workbook includes additional case-specific prompts.
A useful first step
Use the workbook.
Bring us the next question.
Download and use it without booking a call. If you want help applying it, email Chris with the workflow you’re considering and what you want to improve.
Discuss your workflowFurther reading in the library
General operational guidance only. These resources are not legal, privacy, cybersecurity or regulatory advice.