Five board-pack automation mistakes that cost you

Board-pack reporting automation is usually sold as a dashboard project. In practice, the expensive part is not the chart; it is the five days finance spends chasing numbers, reconciling GST ledgers, and rebuilding the same 14-tab deck before every board meeting. This hits finance and operations leads at Indian SMBs hardest, because the same small team owns statutory reporting, collections, and the board narrative.

Mistake 1: Automating the format before defining the decisions Automating the existing deck locks in clutter, not clarity. A board pack exists to support a handful of decisions: hiring, capex, pricing, working capital, and maybe a fundraise. Before wiring any data, list the five decisions your board actually makes and the three numbers behind each one. If a tab has not changed a decision in two quarters, cut it. Otherwise you pay to refresh a 22-tab pack that nobody reads past page six. The output should be one page per decision, with a supporting appendix that is available but not printed by default. That single constraint saves more time than most dashboard features. If you cannot name the decision a tab supports, it belongs in an appendix or nowhere.

Mistake 2: Pulling from source systems that do not reconcile Automation multiplies whatever reconciliation gap already exists. If Tally, bank statements, UPI settlement reports, and CRM exports disagree, a scheduled refresh simply delivers the disagreement faster. Fix the definitions first: revenue recognised versus collected, GST taxable value versus books, TDS receivable ageing, and customer concentration. If GST data is already a monthly headache, sort that out before the board pack; our note on GST billing automation covers the reconciliation basics. Then build one reconciled trial balance and a small mapping table that every report reads from. That mapping table is boring, but it is the difference between an automated pack and an automated argument. No dashboard can fix a 3-way match that has never been done.

Mistake 3: Running the board pack as a month-end sprint A board pack should be a continuous close, not a five-day panic. Teams wait for the last invoice, then three people rebuild links at 11 pm. Move to a close calendar that starts on day one: reconcile bank and UPI settlements by day two, finish GST and TDS by day four, lock revenue and margin by day five, and circulate commentary by day six. Automate the overnight refresh and review exceptions in the morning. Take a 14-tab pack fed by five sources. If each refresh takes 20 minutes and you refresh three times before the meeting, that is 14 hours per cycle before anyone writes a word of commentary. A simple calendar like this is enough: - Day 1-2: bank, UPI, and payment gateway reconciliation - Day 3-4: GST, TDS, vendor ageing, and intercompany balances - Day 5: revenue, margin, cash runway, and collections - Day 6: variance commentary, review, and pack lock

Mistake 4: Buying a BI tool before fixing definitions and ownership Tool-first automation creates a second set of numbers and a new owner nobody appointed. A dashboard is only as good as the metric definitions behind it. Write a one-page data dictionary for revenue, gross margin, net burn, collection days, and pipeline coverage. Assign one owner per metric: finance for revenue and cash, sales ops for pipeline, HR for headcount. Then choose the smallest tool that reads those definitions. A mid-market team usually does not need a large BI programme; it needs scheduled queries, a controlled spreadsheet layer, and clear access rules. The tool should fit the definitions, not become the place where definitions go to die.

Mistake 5: Sending the pack as an email attachment with no audit trail Distribution is part of the control, not an afterthought. Board packs contain salaries, customer concentration, cash runway, and sometimes personal data. A PDF emailed to 11 people, forwarded on WhatsApp, and revised twice is both a governance risk under the DPDP Act and a version-control nightmare. Use a named-access folder or board portal, watermark drafts, log downloads, and keep one canonical version. Automate the commentary workflow too: owners submit variance notes by a deadline, finance edits, and the final pack is locked. AI-assisted review can draft first-pass variance commentary from the numbers and prior notes, but a human must sign off before anything reaches the board.

Where to start Start with one board pack, one owner, and one reconciled number set. Pick the five decisions your board actually makes, document the metric definitions, and automate the refresh before you automate the commentary. If you want a second pair of eyes on the data plumbing, Maysan Labs builds finance dashboards and reporting workflows for Indian SMBs, and we are happy to share what we would fix first.