Notice (Tender)

Overview

A notice is the public procurement opportunity as published by a contracting authority β€” the call for tenders your team researches before deciding to bid. Tendersight continuously imports notices from official European sources (SEAP, TED, and national portals) so you can search, monitor, compare, and open a bid workspace without retyping titles, deadlines, or document lists by hand.

A notice is not your bid. It is market intelligence: read-only, shared across every Tendersight customer, and updated only when the authority publishes a new version or when Tendersight syncs from the source. When your team decides to compete, you create a pursuit (your workspace β€” sometimes labeled project in the interface) on top of that notice. The notice stays in Opportunities; your answers, offers, and submission pack live in the pursuit.

Tip: Before you create a pursuit from a notice, confirm you have:

  • Opened the latest version of the notice (not an obsolete amendment)

  • Reviewed submission deadline, estimated value, and lots

  • Checked that tender documents are available (or that you have PDFs elsewhere)

  • Completed Team β†’ Settings β€” company profile, legal representative, and banking β€” so generated forms auto-fill your legal data

  • Selected the correct active team if you belong to more than one

The more accurately you evaluate the notice up front, the smoother pursuit setup and compliance work will be later.

Important: Notices cannot be edited in Tendersight. If the authority changes the deadline or uploads new documents, you wait for the sync (or open the versions timeline) and adjust your pursuit plan β€” you do not "fix" the notice record yourself.


Notice, tender, and project β€” what each word means

Tendersight uses several labels for related ideas. They confuse new users until you separate market data from your team's work.

Term in the product

What it actually is

Can you edit it?

Notice

Official publication in the catalog (Opportunities β†’ Notices)

No β€” read-only

Tender

Same object as notice; often used on detail pages and in assistant chat

No β€” read-only

Pursuit

Your team's bid workspace linked to a notice (or started standalone)

Yes β€” your team's data

Project

Same workspace as pursuit; common in Romanian UI (proiect)

Yes β€” your team's data

Notice type (CN, SCN, CAN, etc.) describes the kind of publication β€” not a different product object.

Flow diagram

One notice can have many pursuits β€” at most one pursuit per team per notice. Team A and Team B each get their own workspace on the same tender; they never share questionnaire answers or pricing.


How a notice differs from a pursuit

Purpose

Research and bid/no-bid decision

Prepare and track your submission

Owner

Contracting authority (via sync)

Your team

Typical first step

Browse, filter, set alerts

Create from notice or standalone

Documents

Authority's tender files (download / preview)

Your filled forms, offers, evidence

Requirements

Visible in publications and extraction

Tracked in Questionnaire with owners and status

After award

Status becomes Awarded; participants tab updates

You move kanban card to Won or Lost

Creating a pursuit copies key facts at that moment (title, deadline, value, country, CPV, authority). After creation, pursuit data is independent β€” changing your compliance answers does not change the notice, and a notice amendment does not automatically rewrite your pursuit (you review versions and update your plan).


Two ways to start bid work

Not every opportunity in your pipeline comes from the catalog. Tendersight supports both paths; they land in the same pursuit workspace afterward.

Use this when the opportunity appears under Opportunities β†’ Notices or arrived via an alert match.

  1. Open the notice from Notices browse, an alert email, a dashboard widget, or Home assistant search.

  2. On Notice overview, read description, key facts, lots, and documents.

  3. If a yellow obsolete version banner appears, click view latest version before continuing.

  4. Click Create pursuit in the command bar (or Go to pursuit if your team already has one).

  5. If you belong to multiple teams, pick the team that will own the bid.

  6. You land on Pursuit overview; the card appears on Team β†’ Pursuits kanban.

See Create pursuit from notice for team-selection edge cases and what fields copy across.

Path B β€” Standalone pursuit (no catalog notice)

Use this when the buyer sent documents by email, the tender sits on a portal Tendersight does not monitor, or you are responding to a private RFP.

  1. Go to Team β†’ Pursuits.

  2. Click New standalone pursuit.

  3. Complete the three-step wizard: Details β†’ Documents β†’ Review.

  4. You enter title, type, country, and optional uploads yourself β€” there is no automatic link to an official notice reference.

See Create standalone pursuit. Standalone pursuits show Source: standalone on the board; they do not display an official identifier unless you type authority details manually.

Flow diagram

Caution: Choosing standalone when the notice is in the catalog means you lose automatic version tracking, official identifier links, and one-click Go to pursuit from the notice page. Prefer Path A whenever the tender is indexed.


Accessing notice pages

From Notices browse (Lead Finder)

  1. Open Opportunities β†’ Notices in the sidebar.

  2. Apply filters (country, CPV, value, deadline, keywords, status).

  3. Click the contract title on a row to open Notice overview.

Keywords search document text, not only the short description β€” the same engine powers alert matching.

From alerts

  1. Open Opportunities β†’ Alerts β†’ Activity, or follow a link in a digest email.

  2. Click the matched notice title.

  3. Evaluate, then Create pursuit or refine alert rules.

From analytics

From Analytics β†’ Companies or Contracting authorities, open a profile and drill into a tender row. You still arrive on the same read-only notice detail β€” analytics does not create pursuits for you.

From Home assistant

Ask for tenders by topic, authority, or CPV. The assistant can open notice details or guide you toward pursuit creation after you confirm the opportunity.


Notice detail structure

The notice detail experience is one page with scroll sections (desktop: sticky section menu on the left; mobile: horizontal section bar under the command bar).

Section / tab

Article

What you use it for

Overview

Notice overview

Description, key facts, decision band, create pursuit

Lots

Notice lots

Multi-lot scope β€” bid one or all

Participants

Notice participants

Who bid or won (after award)

Versions

Notice versions

Amendment chain β€” always pivot to latest

Products

Notice products

AI extraction of buyer product requirements

Command bar actions (signed in)

Control

What it does

Reference ID

Internal Tendersight ID β€” copy for support

Identifier

Official notice number; external link when available

Share

Copy link for colleagues

Add to calendar

Export deadline to Google, Outlook, ICS

Receive alerts

Seed a new ruleset from this notice's filters

Create pursuit / Go to pursuit

Start or open your team's workspace

Guests may see a reduced bar; documents and pursuit actions often require sign-in and an active subscription.


Key fields and where they matter later

Field

Where it comes from

Why it matters downstream

Reference ID

Tendersight

Support tickets, internal notes

Identifier

Official system

Citations, external portal link

Contract title

Publication

Pursuit title, alert keywords

Estimated value

Publication

Filters, statistics, bid/no-bid band

CPV codes

Publication

Alerts, market stats, company charts

Contracting authority

Publication

Authority profile

Documents

Authority uploads

Download, in-depth analysis, product extraction

Status

Publication

Whether the tender is still actionable

Submission deadline

Publication

Calendar, dashboards, pursuit countdown

Notice type

Publication

Context for publication rules (CN, SCN, …)


Status, versions, and amendments

Status

Meaning for your team

Ongoing

Open for submission β€” actionable

Awarded

Outcome published β€” review Participants

Cancelled / Expired

Not actionable β€” archive research only

When a newer publication replaces the one you are viewing, Tendersight shows an obsolete version banner. Always open the latest version before creating a pursuit or downloading documents for analysis. Amendment history lives on Notice versions timeline.

Caution: A pursuit created on an older notice version does not auto-migrate when the authority publishes an amendment. Re-read the timeline, download new documents, and update your questionnaire and offers manually.


What you can do on a notice (and what you cannot)

You can

  • Search and filter the catalog

  • Set up alerts from notice criteria

  • Download or preview tender documents (subject to plan)

  • Run product extraction on documents (credits may apply)

  • Create pursuit for your team

  • Share links and add deadlines to your calendar

  • Use notice data in Analytics widgets (read-only)

You cannot

  • Edit title, deadline, CPV, or authority data

  • Upload fixes to the authority's PDFs on the notice record

  • Share one pursuit across two teams on the same notice

  • Force a sync β€” updates arrive on Tendersight's schedule from official sources


Where notices appear beyond the detail page

Location

What you see

Alerts activity

New matches against your rulesets

Market statistics

Aggregations by country, year, CPV

Company tenders

Participation history for a market company

Authority tenders

Buyer's publication list

Custom dashboards

Widgets you configured

Home assistant

Search results and summaries

Analytics and Opportunities are separate planes: notices feed decision quality; pursuits feed execution.


Permissions snapshot

Content

Typical access

Overview text and key facts

Often public

Tender documents

Sign in; subscription may apply

Participants

Signed in

Product extraction

Signed in; AI credits

Create pursuit

Team member; pursuit limit on plan

Full matrix: Permissions and access.


  1. Discover β€” browse or alert lands you on a notice.

  2. Validate β€” latest version, deadline, lots, documents.

  3. Decide β€” bid/no-bid using value, authority history, and team capacity.

  4. Prepare team β€” settings and inventory if not already done (Getting started workflow).

  5. Create pursuit β€” from notice (Path A) or standalone (Path B).

  6. Execute β€” in-depth analysis β†’ questionnaire β†’ offers β†’ documents β†’ final checkup (First pursuit workflow).


FAQ

What is the difference between a notice and a pursuit?

A notice is the authority's published opportunity (read-only). A pursuit is your team's workspace to prepare a bid β€” requirements, offers, documents, and checklists.

What is the difference between pursuit and project?

Same workspace. Project appears in some translations and assistant phrasing; pursuit is the primary English label in Team β†’ Pursuits.

Can I create a pursuit without a notice?

Yes. Use New standalone pursuit when the opportunity is not in the catalog. You enter context and upload documents yourself.

Can two teams share one pursuit on the same notice?

No. Each team gets its own pursuit. Team A cannot see Team B's questionnaire or pricing.

Why does the button say "Go to pursuit" instead of "Create pursuit"?

Your current team already has a workspace on this notice. Clicking opens that pursuit directly.

What happens if the authority amends the tender after I created a pursuit?

The notice updates on sync; your pursuit does not auto-update. Review Versions timeline, fetch new documents, and adjust your bid content.

Can I edit the notice title or deadline?

No. Notices are imported read-only. Update your pursuit overview notes or tasks if your internal planning differs.

Do I need team settings before creating a pursuit?

Strongly recommended. Without company profile, legal representative, and banking, document auto-fill and AI filler leave "complete" placeholders in PDFs from day one.


  • Pursuit

  • Create pursuit from notice

  • Create standalone pursuit

  • Notice overview

  • How information flows

  • First pursuit workflow

  • Contracting authority