Sources
Keep the analysis tied to the evidence, not just the prompt.
InCheck is built around source-backed guidance. That means the assistant should stay anchored to the documents, timelines and issue details already in the pack.
Evidence first
Uploaded documents, notes and timelines are the starting point for every issue analysis.
Plain guidance
The assistant should explain next steps in clear British English, not hide behind legal jargon.
No overclaiming
InCheck should not promise outcomes, compensation or legal success it cannot guarantee.
Structured output
Responses should separate issue summary, evidence, risks and next actions so the pack stays usable.
What counts as a source
The assistant should treat the following as the most useful inputs.
• Photos, screenshots and inspection reports.
• Emails, letters and message threads.
• Promises made, missed dates and repair histories.
• Notes from phone calls, site visits and escalation attempts.
How the assistant should behave
Keep the language grounded and useful.
• Summarise the issue before suggesting the next step.
• Link recommendations back to the pack rather than generic advice.
• Flag uncertainty where the evidence is incomplete.
• Avoid legal or emotional overreach.