Attribute mappings
Overview
Attribute mappings connect tender requirement specifications to your solution product attributes β proving each technical parameter in your offer matches or exceeds what the authority asked for. This is a per-requirement sub-page of Technical offer, not a separate sidebar module.
Final checkup flags incomplete mappings before submission. Exports embed compliance tables from saved mapping sets.
Tip: Before automap, confirm you have:
Added all solution parts for the requirement in technical offer
Team product specifications uploaded in inventory
Parsed requirement attributes visible in left panel (if empty, fix requirement spec text)
Saved technical offer changes before opening mappings
Planned manual review for safety-critical parameters (automap is assistive, not proof)
Caution: Leaving with unsaved mapping changes drops work β watch save status in topbar.
When this module appears
How to open
Your proposal β Technical offer.
Select a requirement with specification attributes.
Click Map attributes.
Header includes Back to technical offer.
Layout

Requirement attributes panel
Parsed specification fields from tender text β name, expected value, unit.
Solution attributes panel
Attributes from solution parts (team product specifications).
Mapping grid
Topbar
Key actions
Automap workflow
```mermaid
sequenceDiagram
participant U as User
participant M as Mapping page
participant AI as Automap service
U->>M: Click Automap
M->>AI: Start task
AI-->>M: Stream suggestions
U->>M: Review and save
```
automatic updates pause while you have unsaved local edits.
Numbered workflow β spec-heavy requirement
Add solution parts in technical offer.
Open attribute mappings.
Run Automap.
Sort by unmapped warnings β fix manually.
Validate safety-critical rows against datasheet PDF.
Save.
Return to technical offer β repeat next requirement.
Re-run Final checkup.
Empty and processing states
Downstream dependencies
Multi-part solutions
Map each requirement attribute to the part that actually delivers it β not always part A.
Edge cases
FAQ
Is automap mandatory?
No β manual mapping always valid.
Does mapping change questionnaire status?
Indirectly via checkup only.
Can I map one requirement attribute to two solution fields?
Typically one-to-one β split requirement if needed.
Works pursuits?
Module unavailable β BOQ descriptions instead.
Export mapping table?
Part of technical offer document generation.
Retry automap?
Yes β replaces suggestions not yet saved.
Related articles
Technical offer
Questionnaire
Final checkup
Team product (entity)
Datasheet upload
Specifications viewer