Reporting

Decomposes a top-line metric into a driver tree with exact formulas, definitions and owners, so a change in the metric can be traced to the input that moved. Use for metric design and reviews.

Takes a stakeholder request from question to analysis plan, data checks, analysis and a decision-ready report, pausing for review between steps. Use when an analyst takes on a request.

Designs automation for a recurring report (sources, refresh, transformations, data checks, delivery) with tools matched to the team's skills. Use when a weekly or monthly report eats hours.

Builds an organisation's metrics glossary with definitions, formulas, grain, sources, owners and caveats, and surfaces conflicting definitions. Use when teams quote different numbers.

Builds a slide deck file from analysis results with a script, one finding per slide, charts rendered from the data, speaker notes and a source appendix. Use to present finished analysis.

Compares performance across periods (YoY, MoM, like-for-like), handling trading days, holidays, seasonality and mix, and builds a variance story that adds up. Use before reporting a period change.

Builds a data report file end to end, confirming the question, scripting analysis and charts, drafting traceable findings and exporting a document or deck after review. Use to answer a data question.

Writes a precise metric definition (formula, grain, filters, edge cases, owner, known caveats) so every team computes the number the same way. Use when a metric is disputed or about to be launched.

Designs a Power BI data model with a star schema, relationships, a date table, base measures, storage modes, incremental refresh and row-level security. Use before building a report.

Designs a recurring report template with sections, metric specifications, commentary prompts, formatting rules and a production checklist. Use when setting up a weekly, monthly or board report.

Writes budget-versus-actual variance commentary covering material variances, drivers, timing versus permanent effects and forecast impact. Use as an FP&A analyst or budget holder at month end.

Explains why the same metric differs between tools or teams by checking definitions, filters, time zones, attribution and tracking, then plans a reconciliation. Use when numbers disagree.

Generates personalised letters, certificates or labels from a spreadsheet and a template as Word or PDF files, previewing three records for approval before the rest. Use for batch documents.

Fills a Word report template from data or analysis output with a script, keeping its styles, tables, headings and figure captions, and checks that no placeholder remains. Use for recurring reports.

Runs a monthly reporting cycle in gated steps from data pull and quality checks to metric calculation, variance commentary, review with metric owners and distribution.

Writes the methodology and caveats note for a report or dashboard, covering sources, definitions, cleaning, known biases and how to read the numbers, for the audience who will use them.

Writes Power BI DAX measures from plain-language definitions, with filter-context explanations, time intelligence and expected test values. Use as a BI developer or analyst building a report.

Writes forecast commentary explaining the change from the last forecast with a bridge, drivers, quantified risks, confidence and decisions needed. Use for monthly or quarterly reforecasts.

Turns analysis results into a decision-oriented report with a headline finding, evidence, caveats and a recommendation. Use when you need to share an analysis with people who will act on it.

Writes a monthly business review with headline results, performance against plan by area, drivers, outlook, risks and the decisions needed from leadership. Use as an analyst or operations leader.

Writes an OKR progress report with baseline-adjusted scores, confidence, trends, blockers and the decisions needed from leadership. Use for monthly check-ins and end-of-quarter grading.

Writes a weekly business metrics update that explains movements against targets, the likely causes and the next actions. Use for the Monday update to leadership or the team channel.