Impact report unavailable or incomplete
What to check when your monthly impact report is missing, incomplete or disputed, before you rely on any figure in it.
Start with the report you expected
Identify the account or covered activity, month, report revision, method version, and report reference if one is shown. The report separates accepted useful work, physical activity, and cash records. A missing value is not zero, and the monthly report is not a per-task dashboard.
One task can involve a failed attempt, a retry, and an independent check. A failed attempt that ran may use electricity even when its result is rejected. A device rejected during admission is not an executed attempt; any attributable checking overhead needs its own evidence. Admission, result verification or quorum, and energy qualification answer different questions.
Open Read a Compute impact report and compare the figure you expected with the evidence and method the report names. For the calculation boundary and claim rules, read the Monthly Compute impact report methodology.
If no report appears
Check that you are viewing the right account, covered activity, month, revision, and method. A report may be unavailable for that scope or period. An unavailable report does not mean that no work ran, no electricity was used, or no invoice exists.
Do not replace it with a network-wide average, an earlier month's report, or a billing record. Keep the report reference and period you expected, then contact Lithi with those details.
If Work or energy looks incomplete
Read the evidence label before treating it as an error. A value may be a meter reading, a calibrated Mac reading, a calibrated estimate, an uncalibrated reading, or no usable measurement. The last two are recorded evidence without a reportable amount or visible gaps; neither becomes zero. Not every Mac reports direct kWh for every task.
Check whether the Work section covers accepted useful output or a broader physical-activity group. Preparation, retries, verification, cancellation tails, and other covered activity may use electricity even when the work was not accepted. When a grid-input amount already includes device electricity, the report does not add the device-load reading again.
Keep the unit, denominator, activity covered, observation period, method version, factor source, boundary, and omissions attached to the figure. A precise decimal cannot repair missing evidence.
If an emissions figure looks wrong
Check the usable energy input, units, observation period, factor source, execution or grid region, boundary, and stated uncertainty. Customer reporting region and provider business region do not prove where work ran. A benefit claim also needs a documented comparable baseline for the same kind of work and output quality.
If community value or cash looks wrong
Keep contribution time, contribution allowance, eligible allocations, and confirmed payments separate. A contribution allowance is noncash and creates no provider payout or referral payout. Contribution work can still have physical activity and electricity.
A participation figure is not a payment record. A provider allocation or accrued value is not a confirmed payment. Review billing or provider-finance evidence through its own payment record and period.
Stop when the evidence is disputed
Do not publish, compare, or extrapolate a disputed figure when its period, method, source, denominator, or covered activity cannot be established. Do not call an energy or emissions value a savings result without a documented comparison.
When you contact Lithi, include the report reference, period, field name, unit, activity covered, method, and calculation you are questioning. Leave out task content, exact provider identities or locations, private messages, and bank details.