Gemini as a Review and Quality Assurance Partner Log in and enroll to track lesson completion. By the end of this lesson, students should be able to: Three distinct types of quality failure. Documents and plans fail quality checks for three distinct reasons: Each type requires a different check. Applying all three is the most thorough quality review. The logic audit. "Conduct a logic audit of this document. For each major claim or recommendation: (1) is there explicit supporting evidence or reasoning? (2) does the evidence actually support the claim, or is the connection assumed? (3) are there any statements that contradict each other or undermine the document's argument? Identify and quote the specific text for any logic issues." The instruction to "quote the specific text" is important – it forces Gemini to cite the actual sentence rather than offering a vague general observation, and allows you to locate and address the specific issue. The consistency check. "Conduct a consistency check of this document. Look for: (1) numerical inconsistencies – does the same number appear differently in different places? (2) factual contradictions – does the document make claims in one section that contradict claims elsewhere? (3) timeline contradictions – are dates, sequences, and timelines consistent throughout? (4) reference inconsistencies – does the document refer to figures, tables, or sections that do not exist, or refer to them incorrectly? Quote the specific inconsistencies you find." Consistency checks are where Gemini's ability to hold a long document in context simultaneously is most valuable – humans typically cannot compare page 3 against page 14 without deliberately re-reading. The completeness check. "Read this document as a knowledgeable reader in [field/domain]. What would you expect to find in a document of this type that is not included? Identify specifically: (1) standard sections missing, (2) obvious questions the document raises but does not answer, (3) stakeholder concerns the document should address but ignores, and (4) evidence or data you would expect to support the recommendations that is absent." The completeness check is particularly valuable for documents written by domain experts who forgot what non-experts need explained, and for documents that were written to a deadline where certain sections were inadvertently skipped. Stacking checks for high-stakes documents. For high-stakes documents – board presentations, regulatory submissions, major proposals – stack all three checks: The synthesizing final question produces an actionable priority list from potentially extensive check results. A business development manager submits a partnership proposal for executive approval. She asks her colleague to review it but the colleague does not have time for more than a quick read. She uses Gemini for three checks: Logic audit: Identifies that her claim "this partnership will reduce customer acquisition cost by 40%" is presented without supporting evidence. She adds a data table from a comparable partnership case study. Consistency check: Identifies that the implementation timeline says "Phase 1 complete by Q2" on page 2 but the timeline table on page 6 shows Phase 1 completing in Q3. She corrects the discrepancy before the executives see it. Completeness check: Identifies that the proposal does not address what happens if the partner fails to meet commitments – an obvious risk that a skeptical executive would ask about. She adds a brief risk mitigation section. None of these three issues would have been caught by a quick impressionistic read. The stacked check prevented three embarrassing errors from reaching the executive review. After running all three checks, ask Gemini one final question: "If a hostile reader – someone actively looking for reasons to reject this document – read it, what would they focus on? What is the weakest point that a critic would attack?" This adversarial read identifies the issue most likely to be challenged in a review or presentation – and gives you the opportunity to address it proactively rather than reactively. Logic, consistency, and completeness checks with Gemini identify potential issues based on the document's own text. They do not verify the accuracy of facts against external sources, validate that statistics are correctly cited, or confirm that methodologies are sound. For documents where external accuracy matters – research reports, financial projections, regulatory submissions – external fact-checking with primary sources is a separate, required step. Log in and enroll to take this lesson quiz.
Lesson 2: Logic, Consistency, and Completeness Checks
Lesson Objectives
Lesson Content
Practical Example
Lesser-Known Tip
Safety Notes
Lesson Quiz