{"v":"

Background.<\/strong> Forms V2 is the new paperwork system for client visits. During a visit, staff go through an on-screen interview with the client, and the system fills in the agency's paper forms (Form 3040, the PAS service plan, the consent forms and so on) from the answers. The client then signs on screen. On 29 Sep 2026 Jane showed the customer the Start of Care \/ Annual (SOC\/AO) visit on site. This issue is one item from their feedback (item G1<\/strong> in docs\/ActionItems.md<\/code>).<\/p>\n

What the customer asked<\/h2>\n
\n

"We need to use their labels and questions please. If we don't their people will be confused."\n"Make labels on questions same as on form."<\/p>\n<\/blockquote>\n

How it works today<\/h2>\n

Each interview question is a plain-English rewording written for the visit, e.g. "Is Attendant A competent to do the tasks?". The form's own wording is shown underneath as explanatory text, but it is not the label. Staff trained on the paper forms can't recognise the questions.<\/p>\n

What to do<\/h2>\n

Make the form's printed wording the question label. This reverses an earlier design choice (FormsV2Plan \u00a74.1.2).<\/p>\n

Decision needed from the customer<\/h2>\n

Some answers print on several<\/strong> forms, and each form may word the question differently (one "shared" question fills all of them). For those, which wording do we show?<\/p>\n

    \n
  • one form's wording wins (which form?), or<\/li>\n
  • show each form's wording, listing the forms the answer fills.<\/li>\n<\/ul>\n

    Technical notes<\/h2>\n

    Interview files: docs\/form-v2-interviews\/SOC_AO.json<\/code>. Shared elements: code\/form_v2_shared.inc.php<\/code>. Related: G2 (question numbers), G3 (form names), G4 (update the docs\/memory).<\/p>\n"}