ConsoliSheetBranches tend to send the same report in slightly different shapes. The useful step is making those differences visible before the rows get combined, not after.
Quick answerAgree the fields the combined report needs, check every branch’s submission against that list rather than assuming they match, and keep a Source File or Branch column so any unusual row can be traced back.
- Leeds branch — “Location”
- Bristol branch — “Site”
- Derby branch — “Store”
Branch
Why branch reports drift apart
Each location edits its own copy of the report. Over time, someone adds a note column, renames a heading to match local language, or reorders fields without meaning any harm. None of it is wrong locally — it only becomes a problem the moment the files are combined.
1. Agree the required fields. Decide what the combined report needs, once, centrally.
2. Inspect every submission. Do not assume this month’s file matches last month’s structure.
3. Keep the source visible. A Branch or Source File column turns an odd number into a two-minute check.
Common questions
Do all branches need to use the same template?
It helps, but a consolidation process that only works when every file is identical will fail the first time one branch deviates — which they eventually will.
Collecting from several branches already?
Upload the branch files together and review the proposed matches before exporting one combined workbook.
Try Quick Consolidate