Monthly Reporting Templates

What this document is for

Two report templates the Lead Operator runs every month. Template A is the per-sub-affiliate monthly statement — a one-page document the Lead Operator generates and sends to each contracted sub-affiliate showing their performance, retainer due, gate status, and tier. Template B is the Lead Operator's monthly programme report — a one-page document the Lead Operator generates and sends to the founder showing programme-level totals, distributions, exits, and anomalies.

The Lead Operator runs fifty Statement A's and one Programme Report B each month. Statement A takes about three minutes per sub-affiliate (mostly auto-populated from the registry); Programme Report B takes about thirty minutes once a month. Total monthly reporting load: roughly four hours.

Both templates use the same fields every month, so historical comparison is straightforward and the founder can see trends across months without translating between formats. The format is the discipline — ad-hoc reports drift in shape and become impossible to compare.

Template A · Sub-Affiliate Statement

Sent to each sub-affiliate, monthly

The per-sub-affiliate statement.

One page per sub-affiliate. Generated by the Lead Operator from the master registry; sent to the sub-affiliate via the private channel or email. Sub-affiliate has seven days to dispute any field. After seven days the statement is final and is logged in the audit record.

Below is the template populated with placeholder fields. The Lead Operator fills in the bracketed values from the registry; the rest of the document is fixed.

Monthly Statement · [Sub-Affiliate Name]

[Month YYYY]

Channel: [primary channel] · Contract start: [date] · Statement issued: [date]

Current tier [Tier 1 · pre-delivery / Tier 2 · active / Tier 3 · performing / Tier 4 · bonus-track] [X] / 10,000 cap

[XX]

Paid users this month

[XXX]

Paid users cumulative

[XX]

Click-through this month

[X.X%]

Conversion rate

Retainer due this month

Tier-defined retainer

[$X,XXX]

Adjustments (if any)

[$0 / specify]

Total payable

[$X,XXX]

Funding source

[Founder personal / Operating Fee Reserve]

Gate status

Month 2

[date]

[Passed / Pending]

Month 4

[date]

[Pending]

Month 9

[date]

[Future]

Month 18

[date]

[Future]

Distance to next gate

Next gate

[Month X · date]

Gate threshold

[XXX paid users required]

Distance to threshold

[XX more users needed]

Pace status

[On pace / behind / ahead]

Notes from the Lead Operator

[Free-text notes — one paragraph maximum. Performance commentary, asset feedback, upcoming campaign moments, anything sub-affiliate-specific. Keep brief.]

Dispute window

If any figure on this statement is incorrect, raise it within seven days of issuance. After seven days the statement is final and is logged in the audit record. Disputes are resolved by the Lead Operator with reference to the on-chain attribution data and contract terms.

How the Lead Operator generates this: All bracketed fields are populated from the master sub-affiliate registry, which itself is updated daily from the protocol's attribution data. Once the registry is current, statement generation is roughly 3 minutes per sub-affiliate (1 minute populating fields, 1 minute writing the notes paragraph, 1 minute sending). Across fifty sub-affiliates this is 150 minutes — roughly two and a half hours per month.

Template B · Programme Report

Sent to the founder, monthly

The programme-level report.

One document per month, sent to the founder by the 5th of the following month. Covers programme-level totals, distributions across tiers and channels, gate outcomes, exits, new contracts, and anomalies. Designed to be read in 5–10 minutes by the founder, with everything they need on one page.

Programme Report · Bitcoin Storm Sub-Affiliate Programme

[Month YYYY]

Issued by: [Lead Operator name] · Issued: [date] · To: founder

Programme totals

[XX]

Sub-affiliates active

[X,XXX]

Paid users cumulative

[XXX]

Paid users this month

[X.X%]

Programme conversion rate

Founding cohort progress

Cumulative paid users (all sources)

[XXX,XXX]

Distance to 1M

[XXX,XXX]

Sub-affiliate share of total

[XX%]

Pace vs. plan

[On pace / behind / ahead by Y%]

Tier distribution

Tier	Sub-affiliates at tier	Cumulative users	Avg per sub-aff	Retainer total
Tier 1 · pre-delivery	[XX]	[XXX]	[XX]	[$X,XXX]
Tier 2 · active	[XX]	[X,XXX]	[XXX]	[$XX,XXX]
Tier 3 · performing	[XX]	[XX,XXX]	[X,XXX]	[$XX,XXX]
Tier 4 · bonus-track	[XX]	[XX,XXX]	[X,XXX]	[$XX,XXX]

Deputy layer summary

Deputy	Sub-affiliates supervised	Cohort cumulative users	Stipend this month
Deputy 01 · [name]	[~10]	[XX,XXX]	[$1,150]
Deputy 02 · [name]	[~10]	[XX,XXX]	[$1,150]
Deputy 03 · [name]	[~10]	[XX,XXX]	[$1,150]
Deputy 04 · [name]	[~10]	[XX,XXX]	[$1,150]
Deputy 05 · [name]	[~10]	[XX,XXX]	[$1,150]
Deputy pool total	~50	[XXX,XXX]	[$5,750]

Channel distribution — cumulative users by source

Channel category	Sub-affiliates	Cumulative users	Programme share
Bitcoin podcasters	[XX]	[X,XXX]	[XX%]
Newsletter / Substack	[XX]	[X,XXX]	[XX%]
Regional meetup organisers	[XX]	[X,XXX]	[XX%]
Twitter / X mid-tier	[XX]	[X,XXX]	[XX%]
YouTube creators	[XX]	[X,XXX]	[XX%]
Referrals	[XX]	[X,XXX]	[XX%]

Geographic distribution — paid users by jurisdiction

Jurisdiction	Cumulative users	Share of programme
UK	[X,XXX]	[XX%]
EU (non-UK)	[X,XXX]	[XX%]
Asia-Pacific (non-restricted)	[X,XXX]	[XX%]
Latin America	[X,XXX]	[XX%]
Africa (non-restricted)	[X,XXX]	[XX%]
Other	[X,XXX]	[XX%]

Gate outcomes this month

Sub-affiliates passing gates

[XX of XX scheduled]

Sub-affiliates exited at gates

[XX]

Exits & new contracts this month

Exits (gate failure)

[XX]

Exits (voluntary)

[XX]

Exits (House Rules breach)

[XX]

New contracts signed

[XX]

Programme financials this month

Total retainers paid

[$XXX,XXX]

Funding source breakdown

[Founder: $X,XXX · OFR: $X,XXX]

Anomalies & Lead Operator commentary

[Free-text section. The Lead Operator's qualitative read on the month: what surprised them, what's working, what isn't, what the founder should know about that the numbers don't capture. One to three paragraphs. This is the section that turns the report from a spreadsheet into something useful.]

Asks of the founder

[Anything the Lead Operator needs from the founder this month: a regulatory update to communicate, a budget question, a strategic decision, a flagged concern. Bullet-list format if there are several; prose if there's only one. If nothing is needed: "Nothing this month."]

Compilation time: Most fields auto-populate from the registry. The judgement-heavy sections (anomalies + commentary, asks of founder) are where the Lead Operator's monthly time goes. Total report compilation: ~30 minutes monthly.

"The numbers tell the founder what happened. The commentary tells them what to do about it."

Document use: Both templates are designed to be filled in monthly with data drawn from the master sub-affiliate registry and the protocol's attribution data. The structure is fixed; only the bracketed fields and free-text sections change month to month. Maintaining this fixed structure is what allows the founder to compare month against month at a glance, and what allows the audit record to remain coherent across the eighteen-month engagement. Departures from the templates require seven days' notice to anyone holding them and should be coordinated with the founder.