Financial Hardship Payment Plan Agreement — Apply for Affordable Repayment Support

Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.

Overall Form Summary

The Financial Hardship Payment Plan Agreement Form is an exceptionally well-designed, comprehensive instrument that serves as both a data-collection tool and a formal agreement framework. Its 15-section structure mirrors the natural flow of a hardship assessment conversation: understanding the purpose, identifying the applicant, documenting the debt, explaining the hardship, assessing income and expenses, reviewing assets, summarising the financial position, proposing a plan, requesting assistance, providing evidence, consenting to data use, declaring truthfulness, executing the agreement, recording the creditor's decision, and gathering feedback. This logical progression minimises cognitive load and ensures that every dimension of the applicant's financial situation is captured systematically. The form's inclusion of smart conditional follow-ups, computed formulas in tables, example rows, and clear placeholder text demonstrates a high level of design maturity that will produce structured, actionable data for assessors.

From a strengths perspective, the form excels in several areas: it balances thoroughness with empathy (e.g., the domestic violence follow-up asks applicants to share only what they are comfortable sharing), it provides transparency about consequences (credit reporting, plan termination), and it includes a dedicated feedback section that signals a commitment to continuous improvement. Weaknesses are relatively minor but worth noting: the sheer volume of questions may cause fatigue or abandonment, particularly for applicants under severe stress; some sections (e.g., Section 14, For Official Use Only) are irrelevant to the applicant and should be visually separated or hidden in the applicant-facing version; and the form could benefit from a save-and-return feature to accommodate applicants who need to gather documents mid-process. Overall, this is a best-in-class hardship application form that balances legal rigour, data quality, and user empathy effectively.

Purpose of This Form and How to Complete It

Do you understand the purpose of this form and how the information you provide will be used to assess a payment plan?

This opening question is a critical comprehension checkpoint that serves multiple purposes. First, it ensures the applicant has read and understood the introductory paragraphs before proceeding, reducing the risk of misinformed submissions. Second, it creates a documented record that the applicant was informed about how their data would be used, which is important for regulatory compliance (e.g., GDPR, Australian Privacy Principles, or equivalent frameworks). Third, the no follow-up provides a safety valve: if the applicant does not understand, they can articulate their confusion and receive clarification before investing time in the rest of the form.

From a design standpoint, placing this question at the very beginning is excellent practice. It sets expectations, reduces later disputes, and signals that the organisation values informed consent. The follow-up question is appropriately open-ended, allowing the applicant to describe exactly what is unclear rather than forcing them into a predefined category. This is particularly important for a hardship form where applicants may be stressed, anxious, or unfamiliar with financial terminology.

The data collected here is binary (yes/no) plus optional free text, making it easy to analyse at scale. For the no responses, the free-text field provides qualitative data that can identify common areas of confusion, informing future form improvements or FAQ content. Privacy considerations are minimal here since the question does not collect personal financial data, but the free-text response could contain sensitive information and should be handled accordingly.

From a user experience perspective, this question is low-friction and quick to answer, which is ideal for a first question. It also reassures the applicant that the organisation is transparent and willing to explain things, which can build trust early in a potentially stressful process. The placeholder text in the follow-up is helpful and empathetic, using relatable examples of what might be unclear.

Are you completing this form with the help of a financial counsellor, adviser, support worker, translator, or trusted third party?

This question addresses a critical accessibility and integrity dimension of hardship applications. Many applicants in financial distress seek assistance from professionals or trusted individuals, and the form needs to know this for several reasons: to understand who was involved in preparing the application, to verify the authority of any third party, and to ensure that the applicant is not being unduly influenced or coached. The inclusive list of helper types (counsellor, adviser, support worker, translator, trusted third party) reflects a nuanced understanding of the diverse support networks that hardship applicants rely on.

The conditional follow-up asking for the helper's full name is appropriate and proportionate. It creates accountability without being intrusive. In cases where a financial counsellor is assisting, this information is particularly valuable because it may indicate that the applicant has already received professional advice, potentially streamlining the assessment process. For translators, this information is important for accessibility compliance and record-keeping.

Data collected here is minimal (yes/no plus optional name), which is appropriate for a question that serves primarily as a flag for the assessor. The question does not collect the helper's contact details or credentials, which is a reasonable privacy choice at this stage—those details can be obtained later if needed. The question is optional (not mandatory), which is correct because not all applicants will have assistance and forcing a response could feel intrusive.

From a user experience standpoint, this question is empathetic and non-judgmental. It normalises the idea of seeking help, which can reduce stigma. The placeholder text (e.g., "Alex Morgan") is simple and clear. The question is placed early in the form, which is appropriate because the presence of a helper may influence how subsequent questions are interpreted or answered.

Section 1 — Applicant Identification and Contact Details

Full name

The full legal name is the foundational identifier for the entire application. Without it, the form cannot be linked to the correct account, the agreement cannot be legally enforced, and the assessment cannot proceed. This question is appropriately mandatory and placed at the top of the identification section, following standard form design conventions. The placeholder text (e.g., "Jordan Michael Reyes") clearly communicates the expected format, including middle names, which helps prevent incomplete submissions.

From a data quality perspective, collecting the full legal name (as opposed to a preferred name or nickname) ensures that the data matches the creditor's records and any legal documents. The follow-up question about previous or alternative names is a thoughtful addition that handles common real-world complexities such as maiden names, name changes after marriage or divorce, and spelling variations across systems. This can prevent costly delays in account matching.

Privacy considerations are standard for identity data. The legal name is personally identifiable information (PII) that must be stored securely and used only for the stated purposes. The form's privacy section later addresses this, but the early collection of this data underscores the need for robust access controls and data retention policies.

From a user experience perspective, this is a familiar and low-friction question. Most applicants will have their legal name memorised and can answer instantly. The inclusion of the alternative names question as optional is appropriate because it is a supplementary field that not all applicants will need.

Any previous or alternative names used on the account

This supplementary field is a practical addition that addresses a common source of friction in account matching and verification. Applicants who have changed their name due to marriage, divorce, deed poll, or cultural reasons may have records under multiple names. By capturing this information proactively, the form reduces the need for follow-up queries and prevents delays in processing.

The question is correctly marked as optional because not all applicants will have alternative names. Forcing this field would create unnecessary friction. The placeholder text ("maiden name, name spelling variation") is helpful and provides concrete examples that guide the applicant without being prescriptive.

From a data quality standpoint, this field improves the completeness of the applicant's identity profile. It is particularly important in jurisdictions where name changes are common or where the creditor's legacy systems may not have been updated. The data collected is simple text and poses minimal privacy risks beyond the standard PII considerations.

From a user experience perspective, this question is quick and easy to answer for those who need it and can be safely skipped by others. Its placement immediately after the full legal name is logical and intuitive. The question does not require any supporting documentation at this stage, which keeps the initial experience light.

Date of birth

The date of birth is a critical identity verification field that is mandatory for virtually all financial agreements. It serves as a secondary identifier alongside the legal name, helping to disambiguate applicants with common names and to verify identity against government databases or credit bureau records. Its mandatory status is entirely appropriate and consistent with industry standards.

From a data quality perspective, the date field type ensures a standardised format (e.g., DD/MM/YYYY or MM/DD/YYYY depending on locale), reducing errors that would arise from free-text date entry. This is important for automated verification processes and for matching records across systems. The date of birth is also used to assess the applicant's age, which may be relevant for legal capacity, pension eligibility, or age-related concessions.

Privacy considerations are significant here. Date of birth is a key component of identity theft and must be stored with strong encryption and access controls. The form's privacy section addresses data handling, but the sensitivity of this field warrants additional emphasis in the organisation's data protection policies.

From a user experience perspective, this is a universally familiar question that most applicants can answer instantly. The date picker (implied by the date field type) prevents format errors and is accessible. The question is short and placed logically within the identification section, contributing to a smooth flow.

Government or tax identification number (if required for verification)

This field is conditionally relevant, as indicated by the parenthetical "if required for verification." It is correctly marked as optional because the requirement for a government ID varies by jurisdiction, account type, and creditor policy. For some debts (e.g., tax debts or government-related obligations), this number is essential; for others (e.g., a utility account), it may not be needed.

From a data quality perspective, the placeholder text ("ID, tax file, or social security reference") is broad enough to accommodate different identification systems across jurisdictions. This flexibility is important for a form that may be used internationally or across different regulatory environments. The field is a single-line text input, which is appropriate for short alphanumeric identifiers.

Privacy considerations are paramount. Government identification numbers are among the most sensitive pieces of personal data and are subject to strict regulatory requirements in many jurisdictions (e.g., GDPR, PCI-DSS, or local equivalents). The form should ensure that this data is encrypted at rest and in transit, and that access is restricted to authorised personnel only.

From a user experience perspective, the optional nature of this field is a strength. Applicants who do not need to provide it can skip it without feeling blocked. The placeholder text provides enough guidance without being overwhelming. The question is placed logically within the identification section and does not disrupt the flow.

Email address

The email address is a mandatory field that serves as the primary digital communication channel for the application. It is used for sending acknowledgments, requesting additional information, providing decisions, and delivering the formal payment plan agreement. Its mandatory status is essential because without a reliable email address, the creditor cannot communicate efficiently with the applicant, and the application process could stall.

From a data quality perspective, the placeholder text ("jordan.reyes@example.com") clearly communicates the expected format. Ideally, the form would include email validation (e.g., regex check) to catch common errors like missing @ symbols or domain names. The email address is also used for identity verification and may be cross-referenced with existing account records.

Privacy considerations include the need to protect email addresses from unauthorised access and to comply with anti-spam regulations (e.g., CAN-SPAM, GDPR) when sending communications. The form's later section on communication preferences addresses how the email will be used, which is good practice.

From a user experience perspective, this is a standard and expected question. The placeholder text is helpful and the field is short and easy to complete. The mandatory status is appropriate because email is the most efficient communication channel for a process that may involve multiple rounds of correspondence.

Primary telephone or mobile number

The primary telephone or mobile number is a mandatory field that provides a direct voice communication channel. It is essential for urgent matters, verification calls, and situations where email is not sufficient (e.g., discussing sensitive details or clarifying complex information). Its mandatory status is appropriate because the creditor needs at least one direct contact method beyond email.

From a data quality perspective, the placeholder text ("+00 123 456 789") suggests an international format, which is a good practice for forms that may be used across jurisdictions. The field should ideally include phone number validation to catch common errors. The phone number is also used for identity verification and may be cross-referenced with account records.

Privacy considerations include the need to protect phone numbers from unauthorised access and to comply with telemarketing and telecommunications regulations. The form's communication preferences section addresses how the phone number will be used, which is good practice.

From a user experience perspective, this is a standard question that most applicants can answer quickly. The mandatory status is reasonable because the creditor needs multiple contact methods for a process as important as a hardship arrangement. The placeholder text is clear and helpful.

Alternative telephone number

This optional field provides a backup contact method, which is particularly valuable in hardship situations where the applicant's primary phone may be disconnected, lost, or unreliable. It reflects a practical understanding of the challenges faced by applicants in financial distress and demonstrates empathy in the form's design.

From a data quality perspective, the placeholder text ("work or landline number") provides helpful context about the types of alternative numbers that might be provided. The field is correctly optional because not all applicants will have an alternative number, and forcing one would create unnecessary friction.

Privacy considerations are similar to the primary phone number. The alternative number should be stored securely and used only for the stated purposes. If the alternative number belongs to a third party (e.g., a family member), the form should ideally include a note about consent, though this is a minor consideration.

From a user experience perspective, this question is quick and easy to answer for those who have an alternative number and can be safely skipped by others. Its placement immediately after the primary phone number is logical and intuitive.

Current residential address

The current residential address is a mandatory field that serves multiple critical purposes: it is used for identity verification, for sending physical correspondence (if needed), for assessing the applicant's housing situation and associated costs, and for legal purposes (e.g., serving notices). Its mandatory status is entirely appropriate for a formal financial agreement.

From a data quality perspective, the multiline text format allows for a complete address including street, suburb/city, region/state, and postal code. The placeholder text ("Street address, suburb or city, region or state, postal code") clearly communicates the expected components. Ideally, the form would include address validation or autocomplete to improve accuracy and reduce errors.

Privacy considerations are significant. Residential addresses are sensitive PII that must be stored securely. In cases of domestic violence or safety concerns, the address may need to be handled with additional confidentiality protections. The form's later question about domestic violence as a hardship cause should trigger enhanced privacy protocols.

From a user experience perspective, this is a standard and expected question. The multiline format is appropriate for addresses and the placeholder text is helpful. The mandatory status is reasonable given the legal and operational importance of the address.

Date you moved to this address

This optional field provides context about the applicant's housing stability. A recent move may indicate a significant life change (e.g., separation, eviction, job relocation) that is relevant to the hardship assessment. A long tenure at one address may suggest stability. This information helps the assessor understand the applicant's circumstances more fully.

From a data quality perspective, the date field type ensures a standardised format. The field is correctly optional because the move date may not be relevant for all applicants, and some may not remember the exact date. The question is placed logically within the address section.

Privacy considerations are minimal for this field. The move date is not particularly sensitive on its own, though it could be used in combination with other data to build a profile. Standard data protection practices apply.

From a user experience perspective, this question is quick and easy to answer for those who remember their move date and can be safely skipped by others. It does not disrupt the flow of the form and provides valuable supplementary information.

Preferred method of contact

This mandatory single-choice question is essential for ensuring that the creditor can communicate with the applicant effectively throughout the hardship process. Different applicants have different communication preferences and constraints (e.g., no access to email, hearing impairment, preference for written records), and respecting these preferences is both a practical necessity and a matter of good customer service.

The six options (Email, Telephone call, SMS or text message, Post or mail, In person, Through my representative) cover a comprehensive range of communication channels. The conditional follow-ups are particularly well-designed: selecting Email prompts for the best email address, selecting SMS prompts for the mobile number, and selecting "Through my representative" prompts for the representative's name and relationship. These follow-ups ensure that the chosen communication method is actionable.

From a data quality perspective, the single-choice format prevents ambiguity and ensures structured data. The conditional follow-ups capture the specific details needed to execute the chosen communication method. This is excellent form design that balances simplicity with completeness.

Privacy considerations include the need to protect the chosen contact details and to comply with communication preferences in all correspondence. The form's later section on electronic communications consent further addresses this.

From a user experience perspective, this question is clear, quick, and empowering. It gives the applicant control over how they are contacted, which is particularly important for vulnerable individuals who may have safety concerns or accessibility needs. The mandatory status is appropriate because the creditor must know how to reach the applicant.

Best time of day to reach you

This optional question is a thoughtful addition that improves the efficiency of communication. By knowing when the applicant is available, the creditor can schedule calls at convenient times, reducing the risk of missed connections and improving the overall experience. This is particularly important for applicants who work irregular hours, have caregiving responsibilities, or share a phone with others.

The five options (Morning, Afternoon, Evening, Any time, Weekends only) cover a practical range of availability patterns. The time ranges (before 12:00, 12:00 to 17:00, after 17:00) are clear and unambiguous. The field is correctly optional because not all applicants will have a strong preference.

From a data quality perspective, the single-choice format ensures structured data that can be easily used to schedule communications. The data is low-sensitivity and poses minimal privacy risks.

From a user experience perspective, this question demonstrates respect for the applicant's time and circumstances. It is quick to answer and does not create friction. Its placement after the preferred contact method is logical and intuitive.

Current housing or residential status

This mandatory single-choice question is critical for understanding the applicant's housing costs and stability, which are among the largest components of any household budget. The seven options (Own outright, Own with a mortgage, Renting privately, Renting through a housing or community provider, Living with family or friends, Temporary or emergency accommodation, Other) cover a comprehensive range of housing situations.

The conditional follow-ups are excellent: selecting "Renting privately" prompts for the rent amount, selecting "Renting through a housing or community provider" prompts for the rent/contribution amount, selecting "Living with family or friends" prompts for a description of the arrangement and contribution, and selecting "Other" prompts for a description. These follow-ups capture the specific financial details needed for the budget assessment in Section 5.

From a data quality perspective, the single-choice format with conditional follow-ups produces structured, actionable data. The housing status is a key input for the affordability assessment and for understanding the applicant's vulnerability (e.g., temporary or emergency accommodation may indicate acute distress).

Privacy considerations include the sensitivity of housing information, particularly for applicants in emergency accommodation or domestic violence situations. The form should ensure that this data is handled with appropriate confidentiality.

From a user experience perspective, the question is clear and the options are comprehensive. The conditional follow-ups are relevant and not overwhelming. The mandatory status is appropriate because housing costs are essential for the affordability assessment.

Number of dependants who rely on your income

This optional numeric field captures a key factor in the affordability assessment. Dependants increase essential expenses (food, clothing, education, healthcare) and may reduce the applicant's ability to make repayments. The field is correctly optional because some applicants will have zero dependants, and forcing a response would be redundant.

From a data quality perspective, the numeric field type prevents non-numeric entries and ensures clean data. The placeholder text ("e.g. 2") is simple and clear. The data is used in conjunction with the expenses section to build a complete picture of the applicant's financial obligations.

Privacy considerations are moderate. The number of dependants is not highly sensitive on its own but contributes to the overall financial profile. Standard data protection practices apply.

From a user experience perspective, this question is quick and easy to answer. It is placed logically within the identification section and does not disrupt the flow. The optional status is appropriate.

Do any dependants have additional needs, such as disability, chronic illness, or full-time study?

This optional yes/no question with a conditional follow-up captures important contextual information about the applicant's household. Dependants with additional needs (disability, chronic illness, full-time study) generate higher expenses and may affect the applicant's ability to work or earn income. This information is valuable for the assessor in understanding why the applicant's expenses may be higher than average.

The conditional follow-up ("Please describe the additional needs and any related costs") is appropriately open-ended, allowing the applicant to provide specific details. The placeholder text ("one child requires weekly therapy and specialised equipment") is empathetic and provides a relatable example.

From a data quality perspective, the yes/no format is clean and the follow-up captures qualitative detail. The data is used to contextualise the expenses in Section 5 and to assess the applicant's overall financial pressure.

Privacy considerations are significant. Information about disability or chronic illness is sensitive health data that must be handled with enhanced confidentiality protections under most data protection frameworks (e.g., GDPR Article 9, Australian Privacy Act). The form should ensure that this data is stored securely and accessed only by authorised personnel.

From a user experience perspective, this question is empathetic and non-judgmental. The optional status is appropriate because not all applicants will have dependants with additional needs. The follow-up is optional and open-ended, giving the applicant control over how much they share.

Do you require an interpreter, accessible format, or other communication support?

This optional yes/no question is a critical accessibility feature that ensures the form and subsequent communications are accessible to all applicants. It reflects a commitment to equity and inclusion, which is particularly important for a hardship form that may be used by vulnerable populations including non-native speakers, people with disabilities, and elderly applicants.

The conditional follow-up ("Please specify the language, format, or support required") is practical and actionable. The placeholder text ("large print, sign language interpreter, Spanish") provides helpful examples. This information allows the creditor to arrange appropriate support before and during the assessment process.

From a data quality perspective, the yes/no format is clean and the follow-up captures specific requirements. The data is operationally important for ensuring effective communication and compliance with accessibility legislation (e.g., Disability Discrimination Act, Equality Act).

Privacy considerations include the potential sensitivity of disability or language information. This data should be handled with appropriate confidentiality and used only for the stated purposes.

From a user experience perspective, this question is inclusive and empowering. It signals that the organisation is committed to accessibility and is willing to accommodate diverse needs. The optional status is appropriate because not all applicants will require support.

Section 2 — Account and Existing Debt Details

Account or reference number for the debt covered by this form

The account or reference number is the primary identifier for the debt being addressed by this form. It is mandatory because without it, the creditor cannot locate the correct account, assess the current balance, or apply any agreed payment plan. This field is the bridge between the applicant's identity (Section 1) and the specific financial obligation being restructured.

From a data quality perspective, the placeholder text ("ACCT-000000") provides a clear format example. The single-line text format is appropriate for alphanumeric reference numbers. Ideally, the form would validate this against the creditor's database in real-time to catch errors early.

Privacy considerations are moderate. Account numbers are sensitive financial data that must be protected. They should be stored securely and masked where possible in communications.

From a user experience perspective, this is a standard question that most applicants can answer from their billing statements or account correspondence. The mandatory status is appropriate and the question is placed logically at the start of the account section.

Type of account or debt

This mandatory single-choice question categorises the debt, which is essential for the assessor to understand the nature of the obligation and apply appropriate policies. Different debt types (personal loan, credit card, mortgage, utility, medical, etc.) have different regulatory requirements, hardship policies, and typical resolution pathways. The comprehensive list of 11 options covers virtually all common debt types.

From a data quality perspective, the single-choice format ensures clean, categorised data that can be easily analysed and routed to the appropriate assessment team. The inclusion of "Other" as an option ensures that unusual debt types are not excluded.

Privacy considerations are minimal for this field. The debt type is not particularly sensitive on its own but contributes to the overall financial profile.

From a user experience perspective, the question is clear and the options are comprehensive. The mandatory status is appropriate because the debt type is essential for the assessment. The question is placed logically within the account section.

Date the account was opened or the debt was incurred

This optional date field provides context about the age of the debt, which can be relevant for the assessment. A long-standing account with a good payment history that has recently fallen into hardship may be treated differently from a new account that was never in good standing. The date also helps the assessor understand the timeline of the obligation.

From a data quality perspective, the date field type ensures a standardised format. The field is correctly optional because some applicants may not remember the exact date, and the creditor's records should already contain this information.

Privacy considerations are minimal. The account opening date is not particularly sensitive.

From a user experience perspective, this question is quick to answer for those who know the date and can be safely skipped by others. It does not disrupt the flow of the form.

Original amount borrowed or original balance

This optional currency field captures the starting point of the debt, which provides context for the current balance and the repayment history. A large original balance that has been significantly reduced may indicate a good payment history, while a balance close to the original amount may indicate minimal progress. This information helps the assessor understand the trajectory of the debt.

From a data quality perspective, the currency field type ensures a standardised numeric format. The placeholder text ("e.g. 15000") provides a clear example. The field is correctly optional because the creditor's records should already contain this information.

Privacy considerations are moderate. The original balance is financial data that should be protected.

From a user experience perspective, this question is quick to answer for those who know the amount and can be safely skipped by others. It provides useful context without being burdensome.

Current outstanding balance

The current outstanding balance is a mandatory currency field that is absolutely essential for the hardship assessment. It is the starting point for calculating the total debt, determining the repayment timeline, and assessing whether the proposed payment plan is realistic. Without this figure, the entire assessment cannot proceed.

From a data quality perspective, the currency field type ensures a standardised numeric format. The placeholder text ("e.g. 9840") provides a clear example. Ideally, the form would cross-reference this with the creditor's records to verify accuracy.

Privacy considerations are significant. The outstanding balance is sensitive financial data that must be stored securely and used only for the stated purposes.

From a user experience perspective, this is a standard question that most applicants can answer from their recent statements. The mandatory status is entirely appropriate. The question is placed logically within the account section.

Regular minimum payment normally required

This optional currency field captures the standard payment obligation, which provides context for the applicant's financial strain. A high minimum payment relative to income may explain the hardship, while a low minimum payment that is still unmet may indicate a more severe financial crisis. This information helps the assessor calibrate the proposed payment plan.

From a data quality perspective, the currency field type ensures clean data. The placeholder text ("e.g. 320") provides a clear example. The field is correctly optional because the creditor's records should already contain this information.

Privacy considerations are moderate. The minimum payment is financial data that should be protected.

From a user experience perspective, this question is quick to answer and provides useful context. It does not create friction.

Number of payments missed or months in arrears

This optional numeric field quantifies the extent of the payment default, which is a key indicator of the severity of the hardship. A large number of missed payments may indicate a long-standing crisis, while a small number may indicate a recent shock. This information helps the assessor prioritise the application and determine the appropriate level of intervention.

From a data quality perspective, the numeric field type prevents non-numeric entries. The placeholder text ("e.g. 4") provides a clear example. The field is correctly optional because the creditor's records should already contain this information.

Privacy considerations are moderate. The arrears information is financial data that should be protected.

From a user experience perspective, this question is quick to answer and provides useful context. It does not create friction.

Current arrears amount (if applicable)

This optional currency field captures the monetary value of the arrears, which is essential for calculating the total amount owed and for determining whether the proposed payment plan includes a component for clearing arrears. The parenthetical "if applicable" is helpful because not all applicants will have arrears (e.g., if they have been making partial payments).

From a data quality perspective, the currency field type ensures clean data. The placeholder text ("e.g. 1280") provides a clear example. The field is correctly optional.

Privacy considerations are moderate. The arrears amount is financial data that should be protected.

From a user experience perspective, this question is quick to answer and the "if applicable" qualifier reduces anxiety for applicants who are not in arrears.

Have you previously been placed on a hardship arrangement or payment plan with this organisation?

This optional yes/no question with a conditional follow-up is important for understanding the applicant's history with the creditor. A previous hardship arrangement that ended successfully may indicate good faith and a track record of compliance. A previous arrangement that was defaulted may indicate ongoing or worsening financial difficulties. This information is critical for the assessor's decision-making.

The conditional follow-up ("Please provide details of the previous arrangement, including dates and why it ended") is appropriately detailed and captures the key information needed. The placeholder text ("reduced payments of 150 per month from March to September last year, ended when my hours were cut") is realistic and helpful.

From a data quality perspective, the yes/no format is clean and the follow-up captures qualitative detail. The data is used to assess the applicant's reliability and the sustainability of the proposed plan.

Privacy considerations are moderate. Previous hardship arrangements are sensitive financial history that should be protected.

From a user experience perspective, this question is straightforward and the follow-up is clear. The optional status is appropriate because not all applicants will have a previous arrangement.

Is the account currently with a debt collection agency, in dispute, or subject to legal action?

This optional yes/no question with a conditional follow-up is critical for understanding the urgency and complexity of the situation. An account with a debt collection agency or subject to legal action requires immediate attention and may involve additional stakeholders (e.g., lawyers, courts). This information helps the assessor prioritise the application and coordinate with relevant parties.

The conditional follow-up ("Please describe the current status, including any reference numbers, hearing dates, or deadlines") is practical and captures the key operational details. The placeholder text ("referred to collections on 12 March, letter received with a 21-day response deadline") is realistic and helpful.

From a data quality perspective, the yes/no format is clean and the follow-up captures actionable detail. The data is used to assess urgency and to coordinate the response.

Privacy considerations are significant. Legal and collection information is sensitive and may be subject to legal privilege or other protections.

From a user experience perspective, this question is clear and the follow-up is practical. The optional status is appropriate because not all applicants will be in this situation.

Do you owe money to other creditors or service providers?

This optional yes/no question with a conditional follow-up introduces the Schedule of Other Debts table. It is important for the assessor to understand the applicant's total financial obligations, not just the debt covered by this form. A comprehensive picture of all debts is essential for assessing what payment level is genuinely affordable and sustainable.

The conditional follow-up (a paragraph instructing the applicant to list every other debt) is clear and directs the applicant to the table below. This is a good use of form structure to guide the applicant through a complex data entry task.

From a data quality perspective, the yes/no format is clean and the table provides structured data. The data is used to calculate total monthly debt payments, which is a key input for the affordability assessment in Section 7.

Privacy considerations are significant. Information about other debts is sensitive financial data that must be protected.

From a user experience perspective, this question is clear and the table format is familiar. The optional status is appropriate because some applicants may have no other debts.

Schedule of Other Debts and Financial Commitments (Table)

This table is an excellent data collection tool that captures a comprehensive picture of the applicant's other financial obligations. The seven columns (Creditor name, Debt type, Outstanding balance, Required payment per month, Months in arrears, Currently in a hardship arrangement?, Total owed plus payments due) cover all the key dimensions needed for the affordability assessment. The computed formula in the last column (column3+column4) automatically calculates the total, reducing errors and improving data quality.

The inclusion of example rows (Example Bank, Example Finance Co.) is a best practice that guides the applicant on the expected format and level of detail. The example rows demonstrate realistic values and show how the computed column works. This reduces confusion and improves the quality of the submitted data.

From a data quality perspective, the table format ensures structured, tabular data that can be easily analysed. The computed formula prevents arithmetic errors. The columns are well-chosen and cover the essential information.

Privacy considerations are significant. The table contains detailed financial information about multiple creditors, which must be stored securely and used only for the stated purposes.

From a user experience perspective, the table format is familiar and the example rows are helpful. The table allows the applicant to list all their debts in one place, which is more efficient than separate questions. The computed column reduces the cognitive load on the applicant.

Section 3 — Circumstances Causing Financial Hardship

What are the main causes of your current financial hardship? (Select all that apply)

This mandatory multiple-choice question is the heart of the hardship assessment. It identifies the root causes of the applicant's financial difficulties, which is essential for understanding the nature, severity, and likely duration of the hardship. The comprehensive list of 17 options covers virtually all common causes of financial hardship, from job loss and illness to natural disasters and family breakdown.

The conditional follow-ups are exceptionally well-designed. Each major cause (job loss, illness, family breakdown, domestic violence, natural disaster, business failure, other) has a tailored follow-up question that captures the specific details relevant to that cause. The domestic violence follow-up is particularly thoughtful: it asks the applicant to share only what they are comfortable sharing and offers a referral to specialist support services. This demonstrates a high level of empathy and awareness of the sensitivities involved.

From a data quality perspective, the multiple-choice format with conditional follow-ups produces both structured (categorised) and unstructured (narrative) data. This combination is ideal for assessment purposes: the categories enable routing and prioritisation, while the narratives provide context and nuance.

Privacy considerations are paramount, especially for sensitive categories like domestic violence, mental health, addiction, and gambling. These categories may trigger enhanced confidentiality protections and should be handled with extreme care.

From a user experience perspective, the question is clear and the options are comprehensive. The ability to select multiple causes reflects the reality that financial hardship is often caused by a combination of factors. The conditional follow-ups are relevant and not overwhelming. The mandatory status is appropriate because the cause of hardship is essential for the assessment.

Date the hardship situation began

This mandatory date field establishes the timeline of the hardship, which is critical for assessing its duration, severity, and likely trajectory. A hardship that began recently may be temporary, while one that has persisted for months or years may be more entrenched. The date also helps the assessor verify the applicant's narrative and assess whether the proposed payment plan is realistic.

From a data quality perspective, the date field type ensures a standardised format. The mandatory status is appropriate because the timeline is essential for the assessment.

Privacy considerations are minimal for this field on its own, though it contributes to the overall hardship profile.

From a user experience perspective, this question is straightforward and quick to answer. The mandatory status is reasonable given its importance to the assessment.

How long do you expect the hardship situation to last?

This mandatory single-choice question captures the applicant's expectation about the duration of the hardship, which is a key factor in designing a sustainable payment plan. A short-term hardship may warrant a temporary payment reduction or pause, while a long-term or permanent hardship may require a more fundamental restructuring of the debt.

The six options (Less than 3 months, 3 to 6 months, 6 to 12 months, More than 12 months, Ongoing or permanent, Uncertain at this time) cover a practical range of durations. The inclusion of "Uncertain at this time" is important because many hardship situations are unpredictable.

From a data quality perspective, the single-choice format ensures clean, categorised data. The mandatory status is appropriate because the expected duration is essential for the assessment.

From a user experience perspective, the question is clear and the options are easy to understand. The mandatory status is reasonable.

Is the hardship likely to be temporary or ongoing?

This mandatory single-choice question with conditional follow-ups complements the previous question by capturing the nature of the hardship (temporary vs. ongoing) and the specific details of the expected trajectory. The five options (Temporary with clear end date, Temporary with uncertain end date, Ongoing but improving, Ongoing and unlikely to change, Permanent) provide a nuanced classification that is directly relevant to the payment plan design.

The conditional follow-ups are excellent: selecting "Temporary, with a clear end date" prompts for the expected end date; selecting "Ongoing, but my situation is improving" prompts for a description of the improvements; and selecting "Ongoing and unlikely to change" prompts for a description of the factors. These follow-ups capture the specific details needed to design a realistic plan.

From a data quality perspective, the single-choice format with conditional follow-ups produces structured and narrative data. The mandatory status is appropriate because the nature of the hardship is essential for the assessment.

From a user experience perspective, the question is clear and the follow-ups are relevant. The mandatory status is reasonable.

Please describe in your own words how this situation has affected your ability to make repayments

This mandatory open-ended question is one of the most important in the form. It allows the applicant to tell their story in their own words, providing context and nuance that structured questions cannot capture. The assessor can use this narrative to understand the human impact of the hardship and to assess the sincerity and severity of the application.

The placeholder text ("my income dropped by half while my rent and medical costs increased, leaving nothing after essential expenses") is realistic and helpful. It shows the applicant the level of detail expected without being prescriptive.

From a data quality perspective, the open-ended format produces rich qualitative data that is invaluable for assessment. The mandatory status is appropriate because this narrative is a key component of the hardship case.

Privacy considerations are significant. The narrative may contain sensitive personal information that must be handled with appropriate confidentiality.

From a user experience perspective, this question is empowering because it gives the applicant a voice. The mandatory status is reasonable, though the form should be prepared for applicants who find it difficult to articulate their situation (e.g., due to stress, literacy, or language barriers).

Have you taken, or are you planning to take, steps to improve your financial situation?

This optional yes/no question with a conditional follow-up captures the applicant's proactive efforts to address their financial difficulties. An applicant who has already taken steps (e.g., reducing spending, seeking benefits, getting financial counselling) demonstrates good faith and a commitment to resolving the situation. This information is valuable for the assessor in assessing the sustainability of the proposed plan.

The conditional follow-up is a multiple-choice question listing nine common steps (applied for additional work, reduced spending, sold assets, sought government assistance, sought financial counselling, entered a debt agreement, sought medical treatment, renegotiated rent/mortgage, other). This is a well-designed follow-up that captures structured data about the applicant's efforts.

From a data quality perspective, the yes/no format is clean and the follow-up produces categorised data. The data is used to assess the applicant's commitment and the likelihood of the plan's success.

From a user experience perspective, this question is positive and empowering. It focuses on what the applicant has done rather than what they have failed to do, which is a good approach for a hardship form.

Have you received independent financial counselling or legal advice about this situation?

This optional yes/no question with conditional follow-ups (both yes and no) is a thoughtful addition that serves multiple purposes. For applicants who have received advice, the follow-up captures the details of the advice, which can inform the assessment. For applicants who have not, the follow-up offers information about free or low-cost financial counselling and support services, which is a valuable welfare outcome.

The yes follow-up ("Please provide the name of the service or adviser and a summary of the advice received") is practical and captures the key information. The no follow-up (a checkbox requesting information about free services) is empathetic and demonstrates the organisation's commitment to supporting vulnerable applicants.

From a data quality perspective, the dual follow-ups capture both structured (yes/no, checkbox) and unstructured (narrative) data. The data is used to assess the applicant's level of support and to identify opportunities for referral.

From a user experience perspective, this question is empathetic and supportive. It normalises the idea of seeking help and offers practical assistance to those who have not yet done so.

Are you at risk of losing your home, essential services, or essential transport if this matter is not resolved?

This optional yes/no question with a conditional follow-up is a critical urgency indicator. An applicant at risk of losing their home, essential services (e.g., electricity, water), or essential transport (e.g., a vehicle needed for work) requires immediate attention and may need emergency measures beyond a standard payment plan. This question helps the assessor prioritise the application and identify applicants who need urgent intervention.

The conditional follow-up ("Please describe the immediate risk and any deadlines you are facing") is practical and captures the key operational details. The placeholder text ("utility disconnection notice with a cutoff date of 20 May") is realistic and helpful.

From a data quality perspective, the yes/no format is clean and the follow-up captures actionable detail. The data is used to triage the application and to identify emergency situations.