Final checkup

Overview

Final checkup is the pre-submission review dashboard. It scans active pursuit modules for blocking issues, shows completion progress, and provides section navigation with deep links to fix problems β€” your last gate before packaging the bid and uploading to the authority portal.

Submission to the buyer still happens outside Tendersight. This module validates workspace readiness, not portal upload success.

Tip: At least one week before deadline, confirm you have:

  • Zero red issue badges in section navigation

  • Re-opened checkup after any major edit (report does not auto-refresh in background)

  • Downloaded works construction archive and opened locally (works pursuits)

  • Team sign-off on questionnaire statuses and financial total

  • Kanban card ready to move to Bid submitted after external upload

Important: Informational issues (e.g. empty win themes) may not block β€” destructive/red items do.


When this module appears

Pursuit type

Sidebar

Supplies, services, works

Checkup β†’ Final checkup

Report includes only modules active for your type Γ— country configuration.


How to open

Path

Steps

Pursuit sidebar

Checkup β†’ Final checkup

Overview

Completion block links


Layout

Two-column: sticky navigation (left), scrollable report (right).

Flow diagram

Section navigation

Element

Behavior

Overview

Summary block

Personnel

Works pursuits with HR checks

Section headers

Proposal, documentation groups

Module items

Scroll to block

Issue badges

Red count per module

Active highlight

Scroll spy

Issue labels use destructive styling.

Report blocks

Block

Content

Context alert

Incomplete type/country

Issues overview

Total issue count

Overall summary

Progress ring, qualificative

Personnel

HR assignment gaps (works)

Module blocks

Issue list + deep links


What final checkup evaluates

Dynamic per active modules:

Module

Typical checks

Questionnaire

Unanswered, non-compliant

Technical offer

Missing solutions, mappings

Financial offer

Unpriced lines, zero total

Works BOQ

Unpriced BOQ rows

Documents

Missing required files

Standard forms

Ungenerated templates

Personnel

Unassigned roles (works)

Understanding

Empty award criteria (informational)

Exact checks from country configuration resolver.


Key actions

Action

Result

Click nav item

Scroll to section

Click issue link

Open fixing module

Download construction archive

Works ZIP package

Reload page

Re-evaluate all modules

Pre-submission workflow

```mermaid

flowchart LR

FC[Final checkup]

FIX[Fix in modules]

ZERO[Zero badges]

SUB[External submit]

FC -->|issues| FIX

FIX --> FC

FC -->|clear| ZERO

ZERO --> SUB

```


Numbered workflow β€” clearance pass

  1. Open final checkup fresh (hard refresh if long session).

  2. Fix context alert first on overview.

  3. Work navigation top to bottom β€” click each red badge module.

  4. Resolve issues via deep links.

  5. Return to checkup β€” repeat until badges clear.

  6. Works: download archive; verify file list.

  7. External portal upload.

  8. Team β†’ Pursuits β†’ Bid submitted.


Empty and processing states

State

UI

Loading

Placeholder rows while data loads

Load error

Error empty state

Context incomplete

Context alert

No issues

Green summary

Archive downloading

Button loading

Personnel hidden

Non-works pursuits


Downstream role

Terminal aggregator β€” reads all modules; nothing depends on checkup data. Progress may sync to Overview on load.

Output

Use

Deep links

Fix source modules

Construction archive

Offline submission pack

Progress

Overview completion


Edge cases

Situation

Action

Fixed issue still shows

Refresh checkup page

False positive mapping

Complete mapping; recheck

Archive incomplete

Finish standard forms export

Personnel on supplies

Nav hidden β€” expected


FAQ

Does checkup submit to authority?

No. External portal only.

Auto-refresh?

No β€” reopen page after fixes.

Yellow vs red issues?

Red counts block readiness in navigation badges.

Can I waive an issue?

No β€” fix or change data in source module.

Archive contents?

Generated docs per works profile β€” verify locally.

Multiple reviewers?

Share pursuit; each fixes assigned modules.


  • Pursuit overview

  • Questionnaire

  • Technical offer

  • Financial offer

  • Construction standard forms

  • Documents library

  • First pursuit workflow