Read sponsorship coverage reports
The implemented Sponsorship coverage report describes current sponsorship relationships. It is an aggregate report, not a donor list, paid-instalment report, fundraising campaign dashboard or arrears calculation.
Access and location
Use the application Reports workspace and select Sponsorship coverage (charity.sponsorship-coverage) where available. It requires care.report.view, charity.sponsorship.view, CHARITY_SPONSORSHIP and CARE, alongside report execution access and business-unit scope. The report definition supports JSON, XLSX and PDF.
The current provider accepts an optional business-unit filter. It calculates current relationship coverage, not a historical as-of-date ledger reconstruction. Do not promise an as-of-date control from an older plan if it is absent in this implementation.
Columns
| Column | Current meaning |
|---|---|
| Facility | Facility name for scoped eligible people/facility sponsorships |
| Sponsorable people | Eligible alias-level beneficiaries associated with facilities in report scope |
| Sponsored | Those eligible people with at least one ACTIVE or PAUSED beneficiary sponsorship |
| Not sponsored | Eligible people without such a live relationship |
| Facility sponsorships | Live sponsorship records targeting that scoped facility |
| Programme sponsorships | Tenant-wide live programme sponsorship count, shown on total row |
| Needing transfer | Tenant-wide live beneficiary sponsorship count whose target is no longer sponsorable, shown on total row |
ACTIVE and PAUSED both count as live for this report. Multiple sponsors supporting the same person do not create multiple sponsored-person counts. Community beneficiaries without a facility business unit are not included in the per-facility people rows.
Small-count protection
Non-zero counts from 1 to 4 display as <5. Zero is not the same as a suppressed small value. The policy also requires protection for dependent totals and percentages that would reveal a suppressed count. Screen and exports use the same generated report values.
Training example: A facility's underlying small count displays as <5, not zero. Do not infer or circulate an exact small count from the protected cell or use related figures to reconstruct it.
Current implementation limitation: This provider suppresses individual cells and applies the shared total rule to facility-column totals, but does not apply a full cross-column disclosure check to the related sponsorable/sponsored/not-sponsored values within each row. The output therefore should not be treated as fully reviewed for indirect disclosure. Obtain the responsible team's review before wider circulation; this guide does not claim that the display alone satisfies every dependent-total protection requirement.
Read and export responsibly
- Confirm the report's scope and generation time.
- Review column definitions before comparing facilities.
- Read the note that programme and needs-transfer values are tenant-wide, even when facility rows are scoped.
- Use the offered supported format and preserve suppression in downstream summaries.
- Follow confidentiality procedures for the generated report.
Care report execution is access-logged. Names and beneficiary numbers are not report columns. Do not interpret sponsored coverage as proof that money has been received: commitments are not linked to donations, so this report cannot establish arrears or collection performance.