Source-backed RFP review guide.

Source-backed RFP review keeps the answer, citation, excerpt, status, and human-review note close enough to inspect.

Use source-backed review for public solicitation packages where the team needs traceable requirements, deadlines, flags, and drafting context.

Ask grounded questions only against actor-permitted, customer-authorized source material; keep controlled or prohibited content outside SourceFlag.

Treat answers as review inputs that can be wrong, incomplete, outdated, incorrectly cited, or misapplied.

• Start with public source files.
• Ask grounded questions.
• Inspect citations and excerpts.
• Create review rows.
• Flag needs-review items.
• Prepare kickoff and export handoff.
• Verify before relying on outputs.

• Step 1: confirm the source package is public, unclassified, and within the SourceFlag boundary.
• Step 2: inventory RFP files, amendments, attachments, forms, pricing workbooks, and Q&A documents.
• Step 3: ask grounded questions against the public source package and inspect the cited passages.
• Step 4: turn reviewed answers into compliance rows, deadline rows, risk flags, clarifying-question candidates, or kickoff notes.
• Step 5: verify each output against the original source before using it for drafting or handoff.
• Check that every answer has a source citation, owner, status, and human verification note.
• Use exports as handoff surfaces, not final proposal approval.
• Exclude restricted, non-public, controlled, classified, procurement-sensitive, and regulated personal data.

• Relying on an answer without checking the cited source passage.
• Skipping amendments, Q&A responses, attachments, or workbook instructions.
• Turning a needs-review flag into proposal direction before a human resolves it.
• Allowing CUI, FCI, classified, export-controlled, credential-bearing, regulated personal, procurement-sensitive, or similarly controlled material into SourceFlag.

• SourceFlag keeps answers, citations, excerpts, review flags, and proposal handoff work tied to the original public solicitation package.
• Teams can inspect public-opportunity summaries before creating a workspace.
• AI features and Human Review may be used only with customer-authorized public or unclassified solicitation material. Ordinary business-confidential proposal material may be stored and manually organized only in a private_storage_only project. AI features, Human Review, and background processing are locked off for that project. AI features, Human Review, and background processing are locked off for that project. Human review remains required before reliance.