Current and future workflow
The starting event, principal steps, handovers, decisions, exceptions and completion event—both now and in the proposed AI-assisted process.
Design the AI-assisted workflow before asking somebody to build it
The AI Integration Blueprint defines how AI, deterministic software and people should work together in one sufficiently understood operational workflow.
It creates a practical basis for internal approval, supplier briefing, quotation, prototype planning and staged implementation.
Introductory project fee: £295
Delivery: ten calendar days after complete requirements and
discovery scheduling
The decision this service supports
The Blueprint is designed for organisations asking:
- How should this AI-assisted process actually operate?
- Where should AI, deterministic rules and people each be used?
- What information and systems must interact?
- What may the system propose, change or record?
- Where is human approval required?
- What should happen when information conflicts or the AI service fails?
- What should a developer or supplier be asked to build and prove?
The workflow must be sufficiently understood to design. If the opportunity or readiness is still uncertain, begin with the Readiness Assessment.
What the Blueprint defines
Information and operational truth
The origin, status and authority of important information; what remains evidence, what is proposed, what is verified and where the approved outcome is recorded.
AI, software and human responsibilities
Activities are separated deliberately:
- AI may classify, extract, retrieve, compare, summarise, draft or flag uncertainty where evidence supports it;
- deterministic software should validate rules, create records, enforce permissions and preserve status;
- people retain authority for consequential judgement, exception resolution and commitments.
Integration and control
The systems and interfaces involved, the actions that create operational consequences, approval, audit, durable records, security assumptions and permission boundaries.
Failure, fallback and recovery
What happens when data is missing, systems disagree, the AI is uncertain, an interface fails or a person rejects the proposed output.
Implementation and acceptance
A proportionate staged route—normally preparation, shadow-mode evaluation, human-approved pilot and controlled integration—with measures and acceptance conditions.
What you receive
Your AI Integration Blueprint normally includes:
- executive summary;
- business objective and scope;
- current-state workflow;
- current problems and opportunities;
- information and source-of-truth model;
- decisions, judgement and exceptions;
- proposed AI-assisted workflow;
- AI, deterministic and human responsibilities;
- systems and integration points;
- authority, approval and audit requirements;
- failure, fallback and recovery;
- risks and prerequisites;
- staged implementation plan;
- success measures and acceptance criteria;
- recommended next actions.
Supporting diagrams may include current-state and future-state workflows, system interactions and human approval or exception paths.
Included in the introductory package
- one defined workflow and one principal business function;
- structured discovery questionnaire;
- review of up to ten relevant supplied artefacts;
- up to 90 minutes of structured discussion, normally divided into no more than two sessions;
- current-state and future-state workflow design;
- high-level information and integration architecture;
- human authority, exception and failure controls;
- staged implementation and acceptance measures;
- professional AI Integration Blueprint;
- one revision for factual correction or agreed clarification;
- one post-delivery clarification response.
The Blueprint considers adjacent systems and foreseeable future needs far enough to avoid obvious technology or data dead ends. It does not silently expand into a multi-workflow architecture or organisation-wide transformation plan.
Solution-level design—not disguised development
The Blueprint is specific enough to explain what should happen, where AI is involved, what information it uses, where people remain responsible, which systems interact, what is recorded and how implementation should be staged.
It does not normally include database definitions, detailed API schemas, production infrastructure, code-level specifications, deployment, vendor configuration, penetration testing, complete security architecture or ongoing support.
These boundaries keep the Blueprint proportionate while leaving it useful to a competent developer or supplier.
A better supplier conversation
Without a Blueprint, supplier discussions often begin with a product demonstration. With a Blueprint, the organisation can ask a clearer set of questions:
- Can the solution preserve original evidence and distinguish extracted facts from approved facts?
- How are conflicts, uncertainty and exceptions escalated?
- Which actions require named human approval?
- What permissions does each component receive?
- What is written to the operational system, and when?
- How is every pilot case audited?
- How does work continue when the AI or integration is unavailable?
- What evidence proves that the pilot met its acceptance conditions?
Frequently asked questions
Do we need a particular software platform first?
No. Existing systems and practical interface constraints are considered, but the workflow design should not be distorted around an unnecessary product choice.
Is the Blueprint a technical specification?
It is a solution-level design suitable for briefing and estimation. It is not a complete code-level engineering specification.
Can a developer use it to quote?
Yes, as a structured basis for discussion and quotation. A supplier may still need technical discovery concerning the selected systems and interfaces.
Does it include implementation?
No. Implementation, configuration, supplier management and detailed engineering require separate scope.
What if our workflow is not ready to design?
Codance will not pretend otherwise. The work may need to begin with a Readiness Assessment or a focused clarification engagement.
Define the system before selecting the builder
Tell us the workflow, the systems involved and the decision the Blueprint must enable. Codance will confirm whether the evidence and scope are ready for design.