GovTech Content Strategist and Editor [TO START TODAY]

NOTE: WE SEE TO START THIS PROJECT TODAY (SUNDAY) Infocap is seeking a public-sector content strategist and senior technical editor to revise a series of short guides (in PowerPoint currently) into a more persuasive, credible, and procurement-ready asset for federal, state, and city leaders. THE FIRST DOCUMENT AND EDITING INSTRUCTIONS ARE ATTACHED The first guide introduces document-heavy government workflows, including intake, classification, extraction, validation, routing, review, and human oversight. It also positions document modernization around speed, accuracy, compliance, capacity, and trust. We have prepared a very clear set of identified changes and edits to apply. The role of the editor is to apply these to turn the existing awareness piece into a stronger buyer-facing guide that speaks to agency executives, CIOs, CISOs, procurement leaders, legal counsel, records officers, program administrators, and operational leaders responsible for complex document-driven processes. The ideal candidate should have strong experience in: ** Public-sector technology writing, especially for federal, state, or local government buyers ** GovTech, document automation, AI-enabled workflows, e-permitting, case management, licensing, grants, benefits, claims, procurement, public records, or compliance processes ** Translating technical capabilities into executive-level buyer language ** Writing for skeptical public-sector stakeholders, including CIOs, CISOs, legal, procurement, records, accessibility, and compliance teams ** Editing sales collateral, ebooks, data sheets, pitch decks, white papers, and procurement-support materials ** General grounding GovTech concepts such as AI governance, human-in-the-loop workflows, auditability, source-grounded outputs, confidence scoring, exception handling, and model-risk language ** Exposure to public-sector security and compliance concepts, including FedRAMP, StateRAMP, SOC 2 Type II, NIST, FISMA, SSO, MFA, RBAC, Section 508, data ownership, retention, export, and deletion ** Clear, concise copywriting with disciplined avoidance of hype, unsupported claims, and vague “AI transformation” language Page-by-page content editing in PowerPoint or slide-based ebook formats Evidence of experience requested Candidates should provide: 1. Two to four examples of public-sector technology content they have written or substantially edited 2. At least one example of work involving AI, automation, document workflows, permitting, licensing, benefits, grants, public records, case management, or compliance 3. A short before-and-after writing sample showing how they improved clarity, credibility, or buyer confidence 4. Evidence of familiarity with government procurement concerns, such as security, records retention, auditability, accessibility, data ownership, cost predictability, and implementation risk SCOPE OF WORK The contractor will revise the existing guide page by page and deliver a polished version ready for design update. The work should include: ** Message refinement - strengthen the core positioning so the guide leads with public-sector pain points: manual document handling, fragmented intake, rework, staff capacity, audit readiness, service delays, and trust. ** Page-by-page rewrite - edit each page of the current ebook and provide ready-to-paste replacement copy for headlines, body text, captions, buyer checklist items, and calls to action. ** Trust and governance language - add clear language that automation captures, classifies, extracts, validates, routes, summarizes, drafts, and escalates, while accountable government decisions remain with authorized staff. ** Procurement-readiness additions - add or revise sections addressing security, records, public disclosure, retention, litigation hold, accessibility, data ownership, exit strategy, identity controls, integration with systems of record, cost controls, and implementation risk. ** Proof-point placeholders - create placeholders for evidence that should be added later, including sample workflow diagrams, audit logs, extracted data views, exception queues, public records exports, security architecture diagrams, and pilot metrics. ** Buyer checklist expansion - expand the current readiness questions into a stronger checklist for government executives, CIOs, CISOs, procurement officers, legal counsel, records officers, and program leaders. ** Implementation realism - strengthen the roadmap so it includes discovery, baseline measurement, security review, integration planning, user acceptance testing, staff training, acceptance criteria, launch support, and measured expansion. ** Language cleanup - remove jargon where possible, define technical terms where needed, and replace unsupported claims with more defensible language. All em dashes must be replaced with proper grammar and punctuation. Deliverables are "ready for print" versions of the edited document, as well as a page-by-page change log, a list of recommended visuals, and a final proofread version with no em dashes. Preferred final deliverables The initial job is a focused engagement (estimated 6 to 12 hours) but will include additional work on a similar pace of 12-15 hours per week