How to Create Board Reports from Excel Data

You can create board reports from Excel data without copying the same figures into Word every month. The reliable method is to separate the process into three parts: calculate and approve the numbers in Excel, keep the report layout and standard wording in a Word template, and merge only the approved display values into the final document.

This does not remove judgement. A board report still needs commentary, context, and approval from the people accountable for the figures. Automation should remove repetitive transfer work while making the source and review steps easier to trace.

This guide explains a practical workflow for recurring management and board packs using Excel, Word, and TRYDOKU.

Define the report before you automate it

Start with the questions the board needs answered. Leave out metrics that do not support a decision or discussion.

For each section, record:

• the decision or discussion it supports;
• the metric owner;
• the source system;
• the calculation rule;
• the reporting period;
• the comparison period;
• the approved display format;
• who writes the commentary;
• who signs off the final page.

A simple definition table might look like this:

Field	Meaning	Source	Owner	Display rule
reporting_period	Month covered	Finance calendar	CFO	October 2026
revenue_actual	Approved monthly revenue	Finance workbook	Finance	EUR, no decimals
revenue_variance	Actual minus plan	Finance workbook	Finance	Signed percentage
open_risks	Count of open high risks	Risk register	COO	Whole number
executive_summary	Approved narrative	Review sheet	CEO	Plain paragraph

Do not begin with placeholder names. Begin with the meaning and owner. The placeholder is only the last step.

Decide the unit of generation

TRYDOKU treats one spreadsheet row as one output document. For board reporting, that leads to two common patterns.

One company, one reporting period

Use one row with all top-level fields for the month or quarter. This is suitable when the report has a fixed set of KPIs and narrative sections.

reporting_period | revenue_actual | revenue_variance | open_risks | executive_summary
October 2026     | €840,000        | +3.2%            | 4          | Approved summary...

Several entities or departments

Use one row per report. Each row can represent a subsidiary, region, fund, or department. A batch then creates a separate report for each unit.

This is different from putting one KPI per spreadsheet row. If you upload 30 KPI rows, TRYDOKU will normally treat them as 30 separate documents, not one report with 30 rows. For a variable-length KPI table inside one document, use a repeating list through the composer or a nested array through the API. Plan this shape before preparing the workbook.

Keep calculations in Excel

Use Excel for formulas, source imports, reconciliation, and variance calculations. Use the Word template for presentation. This separation makes each tool responsible for what it does well.

Examples of calculations that belong in Excel include:

• actual versus budget;
• month-over-month change;
• year-to-date totals;
• percentages and ratios;
• traffic-light thresholds;
• currency conversion;
• rolling averages;
• data completeness checks.

The template should receive approved results such as +3.2%, not a formula it must interpret. This keeps the generated report predictable.

Before export, freeze the reporting period. Copy final display values into a controlled output sheet or produce a clean export. Do not point the generation step at a workbook that is still changing through live connections or volatile formulas.

Create a clean output sheet

Large finance workbooks contain helper tabs, pivot tables, notes, and raw imports. Create a small output sheet instead of uploading the whole model.

Create a dedicated sheet or export with:

• one header row;
• one row per intended report;
• only fields used in the template;
• display-ready dates, amounts, and percentages;
• approved narrative text;
• no merged cells;
• no subtotals or decorative headings;
• a unique report reference;
• a status field showing approval.

For example:

report_id	reporting_period	entity_name	revenue_actual	revenue_variance	open_risks	executive_summary	approved
BR-2026-10-NORD	October 2026	Nordhavn Group	€840,000	+3.2%	4	Trading remained above plan...	true

The row count should equal the number of reports you expect. If only approved rows should be generated, export those rows into a separate batch file instead of relying on a visual filter that another person might clear.

Build the Word report template

Start with the approved board-report layout. Preserve the cover, section order, headers, footers, confidentiality marks, table styles, and page numbering.

Replace changing values with placeholders:

Board Report
{{entity_name}}
{{reporting_period}}

Executive summary
{{executive_summary}}

Financial performance
Revenue: {{revenue_actual}}
Variance to plan: {{revenue_variance}}

Risk overview
Open high risks: {{open_risks}}

Use paragraph styles rather than manual formatting. Long narrative fields may run across pages, so test the template with realistic text lengths.

The free Word template variable parser can list detected placeholders and export a matching Excel header file. It is useful as a preflight check before the approved workbook is mapped.

Handle narrative sections carefully

Board commentary should not be generated from raw figures without accountable review. Keep a named owner for each narrative field. A spreadsheet can be a practical review surface if it includes columns such as:

• executive_summary_draft
• executive_summary_approved
• risk_commentary_approved
• finance_commentary_approved
• approved_by
• approved_at

Only the approved columns should map to the Word template. Keep draft notes, reviewer comments, and internal discussion out of the generation export.

Watch for spreadsheet cell limits and line breaks. Very long narrative text is harder to review in a cell. If commentary becomes several pages, it may be better to maintain that section directly in the approved Word template and automate only the structured facts.

Use conditional sections for known exceptions

A report may need a section only when a condition applies. For example, show a liquidity note only when the approved data marks it for inclusion.

{% if include_liquidity_note %}
Liquidity note
{{liquidity_commentary}}
{% endif %}

This is appropriate when the wording is approved and the control column has a clear owner. It is not a substitute for risk judgement. The person responsible for the report must decide whether the note is required.

Keep the number of conditions small. Board packs should be easy to review. If regional reports have substantially different sections, separate templates may be clearer than one template with many branches.

See How to Add Conditional Content to Word Templates Without Code for the supported IF/ELSE structure and test method.

Use repeating rows for variable-length tables

Some report tables have a different number of rows each period: major risks, projects, incidents, or action items. A repeating Word table row is a better fit than fixed placeholders such as risk_1, risk_2, and risk_3.

TRYDOKU supports loop tags for repeating data. However, a normal flat spreadsheet does not automatically group many rows into one report. You have two practical choices:

1. add the list items for the report in the composer; or
2. send nested arrays through the REST API.

If your source workbook has one action per row, reshape or group the data before generation. The dynamic repeating rows guide explains the Word template side of the workflow.

Test empty, short, and long lists. Check whether a table header repeats on a new page, whether rows split badly, and whether long descriptions affect column widths.

Treat charts as a separate production step

Do not assume that uploading Excel will recreate its charts inside Word. Spreadsheet formulas, chart objects, and pivot layouts are not the same as merge data.

Choose a controlled chart process:

• keep stable charts directly in the Word template if they do not change;
• export approved charts as images and insert them through a documented manual step;
• use another reporting tool to create the charts, then assemble the pack;
• build a tested application workflow if dynamic image insertion is a supported requirement.

TRYDOKU’s core spreadsheet workflow fills template data; it should not be presented as an Excel chart renderer. If charts are central to your pack, prove that step separately before promising full automation.

Format values before the merge

The board should not see raw values such as 0.032184 when the intended display is +3.2%. Create separate display columns where needed.

Raw value	Display column	Output
840000	revenue_actual_display	€840,000
0.032184	revenue_variance_display	+3.2%
2026-10-31	period_end_display	31 October 2026

This makes the output easy to verify. The spreadsheet owner can see exactly what will be inserted.

Agree how to show negative values, zero, unavailable data, and estimates. For example, use one standard such as — for not available and do not mix it with 0, which has a different meaning.

Reconcile the report before generation

Add checks to the output workbook:

• total revenue matches the approved finance report;
• percentages use the correct denominator;
• reporting period is consistent across every row;
• entity codes map to the right names;
• every narrative section is approved;
• every required field is populated;
• the expected report count matches the row count;
• no formulas contain errors;
• no source cell is still linked to an unavailable workbook.

Use a visible readiness field. Only rows marked approved should enter the clean generation file.

Generate a controlled test pack

Upload the DOCX template and the clean Excel or CSV export to the TRYDOKU composer. Map columns to placeholders and inspect the grid.

Start with test records that include:

• the longest entity name;
• the longest approved commentary;
• a negative variance;
• a zero value;
• unavailable data;
• every optional section included;
• every optional section excluded;
• a long repeating table, if used.

Generate and open both DOCX and PDF if both formats are part of the process. Word is useful for final controlled edits; PDF is usually the distribution format. The current TRYDOKU documentation describes the available download flow.

Review the output against the source

Use a review checklist with two columns: source and report. For every KPI, compare the displayed value to the approved export. Then review the report as a document.

Check:

• cover date and entity;
• page numbers and contents page;
• all KPI values;
• signs on variances;
• currencies and units;
• narrative approval status;
• conditional sections;
• table continuation across pages;
• confidentiality markings;
• empty pages and bad page breaks;
• chart version, if charts are inserted separately;
• filename and report reference.

For sensitive board packs, use a preparer and an independent reviewer. Keep the reviewed source export and final file together in the approved records system.

Keep an audit-friendly version trail

Use stable identifiers for the period, entity, template, and data export. For example:

Report ID: BR-2026-10-NORD
Template version: board-report-v4
Data export: board-data-2026-10-approved.xlsx
Final file: BR-2026-10-NORD-final.pdf

If a number changes after generation, create a new version. Do not silently replace the final PDF without recording why. The document generation tool is only one part of the control; your records system should hold the durable approved copy.

Protect confidential board information

Board packs can contain financial, strategic, employee, and legal information. Minimize the data sent to the generation service and review the provider’s location, retention, access, and contractual terms.

TRYDOKU states that its primary application and storage servers are in Frankfurt and generated outputs are automatically purged within 24 to 72 hours. Review the current Security and Trust page before using live data.

After download, store the file in the approved board portal or records system. Do not leave final packs in personal download folders or broad shared drives. Apply your normal access, retention, and distribution controls.

Common mistakes

Uploading the finance model instead of an output sheet

Create a small, controlled export with only approved fields. This reduces mapping errors and unnecessary disclosure.

Expecting many Excel rows to become one report

One row maps to one document. Use a single wide report row for fixed fields and loops or API arrays for variable lists.

Mixing calculation and presentation rules

Calculate in Excel and pass display-ready values to the template. Avoid rebuilding finance logic in document tags.

Automating unapproved commentary

Map only approved narrative fields. Keep drafts and review notes out of the export.

Assuming charts will transfer from Excel

Treat charts as a separate tested step. A data merge does not automatically render workbook charts.

Skipping the PDF check

PDF conversion can reveal different pagination from DOCX. Open the actual distribution format before approval.

A repeatable monthly workflow

A controlled process can be simple:

1. refresh the source workbook;
2. reconcile figures to approved systems;
3. write and approve narrative fields;
4. freeze a clean generation export;
5. confirm the template version;
6. generate a small edge-case test;
7. generate the approved report row or batch;
8. review every report against the export;
9. create the final PDF;
10. store and distribute it through the approved channel;
11. record corrections as new versions;
12. remove temporary local copies.

Document the owner and deadline for every step so each handoff is clear.

Begin with one stable report

Do not start by automating the entire board pack. Choose one recurring report with a stable structure and a clear data owner. Prove the output sheet, template, and review checklist. Then apply the pattern to other sections.

To test the merge step, create a TRYDOKU account, use a copy of the Word report with confidential content removed, and generate one synthetic reporting row.

Frequently asked questions

Can TRYDOKU turn every row in a KPI sheet into one report?

Not automatically through the flat spreadsheet import. One row normally produces one document. Put fixed report fields in one row and use repeating list data for variable tables.

Will Excel charts appear in the generated Word report?

Do not assume so. Treat dynamic charts as a separate production step and test how approved chart images enter the final pack.

Can the final report be downloaded as PDF?

Yes. TRYDOKU generates DOCX output and provides PDF downloads for generated files. Review both formats if the board receives PDF.

Where should calculations happen?

Keep calculations and reconciliation in Excel or the source system. Send approved, display-ready values to the Word template.

How should corrections be handled?

Fix the approved source, regenerate the report, give it a new version, and keep a record of what changed. Remove superseded files from the distribution location.