SECURITY & DELIVERY
Security belongs
in the working plan.
Before company information is connected, agree where it goes, who can access it and how results will be checked.
Controls, providers, hosting arrangements and support terms are agreed per engagement.
Identity & source permissions
Map user identity, source access and client boundaries. Agree how permission changes and departures propagate to the system.
Evidence to review: Role-based access tests, including restricted records, changed permissions and denied-access cases.
Providers & data handling
Record what content reaches each provider, where it is processed and stored, and which contractual terms apply. Review model-training use, subprocessors and encryption requirements for the selected services.
Evidence to review: An agreed data-flow diagram, provider list and handling requirements before connecting project data.
Retention, deletion & logs
Define retention separately for source copies, indexes, prompts, outputs, logs and backups. Identify who can inspect or export audit records and how deletion requests are handled.
Evidence to review: Documented retention settings, deletion checks and logging access appropriate to the chosen architecture.
Source freshness & conflicts
Choose authoritative records, refresh expectations and rules for duplicates or conflicting versions. Agree how the experience flags stale information, missing sources and failed connections.
Evidence to review: Checks for updates, deletions, conflicting records and connector failures, with a named maintenance owner.
Answer quality & consistency
Build an evaluation set from representative tasks, difficult questions and known gaps. Check source support, completeness, uncertainty and changes in answers across repeated runs.
Evidence to review: An acceptance record showing results, exceptions, corrections and the business reviewer’s decision.
Latency & operating cost
Agree response-time targets for the workflow and test typical and slower requests under representative load. Separate machine response time from employee checking and correction time.
Evidence to review: Measured response-time distribution, usage assumptions, operating cost estimate and failure behavior.
Human review & approved actions
Define what employees may rely on, when they must inspect sources and which outputs need approval. Any write-back, external message or consequential action requires a separately agreed control path.
Evidence to review: Review instructions, escalation cases and approval tests matched to the actual workflow.
Handover & support ownership
Identify owners for access, content quality, provider changes, incidents and employee help. Agree support scope, escalation channels and response commitments in the engagement.
Evidence to review: An operating runbook, owner list, handover session and agreed support terms before the team takes over.
ONE USEFUL STARTING POINT
What could your team do
with more time?
Bring one process. We’ll explore where AI and automation can help.