Body
Prompt description
A plug-and-play prompt to generate a complete project plan, timeline, and workback schedule for Bowdoin College initiatives, including milestones, dependencies, RACI, risks, and communications.
What you'll need
Best AI models
- GPT-5.2 (Thinking) - excels at multi-step reasoning, structured planning, and generating detailed schedules with clear dependencies and critical path analysis.
- Claude Opus 4.6 - highly capable for long, complex project documents with nuanced stakeholder, risk, and communications planning.
- Claude Sonnet 4.5 - strong long-context analysis and precise writing, ideal for producing organized plans and polished executive summaries.
- DeepSeek R1 - deliberate reasoning model well-suited for complex dependency mapping and critical-path computations.
- GPT-5 (Web Search) - useful when projects require incorporation of up-to-date policies, compliance requirements, or external benchmarks.
- Llama 4 Maverick - solid planning performance with flexibility for private or on-prem environments requiring structured project outputs.
Materials
- Project charter, statement of work, or brief
- Bowdoin academic calendar and observed holidays
- Prior timelines, checklists, or standard operating procedures
- Stakeholder list and org chart for roles/approvals
- Procurement, accessibility, and communications guidelines (if relevant)
- Any RFPs, grant calls, event run-of-show, or course syllabi connected to the work
Instructions
Copy the prompt below and replace the bold items within the left and right double curly brackets ( {{ }} ) to best suit your situation and need. Attach any supporting materials that you'd like to use as reference.
Prompt
Act as a seasoned project manager serving Bowdoin College. Build a practical, right-sized project plan, timeline, and workback schedule that people can immediately execute. When attachments are provided, treat them as authoritative sources. Ask concise clarification questions only if essential to avoid rework.
Context and inputs:
• Project name: {{ Project name }}
• Sponsoring department/unit: {{ Department or unit }}
• Project owner/sponsor: {{ Sponsor name/title }}
• Primary objective(s): {{ 1–3 outcome statements }}
• Final deliverable(s): {{ What must be delivered }}
• Final deadline (anchor for workback): {{ YYYY-MM-DD }}
• Earliest start date (if known): {{ YYYY-MM-DD }}
• Constraints (budget, approvals, policy, space, tech): {{ Key constraints }}
• Stakeholders and required approvers: {{ Names/roles }}
• Non-working days/time zone: {{ Time zone and holidays }}
• Preferred approach (waterfall/agile/hybrid): {{ Method preference }}
• Tools to export to (e.g., CSV for Smartsheet, MS Project, Asana): {{ Target tool/format }}
• Risk tolerance and success metrics: {{ KPIs and thresholds }}
• Notes/attachments to use as reference: {{ File names or “see attachments” }}
What to produce (in order):
1) Executive summary (3–6 sentences) tailored to Bowdoin context.
2) Milestone list with dates (anchor from the final deadline backward).
3) Work breakdown structure (phases → tasks → sub-tasks) with unique IDs.
4) Workback schedule table computed from the final deadline, including: ID, Task, Duration (workdays), Earliest Start, Earliest Finish, Dependencies, Responsible (R), Accountable (A), Consulted (C), Informed (I), Deliverable/Acceptance Criteria, Risk, Buffer/Slack, and Status placeholder.
5) Critical path analysis, highlighted tasks on the path, and recommended buffers (e.g., project, feeding, and resource buffers).
6) RACI matrix (roles as columns, tasks/milestones as rows).
7) Risk and issue (RAID) log with probability, impact, owner, trigger, and response strategy.
8) Communications plan (audiences, message, channel, cadence, owner), aligned to approval gates and key dates.
9) Resource and capacity view (people/skills, estimated effort by week), with assumptions and load risks.
10) Two-week “immediate next steps” sprint plan with concrete actions and owners.
11) Export-ready deliverables: a) a CSV-friendly task table; b) a compact Markdown table; and c) if helpful, a Mermaid Gantt snippet.
12) Open questions and decisions needed, each with a due date and owner.
Planning assumptions and guardrails:
• Default to Monday–Friday workweeks unless specified; respect {{ Time zone and holidays }} and the Bowdoin academic calendar if provided.
• Flag any required reviews (e.g., accessibility, data privacy, procurement, communications/branding) and place them before dependent milestones.
• Keep language concise and action-oriented; prefer tasks that start with a verb.
• Calibrate detail to produce 6–12 milestones and 25–120 tasks for typical initiatives; collapse or expand as needed.
• If inputs are missing, proceed with reasonable assumptions and clearly list them.
Make it your own
- Swap the methodology to fit your team (e.g., agile sprints for IT, phase-gate for events, or hybrid for academic program launches).
- Add role-specific outputs (e.g., faculty onboarding checklist, student communications timeline, or donor/stewardship touchpoints).
- Target a specific tool by adjusting the “Tools to export to” field (e.g., include exact column headers for Smartsheet, Asana, or MS Project).
- Insert Bowdoin-specific calendars (orientation, breaks, athletics, admissions) in Materials to auto-avoid conflicts.
- Tune risk appetite and KPIs for your context (grants compliance, classroom readiness, residence life move-in, IT cutover windows).