An OnlyFans weekly report you can actually use

Fix the measurement basis first

Record the start and end date, reporting time zone, currency and platform. Compare full weeks of the same length. Separate gross revenue, platform fees, agency share and the amount remaining before tax and own costs. Record refunds consistently. Do not combine an account balance awaiting payout with revenue earned during the week: they answer different questions.

A small example with a clear limit

The remaining amount rises by $48, or 10%. That observation does not establish why it rose. If a promotion and a new content format both changed, mark the attribution as uncertain. Review buyer counts and comparable offer prices before calling either change successful.

Add quality and workload

• Content: planned versus completed, with reasons for missed items.
• Chat: open paid requests, complaints and items waiting for creator approval.
• Marketing: visits and subscriptions only where the attribution can be observed. Mark missing data as unknown.
• Creator workload: hours spent and boundaries that need adjustment.
• Next week: one hypothesis, one accountable person and a review date.

Turn the meeting into a decision

Use three lines at the end: what we observed, what we think explains it and what we will change. For example: visits stayed level but new subscriptions fell; the offer page may be unclear; review the profile text while keeping the price unchanged. This is a testable hypothesis, not proof. In the following report, compare the same measures and record whether the change was kept or reversed.

The downloadable report template contains empty measurement fields, a fictional worked example and a decision log. It works locally and asks for no fan-level data.