{"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) for staff to confirm. 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>H2<\/strong> in <code>docs\/ActionItems.md<\/code>).<\/p>\n<h2 id=\"user-content-the-customer-s-rule\" dir=\"auto\">The customer&#39;s rule<\/h2>\n<blockquote>\n<p dir=\"auto\">&#34;Can&#39;t go over authorized hours. Can&#39;t change hours but might change time frame. Can change allotted hours per day but cannot change total hours authorized.&#34;<\/p>\n<\/blockquote>\n<h2 id=\"user-content-how-it-works-today\" dir=\"auto\">How it works today<\/h2>\n<p dir=\"auto\">Authorized weekly hours are pre-filled from the VESTA authorization, but staff can change them. We chose that on 25 Sep (dictionary 2: authorization values are asked and any difference is shown to the office).<\/p>\n<h2 id=\"user-content-what-to-do\" dir=\"auto\">What to do<\/h2>\n<ul dir=\"auto\">\n<li>Show authorized weekly hours as <strong>read-only<\/strong>, straight from VESTA. Not a question.<\/li>\n<li>This reverses the 25 Sep rule for this one value. Add it to the frozen list (<code>FORM_V2_FROZEN_KEYS<\/code>), as was done for <code>auth.program_type<\/code>.<\/li>\n<li>Check whether <code>auth.days_per_week<\/code> should be frozen too.<\/li>\n<li>If the hours are wrong, the route is the &#34;Request hours change&#34; button (H4), not an edit.<\/li>\n<\/ul>\n<h2 id=\"user-content-technical-notes\" dir=\"auto\">Technical notes<\/h2>\n<p dir=\"auto\">Element: <code>auth.weekly_hours<\/code>. Related: H3 (daily hours may move but the total can&#39;t go over), H4.<\/p>\n"}