What should we put in writing when requesting an intake sample or pilot?
Eight points for a written pilot request: domain, exceptions, schema, free text, acceptance test, permitted uses, stated limits and a defect reporting process.
Put these points in writing when you ask MirrorFirm for an intake sample or pilot.
- Name one domain and one component set, such as records with policies, rather than asking for everything at once. - List the exception types your buyers care about, such as duplicates, missing documents or amended requests. - Ask for the schema, manifest and policy file together with the sample, not afterwards. - Include a small amount of generated free text so you can judge grounding and disclosure risk. - Write the acceptance test before the sample arrives, with pass and fail conditions for each check. - Ask what the licence permits for training, fine-tuning, evaluation and derivatives, and have it confirmed in writing. - State any limits you need, such as jurisdiction or industry coverage, and ask what the release does not cover. - Agree how you will report defects back and how corrected samples will be versioned.
A written request with a prepared acceptance test turns a pilot into a clear decision instead of an open-ended trial.
- Audience:
- Licensed resellers
- Content type:
- Checklist
- Buyer question:
- Scope and getting started
Content release: r-a220eb6e099b243b
Related questions
- What does a scoped pilot for a claim lodgement agent look like?
- What should a pilot brief for intake include?
- What should we ask for in an intake sample or pilot?
- How should a team scope a first intake dataset or pilot?
- How do we connect pilot material to our agent harness?
- What delivery layout should I ask for in a pilot so my harness can load it?