Level 6 · In practice

6.4Toolbox

Goal: have operational checklists and essential statement-design landmarks.

Estimated time: 10 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

Distribute: clean joins, totals at the right level and cross-checked, server filter, nulls handled, pagination held.
Draw fast: subtotal in group footer, running total with reset set, Top N by Group Sort, cross-tab narrow in columns.
Rule: a checklist ticked every time beats a method known by heart — at close time, you execute.

Farès thread — the sheets near the desk

After one quarter, the two sheets below stay near the desk of Farès: the distribution one displayed next to the screen, the landmarks one in his notebook. “What saved me,” he says in substance, “is not knowing the points, it is ticking them every time — especially on close days.”

Adapt the wording to your context, keep the structure: it is what avoids omissions and incidents.

Ready-to-use landmarks

A good checklist makes a task fast and omission-free; good landmarks speed up design. Adapt to your context.

Before distributing a report

Are the joins clean (no duplicates)?
Are the totals at the right level and cross-checked?
Is filtering server-side (SQL checked)?
Are null values handled?
Is the formatting consistent and readable?
Does pagination hold (PDF, landscape if needed)?
Does the export format match the use?
Was the report tested on a real volume?

Landmarks & reflexes to draw

Subtotal → Group Footer; grand total → Report Footer
Grouping = sorting + structuring (group header/footer)
Running total: set the RESET (never / per group)
Ranking: group + subtotal + Top N (Group Sort)
Cross-tab: few values in columns, numerous in rows
Chart: bars = compare, line = evolve, pie = shares
Formula: “If IsNull(...) Then ... Else ...”; convert types
Performance: filter server-side, subreports at group level

Common misinterpretation: “collecting checklists”. No. A checklist is only useful when ticked and used: take the one for your next statement, the others can wait.

Text version of the diagram (SEO / screen readers / translation): Two moments, two sheets: 1) Distribute — clean joins, totals at the right level and cross-checked, verified server filter, nulls handled, sober formatting, PDF pagination, matched export, real-volume test. 2) Draw — subtotal in group footer, running total reset per group, Top N by Group Sort, cross-tab narrow in columns, bars/line/pie by message, If IsNull Then Else, subreports at group level. Lesson: no more thinking under pressure, you execute the sheet near the desk.

Ready-to-say script — validating a statement (30 s)

“Clean joins? Totals at the right level and cross-checked? Verified server filter? IsNull handled? Readable formatting? Pagination and export OK? Tested on a real volume? If any no, we do not distribute.”

Copy-paste template — statement follow-up (1 line per point)

statement_followup = {
  "clean_joins": "OK / to redo",
  "totals_level_crosschecked": "OK / to redo",
  "server_filter_sql": "OK / to redo",
  "nulls_formulas": "OK / to redo",
  "readability_pagination_export": "OK / to redo",
  "real_volume_test": "OK / to redo"
}

Small business / tight budget

Sheets on one page displayed on the wall: the essentials (joins, cross-checked totals, export) are enough.

Algeria SME

Plan local realities into the sheet: known contacts, close days, tested real volume.

Remote / hybrid

Add a written-validation line to the follow-up: at a distance, a dated, cross-checked distribution avoids misunderstandings.

Cross-cultural

Spell out headings in writing: what seems obvious (who cross-checks, which export) is not obvious to everyone.

Caution: Generic reminder: correctness and performance commit your organisation — “cross-checked totals and server filter” point ticked every time, credentials never hard-coded, real-volume test kept; this guide gives no legal advice.

48h challenge — apply tomorrow

Take 1 real statement, run the “Before distributing” checklist and tick where it stands. Test a template.

Section exit checklist

I have ticked a checklist on a real statement.
I can draw the distribution sheet and the landmarks at the right time.
I have done the 48h challenge or scheduled its date.

Self-assessment 1-5: tooling of my statements?dated use of checklists?

← Previous : Good practices & pitfalls (V3)Next : Field feedback (V3) →

Check your understanding

Farès is about to distribute his statement with a running balance. What must he tick first?

💡

These checklists prevent 90% of incidents: an unchecked total, a client-side filter, a badly reset running total.