One report. On schedule.
Every month.

Everything we build, test, ship, fix and change
— reported in a single ledger, published
within five working days of each month’s close, with the numbers
we actually have. Not a brochure. A record.
  • 6
    modules per issue, fixed
    order
  • 6–10
    pages per issue
  • ≤ 5
    working days from close to
    publish
  • 0
    login walls — read it, or
    subscribe

The reporting
standard

A monthly ledger with a data-freeze date, a publish date and a signature pair. The same structure every issue, so a habit can run for years without becoming ceremony.
Ask a maker three questions — how many machines did you build last month? What broke in the field? How fast did you fix it? We answer all three on paper, every month, in dated ranges and rates, each figure carrying an evidence ID. Most compact-equipment makers do not answer in public, month by month; that does not change our answer.
So the ledger carries three dates that never blur: when the data froze, when the report published, and who signed it. Output is reported in ranges, quality as rates, failures with root causes, fixes with evidence IDs.

MR-001

the one metric we never negotiate — on-time publication. A report that is late is a report that lies about itself.
  1. Month end

    Monthly snapshot

    Issue the report, freeze the data. Six modules, same vocabulary, every issue.
  2. Quarter end

    Cross-link audit

    Verify every link between transparency pages — the link audit is itself a rule.
  3. Year end

    Annual freeze

    Major versions locked, errata published.
    The ledger only grows.

This issue, module
by module

Below is the issue format — every number an illustrative placeholder until the data pipeline binds. The structure, vocabulary and evidence-chain discipline shown here are the binding template. When real data binds, only the numbers change.

BOLEO MONTHLY REPORT — ISSUE #000 (FORMAT SPECIMEN)

BOLEO-MR-ISSUE-2026-08 · TRANSPARENCY LEDGER
ILLUSTRATIVE · Specimen dates model the monthly cadence (freeze by day 3 · publish by day 5); the specimen itself is registered in the Archive on 2026-08-30 — the same day this page’s v1.0 freezes. Two dates, distinct.
SCOPE
DIWAL X TURBO
ZEWEIT X/Y/Z/3/R/6/9
UNITS TESTED
132
UNITS SHIPPED
128–155 (range)
CLAIMS RECEIVED
12
ECN DIGEST
2
CAPA DISCLOSED
2 (1 closed · 1 open)

M1 Output & Delivery

RULE MR-003 SOURCE QA-2026-08-01
Line Models Completed Shipped
Stand-on loader DIWAL X TURBO 30–40 units 28–38 units
Compact excavator 1.2–2.0T ZEWEIT X · Y · Z 60–80 units 55–75 units
Compact excavator 3.2–3.5T ZEWEIT 3 · R 20–30 units 18–28 units
Compact excavator 6.0–9.0T ZEWEIT 6 · 9 15–25 units 15–22 units
Total 125–175 units 116–163 units
Ranges, never exact counts — precise production volume is commercially sensitive; a dated range is honest without being reverse-engineerable.

M2 Quality Indicators

RULE MR-005 SOURCE SVC-2026-08-01
Indicator This issue Prior Reading Evidence
First-pass yield 96.4% 95.8% ▲ +0.6 pt QA-2026-08-02
Units factory-tested 132 118 Every unit has a report QA-2026-08-03
Retests logged 5 6 All visible, none removed QA-2026-08-04
Retest pass rate 100% 100% STABLE QA-2026-08-04
First-pass yield is defined on the Factory Test page — referenced here, never redefined.

M3 Claims & Closure

RULE MR-005 SOURCE SVC-2026-08-01
Item Count Line Status Evidence
Hydraulic seepage report 2 ZEWEIT X / Z CLOSED ≤30 d SVC-2026-08-07
Control-panel indicator flicker 1 DIWAL X TURBO OPEN · DUE 2026-09-30 SVC-2026-08-19
Closed within 30 days 11 / 12 — 91.7% SVC-2026-08-01
Average closure time 14 d — Prior 17 d SVC-2026-08-01

M4 Parts SLA Attainment

RULE MR-006 SOURCE SVC-2026-08-05
Commitment Target This issue Prior Evidence
Routine parts shipped ≤ 48 h 93% 90% SVC-2026-08-05
Claim response ≤ 2 working days 100% 100% SVC-2026-08-01
Backordered items disclosed 3 5 SVC-2026-08-06
Pricing and warranty terms live on their own page — this module reports attainment against the published SLA, nothing else.

M5 Engineering Change Digest

RULE MR-007
ECN No. Summary Affected Status
ECN-2026-08-01 Control-panel harness routing revision DIWAL X TURBO, from SN DX26-0400 IMPLEMENTED
ECN-2026-08-02 Hydraulic quick-coupler development gate P2 Z17 / Z20 program (pre-production) PASSED
One line per change, linked from affected product pages. Pre-production programs appear only as gates passed — no launch claims before launch.

M6 Problems & Fixes — CAPA Disclosure

RULE MR-007

CAPA-2026-08-01 · CLOSED

What happened. Two field reports of seepage at the hydraulic quick-coupler, ZEWEIT X / Z units. Root cause. A seal batch below specification, isolated to one incoming lot. Fix. Corrective seals dispatched to all channels; affected lots quarantined. Verification. Retest across the affected serial range — zero recurrence.
QA-2026-08-14 · SVC-2026-08-07 · closed 2026-08-22

CAPA-2026-08-02 · OPEN

What happened. One report of control-panel indicator flicker at low ambient temperature, DIWAL X TURBO. Containment. Reproduction confirmed in cold-chamber test; interim inspection instruction issued to the service network. Next update. 2026-09-30, in Issue 2026-09.
SVC-2026-08-19 · QA-2026-08-21 · due 2026-09-30
Publishing a closed failure with its root cause is worth more than any claim of quality — and an open item with a date is not an admission of weakness; it is a schedule.
CORRECTION LOG — 2026-07 issue: prior-period first-pass yield restated from 95.6% to 95.8% (source reconciliation at data freeze). Original value retained above; archived issue unedited. Rule MR-009.

Six modules,
one ledger

The monthly report is where every other transparency page converges — factory test becomes a yield rate, service becomes an SLA attainment, engineering becomes a change digest. Six modules, fixed order, the same vocabulary every issue.
M1

Output & Delivery

Production and shipments per product line, in ranges. Never exact counts, never customer identities.
M2

Quality Indicators

First-pass yield, units tested, retests — definitions owned by the Factory Test page, referenced here.
M3

Claims & Closure

Claims received, closed within 30 days, open items with due dates. Every number carries an SVC evidence ID.
M4

Parts SLA Attainment

Attainment against the published 48-hour and 2-working-day commitments. Terms and prices stay on their own page.
M5

Engineering Change Digest

One line per implemented change and per passed development gate, linked from affected product pages.
M6

CAPA Disclosure

The soul of the report: closed failures with root cause and verification; open items with containment and a due date. Safety-related items follow the regulatory process before publication.

The MR dictionary

Same discipline as every page in this system: IDs are frozen, never reused, and any revision is logged in the Archive. Where a definition is owned by another page, this dictionary references it — one fact, one home.
Code Rule Term Definition
MR-001 Rule · Binding Publication Cadence & Punctuality Each issue publishes no later than the fifth working day after month close. On-time publication is itself a published metric. A report that is late is a report that lies about itself — the cadence commitment outranks the content.
MR-002 Rule · Binding Data Freeze Source data (QA / SVC / delivery) freezes on the third of each month. Anything after the freeze lands in the next issue — a frozen number is never quietly restated inside a live issue.
MR-003 Rule · Anti-reverse-engineering Output Ranges Production and shipment volumes publish as bands (e.g. 30–40 units), never exact counts. Precise volumes are commercially sensitive; a dated band is verifiable by trend without revealing capacity.
MR-004 Reference · Defined at /factory-test FT-008 First-Pass Yield The FPY definition, tolerance rules and retest discipline are owned by the Factory Test dictionary. This page reports the monthly figure only — referencing, never redefining.
MR-005 Rule · Measurement Claims Closure A claim is “closed” when the corrective action is verified at the machine, not when a part ships. Closure window: 30 days from receipt. Open claims publish with a due date — no claim disappears between issues.
MR-006 Rule · Measurement Parts SLA Attainment Attainment = orders shipped within the published SLA (routine parts ≤ 48 h; claim response ≤ 2 working days) ÷ total orders in scope, per calendar month. Backorders are disclosed as a count, with expected clearance in the next issue.
MR-007 Rule · Content ECN Digest Rules One line per implemented engineering change (with affected models and starting serial) and per passed development gate for pre-production programs (Z17 / Z20 articulated loader electric line). No launch claims before launch — a gate passed is a fact; a launch date is a plan, and plans are labeled as plans.
MR-008 Rule · The soul module CAPA Disclosure Only closed-loop failures publish in full (what happened / root cause / fix / verification, with evidence IDs). Open items publish with containment and a due date. Safety-related items follow the regulatory process first, always. No third-party supplier names appear — component references stay generic.
MR-009 Rule · Binding Correction Log A wrong number is never silently edited. Corrections append to a visible correction log with the original value retained in strikethrough; archived issues are immutable. Errors handled in the open accumulate credibility; errors hidden accumulate interest.
MR-010 Rule · Governance Dual Sign-Off Every issue carries two signatures: the Quality Director (data authenticity against source ledgers) and the Brand Owner (copy red lines — no superlatives, no unverifiable claims). One signature missing = not published.
MR-011 Rule · Traceability Evidence Chain IDs Every figure cites a source record: QA-YYYY-MM-NN (quality), SVC-YYYY-MM-NN (service), ECN-YYYY-MM-NN (engineering change), CAPA-YYYY-MM-NN (corrective action). No source record, no publication. Certification statuses are not carried in this ledger — they live at /transparency/certification and are linked, never copied.

Publication discipline

A monthly report’s credibility is a function of process predictability. The pipeline below is fixed; the people in it are accountable by name.
  1. 1

    Data freeze

    Day 3 — QA / SVC / delivery data exported from source systems. Late changes go to the next issue.
    MR-002
  2. 2

    Draft & check

    Day 4 — editorial draft; every indicator checked against the Methodology and dictionary owners.
    MR-011
  3. 3

    Dual sign-off
    & publish

    Day 5 — Quality Director + Brand Owner sign; the issue goes live at its permanent URL.
    MR-010
  4. 4

    Push

    Day 5 — email to subscribers; homepage “current issue” slot updated.
  5. 5

    Archive

    Ongoing — issue moves to /transparency/monthly/YYYY-MM/: URL permanent, content immutable.
    MR-009

The delay rule

If an issue will run more than five working days late, we publish a delay notice with the reason — transparency about the transparency system itself. The notice counts as an on-time action; silence never does.

Cold start

The pipeline is not ready yet, so Issue #001 starts as a quarterly report covering 2026-Q4, then steps up to monthly cadence once two consecutive issues have published on time.

Never late beats never perfect

An on-time report with a range beats a perfect report that never ships. The cadence commitment outranks the content.

What this report is
— and is not

What the monthly report commits to publish — and what it refuses to publish. The boundary is a rule, not a tone.

We publish

  • Production and shipment volumes as dated ranges, per product line
  • Quality rates with definitions owned by their home pages
  • Closed-loop failures with root cause and verification
  • Open items with containment and due dates
  • SLA attainment against published commitments
  • Corrections in the open, originals retained

We don’t publish

  • Exact production counts — ranges only
  • Customer names or machine destinations
  • Supplier part numbers, prices, or third-party brand names
  • Certification statuses — single source at /transparency/certification, linked never copied
  • Unclosed failures presented as closed
Boundary with certification. This ledger reports operations — what we built, tested, shipped, fixed. Compliance status is a different question with a different owner: it lives at /transparency/certification (CRT registry). The two never mix on this page; where a corrective action touches a compliance item, the report names the CAPA and links out. Warranty terms and pricing, likewise, live at their own authoritative page — this report references, never copies.

Archive
& subscribe

Every issue lands at a permanent URL and never moves. The master index of the whole transparency system — including this page’s own version history — lives at /transparency/archive.

Subscribe

One email per issue: the six modules, the correction log, nothing else. No campaigns, no retargeting — the report is the campaign.
SUBSCRIBE TO THE MONTHLY REPORT
The only inbound actions; traffic converges into two pools — subscribe and RFQ.

Use it in diligence

Distributors preparing a factory audit are invited to read the last twelve issues first — most of the documentable portion of an audit is already here. Bring the remaining questions to the audit; we will answer them in person, and the answers will show up in the next issue.
Issue Window Cadence Publish date Status
BOLEO-MR-ISSUE-000 2026-08 Format specimen 2026-08-30 SPECIMEN · ILLUSTRATIVE
BOLEO-MR-ISSUE-001 2026-Q4 Quarterly cold start 2027-01 (≤ 5th working day) SCHEDULED · 2026-Q4
BOLEO-MR-ISSUE-002+ from 2027 Monthly, after 2 consecutive on-time issues ≤ 5th working day PLANNED