START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

G18 - Inventory marketing-account control before an agency handover
Status: Proposed / not tested

WHAT THIS KIT DOES
Provides exact-header blank CSVs, separate fabricated examples, required text-input scaffolds, and expected output examples for one offline review. It does not configure an integration or run a workflow.

PREREQUISITES
1. Read-only screenshots/exports of each platform's access settings, contracts and firm-approved asset roster. Passwords/tokens are neither requested nor stored.
Name a reviewer and keep actual prospect/client data within firm-approved systems. IDs alone are not anonymization.

INPUTS
- assets.csv: asset_id, platform, account_alias, expected_firm_role, dependency_asset_ids
- access-evidence.csv: evidence_id, asset_id, principal_alias, organization_role, platform_role, observed_at, source_ref
- contract-excerpts.csv: excerpt_id, asset_id, excerpt_text, source_ref; scope.txt: as-of time, approved asset roster, coverage and access-role definitions

OUTPUT SHAPE
handover-inventory.csv: asset_id, observed_control, evidence_refs, missing_access_evidence, dependency_gaps, draft_request, reviewer_status

SETUP AND FIRST TRIAL
1. Keep the original exports unchanged. Copy this kit into an approved working folder.
2. Start with only the files ending -example. They contain fabricated data. CSV files without -example contain headers only; text inputs without -example contain empty preparation scaffolds.
3. For the synthetic trial, copy each example into a separate trial folder under its canonical input filename. Do not mix example rows with real exports. Supply the matching example policies too. Output examples are for comparison after drafting, not evidence inputs.
4. Import CSVs as UTF-8 comma-delimited data. Preserve identifiers as text and date/timestamp strings in their specified ISO format. Boolean examples use true/false. Empty cells mean unknown or not supplied, never automatic zero/no. Amounts are numeric; use the stated currency and do not combine currencies. No formulas or macros are included.
5. Paste starter-prompt.txt into the firm's approved assistant with only the input files. A staff member can also perform the comparison in a spreadsheet. No account connector is needed for this file-based trial.
6. Check the draft against fixture-expectations.txt and the matching output examples. Use exact arithmetic in native spreadsheet tools or code and inspect source IDs manually. An AI response has not been run or validated for this kit.
7. Resolve missing policies, uncertainty, permissions and coverage with the named reviewer. Live platform configuration, messages, uploads and other changes require their own approval and testing.

FIXTURE TARGET
AS1 has observed firm admin access, AS2 observed agency admin access, and AS3 unknown access. AS1 depends on AS2. No conclusion about legal ownership and no access changes.

LIMITS
- No credential sharing, ownership takeover or permission changes without explicit authorization. Administrative access is not proof of legal ownership.
- Only file/header and synthetic fixture consistency are checked. No workflow, connector, AI response, product feature or integration is tested.
- Every example is fabricated. IDs alone do not anonymize actual firm data. Use approved minimized data, access, processing terms and retention controls.
Source-policy text scaffolds are not legal advice or production configuration. No real review link, phone destination, contact address, API token or credential is included in examples. example.invalid and fixture: references are deliberate non-live placeholders.

SOURCES
Research source: https://www.reddit.com/r/LawFirm/comments/t93lfc
Research source: https://support.google.com/google-ads/answer/6372672?hl=en-gb
Research source: https://support.google.com/localservices/answer/7652468?hl=en

VALIDATION SCOPE
Header and fixture validation passed; workflow not tested. Read the exact checks and limits in fixture-expectations.txt.