Real-Time Event Monitoring Assistant Prompt
161 views1 forks
analysismonitoringbusiness-intelligencereportingtechnical
Prompt Content
# Real-Time Event Monitoring Assistant
## Role
You are a professional event monitoring analyst tasked with providing comprehensive, fact-based updates about {{target_entity}} (company/technology/event).
## Objective
Create a structured summary of verified developments within the past 48 hours, prioritizing accuracy and credibility over speed.
## Data Sources (in order of priority)
- Official company/organization statements
- Regulatory filings and legal documents
- Verified social media accounts
- Reputable news organizations
- Industry expert analyses
- Public records and databases
## Output Format
### 1. Executive Summary
- 2-3 bullet points highlighting the most significant developments
### 2. Detailed Timeline
- Chronological listing of events
- Include timestamp (UTC)
- Source attribution for each item
### 3. Source Classification
For each development, indicate reliability level:
- Confirmed (official sources)
- Highly Reliable (multiple credible sources)
- Developing (limited verification)
## Constraints
- Exclude unverified rumors and speculation
- Only include information from the past 48 hours
- Clearly distinguish between facts and analysis
- Note any conflicting reports from credible sources
## Evaluation Criteria
- Accuracy of information
- Comprehensiveness of coverage
- Clear source attribution
- Timeliness of updates
- Relevance to {{target_entity}}
## Required Input Variables
- {{target_entity}}: Specific company, technology, or event to monitor
- {{start_time}}: Beginning of 48-hour monitoring period
- {{end_time}}: Current time/end of monitoring periodHow to use Real-Time Event Monitoring Assistant Prompt
Use this template as a starting point for analysis, monitoring, business-intelligence. Read the full prompt first, then adapt the details so the model has enough context to produce a useful answer.
- Copy the prompt: Start with the full template so the structure stays intact.
- Replace placeholders: Swap bracketed notes or generic examples with your real goal, audience, constraints, and source material.
- Add success criteria: Tell the model what a good answer should include, avoid, or prioritize.
- Iterate once: If the first answer misses the mark, ask for a revision with one concrete change.
Prompt engineering tips
- Use the tags as guardrails: Keep the output focused on analysis, monitoring, business-intelligence.
- Define the role: Tell the model what expert perspective it should use before it answers.
- Set the format: Specify whether you want bullets, a table, code, a checklist, or a polished draft.
Best use cases
Real-Time Event Monitoring Assistant Prompt is most useful for people working on analysis and monitoring. It works best when you have a clear input, a specific output format, and enough background detail for the model to avoid generic advice.
- Turn a rough idea into a structured first draft.
- Create a repeatable workflow for analysis, monitoring, business-intelligence.
- Compare several options before choosing the final direction.
Customization checklist
Before running the prompt, add the details that make your situation different from a generic example. The strongest results usually include constraints, examples, audience notes, and a clear definition of done.
- Add your audience, product, role, industry, or project context.
- Include examples of what good and bad output looks like.
- Ask for one final review pass for clarity, accuracy, and missing assumptions.
Was this prompt helpful?
Sign in to leave feedback and help improve the catalogue.