{"v":"<p dir=\"auto\"><strong>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&#39;s paper forms from the answers. Some answers start pre-filled from VESTA (the agency&#39;s EVV\/scheduling system). 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 <strong>S4<\/strong> in <code>docs\/ActionItems.md<\/code>).<\/p>\n<h2 id=\"user-content-what-the-customer-asked\" dir=\"auto\">What the customer asked<\/h2>\n<p dir=\"auto\">The service plan&#39;s task list should show <strong>only the tasks authorized in VESTA<\/strong> for this client.<\/p>\n<h2 id=\"user-content-how-it-works-today\" dir=\"auto\">How it works today<\/h2>\n<p dir=\"auto\">The tasks are pre-ticked from VESTA, but staff see the full list of every possible task and can tick or untick any of them. The paper could then list tasks the client isn&#39;t authorized for.<\/p>\n<h2 id=\"user-content-what-to-do\" dir=\"auto\">What to do<\/h2>\n<ul dir=\"auto\">\n<li>Show only the client&#39;s VESTA tasks, read-only or confirm-only.<\/li>\n<li>Decide what happens when a task is wrong in VESTA. Probably the same route as hours: a change request to the coordinator (H4), not an edit in the visit.<\/li>\n<li>Check what &#34;Other tasks&#34; (<code>shared.plan.tasks_other<\/code>) should do.<\/li>\n<\/ul>\n<h2 id=\"user-content-technical-notes\" dir=\"auto\">Technical notes<\/h2>\n<p dir=\"auto\">Elements: <code>auth.service_tasks<\/code>, <code>shared.plan.tasks_other<\/code>. This same task list also drives T2 (task guide highlighting) and A4 (3040 orientation tasks), so build it once and reuse it.<\/p>\n"}