Compliance LAQAPP
Validation Checks by Instafill.ai
1
Applicant name fields completed and title/other-title consistency
Validate that Family name and First name are provided, and that a Title option is selected. If Title is set to “Other”, require the “Give details” text to be completed and non-trivial (not blank/whitespace). If this validation fails, the submission should be rejected or routed for correction because the applicant cannot be reliably identified or addressed.
2
Other names section required when 'Yes' is selected
If the applicant indicates they have used other names, require at least one other-name entry with Family name, First name, and Type of name. If “No” is selected, ensure the other-name fields are empty to avoid conflicting data. Failure should block submission because identity matching and conflict checks may be inaccurate without complete alias information.
3
Birth date format and plausibility checks
Validate Birth date fields are in DDMMYYYY format and represent a real calendar date (including leap-year rules). Also check plausibility (e.g., not in the future and not unreasonably old such as >120 years). If invalid, prompt correction because age-based routing (e.g., financial section skip for 17 or younger) and identity verification depend on a valid DOB.
4
Age-based financial section logic (Question 3 gating)
If the applicant answers “Yes” to being 17 years or younger, enforce that the financial details section (Questions 4–9) is not required and the workflow proceeds to Question 10 as instructed. If they answer “No”, require completion of the financial details section. If inconsistent (e.g., DOB indicates 16 but they answered “No”), flag for review and require confirmation to prevent incorrect eligibility assessment.
5
Gender and 'Other' details requirement
Ensure exactly one gender option is selected, and if “Other” is selected, require the accompanying details field to be completed. If “Male” or “Female” is selected, the “Other details” field should be empty to avoid ambiguity. Failure should prevent submission because demographic fields are used for records accuracy and may affect service delivery.
6
Interpreter requirement and language/dialect completeness
If the applicant indicates they need an interpreter, require the language and dialect field to be completed with meaningful text. If they indicate “No”, ensure the language/dialect field is blank. If this fails, the form should be returned for correction because service accessibility and communication depend on accurate interpreter needs.
7
Disability and access-help conditional detail validation
If the applicant answers “Yes” to having a disability affecting access, require at least one disability type checkbox to be selected and require details when “Physical” (or any “Give details” prompt) is selected. Similarly, if they answer “Yes” to needing extra/practical help, require the “Give details” field. Failure should trigger correction because these fields drive reasonable adjustments and service planning.
8
Address completeness and Australian postcode/state validation
Require Home address, Suburb/Town, State, and Postcode to be completed. Validate Postcode is 4 digits and State is a valid Australian state/territory value (e.g., QLD, NSW, VIC, etc.), and optionally cross-check that the postcode is plausible for the selected state. If invalid, block submission because correspondence and jurisdiction handling rely on accurate address data.
9
Postal/contact address rule (blank means same as home) and partial-entry prevention
If the “Address where we can contact you” section is left blank, treat it as “same as home” and do not allow partial entries (e.g., only postcode filled). If any field in the contact address is provided, require all required address components (address line, suburb/town, state, postcode). Failure should require correction to prevent misdirected mail and inconsistent records.
10
Contact details format validation (phones and email) and minimum contact method
Validate phone numbers contain only permitted characters and meet expected Australian length patterns (e.g., 10 digits for mobile starting with 04; landlines with area code). Validate email address format if provided. Require at least one reliable contact method (mobile, home phone, work phone, or email) unless the applicant is in prison (where alternative contact may apply). If invalid, return for correction because LAQ must be able to contact the applicant about urgent court dates and eligibility.
11
Prison status and IOMS number conditional requirement
If “Are you in prison?” is “Yes”, require the prison/detention centre name and validate that an IOMS number is provided and matches an expected numeric pattern/length (as configured). If “No”, ensure prison centre and IOMS fields are empty. Failure should block submission because custody status affects communication, bail questions, and administrative lookup.
12
Financial help and self-employment conditional attachments/details
If the applicant receives financial help, require a clear indication of the helper and ensure related financial information is included in the financial assessment inputs (income/assets questions). If self-employed/small business/farmer is “Yes”, require the “Give details” field and enforce that required supporting documents are attached (e.g., tax returns for two years, bank statements for three months, profit & loss, balance sheet). If missing, mark the application incomplete because eligibility cannot be assessed without mandated evidence.
13
Centrelink/Veterans payment selection and card details validation
If Centrelink/Veterans payment is “Yes”, require at least one payment type to be selected and whether it is Full or Part. If a health care/pension card is provided, validate card number presence, expiry date format (MMYYYY) and that expiry is not in the past; also require card type selection (Health care vs Pension). If this fails, route for correction because concession status and income verification depend on accurate payment/card data.
14
Household income and dependents numeric validation and employment situation consistency
Validate that the living/employment situation selection is made and that total weekly gross household income is a valid non-negative currency amount. Validate number of dependent children under 18 is a non-negative integer. If “both not working”/“not working” is selected but income is high (or income is zero with no explanation), flag for review and require clarification at Question 18 to prevent incorrect means testing.
15
Assets section completeness and equity arithmetic checks (Question 7 a/b/c required)
Enforce that parts a), b), and c) of Question 7 are answered (Yes/No) as explicitly required by the form. When “Yes” is selected for property/real estate/vehicle, require value and debt/mortgage fields and validate equity equals value minus debt within a reasonable tolerance; also validate dates (e.g., purchase date) where requested. If missing or inconsistent, block or flag because asset equity is central to financial eligibility and errors can materially change the assessment.
16
Court/tribunal details required when court involvement is 'Yes'
If the applicant must go to court/tribunal, require court/tribunal selection, suburb/town, and next court date fields where known; validate date format (DDMMYYYY) and time format if provided. Require that court documents are attached (or a reason captured in Question 18 if unavailable). Failure should prevent submission or trigger an “incomplete—documents missing” status because urgency and correct case routing depend on accurate court information.
17
Legal problem section gating and mandatory narrative at Question 18
Require at least one legal problem pathway to be completed: criminal (Q11–12), family/relationship (Q13–16), or civil (Q17), consistent with the applicant’s selections. Always require Question 18 narrative to be non-empty and to include sufficient detail (e.g., minimum character count) especially when the checklist indicates it must be answered. If missing, reject submission because assessors cannot determine merit, urgency, or scope of aid without the narrative.
18
Criminal law consistency: charges, plea, record, and proceeds-of-crime attachments
If the applicant has been charged, require at least one charge listed and a date charged (DDMMYYYY) where applicable; if they have pleaded guilty, ensure the “How do you want to plead?” selection is consistent or require clarification. If they indicate they have a criminal record, require either an attachment or a completed list of offences/penalties/years; if proceeds-of-crime order is “Yes”, require the order attachment. Failure should block or flag because criminal eligibility and conflict/merit assessment rely on complete charge and history information.
19
Family/relationship details: orders, parties, children, and relationship dates validation
If applying for family/relationship aid, require at least one problem type to be selected and require details for domestic/family violence when that option is chosen. If current orders exist, require attachments; if a party is listed (Q15), validate their contact fields (phone/email formats) and relationship-to-you is provided. If married/defacto is “Yes”, validate marriage/relationship and separation/divorce dates (DDMMYYYY) and ensure chronological order (relationship/marriage date ≤ separation date ≤ divorce date). Failure should trigger correction because court readiness and correct service stream depend on accurate relationship and orders information.
20
Declaration, authority, and signature/date completion (including third-party completion authority)
Require the applicant (or authorised person) to indicate whether they are completing the application for themselves; if “No”, require the authority type (e.g., power of attorney/QCAT order/guardian) and the authorised person’s name. Require signatures and dates on the authority/declaration sections, and validate dates are in DDMMYYYY format and not in the future. If missing, the application must not be accepted because LAQ cannot lawfully rely on the information or request/handle sensitive records without executed declarations/authority.