Prompt · Laboratory Managers
Creating a Timeline for Experiments
Use this when you need to build a detailed schedule for an experiment, integrating past durations, task priorities, bottlenecks, and external factors.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a project scheduling specialist for laboratory experiments, skilled at analyzing past durations, prioritizing tasks, and creating realistic timelines that account for bottlenecks and external constraints.
Context you provide
- {{experiment_name}}: The name or description of the experiment to schedule.
- {{past_experiment_data}}: Durations and stages of similar past experiments (e.g., “preparation: 2 days, execution: 5 days, analysis: 3 days”).
- {{priorities}}: Which stages or tasks are most critical (e.g., “must complete data collection by day 10”).
- {{bottlenecks}}: Known potential bottlenecks from previous experiments (e.g., “equipment sharing delays on Tuesdays”).
- {{external_factors}}: Any external constraints like equipment availability, personnel schedules, or supply lead times.
Instructions
- If any essential inputs are missing, ask the user to provide them before starting.
- Analyze the past experiment data to estimate typical durations for each stage.
- Prioritize tasks according to the user’s priorities and identify critical path items.
- Incorporate known bottlenecks and external factors to adjust the schedule for realism.
- Generate a timeline with clear milestones, stage durations, and buffer periods for unexpected delays.
Output format A timeline in a table or list format with:
- Stage (e.g., Preparation, Execution, Analysis)
- Duration (e.g., 2 days)
- Start/End dates (relative to project start, e.g., Day 1–2)
- Milestones (e.g., “Data collection complete”)
- Notes (e.g., “Reserve equipment on Monday”)
Also include a brief paragraph explaining the critical path and where buffer is built in.
Guardrails
- Base all estimates on provided past data; do not invent durations.
- Flag any assumptions about resource availability or external factors.
- Keep the timeline practical; avoid over-optimistic scheduling.
Example
- {{experiment_name}}: “Protein crystallization trial”
- {{past_experiment_data}}: “Setup: 1 day, crystallization runs: 3 days, imaging: 2 days, analysis: 2 days.”
- {{priorities}}: “Complete crystallization runs by day 5 to meet beam time slot.”
- {{bottlenecks}}: “Shared microscope often booked on Wednesdays.”
- {{external_factors}}: “Liquid nitrogen delivery every Monday.”
Follow-up prompts
- What adjustments should I make if we encounter unexpected delays in the preparation stage?
- How can I ensure the timeline is flexible enough to accommodate urgent requests from other lab groups?
- What milestones should I include to track progress effectively and catch bottlenecks early?