ChatGPT Prompts for Microsoft OneNote

Design OneNote notebook structure for [role / use case]. Output: notebook → section group → section → page hierarchy, naming convention, what goes where (decision rules), what does NOT go in OneNote (use other tools). Avoid generic templates.

Build OneNote tag system. Categories: action items, important, follow-up, decisions, ideas, references. Per tag: when to use, color, visual distinction, query strategy. Tags are searchable; without them, notes are write-only.

When to use OneNote section groups vs sections vs pages. My usage: [describe]. Output: structural rules (groups for major projects/years, sections for sub-projects, pages for individual items), depth limit (3 levels max), maintenance cadence.

I have multiple OneNote notebooks. Help me search across them: search syntax, tag queries, recently modified, naming conventions that aid search. OneNote search powerful but underused.

OneNote meeting notes template. Output: header (date, attendees, agenda), discussion section, decisions section (highlighted), action items table (owner, due date, status), parking lot, next meeting. Reusable across meeting types.

[Paste raw meeting notes]. Extract action items: per item, owner, action verb, deadline. Tag with @owner for searchability later. Skip vague mentions. Force ownership + dates.

Convert action items in OneNote to Outlook Tasks. Output: process for tagging in OneNote, syncing to Outlook (built-in), managing in Outlook, marking complete in OneNote. Workflow chain that actually works.

Recurring meeting structure for OneNote. Pattern: [weekly / biweekly]. Output: per-meeting page template (linked to recurring), running notes section (cross-meeting context), action items roll-forward, search-friendly naming.

Set up personal wiki in OneNote. Goal: [searchable knowledge base on topics I work with]. Output: notebook structure, page templates (concept, how-to, decisions, references), linking strategy (internal links), maintenance cadence.

Project knowledge page template. Per project: overview, goals, stakeholders, key decisions (with date), open questions, references, status updates log. Living doc, not write-once.

Capture reference material from web/email/docs into OneNote. Output: capture method (Send to OneNote / Web Clipper / etc.), tagging at capture, summary requirement, original-link preservation. Capture without organization = pile.

Decision log section in OneNote. Output: per decision — date, decision, who decided, context (1 paragraph), why this option, what was rejected. Indexed for searchability later. "Why did we decide X?" answerable in 30 seconds.

OneNote linked to Teams channel. Setup: shared notebook for [team], channel notes vs personal notes split, who edits, version control, conflicts handling. Team OneNote = shared brain.

OneNote audio recording during meetings. Output: when to record (always vs sensitive), tagging audio with time-stamped notes, search via audio OCR (limited), legal considerations (consent in some jurisdictions). Underused feature.

I want to migrate from OneNote to Notion. Help me plan: what migrates well, what doesn't (OneNote's freeform spatial layout doesn't in Notion), tools/exports available, what to keep in OneNote, when worth doing. Honest tradeoffs.