| AQ-021 · Which northern trees face removal or retention? | [P05] DEM-1–20; PL-1; PP-1–24; resident atlas [A1/A4] | Long Beach Public Works; official plan custodian and designated project Engineer | Current uniquely identified existing-tree inventory, latest dated removal/retention plans, and reconciliation with each atlas observation. | Time-critical · final designations not yet recovered |
| AQ-003 · Where is the completed VIS-2 design-stage verification? | [P08] 2020 EIR/EA commitments; [P07] 2019 visual assessment | City environmental-compliance lead; engineering/design reviewers | The completed verification, signoff/date, alternatives and trees conserved due to design decisions. | Unlocated record · document applicability must be authenticated |
| AQ-005 · Why does PL-1 show a preserved-tree symbol without located individual uses? | [P05] PL-1 PDF p.362; PP-1–24 pp.363–386; DEM Note 7 pp.21–40 | City / landscape-design plan author / designated Engineer | Tree-by-tree retained schedule, approved plan revisions, field protection map and relevant graphical markings. | Investigator did not find mapped applications; exhaustive current-revision audit pending |
| AQ-011 · Who verifies before the first irreversible cut? | [P06] Division I §300-1.2.4; [P05] DEM Note 7 | Contractually designated Engineer; construction manager/inspectors; contractor | Signed pre-removal identification, approval and stop-work escalation protocol; field marking and applicable notice. | Urgent · role and procedure require written confirmation |
| AQ-010 · Which removals are physically unavoidable? | [P05] DEM, L, grading and utility drawings; [P08] VIS-2 | City design engineers; preservation-oriented independent engineer/arborist | Documented tree-specific alternatives, constraints, costs and root-zone preservation options. | Unresolved design necessity |
| AQ-007 · What is the actual number of unique trees to be lost? | [P01] City ~170; [P05] DEM marks; [P06] 300 EA bid item | City estimator, Engineer and inspector; contractor for actual measurements | One current unique-tree list with size thresholds, separate clearing/grubbing counts and final change orders. | Different counting units; not a verified contradiction |
| AQ-009 · What will new planting actually provide? | [P01] 500 native; [P05] PL-1=522; [P06] bid=530 | City landscape/environmental team; plant-establishment staff | Approved species/quantity list, planted locations, maturity/canopy projections, survival and monitoring rules. | Plant counts do not measure present canopy |
| AQ-013 · How will wildlife and nesting protections be applied? | [P06] §300-1.2.2.1; [P09] Coastal Special Condition 3 (south only) | City environmental staff; qualified biologists; permit-specific monitors | Applicable pre-cut surveys, work restrictions, permits and dated biological signoffs. | Specific work-site applicability must be checked |
| AQ-022 · Which 37 trees were retained within the coastal permit? | [P09] p.18; [P12] special conditions | City permit applicant; California Coastal Commission permit record | Coastal revised before/after plans and individual 44-tree mapping, subsequent approved construction/landscape submissions. | Southern precedent; not northern preservation |
| AQ-015 · Why did the bid introduction omit explicit tree removals? | [P06] Notice Inviting Bids Division A p.A-1 | City Public Works and procurement drafting/approving office | Scope drafting and review history, referenced tree-treatment instructions, explanation of public-facing wording. | Absence in introductory synopsis, not complete contract omission |
| AQ-016 · What public review is still available? | [P13] City forestry policy; [P09] permit conditions | City Public Works; permitting staff; legal counsel for applicability | Notice and appeal rules applying to each tree; current permits; who can pause/review removals. | Urgent · do not presume ordinary street-tree appeal applies |
| AQ-014 · What are retained mature assets worth? | [P04] City inventories/value; existing tree assessments | City urban-forestry data custodian; independent ISA arborist | 2015 park-tree entries (if any for site), per-tree condition, canopy and ecosystem-service appraisal. | Historical valuation citywide, not a local appraisal |
| AQ-018 · Who has been notified and when? | [P01] project announcements; procurement record; tree policy/permit notices | City outreach and project manager; construction coordinator if designated | Dated notifications, alternatives presented, accessible tree-level maps and actual remaining decision opportunities. | Meaningful review may depend on timing |
| AQ-023 · Which trees left standing may be killed later? | [P05] grading, utility, irrigation drawings; [P08] PF-50 (scope to confirm) | Project arborist if assigned; City Engineer; construction inspector | Protection zones, root cuts, compaction plans, arborist inspections and post-construction monitoring. | Standing trunk ≠ protected living system |
| AQ-024 · Who can coordinate an immediate independent review? | [P14] October 2026 council project decision; [P01] project status | Potential lead recipient; City project manager; environmental legal counsel | Named review coordinator, earliest planned clearing date and decision point for feasible retention changes. | Need actionable contact / no verified first-cut date |
| AQ-025 · Who verifies tree identification, protection and removal authorization in the field? | [P15 · Council item 26-56261]; [P17 · signed DEM Note 7 / procurement] | Project Engineer; City inspection lead; Sully-Miller; PMCS under actual executed scope | Executed field responsibility matrix and inspection scope; tree-tag inventory; signed pre-removal checklists; written Engineer instructions; inspector logs; hold/release protocol. | Urgent before any removal or root-damaging work; duty-holder not yet verified |
| AQ-026 · When did contract and delivery deadlines constrain preservation alternatives? | [P16 · Metro 2026-0662]; [P15 · October 6 item] | Metro funding agreement custodian; City Public Works scheduling/design leads; City Manager designee | Baseline schedules, grant award milestone terms, design-decision chronology, risk registers, alternatives considered, change-order impact calculations and actual notice-to-proceed. | Documented financial/schedule pressures; relationship to tree decisions unverified |
| AQ-027 · Who authorized, purchased and oversees the tree-removal pay item? | [P17 · PW-26-759, Addendum 2, Item 46] | Long Beach Public Works, Procurement, Project Engineer and contract administrator | Bid quantity assumptions, unique tree-count reconciliation, signed contract, schedule of values, unit measurement rules, change-order and payment records; distinguish tree removal from clearing vegetation. | 300 EA bid estimate is not an actual tree census |
| AQ-028 · What environmental review duties were purchased from PMCS? | [P15 · RFP PW-25-547]; [P18 · executed contracts portal] | City Council/City Manager; PMCS Group; City Public Works consultant administrator | RFP PW-25-547, PMCS proposal and executed scope, staff qualifications, tree-related inspection and escalation protocols, field reporting requirements. | An inspection contract is documented; its specific tree-verification duties remain unresolved |
| AQ-029 · How did Metro handle the stated tension between urgent financing and planned community-led allocations? | [P16 · Alternatives Considered] | Metro Board and CMIP program staff; City funding liaison; community oversight participants | Board materials, contingency attachments, funding agreement, outreach records, revisions, and identification of which stakeholder process applied to this specific decision. | Metro acknowledged a process tension; this is not evidence that tree protections were waived |