Create standalone pursuit

Overview

A standalone pursuit is a bid workspace you start without picking a notice from Tendersight's catalog. You describe the opportunity yourself β€” title, type, country, owner, optional deadline and value β€” and optionally attach tender files you received offline. The result is the same pursuit workspace as a notice-linked pursuit: questionnaire, offers, documents, and final checkup modules all work identically afterward.

Use standalone when the buyer sent documents by email, the tender sits on a portal Tendersight does not monitor, you respond to a private RFP, or you need a workspace before the official publication syncs. The card on Team β†’ Pursuits shows Source: standalone and no official notice identifier unless you type authority details manually.

Tip: Before you start the wizard, confirm you have:

  • Completed Team β†’ Settings β€” company profile, legal representative, and banking β€” for document auto-fill

  • Selected the correct active team in the sidebar (team is fixed for the wizard)

  • Chosen the right pursuit type (works / supplies / services) β€” it controls sidebar modules

  • Selected the correct country β€” drives form volumes and country profiles

  • Assigned the bid owner (defaults to you)

  • Gathered tender PDFs to upload in step 2 if you plan in-depth analysis soon

Important: You cannot attach a standalone pursuit to a catalog notice later as a merge. If the tender appears in Opportunities β†’ Notices, create a new notice-linked pursuit instead (Create pursuit from notice).


When to use standalone vs from a notice

Situation

Recommended path

Notice appears under Opportunities β†’ Notices

Create from notice

Opportunity not in catalog

Standalone β€” manual context

You only have PDFs from the buyer

Standalone β€” upload in step 2

Framework call-off with no synced publication

Standalone

Private invite or email-only package

Standalone

Flow diagram

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


How to open

Path

What you click

From pursuits list

Team β†’ Pursuits β†’ New standalone pursuit (toolbar)

After leaving wizard

Back arrow returns to pursuits list

You must belong to the team and have permission to create pursuits. If your plan limits active pursuits, creation fails with an upgrade message on the last step.


Wizard layout

Full-width three-step wizard inside the main app shell.

Top bar

Element

Behavior

Back arrow

Returns to pursuits list without saving

Title

New standalone pursuit

Step indicator

Step

Name

Subtitle on screen

1

Details

Provide the basic details for your pursuit.

2

Documents

Attach relevant tender documentation.

3

Review

Review and confirm your pursuit.

The active step is highlighted; completed steps remain visible.

Button

When shown

Enabled when

Previous

Steps 2–3

Disabled on step 1

Continue

Steps 1–2

Current step passes validation

Create pursuit

Step 3 only

Review valid; not submitting

While the next step loads: Please wait while we prepare the form.


Step 1 β€” Details (numbered)

Fields use a two-column layout on desktop: label and helper on the left, control on the right.

  1. Team (read-only) β€” shows team name. Switch team in sidebar before opening the wizard if needed.

  2. Owner (required) β€” searchable team member list; defaults to you. Avatar + name when selected.

  3. Title (required) β€” pursuit name on kanban and sidebar. Use authority + subject + year for recognition months later.

  4. Description (optional) β€” internal notes; not exported unless you copy into documents later.

  5. Pursuit type (required) β€” Works, Supplies, or Services. With Country, controls which modules appear (technical offer, works offer, financial forms).

  6. Country (required) β€” searchable EU country list. Sets procurement rules and form volumes.

  7. Estimated value (optional) β€” amount + currency. Feeds pipeline totals on Team β†’ Pursuits.

  8. Deadline (optional) β€” calendar date + time (defaults 12:00). Powers dashboard deadline widgets.

  9. CPV code (optional) β€” searchable catalog with infinite scroll. Code + name display; clearable.

  10. Contracting authority (optional) β€” plain text buyer name. Not linked to analytics authority profile unless names match.

Continue stays disabled until title, type, country, and owner are valid.


Step 2 β€” Documents (numbered)

Optional but strongly recommended for in-depth analysis and AI document filling.

  1. Open the dashed drop zone β€” Drop files here or click to browse.

  2. Drag multiple files or use the file picker repeatedly.

  3. Accepted: PDF, Word, Excel, plain text, OpenDocument, PowerPoint.

  4. Review Selected files (N) list β€” each shows name, size, and Remove (trash).

  5. Add or remove freely before Continue β€” nothing attaches until Create pursuit on step 3.

Helper: Attach tender documentation, specifications, or any relevant files. This step is optional.


Step 3 β€” Review (numbered)

  1. Read the read-only summary table:

Row

Content

Title

Your title or -

Description

Shown only if entered

Estimated value

Formatted number + currency or -

Deadline

Long formatted date or -

Contracting authority

Text or -

CPV code

Code and name or -

Documents

File names and sizes, or No documents attached

  1. Click Create pursuit when satisfied β€” one click, no undo on the wizard itself.


Creating the pursuit β€” outcomes

Success

  1. Toast: Pursuit created β€” Your standalone pursuit has been created successfully.

  2. You land on Pursuit overview.

  3. Card appears on Team β†’ Pursuits in Active with Source: standalone.

Failure

Toast: Something went wrong β€” Our system was unable to create your pursuit. Please try again!

You stay on review step. Fix plan limits or network issues and retry.


What to do immediately after creation

Flow diagram
  1. Open Pursuit overview β€” confirm pursuit type and country; incomplete context blocks some modules.

  2. Open Documents if you skipped files in the wizard.

  3. Run In-depth analysis on tender PDFs to populate the questionnaire.

  4. Follow First pursuit workflow for the full module sequence.


Standalone vs notice-linked (reference)

Title, deadline, value

You enter

Copied from notice

Authority

Text you type

Linked buyer profile when available

External notice ID on card

None

Official identifier

Documents at start

Your uploads

Notice sync + your uploads

Version tracking

Manual

Notice Versions tab

Best for

Offline / private RFP

Public portal tenders


Permissions and roles

Role

Create standalone pursuit

Team owner

Yes

Administrator

Yes

Collaborator

Yes, when team policy allows

Owner assignment is limited to current team members.

Subscription gates

Gate

Effect

Active pursuit limit

Create pursuit fails on step 3

Module access

Country profile may hide modules until context complete


Best practices

  • Use a title that includes authority and subject β€” you will accumulate many pursuits over time.

  • Set deadline even if soft β€” dashboard and assistant reminders depend on it.

  • Upload full tender PDFs in step 2 so analysis does not wait on manual uploads inside the pursuit.

  • Match pursuit type and country to the actual procedure β€” Romania works β‰  Finland supplies in sidebar modules.

  • Assign owner to the bid lead before the team starts questionnaire work.

  • Prefer create from notice the moment the tender appears in the catalog β€” create a new linked pursuit rather than continuing standalone alone.


What you can and cannot do

You can

  • Create a pursuit with zero documents and upload later

  • Change owner after creation from pursuits list or overview

  • Edit type, country, and metadata on pursuit overview

  • Run the same modules as a notice-linked pursuit

You cannot

  • Link an existing standalone pursuit to a notice retroactively

  • Auto-sync deadline changes from a catalog you did not link

  • Share the workspace across two teams


FAQ

Are documents required in step 2?

No. You can create an empty shell and upload inside the pursuit later.

Can I change owner after creation?

Yes β€” pursuit card menu on Team β†’ Pursuits or team section on pursuit overview.

Why is Continue disabled on step 1?

Usually missing title, pursuit type, country, or owner.

Will standalone pursuits appear in analytics as notices?

No. They are internal workspaces unless you later create a notice-linked pursuit for the same opportunity.

Can I switch team mid-wizard?

No. Team is read-only. Switch in the sidebar, return to Team β†’ Pursuits, and start again.

What if I picked wrong pursuit type?

Edit on Pursuit overview β€” sidebar modules may refresh; review before heavy questionnaire work.

Does standalone skip team settings requirements?

No. PDF auto-fill still needs company profile, legal representative, and banking.


Troubleshooting

What you see

Likely cause

What to do

Continue stays disabled

Required field empty

Fill title, type, country, owner

Create pursuit fails repeatedly

Plan limit or connection

Check billing; retry

Wrong modules in sidebar

Type or country mismatch

Edit context on pursuit overview

Empty PDF headers after generation

Team settings incomplete

Finish company profile, legal rep, banking

CPV list empty

Search too narrow

Clear search; scroll to load more

Wizard back arrow lost work

Expected β€” no autosave

Re-enter if you left before step 3 submit


  • Pursuits list

  • Create pursuit from notice

  • Pursuit

  • Notice (Tender)

  • Team settings

  • First pursuit workflow