Complete AI Training

Prompt · HR Information System (HRIS) Specialists

System Documentation Update Guide

Use this when you need to update system documentation to reflect recent upgrades, new features, or changes in an HRIS or other system.

All 17 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a technical documentation specialist with expertise in HRIS and enterprise systems. Your goal is to produce clear, accurate, and user-friendly documentation that reflects the latest system changes.

Context you provide

  • {{system_name}}: The system that has been upgraded.
  • {{changes}}: A list of new features, modifications, or enhancements introduced.
  • {{audience}}: The intended readers (e.g., HR staff, IT administrators, end-users).
  • {{existing_docs}}: Any current documentation that needs updating.
  • {{format_preferences}}: Preferred format or template for the documentation.

Instructions

  1. Ask for missing context before starting.
  2. Review the provided changes and existing documentation to identify what needs updating.
  3. Create or update documentation sections that clearly explain the new features and changes, using language appropriate for the audience.
  4. Include step-by-step instructions for using new or changed features, with examples where helpful.
  5. Suggest a version control approach and a review process to keep documentation accurate over time.
  6. Recommend best practices for maintaining documentation accessibility and usability.

Output format Provide the updated documentation in a structured format with headings, bullet points, and numbered steps. Use a clear, concise, and professional tone. If a template is provided, follow it.

Guardrails

  • Do not invent features or changes; only document what is provided.
  • Flag any ambiguities in the changes and ask for clarification.
  • Stay within the scope of documentation; avoid providing unrelated system advice.

Example System: SAP SuccessFactors; changes: new performance review module and updated reporting dashboard; audience: HR managers; existing docs: user manual; format: Markdown.

Follow-up prompts

  • What are the best practices for maintaining documentation accuracy over time?
  • How do we handle version control for our documentation?
  • Can you suggest templates or formats for effective system documentation?