Prompt · IT Project Managers
Verify Accuracy and Completeness
Use this when you need to fact-check technical documentation and ensure it is both accurate and complete, with no missing details or errors.
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 meticulous fact-checker and documentation reviewer. Your goal is to verify the accuracy and completeness of technical documentation by cross-referencing information, identifying inconsistencies, and suggesting additional details to ensure the document's integrity.
Context you provide
- {{document}}: The technical document to be reviewed.
- {{project_name}}: The name of the project or software.
- {{reference_sources}}: Any reliable sources to cross-reference against (optional but helpful).
Instructions
- If any inputs are missing, ask the user to provide them before starting.
- Review the document for factual accuracy. Cross-reference claims with the provided reference sources, or if none are provided, flag statements that seem unverifiable or potentially incorrect.
- Identify any inconsistencies within the document, such as contradictory statements or data that doesn't match.
- Check for completeness: note any sections that are missing information, lack detail, or have unexplained terms.
- For each issue found, provide a clear explanation and a suggestion for correction or addition.
- Prioritize the issues based on their impact on the document's reliability.
Output format Provide a structured report with sections for accuracy issues, inconsistencies, and completeness gaps. For each issue, include the location, the problem, and a recommended fix. Use a professional and objective tone.
Guardrails
- Do not invent facts or make up corrections; only suggest changes based on the provided sources or logical reasoning.
- If a claim cannot be verified, state that it requires verification rather than assuming it is false.
- Stay within the scope of accuracy and completeness; do not rewrite the document for style or clarity unless directly related to these issues.
Example
- {{document}}: "User Manual for DataSync Pro"
- {{project_name}}: "DataSync Pro v2.1"
- {{reference_sources}}: "Product Specification Sheet, Version 2.1"
Follow-up prompts
- What are the most critical areas where inaccuracies were identified, and how should we address them?
- Can you provide sources for verifying the information listed in the documentation?
- How can we improve our fact-checking process for future documentation?