BidOps Desk

Operator workspace

The clearest next action across source health, pursuit readiness, and evidence.

Updated View data
operator-dashboard-read-model.v3 generated from seedEvidence-first operating view

Current opportunity

Dallas facilities maintenance RFP

City of DallasResponse due Aug 22, 2026, 10:00 PM UTC
Decision pulseReview context

pursue_with_conditions: strong service fit but insurance evidence is missing

Pursuit activeApproval package blocked pending client evidence
Open actions6ranked for today
Evidence blockers1need client resolution
Launch readiness11/121 blocked · 0 stale
Change impact3artifacts to recheck

01 · Today

What should happen next?

Every item is ranked by severity, category, then due date.

Ranked operator queue

Priority reflects the recorded blocker, deadline, or freshness risk.

6 open items
RankQueue itemSeverityDueSource
#1Overdue EvidenceRanking rationale: Commercial auto insurance evidence is overdue and blocks package approval.Next operator step: Request and review the current commercial auto insurance certificate.criticalJul 17, 2026, 5:00 PM UTCclient-evidence-version-insurance-1
#2Change ImpactRanking rationale: Addendum 1 invalidated mandatory package coverage and client authorization.Next operator step: Revalidate requirements, regenerate the package, and request fresh approval.criticalJul 18, 2026, 5:00 PM UTCopportunity-document-1#addendum-1
#3Deadline RiskRanking rationale: The response deadline is inside the operator escalation window.Next operator step: Confirm the remaining response plan and assign every open requirement.criticalJul 19, 2026, 5:00 PM UTCopportunity-version-1
#4Launch BlockerRanking rationale: Paid-pilot launch is blocked until the first human submission receipt exists.Next operator step: Follow td-bea653: a human authorizes and performs final submit, then attaches the receipt.criticalNo due datedocs/operations/first-human-submission-receipt.md
#5Approval ExpirationRanking rationale: The current package approval expires before the response deadline.Next operator step: Renew authorization against the immutable package version before expiration.warningJul 20, 2026, 5:00 PM UTCpackage-approval-version-1
#6Source HealthRanking rationale: The Texas ESBD checkpoint is outside its freshness SLA.Next operator step: Rerun the ESBD connector and inspect the checkpoint receipt.warningNo due datesource-run-esbd-1

Evidence autopilot · request workflow

Resolve evidence before submission

Pilot client · read model generated Jul 16, 2026, 8:05 PM UTC

  1. STEP 1RequestAutopilot queue
  2. STEP 2EvidenceClient records
  3. STEP 3SubmitPackage approval

1. Autopilot requests

3 open · 1 blocking

2 unresolved requirements

2. Evidence provenance

Evidence request records retain their stated source references and current state.

Current commercial auto insurance certificateneeds_client_upload

A current commercial auto certificate is missing from the approved client evidence vault.

source: opportunity-document-1#section-5.4requirement: RFP section 5.4 — Commercial auto insuranceformats: PDF, JPG, PNG
Approved HUB certificationapproved

No blocker. The approved HUB certification is current and proposal-safe.

source: client-evidence-version-cert-1requirement: RFP section 3.1 — HUB certificationformats: PDF
Current signed W-9needs_client_upload

The approved W-9 expired and cannot support the current package.

source: client-evidence-version-w9-1requirement: RFP attachment C — Vendor tax formformats: PDF
Proposal-use approval or a replacement approved case studysubmitted

The reference evidence is on file but is not approved for use in proposal claims.

source: client-evidence-version-reference-1requirement: RFP section 7.2 — Relevant experienceformats: PDF, approval record

3. Package submission

Approval unavailable until mandatory evidence requests are resolved.

Cannot submit: package approval status is blocked.

Approved evidence records change only after client approval; unresolved requirements stay unknown until then.

Change radar

Impact heatmap

Addendum changes linked to Dallas facilities maintenance RFP

Current source state

Source changes are live: invalidated approvals and packages must be regenerated before submission.

Invalidated
2invalidated
Flagged
1flagged

Requirement impact matrix

Rows are grouped by requirement and ordered from invalidated to flagged impacts.

invalidatedflagged
RequirementSource deltaAffected artifactsImpact level
Requirement · req-bondrequirement_changed

Requirement changed from "Bid bond of 5%" to "Bid bond of 10%".

Bid bond of ten percent (10%) is required.

docver-1 → docver-2
invalidated · approval
approval-1
Client approval of bond response is invalidated because requirement req-bond changed.
invalidated · package_file
package-1
Submission package version 1 is invalidated because requirement req-bond changed.
invalidated
Response deadlinedeadline_changed

Response deadline changed from 2026-08-15 to 2026-08-01.

oppver-1 → oppver-2
flagged · evidence_mapping
mapping-1
Insurance evidence mapping must be rechecked against the new response deadline.
flagged

Affected opportunity

Dallas facilities maintenance RFP

Explainability / Vertical timeline

Evidence chain for a matrix row

Bid bond of 5% is required and supported by client evidence.

matrix row
Chain status
Complete
Missing links
0
Excluded evidence
0
5-stage chain
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
Audit trail
TimeActorEvent
Jul 18, 2026, 10:00 AM UTCoperator-1Approved bond letter evidence.
Jul 19, 2026, 9:30 AM UTCsystemLinked evidence to matrix row.

Every link in this chain is inspectable from source document to output.

Client approval inbox

Pilot client

BidOps recommends pursuing with conditions because service fit is strong and insurance evidence is still missing.

Package approval
blockedApproval unavailable until mandatory evidence requests are resolved.
Client scopeShowing requests for Pilot client only.
Requests4

Selected request

Upload current commercial auto certificate.

needs_client_upload
Evidence state
missing
Required artifact
Current commercial auto insurance certificate
Requirement reference
RFP section 5.4 — Commercial auto insurance
Source reference
opportunity-document-1#section-5.4
Request text

Please upload the current commercial auto insurance certificate as a PDF, JPG, or PNG so we can verify RFP section 5.4 before package approval.

Blocker reason

A current commercial auto certificate is missing from the approved client evidence vault.

Upload certificate for review.

Submission safety

Human final submit required

The system prepares the approved package, then stops. A human completes final submit.

Resolve blockers before human final submit
System final submit

Disabled

Immutable package

proposal-version-2

sha256:proposal-version-2
Authorization

Not yet recorded for this package

Human submission checklist
  • Required: Current package approval
  • Required: Package-bound authorization
  • Required: Stopped before final submit
  • Required: Human submission receipt
Why final submit is blocked
  • A current approval is required for the immutable package version.
  • Portal assistance must complete visible preparation before human final submit.
  • Replay evidence must show the workflow stopped before final submit.
  • A human must authorize this exact immutable package before final submit.

After the human submits, attach the portal confirmation to this immutable package version.

Traceability

Audit events

2 events
  1. Generated evidence-linked decision rationale.

    qualification-analyst ·
  2. Blocked package approval because mandatory evidence is missing.

    proposal-drafter ·