Skip to content
MirrorFirm

What should I put in writing when asking for an intake sample or pilot?

A checklist of items to specify in a sample request, from request types and exception families to formats, reference solutions, licence terms and defect reporting.

When you ask for a sample or pilot, put these requests in writing so the first delivery can be tested end to end.

- Name one or two request types and the domain they sit in, such as claims lodgement or loan applications - List the exception families you want tagged, for instance duplicates, late attachments and withdrawals - State the file formats and schema conventions your harness loads, including JSONL, Parquet or both - Ask for the tool vocabulary and error codes the environment will expose to the agent - Request a reference solution for each task so you can test the grader before any agent run - Say whether you need training use, evaluation use or both, and ask for the licence terms in writing - Ask how grounding was approached and what review of disclosure risk the sample has had - Agree how defects will be reported, with task ids, and how corrected versions will be versioned

A written request makes the first delivery testable end to end and keeps scope and licence terms explicit.

Audience:
Environment builders
Content type:
Checklist
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Application intake