Open to selected opportunities

Documentation built for people, search, and AI retrieval.

I turn product knowledge into clear, searchable, AI-retrievable content that improves self-service, strengthens discoverability, and makes accurate answers easier to surface across search and AI systems.

View case studies → Work with me
Currently Knowledge Management Analyst, Sovos
Based in Philippines · Remote
Practice Technical documentation & knowledge management
Focused on Retrieval-ready knowledge architecture

Documentation used to have one reader. It now has three: The person searching, the search engine ranking, and the model retrieving.

Most content fails the last two for the same reason. It was written as a document instead of as a set of answers.

Systems built to hold up.

Six connected areas of practice, grounded in shipped work rather than framework theory.

01

Technical writing & documentation

Documentation a reader can act on without asking for help. Product, support, and process documentation, with procedures written to ASD-STE100 principles.

02

Knowledge management

A knowledge base the team can rely on instead of asking around. Structure and content lifecycle: Ownership, review commitments, escalation paths, audits, and migration.

03

Information architecture & documentation systems

Taxonomy, metadata, and structure. The rules that decide where a piece of content lives and what it is called, so content gets found and reused instead of rewritten.

04

Search & retrieval optimization

Content shaped for how it is found: Chunk boundaries, answer-first openings, naming, and metadata, for search engines and for retrieval alike. Boundaries drawn to the answer are what give a retrieval step context efficiency.

05

AI-assisted documentation

AI throughput with quality held by the system, not by hope: LLM-assisted drafting behind human review, output contracts, and QA gates. Knowledge gap analysis against what a chatbot or AI assistant actually answers.

06

Context engineering & prompt design

Designs prompts and AI workflows around model capabilities, context limits, and task structure to improve output reliability while minimizing unnecessary token use.

Procedural & Instructional Writing

Turn specialist knowledge into instructions people can execute correctly the first time.

I create manuals, SOPs, training guides, and support procedures that reduce ambiguity, speed up onboarding, and make complex processes easier to perform consistently.

Raw source knowledge if they want the reports to download as csv instead of excel you can change it somewhere in admin settings. go to reporting then export settings I think, change the file type dropdown to csv and save. this only changes new exports, old ones stay the same. probably do a test download after.
Published procedure

Set report exports to CSV

New report exports will download as CSV files.

  1. In the Admin panel, open Default file format.
  2. In the upper-right corner, select CSV (.csv).
  3. Select Save changes.
  4. Export a test report and confirm that it downloads as a .csv file.

Note: Existing exported files are not affected.

Raw source

Unstructured source material such as notes, brain dumps, meeting transcripts, recordings, SME input, or rough drafts. The information is there, but the reader has to interpret and organize it.

Published content

Structured, task-focused documentation with clear outcomes, navigation, actions, and supporting notes. Designed to be easy to follow, scan, search, maintain, and retrieve.

Fewer support questions Faster onboarding More consistent execution
Explore my documentation approach

Featured Work

Three documentation systems, and the method behind the retrieval work.

01 · Documentation Systems

AI-Assisted Documentation Pipeline

Every hour a writer spends on transcription and formatting is paid for and returns no judgment. The pipeline moves that work onto a deterministic layer with QA gates and audit logs, so writer attention goes back to judgment and draft quality stops depending on individual discipline.

Evidence

Team drafting reached 93 drafts in its peak week against a 40-per-week baseline, drafting stage only. Separately, in the Claude Cowork experiment, one person produced 63 QA-validated articles from 22 source documents in one week.

Output Contracts Deterministic Rendering Audit Logs AI Drafting Human-in-the-Loop Review
Read case study →
02 · Knowledge Management

Knowledge Lifecycle & Governance Framework

When process lives in tribal knowledge, work gets duplicated and no one can say where an article stands. One controlled model for how content is created, reviewed, retired, and escalated: Nine lifecycle statuses, each with a named owner and the evidence required to leave it.

Evidence

Nine controlled statuses, each with one named owner and required evidence. Endorsed by the Team Lead.

Lifecycle Design Content Governance Ownership & Handoff Evidence Gates SLAs & Escalation
Read case study →
03 · Publishing Workflow

Knowledge Article Staging Tool

A writer with no HTML background publishes clean, validated, Salesforce-ready HTML without hand-editing markup. The formatting toll on every article collapses to minutes, and validation catches defects before publication instead of after.

Evidence

Typical article staging: 30–60 minutes down to about 15, with validation built in. Every member of the knowledge team uses it.

Documentation Publishing HTML Validation Style Standardization Salesforce Knowledge
Read case study →

Beyond the case studies

Smaller builds and frameworks that show the range behind the case studies.

Measurement & evidence

Built a nine-tab AI productivity model isolating active work time from cycle time, normalized by task complexity.

Retrieval architecture

Designed how guides are scoped, chunked, and named across my product area for RAG retrieval and SEO, and structured the source content an internal support chatbot trains on.

Documentation standards

SLAs, KPI definitions, and escalation paths endorsed as the knowledge function’s source of truth.

Working together

Three ways I take on outside work.

Technical & procedural writing

Specialist knowledge your users cannot act on yet. Manuals, SOPs, and training guides written so a reader follows them without help.

Technical & procedural writing service

Documentation systems & KM setup

Knowledge that lives in inboxes and heads. Structure, ownership, and lifecycle rules that keep content findable and current.

Documentation systems service

Retrieval-ready content

A chatbot or AI assistant that answers using the wrong guide. Article boundaries, naming, and metadata designed for retrieval, search, and people at once.

Retrieval-ready content service

Documentation that people and machines can both find.
Let’s talk.

I started in technical documentation and moved upstream, into the systems that control how knowledge gets created, governed, measured, and delivered: To people and, increasingly, to AI.

Tools & methods
Technical documentation Procedural writing ASD-STE100 principles Salesforce Knowledge Confluence Jira RAG & SEO Claude Microsoft Copilot
Start a conversation View resume
Connect on LinkedIn ↗ Open to roles and selected projects in technical documentation, knowledge management, and retrieval-ready content.