Profiling → /assessments
Assessments is a general questionnaire engine. You define a questionnaire, publish a version, and officers capture submissions against it — in an office or on a phone during a field visit.
It exists because profiling forms change. Rather than building a screen per questionnaire and shipping a release every time a question is reworded, the questionnaire is data: revise it, publish a new version, and capture against it the same day.
The pieces
| Concept | Meaning |
|---|---|
| Questionnaire (template) | The named form — "Beneficiary profiling", "Move-out inspection", "Arrears cause interview". |
| Version | A published, immutable revision of a questionnaire. Answers are recorded against the version that was live when they were captured. |
| Submission | One completed capture, against a subject (typically a lease or resident). |
The pages
| Page | Route | Purpose |
|---|---|---|
| Profiling | /assessments | Submissions across the branch. |
| Questionnaires | /assessments/templates | The template library. |
| New questionnaire | /assessments/templates/new | Create a template. |
| Edit questionnaire | /assessments/templates/:uuid | Revise a template and publish a version. |
| Capture assessment | /assessments/capture | Fill in a questionnaire. |
| Assessment | /assessments/:uuid | A completed submission. |
Building a questionnaire
A questionnaire is organised into steps and sections containing fields.
| Capability | Use |
|---|---|
| Field types | Text, number, date, choice, and the richer types below. |
| Photo capture | Attach photographs to an answer — essential for inspections. |
| Signature capture | Capture a signature at the point of completion. |
| Repeatable groups | Repeat a set of questions per item — per household member, per room, per defect. |
| Conditional visibility | Show a question only when a previous answer warrants it. |
| Conditional requirement | Make a question mandatory only in the circumstances where it matters. |
Draft the questionnaire
Group questions into sections that match the order the conversation actually happens in. A form that jumps between topics produces worse data.
Add conditions
Use conditional visibility rather than "if not applicable, write N/A". Conditions produce clean data; free-text disclaimers do not.
Use repeatable groups for lists
Household members, rooms, defects — anything with an unknown count.
Publish a version
Published versions are immutable. Revising creates a new version rather than editing history.
Capturing an assessment
Choose the questionnaire and the subject
Typically a lease. The subject is what links the submission back to the tenancy.
Work through the sections
Conditional questions appear as the answers warrant.
Capture photos and signature where required
Photos taken at the visit are worth far more than photos taken later.
Submit
The submission is recorded against the questionnaire version that was live.
Typical uses
| Use | Questionnaire |
|---|---|
| Beneficiary profiling | Household, income and occupancy data collected during a home visit — for example under an ownership scheme. See Ownership plans. |
| Move-in / move-out inspection | Condition of the unit, with photos and a tenant signature. |
| Arrears cause interview | Structured capture of why a tenant is behind, feeding collections. |
| Owner or vendor vetting | Due-diligence questions at onboarding. |
Reading the results
Because answers are structured and versioned, submissions can be analysed rather than read one at a time: distribution of answers, comparison across branches, and change over time within one questionnaire version.
Assessments vs checklists
They are different tools and it is worth not confusing them:
| Assessment | Application checklist | |
|---|---|---|
| Purpose | Capture data | Gate a workflow stage |
| Question | "What is the household income?" | "Has the ID copy been uploaded?" |
| Versioned | Yes | No |
| Holds answer values | Yes | No |
Application checklists live in Lease applications.
Common problems
| Symptom | Cause |
|---|---|
| Cannot edit a questionnaire | Published versions are immutable — create a new version. |
| Answers missing from a report | They belong to a different questionnaire version. |
| Officers skipping questions | The questions are not conditional and do not apply — fix the form, not the officer. |
| Photos not captured | The field type is not a photo field, or the device denied camera access. |