Your data
This page is a plain-language tour of the main things Bidderops stores. You never have to think about tables or databases — but understanding the entities helps you reason about how the product fits together.
Core entities
| Entity | What it represents |
|---|---|
| Opportunity | A single tender or bid: title, reference number, status, contracting authority, funding source, country, sector, estimated value, your bid value, currency, procurement method, and the key dates (publication, clarification, submission, expected award). |
| Team member | An internal person assigned to a bid, with their role on that bid. |
| JV invite | An external partner invited to one opportunity, with a permission level. |
| Outcome | The recorded result of a bid: won or lost, award value, winner, loss reason, and lessons learned. |
| Go/No-Go decision | The captured decision to pursue or pass, with the rationale and supporting scores. |
| Milestone | An internal task with a due date and completion state. |
| Note | A timestamped comment by a team member. |
| Document | A categorized reference to a file or link. |
| Company experience | A past project your firm delivered — used as a reference in proposals. |
| Personnel | A person’s CV and their project assignment history. |
| Sourced opportunity | A tender discovered from an external feed, with a match score. |
Isolation between organizations
Your data belongs to your organization and only your organization can see it. This boundary is enforced at the database level, not just in the interface — every read and write is automatically scoped to the organization you belong to.
JV partners are the one deliberate exception: an external partner sees a single bid they were explicitly invited to, and nothing else. See JV partners for how that works.
Activity and history
Most meaningful actions are written to an activity log on the opportunity, giving you an audit trail of status changes, team edits, document changes, notes, and the recorded outcome.