How to compare client reports with local AI
A practical checklist and reusable prompt for comparing client reports, checking conflicting figures and drafting a source-backed client update.
Start with a question, not a summary
Two client reports can disagree without either being wrong. One may cover a different period, include a different set of accounts, or use a revised definition. Asking an AI to “summarize these files” can hide the difference you actually need to understand.
Start with a narrow question: What changed between these reports, and which differences need a decision? This guide gives you a reusable comparison method and a prompt to try in Lemonade, the local AI desktop assistant from AIon X. The example is fictional and uses invented numbers; it is not a customer result.
1. Put the source files in a small working set
Choose the two reports you intend to compare. Add a notes file explaining their dates and purpose. Avoid starting with your entire client archive: a smaller set makes it easier to tell which evidence supports the answer.
Keep the originals. Use a separate folder for draft outputs, and give each report an unambiguous filename, such as April-client-report and May-client-report. If a PDF is scanned or its tables cannot be read reliably, extract and check its text before relying on a comparison. Do not assume a model has read a page simply because you attached the file.
2. Define what counts as a meaningful change
Pick a few fields before asking for prose. For a monthly service report, they might be the reporting period, open issues, committed delivery dates, costs and decisions awaiting the client.
Here is a fictional mismatch: April's report lists 12 open issues and May's lists 9. That looks like three issues were resolved. But if May excludes three paused projects, the apparent improvement may only reflect a change in scope. Your comparison needs the definitions and source locations alongside the numbers.
Use this checklist:
- Are the reporting periods comparable?
- Do both reports include the same projects or customers?
- Are units, currencies and definitions consistent?
- Is a value missing, or explicitly zero?
- Is a changed date a new commitment or just a forecast?
3. Ask for an evidence table before an executive summary
In Lemonade, make the relevant files available and try the prompt below. It is a starting point for review, not a guarantee that the generated answer will be complete or correct.
Reusable prompt: Compare the two reports I selected. First identify each report's date and scope. For each material difference, list the topic, earlier value, later value, source file and location, and a question I should resolve. Separate directly stated facts from possible explanations. If you cannot locate a value, say “not found.” Do not infer that a missing value is zero. Do not write a recommendation until the differences are listed.
Lemonade can help find answers in files, compare documents and link answers back to sources. Check the linked passages yourself, especially dates, money and commitments. A citation is a way to inspect the evidence; it does not certify the interpretation.
4. Turn the checked differences into a client update
After checking the table, ask for a short draft with three sections: confirmed changes, unresolved questions and decisions needed. Keep uncertain explanations in the questions section. A useful update should make the next conversation easier, rather than sound confident about facts you have not established.
For the fictional issue-count example, the useful question is “Does May exclude the paused projects?” The useful update is not “Issue resolution improved.” Once you have the answer, revise the draft and check it against the original reports.
Lemonade supports creating Word, Excel, PowerPoint and PDF files. Ask for the format you need, then inspect the saved output before sending it to a client. Keep file permissions narrow and review proposed writes with Ask enabled.
5. Keep the comparison reusable
Save your field checklist and the questions you had to resolve. Next month, reuse the structure while replacing the source files and dates. Do not reuse last month's conclusions as evidence for this month's report.
If your bottleneck is finding the relevant material in the first place, start with a project brief from scattered notes.
Try it with two non-sensitive reports
Lemonade by AIon X runs AI on your Windows or Linux computer and helps you work with documents. Local inference does not mean every feature is disconnected: setup, downloads and optional network features have their own network behavior. Read the privacy and network details before choosing a workflow for confidential material.
Begin with two reports you can verify easily. A good first result is a comparison you can trace back to the source and use in your next client conversation. Try Lemonade.
Join the product community
Want to discuss a document workflow or ask about Lemonade? Join the AION X Discord community, our shared server for Lemonade and CineGen. Describe the task you are trying to complete; use sample material instead of sharing confidential files.