Tender Portal — wTVision

Log a new opportunity on the tenders board. Everything below maps to the Tender Submission Template — the tender title, scoped labels and folder path are generated for you, per the workspace and internal process rules.

Key metadata

Client name Tender / project name Submission deadline

Expected decision date optional

Expected revenue optional

Pipeline value in EUR — can be refined later.

Tender type

RFP RFQ RFI Other

Need pre-sales assistance with a client, but it's not a tender? Pick Other.

Tender documentation optional

Choose files

Committed to the tender's From Client/ folder in the repo.

Origin

wTVision office Reseller / other region

Origin office

Strategic tier

TIER 1 High priority / strategic Utmost financial or strategic importance. Complex solution, custom architecture, cross-departmental coordination. Pre-sales leads the drafting. TIER 2 Standard / common Typical commercial opportunity. Sales leads; pre-sales supports with diagrams and engineering clarifications. TIER 3 Commodity / tactical Sales knows exactly what to sell, no technical doubts. Zero pre-sales allocation expected.

Sales brief

Tender / opportunity summary

Commercial approach & winning strategy optional

Client insights & intelligence optional

Assignment

Sales lead GitLab @username, optional Pre-sales technical lead optional — leave blank for Tier 3

Live tender request preview

[DEADLINE DD-MM-YYYY] Client Name - Tender Name

—

Entry date — Draft deadline —

SCAFFOLDING PATH created automatically on submission

YYYY/
└─ Office/
   └─ Client/
      └─ Tender/
         ├─ From Client/
         ├─ Deliverables/
         └─ PreSales/

Title format [DEADLINE DD-MM-YYYY] Client - Tender
Valid origin (office or Other-…)
Exactly one Tier:: label
Request type (Type:: RFP / RFQ / RFI / Other)
Sales brief for the pre-sales team

Scoped labels are applied via the GitLab API on creation — no quick actions needed.

TenderPortal

Tender request created

Tender
Portal