AFFORDABLE HOUSING AND COMMUNITY DEVELOPMENT
Homes, residents and funders, kept on one record.
From a household's first application to the funder's yearly report, on the same platform and the same built-in security.
A worked example: affordable housing on Alaflow.
Every screen and step below is illustrative. They show how the platform handles this kind of work, set up the way your own rules require.
Housing authorities and community development organisations serve two groups at once: the households who need a home, and the funders and partners who make homes possible. Both depend on the same records. A household applies, is checked against the rules of a programme, waits for a suitable home, and is then supported, recertified and inspected over the years that follow. The funder, meanwhile, expects regular reports that show who was helped and how the money was used, without exposing the personal details of the people behind the numbers.
The service on this page is an affordable housing programme service. Each household has one record that holds its application, documents, support plan and history, and the funder’s report is built from the same records, with protected identifiers left out. Households follow their own case in a portal. The sections below show how that service is made up.
What this service is made of.
The people who use it
Staff work on their own screens. People outside your organisation use a separate portal.
- Housing staff
- Applicants and residents on the portal
- Funders and partners, with a limited view
Your services
Set up for each kind of work, in days, and changed as your rules change.
- Affordable housing and community development
This layer and the two below it are set up in days and changed as your rules change.
What you keep track of
recordsThe record types your services need.
- An applicant household
- A waitlist place
- A unit and its lease
- An income recertification
- A support plan
- A repair or home-purchase file
- A funder and a grant
- A report to a funder
What each record can do
capabilitiesBuilding blocks you switch on for each record type.
- Stages with deadlines
- Tasks and checklists
- Versioned documents
- Interactions
- Reports
- A portal for residents and applicants
What is built in
controlsBuilt in from the first day, tuned to your rules when your services are built, and not switched off by accident.
- Access control
- Classification
- Protected identifiers
- Retention and legal hold
- Audit trail
- Emergency access
Built in from day one. Cannot be switched off by accident.
A worked storyline.
How one household's case could move, and where the funder's report comes from.
- A household applies on the portal and adds income documents.
- Staff check the application against the income limits for the programme.
- The household joins a waitlist and is matched to a suitable unit.
- A support plan tracks the help a household needs: rent assistance, work, childcare, referrals.
- Each year the household is recertified, the unit is inspected and maintenance requests are tracked.
- The funder’s yearly report is built from the same records, with protected identifiers left out.
More than one kind of programme.
The same building blocks serve each of these.
Applications and waitlists
Resident support
Home purchase and repair
Compliance and upkeep
Where the two sides meet.
Relationship records and case records can inform each other, with access still decided by role.
Reporting to funders
Working with landlords
Community land trusts
What already works.
The capabilities underneath are available today.