Skip to content
Academy
Marketing Academy · Field WorkAI in Marketing
MiniTeardown· 20 minutes

Would You Feed This to Your RAG System? Three Documents, One Decision

Awfis Space Solutions

Objective: Given three candidate documents proposed for a RAG knowledge base, correctly decide which to include, which to exclude, and which needs a fix before inclusion, applying the lesson's 'What NOT to Include' checklist without over-flagging documents that are actually fine.

You're setting up Awfis Space Solutions' first RAG-powered content assistant, meant to draft location pages and pricing emails from a shared knowledge base before a national sales push.

Review all three candidate documents. For each, decide: include as-is, exclude entirely, or fix-then-include. Name the specific defect if you flag one.

Before you start

What you'll need

Free path (everything below is enough to finish)

FreeLog each candidate document with an include/exclude/fix decision and the reason

Free, sufficient for a document intake checklist

The process

Specimens to review

Include as-is, exclude, or fix-then-include? Name every defect you find.

Sample output
Awfis Coworking Plans
Hot Desk: Rs 6,500/seat/month
Dedicated Desk: Rs 9,800/seat/month
Private Cabin (4-seat): Rs 42,000/month
All plans include high-speed WiFi, unlimited coffee, and access to meeting rooms (2 hours/month included).
[filename: 'pricing_final_v2.docx', no date field anywhere in the document]

Specimen: synthetic, realistic

Include as-is, exclude, or fix-then-include? Name every defect you find, or state clearly that there are none.

Sample output
Awfis Brand Voice Guide, v4, last reviewed March 2026
Tone: Direct, practical, never corporate-jargon-heavy. We write like an ops manager, not a marketer.
Always say: 'centres' (not 'locations'), 'members' (not 'clients' or 'tenants').
Never claim 'largest in India' without citing the specific metric (for example, 'largest by number of centres, per FY24 filings').

Specimen: synthetic, realistic

Include as-is, exclude, or fix-then-include? Name every defect you find.

Sample output
Internal Slack thread export, #product-ideas channel, March 2026
'What if we offered a Rs 3,999 hot-desk plan for students and freelancers? Could undercut everyone in the market. Sales team thinks it could work if we cut the coffee/meeting-room perks.'
[No approval, no follow-up, thread has 4 replies, none from leadership]

Specimen: synthetic, realistic

Final deliverable

A document-intake decision log (include / exclude / fix-then-include) with the specific defect named for every excluded or flagged document.

See a reference example
Sample output
Slack RAG knowledge base intake log (excerpt)

Doc: 'Enterprise Plan Pricing Q2 2025.pdf'         Decision: EXCLUDE   Reason: no date stamp, superseded by Q3 2026 pricing already in CRM
Doc: 'Slack Brand Voice & Terminology Guide v6'    Decision: INCLUDE   Reason: dated March 2026, reviewed, no defects found
Doc: '#pricing-ideas Slack export, unreviewed'      Decision: EXCLUDE   Reason: internal speculation, no approval, no real product

Success criteria

You're done when you can:

  • Correctly identifies item 2 as clean with no defects
  • Names the specific missing element (date/version label, or approval status) rather than a vague 'looks off' judgment
  • Does not flag exact numeric pricing or document source (Slack vs formal doc) as defects on their own