Draft conditional forms from approved questions Get the source data and prepare the review Documentation-checked component path; proposed workflow, not tested WHAT WAS CHECKED Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution. BEFORE YOU START - Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. - Responsible lawyer/operations reviewer approves scope, definitions and any later action. - AI optional; use only approved minimized data and retain originals separately. DATA ACQUISITION LIMITS - Native form logic is documented; this workflow drafts a spec, not a generated/importable form. STOP IF - No approved questions/options, missing field map or unsupported conditional rule. KEEP THE ANALYSIS COPY SEPARATE Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. INPUT FORMAT LIMIT All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data. NATIVE REVIEW INPUTS version: 1 status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible compatibleWithoutMapping: False existingKitFilesInspected: - file: approved-script.csv firstLine: question_id,exact_wording,answer_type,required,approved_branch_rule,practice_area - file: branch-tests.csv firstLine: test_id,input_answer,expected_path,unresolved_rule - file: field-dictionary.csv firstLine: field_id,type,persist_in_crm,allowed_values - file: form-spec.csv firstLine: question_id,exact_wording,field_id,field_type,required,branch_rule,persistence - file: policy.txt firstLine: G12: policy.txt requiredNativeInputs: - name: Questions kind: editorial_table proposedDistinctTemplate: native-questions-template.csv columns: - question_id - approved_wording - field_type - crm_mapping - required - controller_question - allowed_answers - show_if_answer - source_ref acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: Scope kind: approved_text_section proposedDistinctTemplate: native-scope-template.txt requiredContent: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. templateFilesCreatedByThisTask: False requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence. OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. Questions: native-questions-template.csv Scope: native-scope-template.txt STEP 1: Read the existing question and field map Tool: Lawmatics Open: Docs & Forms > Custom Forms > selected form > field settings; Settings > Custom Field Settings Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Capture only attorney-approved questions, answer options, field type, required flag and CRM destination. Use the actual existing form or approved question document. Do not edit or Save Form during evidence gathering. Expected output: Question inventory with source question IDs and mappings. Use it next: Paste the approved, nonconfidential specification into the drafting workspace. Check: General/Form Only fields do not store in CRM, appear in reports or sync to case management. Changing a label does not change its mapped field. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://help.lawmatics.com/en/articles/10699800-lawmatics-navigation-experience https://help.lawmatics.com/en/articles/10738644-adding-fields-to-a-custom-form STEP 2: Draft from the approved source packet Tool: Acrobat PDF Spaces / AI Assistant, optional Open: Acrobat home > PDF Spaces > Create a PDF Space > Paste copied text > Add to PDF Space > chat Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: downstream_application_ai Paste only the approved nonconfidential packet, source IDs and full Scope note. Paste the exact prompt into the Space chat. Do not upload raw client records; this is a downstream drafting assistant, not an AI in the source application. PASTE THIS PROMPT Using only Questions and Scope, draft a Lawmatics form specification. For each question give approved question_id, exact or approved simplified wording, field type, CRM mapping, required flag, controller question and explicit show-if answer. Conditional controllers must be true/false, picklist or multi-picklist; do not derive branches from free text. Include unanswered, every allowed answer, hidden-required and contradictory-answer test cases. Flag any unsupported control or missing CRM mapping. Do not add eligibility scoring, legal advice or sensitive questions; do not edit or publish the form. Expected output: Question-by-question branch specification and synthetic test matrix. Use it next: Copy reviewed output into an internal review document or the named downstream tool, preserving evidence IDs. Check: A required hidden question, unmapped Form Only value or unsupported free-text controller is blocked. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html STEP 3: Translate the checked branch spec into a build handoff Tool: Form owner, no execution in this research Open: Lawmatics form editor > select dependent field/block > right sidebar Conditional Logic > controller field > answer that shows the field Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Reviewer maps each approved spec line to these documented controls. Blocks may carry section conditions. Record unsupported compound requirements for manual resolution rather than inventing controls. Expected output: Implementation-ready spec or a list of unsupported conditions. Use it next: A separately authorized form editor can build a non-live copy and use synthetic test cases before any publishing/embedding. Check: Set logic on the dependent question, not the controlling question. Saving changes is outside this read-only verification. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://help.lawmatics.com/en/articles/10699872-conditional-logic-in-custom-forms STEP 4: Human review and final action Tool: Responsible firm reviewer Open: Internal Review worksheet / review document Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Attorney approves data minimization, questions and branching. Form owner checks every synthetic branch and CRM mapping before enabling any client-facing use. Expected output: Approved specification and test checklist; untested implementation. Use it next: Human builder receives the spec and question-ID map. Check: No real intake submission, customer data or automatic case decision. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://help.lawmatics.com/en/articles/10699872-conditional-logic-in-custom-forms https://help.lawmatics.com/en/articles/10738644-adding-fields-to-a-custom-form ACCOUNT AND SOURCE CHECKS STILL NEEDED - The live account, entitlement, exact headers, records and field coverage have not been observed. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.