
Separate customer reports
One tester file. Several customers. Separate reports. A day’s testing does not always fit neatly into one customer file. If your supported export contains several sites or customers, the reporting stage needs a clear way to keep each group together.
Start with the structure
Before splitting anything, review the imported workspace. Find the field that consistently separates the jobs, such as Site. Check its values against the reports you intend to produce. A misspelt or inconsistent value deserves attention before the file is divided.
Open Split Report
PatConnect uses the column you group by to segment rows into separate sub-workspaces. Each segment can be saved as an independent report with its designated customer profile. This helps organise reporting around the recorded data. Compatibility depends on the tester export.
Check the customer assignment
Match each segment with its intended customer. Review the report details and records before saving. If the original export does not clearly separate the jobs, bring a sample to a demonstration and check the workflow before relying on it for live work.
Review the finished PDF
Open the saved report and check the customer details, site and asset rows. Keep your original export alongside your normal records. A professional layout does not replace reviewing the information you send to a customer.
Keep the process connected
PatConnect also includes saved reports, customer records and a calendar workflow. Explore how these fit your working day: importing a supported file, separating jobs, saving reports and finding them again later.
PatConnect team · 26 October 2026
If mixed files are a regular part of your work, ask to see that scenario in a free demo through the Shop page. £399 once for a lifetime licence. No subscription. Direct WhatsApp support.