Skip to main content

Document Package

How to use Document Package in Proposals V2, including document upload, tagging, workflow setup, and automated requirement extraction.

Written by Denise DeFilippo

Overview

The Document Package is the starting point for the Proposals V2 workflow. It allows you to upload solicitation documents, tag them by type, and run an automated workflow that extracts requirements and builds your initial proposal structure.

Using this step ensures your proposal is grounded in the actual RFP content from the beginning.

Step 1: Upload Documents

From the Document Package tab, click Upload to add solicitation documents.

You can upload or select:

  • RFP / Solicitation

  • PWS / SOW

  • Amendments

  • Attachments (Instructions, Templates, Pricing, etc.)

You may also select documents already pulled in from SAM.gov.

Step 2: Select Documents

Choose the documents you want to include in your proposal package.

Tip:

  • Include all relevant attachments and amendments to avoid missing requirements

  • You can upload additional files if needed

Step 3: Tag Documents

After selecting documents, assign a Document Type to each file.

Common document types include:

  • RFP/RFI/RFQ

  • PWS / SOW

  • Instructions

  • Amendment

  • Pricing

  • Q&A

  • Evaluation

  • Other

Why this matters:
Tags help the system understand how to interpret each document and which content to prioritize during extraction.

Step 4: Review Uploaded Documents

Once added, your documents will appear in the Document Package list.

Here you can:

  • Confirm document tags

  • Add or update tags

  • Remove documents if needed

  • See processing status

Step 5: Run the Workflow

Click Start Workflow to begin processing your Document Package.

Configure:

  • Outline Name

  • Outline Type (Proposal or RFI)

  • Overwrite Existing Data (Yes or No)

Then click Run Workflow.

Step 6: Workflow Processing

The system will automatically process your documents and generate proposal components.

This includes:

  • Parsing documents and extracting structure

  • Building the Compliance Matrix

  • Generating Win Themes

  • Identifying Key Personnel needs

  • Extracting Past Performance requirements

  • Mapping Technical Task Areas

  • Creating an initial Outline

Each step will show status and may require user review.

What happens next?

After the workflow completes, move into each stage to review and refine:

  • Validate requirements in the Compliance Matrix

  • Customize Win Themes

  • Assign Key Personnel

  • Select Past Performance references

  • Refine your Solution and Task Areas

  • Review and adjust the Outline

When should I use Document Package?

Use Document Package when:

  • You have a full RFP package

  • You want a fast, structured starting point

  • You want alignment across all proposal stages

Skip or use manual upload when:

  • You only have partial or early-stage documents

  • You are working in a single section

  • You are updating an existing proposal

Best Practices

  • Upload the complete document set whenever possible

  • Always include amendments and attachments

  • Ensure documents are clear and readable (poor OCR can impact results)

  • Review outputs in each stage. The workflow accelerates setup but does not replace validation

Common Issues

  • Missing requirements
    Often caused by missing attachments or amendments

  • Incorrect or incomplete extraction
    Usually due to poor document quality or OCR issues

  • Content mapped to the wrong sections
    Often caused by incorrect or incomplete document tagging

Expected Outcome

Running the Document Package workflow results in a structured proposal workspace with extracted requirements, aligned content, and an initial outline ready for refinement and draft generation.

Did this answer your question?