Prepare a Google profile reinstatement review 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 - Preparation does not establish eligibility or guaranteed reinstatement. No live restriction screen or upload limits were inspected. STOP IF - No actual suspension notice, contradictory business facts, ineligible service model or missing genuine evidence. 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: appeal-draft.txt firstLine: EMPTY OUTPUT TEMPLATE: appeal-draft.txt - file: business-facts.csv firstLine: fact_id,fact_name,verified_value,evidence_ref,verified_at - file: eligibility-policy.txt firstLine: G17: eligibility-policy.txt - file: evidence.csv firstLine: evidence_id,evidence_type,source_ref,available,discrepancy - file: reinstatement-readiness.csv firstLine: fact_id,requirement,evidence_refs,contradiction_or_gap,readiness,human_next_step - file: suspension-notice.txt firstLine: G17: suspension-notice.txt requiredNativeInputs: - name: BusinessFacts kind: editorial_table proposedDistinctTemplate: native-businessfacts-template.csv columns: - fact_id - fact_name - verified_value - evidence_ref - verified_at acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: EvidenceIndex kind: editorial_table proposedDistinctTemplate: native-evidenceindex-template.csv columns: - evidence_id - evidence_type - source_ref - available - discrepancy acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: RestrictionAndPolicy kind: approved_text_section proposedDistinctTemplate: native-restrictionandpolicy-template.txt requiredContent: Captured actual restriction reason, linked current official policy excerpts and source URLs. Do not infer a reason from a generic help article. - 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. BusinessFacts: native-businessfacts-template.csv EvidenceIndex: native-evidenceindex-template.csv RestrictionAndPolicy: native-restrictionandpolicy-template.txt Scope: native-scope-template.txt STEP 1: Capture the actual restriction and policy Tool: Google Business Profile appeals tool / existing notice Open: Official appeals tool linked from Google’s suspended-profile help > correct profile > restriction reason and policy link 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 Read the existing notice and, with already authorized account access, the displayed decision/reason. Preserve text/screenshots and date. Do not Submit Appeal or open the timed evidence form during preparation. Expected output: Restriction/decision capture and exact linked policy. Use it next: Use current official guidelines plus staff-verified business facts in the evidence inventory. Check: Do not create a replacement profile while an appeal is pending. Account restriction versus profile/content restriction needs the right route. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.google.com/business/answer/4569145?hl=en STEP 2: Inventory genuine proof locally Tool: Firm’s business records and published profile Open: Approved local registration/licence/utility records; profile name/address/service model 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 Human checks actual operating location, signage, staffed hours and in-person/service-area eligibility. Inventory evidence IDs, dates and name/address consistency. Keep tax IDs, personal details and entire original documents out of downstream AI. Expected output: Nonconfidential facts sheet and evidence-presence index, with gaps. Use it next: Paste the facts, restriction reason, relevant approved policy excerpts and evidence index into PDF Spaces. Check: Mail-only virtual offices are ineligible; co-working offices require qualifying signage, customer reception and the firm’s own staffing. Do not invent facts to fit rules. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.google.com/business/answer/3038177?hl=en https://support.google.com/business/answer/4569145?hl=en STEP 3: 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 Compare only the captured restriction reason, current supplied official policy excerpts and verified BusinessFacts/EvidenceIndex. List factual inconsistencies, unsupported eligibility claims and missing genuine proof. Draft a short factual appeal only if the evidence supports each claim; cite evidence IDs. Otherwise return blocked readiness questions. Do not fabricate an office, signage, staff, service area, registration or narrative, and do not guarantee reinstatement or submit anything. Expected output: Readiness checklist and factual appeal draft, or an explicit blocked result. Use it next: Copy reviewed output into an internal review document or the named downstream tool, preserving evidence IDs. Check: A human verifies eligibility and every claim; AI does not certify location/legal compliance. 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 4: Human review and final action Tool: Responsible firm reviewer Open: Prepared internal appeal packet 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 Profile owner and lawyer check final wording and genuine attachments before any submission. Only after separately approving the destination and files should a human use Submit Appeal, then Add evidence if offered. Complete the evidence step within Google’s 60-minute window. Expected output: Prepared appeal packet; no appeal or evidence upload performed. Use it next: Authorized owner uses the official appeals tool; record the returned decision/status reference afterward. Check: Opening a timed form before the packet is ready risks missing the window. Never upload unrelated personal/tax identifiers. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.google.com/business/answer/4569145?hl=en 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.