Velocibid

Submission Rules

Enforce response quality with word limits, banned terms, and custom AI instructions that align every submission to policy.

What are Submission Rules?

Submission Rules allow you to enforce strict compliance standards across your proposal. You can set word limits, ban specific terms, and create custom AI-powered instructions to ensure every answer meets your quality standards.

How to Configure Rules

  1. Open your project dashboard
  2. Click the Actions dropdown menu in the header
  3. Select Submission Rules
  4. Configure your Banned Terms and Custom AI Instructions
  5. Global rules apply to the entire project

Rule Types

1. Word Limits

Set maximum word counts for individual questions.
How to set: Click the "Set Limit" dashed usage badge on any Question Card.

2. Banned Terms

Define words or phrases that should never appear in your proposal (e.g., competitors' names, insecure technologies).
Enforcement: Answers containing these terms are flagged as "High Severity" issues.

3. Custom AI Instructions

Create flexible, plain-English rules that the AI validates semantically.
Examples:

  • "Must explicitly mention our ISO 27001 certification"
  • "Do not discuss pricing in the executive summary"
  • "Always refer to the customer as 'The Client'"

Validation & Scoring

Rules are enforced when you run a Quality Score check.

Penalties

  • Word Limit Violation: -15 points
  • Banned Term Found: -20 points
  • Custom Rule Violation: -15 points per violation

Best Practices

  • ✓Use Banned Terms for strict keywords (competitors, old product names)
  • ✓Use Custom AI Instructions for complex logic or tone requirements
  • ✓Set Word Limits on summary questions to keep them concise

Practical Implementation Notes

This guide is designed to help proposal, security, and operations teams execute Submission Rules consistently inside Velocibid. If you are onboarding new contributors, use this page as a standard operating reference and pair it with related documentation so your team follows one repeatable workflow.

For stronger outcomes, combine this playbook with adjacent guides in the same lifecycle stage (discovery, response, compliance, and delivery). Cross-functional teams that align their process across these modules typically reduce rework and improve proposal quality.