This article explains what Altivo is, who uses it, and how it fits into a school's sponsorship workflow. It is intended for school administrators and d6 support staff who need a high-level understanding of the platform.
Dashboard > All pages
Altivo is a web-based platform that helps schools manage their sponsorship programmes. Schools use Altivo to:
Sponsor register: Keep a central record of all sponsors and their contact details
Asset inventory: Maintain a register of sponsorship assets (billboards, jersey branding, event naming rights, PA announcements, programme adverts)
Contribution tracking: Record sponsorship contributions (cash, goods, or services)
Allocation management: Allocate specific assets to sponsors for defined time periods
Availability tracking: Track which assets are available, booked, or expiring soon
Dashboards and reports: Generate reports showing sponsorship revenue, asset utilisation, and sponsor activity
Sponsor Portal: Provide a public page where potential sponsors can browse available assets and submit enquiries
There are two types of users:
School administrators — the staff at a school who manage the sponsorship programme. They log in to Altivo to add sponsors, create sponsorships, allocate assets, and view reports.
Sponsors — external companies or individuals who sponsor the school. Sponsors do not log in to Altivo. Instead, they can view available assets on the school’s public Sponsor Portal and submit enquiries.
Altivo is built around four core entities. Think of them as the building blocks of any sponsorship deal:
| Concept | What it is | Example |
|---|---|---|
| Sponsor | A company or individual that contributes to the school | “ABC Financial Services” |
| Asset | A sponsorship opportunity the school can offer | “Main field billboard — large” |
| Sponsorship | A recorded contribution from a sponsor (cash, goods, or services) | “R50,000 cash donation from ABC Financial Services” |
| Allocation | The assignment of a specific asset to a sponsor for a defined period | “Main field billboard assigned to ABC Financial Services, 1 Feb – 30 Nov 2026” |
The relationship flows like this: a Sponsor makes a Sponsorship (contribution), and the school then Allocates one or more Assets to that sponsor as part of the deal.
A school signs up and sets up their profile (school name, address, student count, PBO number if applicable)
The school adds their sponsorship assets to the inventory (billboards, events, digital placements)
When a sponsor approaches the school, the school creates a Sponsor record
When a deal is agreed, the school records a Sponsorship with the contribution details
The school then Allocates specific assets to that sponsor for the agreed period
The dashboard shows real-time data on revenue, asset utilisation, and upcoming expiries
Optionally, the school enables their Sponsor Portal so new sponsors can discover available assets and submit enquiries
Payment processing: Altivo records that a sponsorship was received, but payment collection happens outside the platform.
School finances: Altivo does not manage non-sponsorship school finances (fees, budgets, payroll).
Automatic invoicing: Invoice generation is planned for a future release.
No. Altivo is purpose-built for school sponsorship management. Unlike a generic CRM, every feature — from asset inventory to Section 18A tax receipts — is designed around how schools manage sponsors.
No. Sponsors interact with the school through the public Sponsor Portal, which does not require a login. Only school administrators log in to manage data.
Yes. Each sponsorship can include multiple contributions of different types: Cash, Goods, or Services. The total value is the sum of all contributions.
No. Altivo is multi-tenant with complete data isolation. Each school’s data is invisible to every other school, enforced at the database level.
Yes. Altivo 2.0 is the production-grade replacement for the original AppSheet prototype. It provides the same sponsorship management capabilities with improved performance, security, and a modern web interface.
Last updated: March 2026 | Version 2.0