Skip to main content

Document Shred

Written by Matt Miller
Updated over a month ago

On this page

  • Overview

  • Why Document Shred Is Required

  • Create a New Shred

  • Select Documents and Keywords

  • Review Extracted Requirements

  • Use Filters and AI Recommendations

  • Bulk Approve or Reject Requirements

  • How Document Shred Is Used

  • Best Practices

Overview

Document Shred is the first and required step in the Proposals V2 workflow. It extracts, categorizes, and validates solicitation requirements from your uploaded documents, creating the compliance foundation for proposal development.

Approved requirements from Document Shred are used to generate your Proposal Outline, Technical Task Areas, and Pink Team Draft.

Navigate to Proposals β†’ Shred to begin.


Why Document Shred Is Required

Document Shred replaces manual compliance matrix creation by automatically identifying proposal requirements from solicitation documents.

It helps teams:

  • Ensure all requirements are captured

  • Improve compliance accuracy

  • Reduce manual compliance review effort

  • Enable structured and collaborative requirement validation

  • Provide validated inputs for proposal generation

Document Shred ensures downstream proposal content aligns with solicitation requirements.


Step 1: Create a New Shred

Click Create New Shred.

Select the solicitation documents you want to analyze, such as:

  • Request for Proposal (RFP)

  • Performance Work Statement (PWS)

  • Statement of Work (SOW)

  • Amendments and attachments

Keywords used to extract requirements are preconfigured and include terms such as:

  • shall

  • must

  • required

  • will

  • provide

Click Create Shred to begin processing.


Step 2: Wait for Processing to Complete

The system will analyze the selected documents and extract requirements.

Processing typically takes a few minutes.

Once complete, the Generation Status will show Completed.

Click on a document to review extracted requirements.


Step 3: Review Extracted Requirements

Each extracted requirement includes the following information:

Source Location
Displays where the requirement appears in the original document.

Content
Displays the extracted requirement text.

Category
Identifies requirement type, such as:

  • Technical

  • Management

  • Personnel

  • Proposal Submission

AI Suggestion
Provides an AI recommendation to Accept or Reject the requirement, including reasoning.

Confidence Level
Indicates how confident the AI is in its recommendation.

Review Status
Shows current review state:

  • Accepted

  • Pending

  • Rejected

Notes
Allows users to add comments or clarification.


Step 4: Use Filters and AI Recommendations

Filters help prioritize and accelerate requirement review.

Available filters include:

  • Keywords

  • Categories

  • AI Confidence

  • AI Recommendation (Accept or Reject)

  • Review Status

These filters allow users to quickly review high-confidence requirements and validate compliance efficiently.


Step 5: Bulk Approve or Reject Requirements

You can review requirements individually or in bulk.

To bulk approve requirements:

  1. Filter by AI Recommendation = Accept and Review Status = Pending

  2. Select the requirements

  3. Click Approve

To reject requirements, follow the same process and click Reject.

Bulk actions help teams efficiently validate large solicitations.


How Document Shred Is Used

Approved requirements from Document Shred are used to generate:

  • Proposal Outline

  • Technical Task Areas

  • Compliance alignment

  • Pink Team Draft

Document Shred provides the structured compliance foundation for proposal development.


Best Practices

  • Upload complete solicitation documents, including amendments

  • Review all extracted requirements before generating the outline

  • Use AI recommendations to accelerate review, but validate manually

  • Use filters to prioritize review

  • Complete requirement review before proceeding to Outline and Solution steps

Did this answer your question?