AI for daily operations

You're helping me triage my inbox. Sort the messages below into four groups:

1. Needs my response today
2. Needs response this week
3. Can be delegated or batched
4. Informational or low priority

For each message, give:
- Suggested priority
- Why it belongs there
- Recommended next action
- Any deadline or risk you see

Don't draft replies yet.

Business context:
[Briefly describe your business and role]

Messages:
[Paste subject lines, sender names, and short previews. Remove sensitive data where possible.]

Draft a clear internal email response based on the message below.

Goal:
[Confirm / ask for missing information / decline / delegate / follow up / summarize decision]

Relationship:
[Team member / vendor / partner / contractor / internal stakeholder]

Tone:
Direct, warm, and concise.

Constraints:
- Don't overpromise.
- Don't add facts not included here.
- If information is missing, ask for it clearly.
- Keep the email easy to scan.

Original message:
[Paste the message or summary]

My intended response:
[Explain what you want to say]

Turn the meeting notes or transcript below into a clean meeting recap.

Include:
1. Meeting purpose
2. Key decisions
3. Open questions
4. Action items with owner and deadline
5. Risks or blockers
6. Follow-up message I can send to attendees

Rules:
- If an owner or deadline isn't clear, mark it as "needs confirmation."
- Don't invent decisions.
- Keep the recap concise.
- Separate confirmed actions from possible next steps.

Meeting context:
[Project, client, team, or topic]

Notes or transcript:
[Paste notes or transcript]

Turn my rough process notes into a practical SOP.

Audience:
[Who will use this SOP]

Process purpose:
[What this process accomplishes]

Create:
1. Process overview
2. When to use this SOP
3. Inputs needed
4. Step-by-step instructions
5. Decision points
6. Common mistakes
7. Quality check before marking done
8. Final checklist

Rules:
- Use clear steps.
- Keep the language practical.
- Mark missing details as questions.
- Don't add steps that I didn't describe unless you label them as suggestions.

Rough process notes:
[Paste notes or voice-to-text transcript]

Create a first draft of a [proposal/report/project brief] from the information below.

Audience:
[Who will read it]

Purpose:
[What the document needs to accomplish]

Required sections:
[List sections or ask AI to suggest a structure]

Tone:
Professional, clear, and practical.

Rules:
- Don't invent numbers, promises, dates, or pricing.
- Flag any missing information.
- Keep assumptions in a separate section.
- End with clear next steps.

Source information:
[Paste notes, call summary, project details, or bullet points]

Analyze the data below and create a plain-language summary.

Business question:
[What you want to understand]

Focus on:
- Trends
- Outliers
- Changes over time
- Categories that need review
- Questions I should investigate

Rules:
- Show the calculations or explain how you reached the summary.
- Don't make claims the data doesn't support.
- Flag missing or unclear fields.
- Keep recommendations separate from observations.

Data:
[Paste a small table or upload an approved file. Remove sensitive fields where possible.]

Draft an invoice instruction or payment reminder from the approved details below.

Task:
[Invoice instruction / payment reminder / internal billing note]

Rules:
- Don't change amounts, dates, tax details, or payment terms.
- Flag any missing information.
- Keep the tone polite and clear.
- Include only the details provided.

Approved details:
Client:
Invoice number:
Amount:
Due date:
Services or products:
Payment instructions:
Notes:

Review the transactions below and suggest expense categories.

Rules:
- Treat categories as suggestions, not final bookkeeping decisions.
- Flag anything uncertain, unusual, large, duplicated, or possibly personal.
- Don't guess when the vendor or purpose is unclear.
- Group recurring vendors when possible.

Business context:
[Type of business]

Category list:
[Paste your approved chart of accounts or common categories]

Transactions:
[Paste transaction list with sensitive fields removed where possible]

Help me think through a cash flow scenario.

Use the numbers below to create three scenarios:
1. Expected case
2. Conservative case
3. Stress case

For each scenario, summarize:
- Starting cash
- Expected inflows
- Expected outflows
- Timing risks
- Cash pressure points
- Questions I should ask my accountant or bookkeeper

Rules:
- This is planning support, not financial advice.
- Don't make assumptions without labeling them.
- Keep recommendations separate from calculations.
- Flag any missing information.

Business context:
[Brief context]

Inputs:
[Paste approved numbers and assumptions]

Turn this project idea into a practical project kickoff brief.

Include:
1. Project goal
2. Success criteria
3. Key milestones
4. Task list
5. Suggested owners
6. Dependencies
7. Risks
8. Questions to resolve
9. Weekly status update format

Rules:
- Don't assume capacity or deadlines unless provided.
- Mark unclear items as questions.
- Keep the plan realistic for a small team.

Project notes:
[Paste project description, deadline, team members, constraints, and desired outcome]

# [Process or topic name]

## Purpose
[What this page helps the team do]

## When to use this
[Trigger or situation]

## Who owns this
[Role or person]

## Inputs needed
[Documents, tools, approvals, customer details, etc.]

## Steps
1. [Step]
2. [Step]
3. [Step]

## Decision points
[What to do when the situation changes]

## Common mistakes
[What usually goes wrong]

## Quality check
[How to know the work is done correctly]

## Escalation
[When to ask for help and who to contact]

## Last reviewed
[Date and owner]

Help me create hiring support materials for the role below.

Create:
1. Clear job description
2. Required skills vs. nice-to-have skills
3. Screening rubric tied to the actual work
4. Interview questions
5. Practical work-sample exercise
6. Candidate communication templates

Rules:
- Don't include requirements that aren't necessary for the role.
- Avoid vague culture-fit language.
- Keep evaluation criteria tied to evidence.
- Don't rank or reject candidates.
- Flag anything that could create fairness or bias concerns.

Role context:
[Role title, responsibilities, must-have skills, schedule, location, compensation range if available, team context]

Workflow chosen:
[Name]

Why this workflow:
[Time cost, frustration, mistakes, delay, or repeat volume]

Current process:
[Describe how it works today]

AI-assisted process:
[Describe the new version]

AI will handle:
[Summarize, draft, categorize, analyze, organize, etc.]

Human will review:
[What must be checked before the work is final]

Allowed data:
[What can be used]

Restricted data:
[What can't be used or needs an approved tool]

Success metric:
[Time saved, faster response, fewer missed tasks, cleaner documentation, etc.]

Test period:
[Dates]

Owner:
[Person responsible]