Interview coding with a maintained codebook

Assign supplied codes to interview segments with exact quotations, review uncoded passages and conflicting proposals, and count segments or interviews.

Input

Result

Qualitative coding needs a visible relationship between a code definition and the passage being interpreted. This tool uses a confirmed, version-labelled codebook and supplied interview segments. The AI proposes only existing codes and preserves the exact supporting passages. Deterministic checks reject invented IDs and quotations, flag mutually exclusive code proposals and count distinct coded segments or interviews. Human interpretation remains necessary even when every structural check passes.

Your texts, pages and images are processed on our own servers in the EU. Trust Center

Try it now Pricing

Who it is for

Qualitative researchers, service-design teams and internal process-review groups working with appropriately collected interview material. Suitable for organizing draft coding against a maintained codebook. It does not identify speakers, diagnose individuals or replace methodological and ethical review.

Typical uses

Code selected interview segments with a supplied version of a maintained codebook.
Allow one code or several distinct codes per segment with a clear upper bound.
Inspect uncoded passages and mutually exclusive code proposals without inventing a replacement code.
Compare distinct-segment and distinct-interview frequencies while keeping source IDs and exact quotations.

Example

Input

Interview segments CSV: id,interview,speaker,text S1,I1,Participant A,The handover checklist helped me locate the missing files. S2,I1,Participant A,I still needed a colleague to explain the approval step. S3,I2,Participant B,The process takes place every Monday. Confirmed codebook CSV: id,name,definition,exclusion,group C1,Helpful guidance,An explicit description of guidance that helped complete work.,A neutral mention without reported help., C2,Unclear approval,An explicit need for clarification of the approval procedure.,A statement that approval was already clear.,APPROVAL C3,Clear approval,An explicit statement that the approval procedure was clear.,A request for help understanding approval.,APPROVAL Confirm supplied definitions: Confirmed for this review Confirmed definition version: CODEBOOK-1 Quotation detail: Detailed Result order: Source order Coding mode: Multiple codes per segment Maximum codes per segment: 3 Low-frequency review threshold: 2 Code frequency unit: Distinct segments Uncoded segment handling: Flag for review

Result

The checklist passage supports a helpful-guidance proposal. The request for a colleague's explanation supports an unclear-approval proposal. The neutral Monday statement remains uncoded when no supplied definition fits. Frequency counts distinguish segments from interviews, and low-count findings remain review prompts rather than statistical claims.

A fixed example, shortened. Real results are AI-generated: please check them.

Price and limits

Price: usually 1–3 credits
Available with: Free, With package
Input limit: One page with up to 80,000 characters of HTML

Privacy

Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.

In the API

Tool name: interview_coding. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.

curl -X POST https://do4u.eu/api/v1/jobs \
  -H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
  -d '{"tool": "interview_coding", "url": "https://example.com/"}'

Full API documentation →

Questions and answers

Can the model create a code or diagnose a participant?

No. Only supplied code IDs and exact segment quotations are accepted. No free-form diagnosis, identity claim or new code is part of the output schema. Code assignment is still an interpretation: a human must check the definition, exclusion and surrounding context.

What happens when no code fits?

The segment receives an explicit uncoded row. The selected uncoded policy adds or omits an extra warning, but never removes the row or fabricates a quotation. Codebook changes require a new explicit confirmation.

How are multiple codes and frequencies handled?

Repeated codes within a segment are rejected. Proposals sharing a nonempty exclusivity-group ID are flagged for review rather than silently deleted. Segment counts count each segment once per code; interview counts count each supplied interview ID once per code. Neither implies prevalence or thematic saturation.

Is my text stored?

Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).

Can I use the result right away?

Results are AI-generated. Please read them before you publish or send them.