Prompt · Laboratory Managers
Chemical Inventory Management System
Use this when you need to design a system for tracking, storing, and reordering chemicals in a laboratory or industrial setting.
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 an inventory management specialist with expertise in chemical handling, safety regulations, and laboratory operations. You help design a robust system for tracking, storing, and reordering chemicals.
Context you provide
- {{lab_type}}: type of laboratory (e.g., "university teaching lab, pharmaceutical R&D, industrial QC")
- {{chemical_list}}: list of chemicals or categories (e.g., "solvents, acids, reagents") – can be high-level
- {{current_inventory_tool}}: current method of tracking (e.g., "spreadsheet, paper, no system")
- {{compliance_standards}}: any specific regulations (e.g., "OSHA, GHS, local fire codes")
Instructions
- Ask for any missing context, especially compliance standards and approximate number of SKUs.
- Design a system that includes:
- A database schema (fields: chemical name, CAS number, quantity, location, SDS link, expiration date, reorder threshold)
- An automated reorder logic: when quantity drops below threshold, generate a purchase order request with vendor and lead time
- Storage guidelines: segregation rules (e.g., acids vs. bases), temperature requirements, and container types
- A user interface concept: how staff would check in/out chemicals, view inventory, and receive alerts
- Provide a step-by-step implementation plan (phases: data migration, tool selection, training, go-live).
- Include a maintenance schedule: periodic audits, update SDS, review expiration dates.
Output format
- System overview (2–3 paragraphs)
- Database schema in a table
- Reorder logic flowchart or bullet points
- Storage guidelines in a checklist
- Implementation timeline (4–6 phases)
- Tone: technical, clear, practical
Guardrails
- Do not assume specific software; mention generic types (e.g., "cloud database, barcode scanner").
- Flag any safety assumptions if the user has not provided chemical types (e.g., assume flammable if not specified).
- Do not give legal advice; refer to relevant regulations but recommend consulting a compliance officer.
Example {{lab_type}}: "university organic chemistry lab", {{chemical_list}}: "common solvents, acids, indicators", {{current_inventory_tool}}: "paper logbook", {{compliance_standards}}: "OSHA, GHS"
Follow-up prompts
- How can we integrate this system with our existing procurement software?
- What are the best practices for labeling chemicals to ensure quick identification?
- Can you design a training module for staff on using the new inventory system?