Create and edit specifications

A bid specification is created in two ways: by generating it with the AI agent from a conversation, or by starting from documents you already have in the Repository. The document is built at the same time as the chat: you talk to the AI on one side and watch the specification grow on the other.

The AI chat

Tell it what you need the way you'd explain it to a colleague. The agent accepts much more than text:

Voice: you record a spoken message and it's transcribed to text automatically.
Photos and images: you take a photo of the equipment or the location, or upload images; the AI interprets them.
Tables and files: Excel/CSV and PDFs (drawings, standards, old specifications). Word isn't processed: convert it to PDF.
Technical data: brands, models, measurements, standards, deadlines.
Internet research: ask it to look for references or standards ("research what standard X requires") and it brings them back with their sources.

The agent works in stages (it researches, plans, drafts) and builds the specification section by section, with the formality and order that a tender requires. Long generations keep running in the background: you can leave and come back. Iterate via chat, request scope changes, add sections or adjust requirements, and the AI edits the document in place.

The editor

Rich text by sections: you edit any part directly without going through the chat, and you can embed images and tables.
Quality score (0 to 100%): an automatic validation that detects typical gaps, such as ambiguous requirements, missing acceptance criteria or uncited standards. Use it as a checklist before approving.
Export to PDF: a formal document, with a cover and structure, ready to circulate outside the platform.

Review and approval

A bid specification can be sent for review or approval before considering it ready. You can define chains of people in the company who review, edit and approve the specifications made by other users.

Each reviewer receives an email with a single link-based access; they don't need an account and verify their identity with a code.
From there they approve, reject or request changes, and depending on the case can edit their part of the document.
The flow by area (Health and Safety, Labor, Management Control, with a final approver) is detailed in Contribution chain.

From the specification to the purchase

When it's Approved, download it as a PDF to upload it to your ERP or make it available so purchasing can take what it needs.
Or export it directly to a quotation / attach it to a tender as a specification document.