EDO AI PLAYBOOK · 14 OF 15 · VERSION 1.0

By Andy Greiner

An intelligence brief earns its place by changing what the team does next. A list of headlines is only an input. This workflow deduplicates the material, distinguishes events from speculation and makes local relevance explicit without treating every signal as a confirmed prospect.

What to bring

A defined reporting window; approved geography and sectors; company announcements, filings, earnings material, notices, permits, hiring and real estate signals; source links or extracts; previous briefing and tracked actions.

The prompt

Copy and paste this directly into your AI Assitant

Act as an EDO intelligence editor. State the reporting window and source coverage. If you cannot access a source, say so; do not describe the scan as comprehensive. Record both publication date and event date, and distinguish new events from newly discovered old information.

Deduplicate reports of the same event. Prefer original company, government or filing material where available and retain attribution to original reporting when used. For each item record entity, location, event, status, source, date and confidence. Separate announcement, proposal, approval, construction, operation and cancellation. Do not treat a permit or job posting as proof of an expansion.

Assess relevance to existing employers, prospecting, workforce, sites, infrastructure and competitive positioning. State the connection in one sentence. Use Direct local relevance / Potential relevance / Watch only categories and explain uncertainty. Avoid ranking by headline size alone.

Prepare a brief with at most five priority developments, followed by a compact watchlist and corrections to prior items. Each priority item needs: what happened, what is verified, why it matters locally, what remains unknown, proposed next action, owner role and source link. Include announced figures only with their status and source.

Create a separate verification queue for actionable but unconfirmed signals. Flag contradictory sources and never resolve the conflict by choosing the more dramatic number. Preserve confidentiality boundaries when using internal notes.

End with three decisions or follow-ups for the staff meeting and carry forward unresolved commitments from the previous brief. If there are no meaningful developments, say so. Do not fill space with low-value items or imply that surveillance, notifications or future scans have been scheduled.

Human check

Open the primary links, verify the event dates and confirm that each proposed action follows from the evidence. A human editor should review sensitive employment or company-risk interpretations.

Follow-up prompt

Compress the approved brief into a five-minute meeting agenda with decisions first, then owner assignments and verification work.

Do this Monday

Track whether last week’s top three intelligence items led to an action or a justified decision to wait.

Why I built this

For three years, part of my work while editing Area Development involved processing economic-development thought leadership: conference material, interviews, presentations and panels. That editorial experience informs the problems I choose to tackle here. These workflows are Location Decision’s practical tools, developed to help economic developers organize evidence, ask better questions and prepare stronger work.

Get the complete operating kit

Get all 15 copy-and-use AI workflows free with your Location Decision subscription. Put them to work on workforce, BRE, site visits, consultant relations, intelligence and strategy.

Get the next one in your inbox

Keep Reading