Candidate Knowledge Base

1. 1

   Core candidate and campaign facts

   Candidate name, office sought, district or jurisdiction, campaign website, biography, professional/community background, campaign priorities, and other approved identity information.

2. 2

   Policy positions and issue knowledge

   Campaign-approved positions, issue explanations, priorities, talking points, supporting details, and boundaries around topics that require additional review.

3. 3

   FAQs and approved responses

   Common voter questions and concise, campaign-approved answers that can support two-way SMS, campaign AI experiences, phone support where enabled, and the WhyIVote candidate profile and Q&A experience.

4. 4

   Sources, approvals, and freshness

   Each important knowledge item should preserve where it came from, who approved it, and when it was last reviewed so the campaign can update the record when positions, wording, endorsements, schedules, or other facts change.

1. 1

   Authorized content owner / approver

   A campaign manager, communications lead, candidate, consultant, or other authorized person who can approve candidate facts, issue positions, FAQs, and voter-facing response language.

2. 2

   Official candidate background

   Candidate biography, office sought, district/jurisdiction, campaign website, professional and community background, relevant accomplishments, and other campaign-approved profile information.

3. 3

   Policy and issue materials

   Platform documents, issue pages, position statements, campaign memos, approved talking points, speeches, public statements, and other source material the campaign wants reflected in voter-facing answers.

4. 4

   Frequently asked questions and prior answers

   Questions the campaign already receives from voters, donors, volunteers, press, events, social media, canvassing, or prior texting, together with any existing approved responses.

5. 5

   Approval rules and sensitive-topic boundaries

   Direction on topics that require candidate review, legal/compliance review, staff follow-up, or a “do not answer automatically” rule.

6. 6

   WhyIVote profile assets and preferences

   Approved candidate photo, short biography, key priorities, issue ordering, campaign links, and other information needed when the campaign will use a WhyIVote mobile candidate profile.

7. 7

   Language requirements

   Any approved non-English source materials, translation requirements, or language-review contacts needed for multilingual voter-facing content.

8. 8

   Update and review expectations

   The campaign contact and turnaround expectations for approving new answers and updating the knowledge base when campaign positions or facts change.

• Collect and inventory approved candidate, campaign, policy, issue, FAQ, and source materials provided or authorized by the campaign.
• Create a structured knowledge taxonomy covering candidate profile, office/district, priorities, policy/issue topics, FAQs, approved responses, campaign links, and escalation categories.
• Normalize overlapping source material into clear knowledge records without silently changing the campaign's substantive position.
• Draft concise answer-ready summaries and fuller supporting answers for campaign review when source material supports them.
• Attach source references, approval status, reviewer, and last-reviewed metadata to important knowledge items.
• Configure answer boundaries so unsupported, ambiguous, sensitive, or out-of-scope questions can be captured and escalated instead of improvised.
• Prepare approved knowledge for downstream uses such as Step 7 messaging design, AI-assisted SMS conversations, candidate-facing phone support where enabled, and WhyIVote candidate-profile / voter-Q&A content.
• Support campaign review, revision, approval, versioning, and re-publication as campaign facts or positions change.
• Run sample-question and coverage checks before declaring the knowledge base ready for messaging design and launch.

• Authorized campaign content owner / approver
• Candidate full name, office sought, district/jurisdiction, election date, and campaign website
• Approved candidate biography and background materials
• Policy platform, issue pages, position statements, campaign talking points, and other approved source documents
• Current campaign priorities and the issues most likely to appear in voter conversations
• Existing FAQs, prior voter questions, and any approved response language
• Topics that must be escalated or not answered automatically
• Approved campaign links, social links, and contact/action destinations
• WhyIVote profile photo, short bio, issue ordering, and profile preferences if the integration will be used
• Language / translation requirements and designated reviewers where applicable
• Approval turnaround expectations and the process for urgent updates during the campaign

• The campaign has not designated a single authorized reviewer, resulting in conflicting edits or unclear approval authority.
• Candidate positions differ across the campaign website, policy documents, prior speeches, social posts, or internal talking points and the campaign has not resolved which version controls.
• The campaign provides broad policy documents but no concise approved language suitable for voter conversations, requiring additional review before deployment.
• Frequently asked voter questions are not yet documented, leaving obvious knowledge gaps that must be filled before launch.
• Sensitive topics lack clear escalation rules, creating a risk that staff and AI systems do not know when to stop and request human review.
• Candidate biography, endorsements, event details, office information, or other time-sensitive facts change after approval and the knowledge base is not updated promptly.
• Multilingual content is requested without an approved translation/review workflow for policy-sensitive language.
• The campaign wants the system to answer questions that are not supported by approved source material. Those questions should be captured and escalated rather than answered from general knowledge.
• WhyIVote candidate-profile content is treated as a separate copy instead of being tied back to the approved Candidate Knowledge Base, increasing the risk of inconsistent information across channels.

Questions