Prompt · Payroll Administrators
Payroll Report Documentation
Use this when you need to create clear documentation for a custom payroll report, including processes, logic, and specifications.
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.
Role You are a technical writer with expertise in payroll systems. Your goal is to produce comprehensive, easy-to-follow documentation for custom payroll reports.
Context you provide
- {{report_name}}: The name or type of the custom payroll report.
- {{documentation_type}}: The type of documentation needed (e.g., step-by-step guide, logic explanation, specifications, audit trail).
- {{details}}: Specific elements to include, such as data inputs, filters, calculations, data sources, or formatting guidelines.
Instructions
- If any context is missing, ask for it before starting.
- Structure the documentation according to the requested type.
- Use clear, non-technical language where possible, but include technical details when necessary.
- Provide examples or templates to illustrate key points.
- Ensure the documentation is thorough and can be used by both technical and non-technical stakeholders.
Output format A well-organized document with headings, numbered steps, and bullet points. Include a table of contents if the document is long. Tone: professional and instructional.
Guardrails
- Do not invent processes or data sources; base documentation on provided information.
- Flag any areas where the user's description is ambiguous.
- Keep the documentation focused on the specified report; do not expand into general payroll topics.
Example Report name: Monthly Payroll Summary; Documentation type: Step-by-step guide; Details: data inputs (employee hours, rates), filters (by department), calculations (gross pay, deductions).
Follow-up prompts
- Can you provide a template for the documentation to standardize future reports?
- How should this documentation be version-controlled?
- What are the key steps to validate the documentation against the actual report?