What should a pilot brief for intake include?
A checklist for assembling a brief that is specific enough to scope and judge, covering path, systems, policies, exceptions, delivery form, intended use, success criteria and review.
Before contacting MirrorFirm, assemble a brief that makes a pilot specific enough to scope and to judge.
- The intake path to cover, with case type, channels and the roles that receive the case. - The systems and tool actions your agent will use, with argument names where known. - The policies to model: completeness rules, routing rules and any tie-break logic. - The exception classes you most need represented, ranked by cost to your business. - The delivery form wanted: files, task pack or environment with reset and export. - Your intended use: internal evaluation, training, or both, and whether results will be published. - Success criteria written as checks, such as consistent keys and reproducible expected outcomes. - A plan to review the sample for grounding and disclosure risk, with a named reviewer.
Do not include real applicant data in the brief. Describe the shape of records and rules instead. Timing, volume and commercial terms are agreed in discussion, not assumed from a template.
A specific brief makes the pilot quotable and judgeable, without exposing any real applicant data.
- Audience:
- Agent developers
- 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 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?
- What does a first pilot look like for a professional services engagement request environment?