How to complete your Codance workflow questionnaire
For a Readiness Assessment or Integration Blueprint, your answers form the evidence base for the engagement. Each question reveals a different part of the workflow: what happens, where information is held, who exercises judgement, where exceptions arise and what a worthwhile improvement would need to achieve.
This is not a test. We do not expect polished, technical or “correct” answers. Candid descriptions of what really happens—including uncertainty, workarounds and occasions where “it depends”—are often the most valuable.
What a useful answer does
A detailed answer does not need to be long. It needs to be concrete enough for Codance to understand the operation, distinguish evidence from assumption and ask sensible follow-up questions.
| Question area | What it helps Codance understand |
|---|---|
| Boundary and outcome | Where the workflow begins and ends, what is included and what useful result must be produced. |
| Actual steps and handovers | How work moves in practice, including informal routes, waits, repetition and ownership gaps. |
| Information, decisions and exceptions | Which facts are authoritative, what follows a rule, what requires judgement and what happens when the normal path breaks down. |
| Value, authority and constraints | Whether the opportunity matters, what AI may assist with, what people must control and which limits apply. |
How to answer well
- Describe one workflow that actually operates, not only the written procedure.
- Identify the event that starts it and the event that proves completion.
- Use roles rather than personal names unless a name is genuinely necessary to understand authority.
- Give ranges or estimates where exact measurements do not exist, and say “unknown” where the organisation does not know.
- Include normal cases and exceptions. A rare but consequential exception may matter more than a common easy case.
- Identify where information conflicts, is copied between systems or depends on an experienced person’s memory.
- Explain the consequence of delay or error in practical terms: customer impact, rework, financial exposure, compliance, safety or lost visibility.
What useful detail looks like
Starting event
Too brief: “We receive enquiries by email.”
More useful: “Most enquiries reach the shared sales inbox, but established customers sometimes email the estimator directly, so not every enquiry enters the shared log.”
Current difficulty
Too brief: “Quotations take too long.”
More useful: “Average elapsed time is about four working days. Delay occurs while attachments are checked, previous jobs are found and missing information or supplier prices are obtained.”
Source of truth
Too brief: “We use JobFlow and Excel.”
More useful: “Excel is treated as the outstanding-enquiry list, JobFlow stores formal job records and the shared drive often contains the most complete historic quotation. None reliably shows the whole current status.”
Judgement and authority
Too brief: “The estimator approves it.”
More useful: “The estimator interprets the drawing and estimates labour. Quotations above £5,000, or involving unusual technical risk, require technical-director approval.”
The most useful habit
When possible, describe one recent real case: what arrived, who handled it, what was missing, which systems were used, where it waited and how completion was recorded.
Evidence and confidentiality
Helpful evidence may include anonymised forms, emails, screenshots, checklists, process notes, example inputs and outputs, supplier proposals and summary measurements.
A small set covering successful, incomplete, conflicting and unusual cases is generally more useful than a large unfiltered export.
Please do not provide:
- passwords, API keys, access tokens or private keys;
- unnecessary personal information;
- unauthorised customer or employee material;
- confidential files unrelated to the agreed workflow;
- material you are not authorised to share.
Anonymise supporting material wherever reasonably possible.
Before you submit
- Confirm that the answers concern one defined workflow and one principal business function.
- Check that the initiating event, useful outcome and completion event are clear.
- Include unofficial routes, workarounds, delays and exception cases that materially affect the result.
- Distinguish known facts, estimates, assumptions and unknowns.
- Anonymise supporting material and remove information Codance does not need.
- Confirm that you are authorised to commission the work and provide the supplied information.
What happens after submission
Review
Codance checks the workflow boundary, authority, package fit, completeness and safe use of evidence.
Clarification
We ask focused follow-up questions where an answer could materially change the finding or design.
Evidence cutoff
We record the evidence included in the engagement so later additions do not silently change the scope.
Analysis
We separate process improvement, deterministic control, AI assistance and decisions that must remain human.
Delivery
We produce the agreed Readiness Report or Integration Blueprint, with assumptions and limitations stated plainly.
Need help with a question?
Explain what you think it is asking and describe the situation in your own words. Codance would rather clarify an honest answer than receive a confident guess.
The quality of the engagement depends on shared clarity, not specialist vocabulary. Your operational knowledge and our structured analysis perform different—and equally necessary—parts of the work.