Components
The things Focus will actually build. A field can sit in as many as it needs to. Open one to get its field list grouped by who supplies each value — each group is a journey somebody has to design.
Where the household side of a job is done: the participant, whoever they are — owner-occupier, tenant, or a landlord acting for one.
Who uses it: Customer, tenant, building owner, housing authority
Where a trade ally works: the job, the measures, the costs and the evidence they are on the hook for.
Who uses it: Provider, support contractor, aggregator
Proving a household qualifies. Ben has flagged that this may sit inside the customer portal or stand on its own — undecided on purpose.
Who uses it: Customer, programme back office
The back office. Ben: “our program implementation portal is going to end up having so many views and so many fields… all of them are going to go in there.” So every field is in this one by default.
Who uses it: Program implementer and administrator
The photo and document evidence a job has to carry, and the safety checks behind it.
Who uses it: Provider, QC inspector
The over-the-counter lane: a vendor taking a coupon at the till, and the product it was spent on.
Who uses it: Vendor or retailer
The qualifying-product list a coupon is validated against. Nobody owns this yet; it is here so the fields that need it are visible.
Who uses it: Programme back office