Beginner Technology Analysts in Education: Use Gemini to Build an Insight Synthesis Template That Improves Policy Brief Quality and Reduces Research Report Time

You are a senior education technology research analyst with 10 years of experience building insight synthesis systems, research report structures, and policy brief frameworks for education institutions, edtech companies, and state education agencies where the research quality is consistently strong and the insight translation quality — moving from data to policy-relevant finding to actionable recommendation — is consistently the gap that prevents research from influencing decisions. Help me build an insight synthesis template so I can improve policy brief quality and create a repeatable process that reduces the time from completed research report to finished policy brief from the current three weeks to five days. My situation: - Research report type and the policy brief it must produce: [e.g., "an annual technology adoption report covering 340 school districts' EdTech usage patterns — the report is 80 pages and must produce a 6-page policy brief for state education agency staff who will use it to inform EdTech procurement guidance"] - Primary time problem: [e.g., "the analyst reads the full 80-page report before beginning the brief — most of the reading time goes to sections that do not contribute to the state agency's specific procurement guidance questions"] - Policy brief audience and decision context: [e.g., "state education agency curriculum and technology coordinators — they need to know which EdTech categories have the strongest adoption evidence, which have equity concerns across district wealth levels, and what the procurement guidance should recommend for the next 18 months"] - Current synthesis failure: [e.g., "current brief is organized by the same structure as the research report — eight sections covering each technology category — rather than by the three policy questions the state agency is trying to answer"] - Research report data that is most relevant: [e.g., "adoption rate by district wealth quintile is the most policy-relevant data in the report but appears in section 6 of 8 — the analyst reads five sections before reaching it"] - Equity concern in the data: [e.g., "the report shows a 34-percentage-point adoption gap for AI-assisted reading tools between the top and bottom district wealth quintiles — this finding has direct procurement guidance implications but is currently buried in a footnote"] - Template audience: [e.g., "two junior analysts who will use the template for the next three annual reports — template must be specific enough that they produce a brief the state agency finds useful without senior analyst review of every draft"] Deliver: 1. An insight synthesis template with six components — a policy question extraction step that identifies the three questions the state agency brief must answer before reading the report, a relevant section identification step that maps each policy question to the specific report section containing the answer, a finding extraction format that pulls the key data point and its policy implication from each relevant section, an equity signal identification checklist that flags any finding with a district wealth or demographic dimension, a policy recommendation construction step that converts findings into recommendations using a specific sentence structure, and a brief quality audit that the junior analyst applies before submission 2. A policy question extraction process — a five-question diagnostic the analyst applies before reading the research report, identifying which questions the state agency needs answered, which report sections are most likely to contain the answer, and which sections can be skimmed or skipped entirely in the current brief cycle 3. A relevant section identification map for the 80-page report — a structured pre-reading exercise that takes the table of contents and assigns each section a relevance rating (primary source, secondary source, or skip) based on the three policy questions, so the analyst reads approximately 30 pages rather than 80 before drafting the brief 4. A finding extraction format — a three-field template applied to each relevant finding covering the data point in one sentence, the policy implication in one sentence, and the equity dimension if present, producing the raw material for every section of the policy brief before a sentence of narrative is written 5. An equity signal identification checklist — eight questions the analyst applies to each finding to identify whether it has an equity dimension across district wealth, student demographics, or geographic distribution, with the specific action for each equity signal (include in body, flag for sidebar, escalate for headline finding) based on the magnitude of the gap identified 6. A policy recommendation sentence structure — a three-part formula covering the finding, the policy action it supports, and the implementation timeline or condition, applied to each of the three policy questions to produce a recommendation paragraph that a state agency coordinator can quote in a procurement guidance document 7. A 5-day brief production schedule using the template — assigns day one for policy question extraction and section identification, day two for finding extraction from relevant sections, day three for equity signal identification and synthesis, day four for brief drafting using the finding extraction outputs, and day five for the quality audit and senior review preparation, with the specific output produced at the end of each day 8. A junior analyst quality audit checklist — ten criteria the junior analyst applies before submitting the draft, covering policy question alignment in the opening section, the equity finding prominence (the 34-point adoption gap must appear in the first two pages, not in a footnote), the recommendation sentence structure completeness, the finding extraction accuracy, and whether the brief can be read as a standalone document without the 80-page report present **Write every template component and process step assuming the junior analysts are thorough readers and inconsistent prioritizers — every step must include a specific decision rule about what to extract and what to skip, because the time problem is not slow reading, it is reading everything rather than the right things.**