Document Types

What are Document Types?

Document Types, put simply, are types of documents that GovDash recognizes. This categorization gives GovDash the flexibility to tailor processing for each document individually based on where it is best suited.

What are They Used For?

Document Types are primarily used to determine the way a document is categorized, which dictates when it is used within GovDash. For example, GovDash will not attempt to search for Task Area (Work) Requirement text from a Staffing Roster or Win Themes document. By categorizing (or classifying) sentences within a document, we can provide a standard way to use the important and relevant parts of a document throughout GovDash.

When Are Documents Categorized?

In most cases, right when you upload a document into GovDash! In most document workflows, the very first thing GovDash does is run documents through our AI Document Classification system. This performs a combination of checks as well as AI evaluation of the contents of a document to try to determine a document’s type.

In the Data Library, this happens as soon as documents are uploaded and processed. In Proposal Cloud and Contract Cloud, we don’t classify document types until you initiate their respective workflow process (i.e. starting a proposal draft, or uploading a contract).

GovDash Cloud-Specific Use Cases

As each area (or Cloud) of GovDash serves a different purpose and role within an opportunity’s lifecycle, naturally documents would be used differently depending on the context of each Cloud. Below we will outline some Cloud-specific use cases for document types.

Capture Cloud

Within the Capture Cloud, document types are primarily used to discern which documents we use to populate Capability Matrices, as well as populating the Shred View tab (line-by-line shreds of documents). These classification runs are preserved and un-changed when you bring an opportunity from the Pipeline to the Proposal Cloud, which saves you time to generate your outline.

Proposal Cloud

Document types are a foundational part of Proposal Cloud. When building an outline, GovDash tries to cut out as much noise as possible from the documents and focus squarely on text that fall into these main categories: Proposal Preparation Instructions, Task Area Requirements, and Evaluation Criteria.

Document types are the sole determinant for which documents get these categorization processes run on them. There is often too much text and noise to sift through in a typical solicitation package of documents to try to get a usable or worthwhile outline from it, so we rely on document types to discern what matters for creating outlines, generating compliance matrices, and generating content.

If you want to be certain that the contents of a document are being used in Proposal Cloud, you must double-check that the types on the solicitation package documents are being set appropriately or otherwise its contents will be not visible to our AI systems responsible for extracting these key details.

When you changing the document types in your solicitation package in Proposal Cloud, we enforce a process called Re-Processing for your outline.

Changing a document’s type means a different context will be used when GovDash potentially uses the document to create your outline, which can influence which documents will appear in areas like Shred Views, and which documents can be cited from in the Citation Editor for compliance. This ultimately means the resulting content generated after changing document types can greatly diverge from the initial version.

Contract Cloud

Document types serve a critical role when creating contract awards in the Contract Cloud. They determine which documents are eligible to be considered the main document types on an award, which is composed of a Contract Award Summary and the PWS/SOW.

Similar to Proposal Cloud, Contract Cloud relies on the same document text categorization, and therefore document types, to build your capabilities “database”. Since capabilities are made up of Task Area / Work Requirements, GovDash relies heavily on these document types to ensure it’s getting accurate data from the correct documents.

List of Document Type-to-Categorization Mappings

Below is a list of examples of where GovDash will utilize specific document types for specific tasks.

Document types we consider to contain Task Area / Work Requirements. These are used primarily in capability matrices, document shreds, and compliance matrices.

PWS
SOW
RFP
RFI
RFQ
TO (Task Order)
Sources Sought

Document types we consider to contain Proposal Preparation Instructions & Evaluation Criteria. These are used primarily in document shreds and compliance matrices.

ITO
RFP
RFI
RFQ
TO (Task Order)
Sources Sought
Questionnaire

Document Type Descriptions

Document Type	Description
RFP	Request for Proposals, a formal government request soliciting detailed, structured proposals from vendors. Typically includes stated requirements, evaluation criteria, specific instructions for submitting proposals, solicitation numbers (e.g., RFP numbers, solicitation IDs), and due dates.
RFI	Request for Information, a preliminary document in which the government seeks industry/vendor input, insights, or comments regarding potential procurements. Usually does not lead directly to contract awards. May mention possible future solicitations or RFPs/RFQs, but they primarily ask vendors general questions about capabilities, technologies, market status, or approaches.
RFQ	Request for Quotations, a government document requesting pricing quotations from pre-qualified vendors for specified products or services. Usually shorter and simpler than an RFP, directly emphasizes price/cost responses, clearly referencing the solicitation or request number.
TO	Task Order, a document issued under an existing master or IDIQ (indefinite delivery, indefinite quantity) parent contract, identifying specific discrete requirements or projects, obtaining goods/services already agreed upon through overarching contracts. Clearly references the parent or master contract ID/number.
DATA CALL	Document from a government agency or prime contractor requesting specific data, metrics, reports, technical information, or status updates. Typically references existing contract numbers, task orders, projects, or known efforts.
SOURCES SOUGHT	Market research notice from the government designed to determine vendors' capabilities and interest in a potential procurement. It asks explicitly for vendor qualification, past performance, relevant experience, capabilities statements. This is not an invitation for proposals; no specific price is requested at this stage.
PWS	Performance Work Statement, a type of statement of work defining contract work in terms of outcomes, deliverables, and measurable performance criteria/standards, commonly metrics and targets that clearly evaluate contractor performance. Usually provided by government.
SOW	Statement of Work, a detailed narrative description from the government defining the specific tasks, deliverables, expectations, requirements, and timelines for goods/services under a particular contract or solicitation. Often referenced in RFPs, RFQs, and contracts.
MONTHLY STATUS REPORT	Regular, periodic report (often monthly), prepared by a contractor outlining progress, tasks completed, remaining work, project status, significant events/milestones achieved, issues, risks, and status relative to agreed scope requirements and deliverables.
CONTRACT AWARD SUMMARY	Announcement or summary describing details of the awarded government contract to the vendor, explicitly stating contract number, award date, amount awarded, vendor name, any known subcontractors or partners, brief scope and service/product specifications.
CONTRACT AWARD SPREADSHEET	Excel spreadsheet or tabular structured data clearly listing awarded contracts, award dates, awarded vendors, dollar amounts, task/item descriptions, relevant ID/numbers, periods of performance, item quantities, and pricing info.
DELIVERABLES	Defined items or documents explicitly required under a contract, including reports, software, hardware, data submissions, technical/performance results, documentation, presentations, or other tangible outputs.
TEAMING AGREEMENT	A formal, signed agreement between businesses/partners made prior to proposal submission. Clearly identifies potential RFPs or upcoming contracts, highlighting the division of roles, responsibilities, and exclusivity terms.
SUBCONTRACT AGREEMENT	Contractual document between prime contractor and subcontractors, clearly referencing the contractual terms, conditions, requirements, scope, and flow-down clauses from the prime (main) government contract.
CONTRACT MODIFICATION	Official modification or amendment to an existing awarded contract explicitly stating changes to original contract terms, schedule, pricing, scope, or deliverables. Clearly references the original contract award ID, modification number, and effective date.
ITO	Instructions to offerors, government-provided clear instructions outlining formatting, content requirements, submission procedures, schedules, evaluation criteria, required proposal structure, and compliance details specific to submitting proposals.
KEY PERSONNEL RESUME	Resume, CV, or biographical profile of key individuals, usually submitted alongside a proposal. Identifies someone's qualifications, experiences, responsibilities, roles, and relationship, sometimes framed as helping a proposed effort.
STAFFING ROSTER	A staffing roster/staffing plan/management approach will explicitly identify organizational personnel, titles, roles, responsibilities, and positions designated to fulfill a specific contract or project.
PROPOSAL	Lengthy detailed authoritative document prepared by the contractor, addressing government requirements. Explicitly composed of multiple sections presenting technical, management, pricing/cost strategies, and vendor qualifications in response to an RFP, RFQ, or other solicitation.
ORGANIZATIONAL CHART	Visual schematic clearly illustrating the organizational structure, reporting hierarchy, roles, responsibilities, and communication pathways of teams participating in a proposal or project.
FINANCIAL STATEMENT	Formal financial documents clearly presenting financial status, assets, liabilities, balance sheet, cash flow statements, or financial projections submitted as reference during proposal and contracting phases.
TECHNICAL VOLUME	Detailed proposal volume addressing the technical aspects, methodologies, processes, technology, and solutions proposed for meeting solicitation technical requirements.
MANAGEMENT VOLUME	Detailed proposal volume outlining project management approach, key personnel management roles, project schedules, resource allocations, KPIs, supervision, organizational structure, and performance monitoring strategies.
COST VOLUME	Specific volume of proposal containing detailed price breakdown, hourly rates, materials costs, direct/indirect costs, profit, overhead, pricing assumptions, and associated budget justifications.
PAST PERFORMANCE VOLUME	Volume presenting historical and recent performance examples demonstrating capability, credibility, reliability, and qualifications through references, customer testimonials, ratings, awards, and completed project summaries.
COMPLIANCE CERTIFICATION	Signed formal document certifying contractual, policy, regulatory, statutory, or cybersecurity compliance requirements related to an RFP or contract. Clearly states specific compliance requirements applicable.
SECURITY CLEARANCE	Document explicitly identifying personnel or facility security clearance details, clearance levels, statuses, evidence of clearance authorization relevant to classified or security-sensitive contracts.
QUALITY ASSURANCE VOLUME	Proposal content strongly detailing contractor's internal quality control systems, processes, standards, inspections, auditing practices, protocols to ensure deliverable quality conformance to contractual requirements.
RISK MANAGEMENT VOLUME	Proposal volume clearly outlining identification, analysis, assessment, handling plans, mitigation strategies, contingency actions, and proactive management of identified project-related risks.
MEETING MINUTES	Official summary/transcripts documenting meeting discussions, action points, resolutions, decisions, attendees, agenda items, clearly linking to contract deliverables/tasks.
TRAINING MATERIALS	Instructional materials/documentation prepared to fulfill employee/customer/user training obligations clearly defined under a contract.
GAO REPORT	Government Accountability Office-issued official reports containing audit findings, financial assessments, procurement evaluations.
BACKGROUND INFORMATION	Supporting informational documents providing historical context, strategic relevance, or previous studies/data relating directly to project/contract scopes.
CUSTOMER INFORMATION	Details about the customer or agency.
WIN THEMES	Strategic proposal themes and differentiators.
CUSTOMER NEEDS	Analysis/writeup of customer requirements and pain points.
TEAMING PARTNERS	Information about team members and partners.
QUESTIONNAIRE	Structured set of written questions provided by the government or prime contractor, clearly requesting vendor-supplied responses on specific topics. These documents typically seek detailed information about a contractor's capabilities, past performance, compliance status, security posture, technical expertise, financial health, risk profile, or other areas critical for government evaluation and assessment. Usually formatted explicitly as discrete questions and answer fields, tables, checklists, or clearly numbered/lettered sections intended for direct responses.
CONTRACT ATTACHMENT	An additional document explicitly defined as an attachment, exhibit, annex, or addendum linked directly to a key contract. Typically includes supplementary information, terms, drawings, specs, requirements, or reference materials.
UNKNOWN	Documents that cannot clearly be categorized under any given classifications due to insufficient information or unfamiliar content.
CPARS	Documents that report and rate the contractor's performance according to the government's “Contractor Performance Assessment Reporting System”.