Turn project intent into construction-ready scope.
KrionSE helps AEC teams create, structure, review, package and release specifications in one connected workflow — with AI, voice input, standards-aware codes, product links, timeline tasks and BIM context.
Pr_20_31_04 Cementitious adhesive
Ss_30_42_70 Tile laying system
Autogenerated from the design brief. Select a linked code to open the standards library or product catalogue.
Voice → specification
Capture design intent while reviewing drawings or walking the site.
“Use 600×600 matt porcelain tile, R10 slip resistance, light grey…”
Specifications decide cost, and they are still written last.
On most projects the specification trails the design, gets copied from the previous job and is reconciled with procurement only when the wrong thing arrives on site. KrionSE treats scope as structured project data from the first section onward.
Copied from the last project
Reused documents carry clauses that were never checked against this building, this client or this contract. Nobody can see what actually changed.
Standards nobody can find
The company library exists, but searching it takes longer than retyping the clause — so it is never used, and never improved.
Review happens in email
Comments arrive as attachments and margin notes. There is no section status, no owner and no way to tell whether a category is complete.
Requirements and products drift apart
Approved manufacturer lists sit outside the specification, so a substitution never reaches the clause that justified the original choice.
Procurement retypes everything
Trade packages are rebuilt by hand in spreadsheets, and the quantities quietly stop matching the scope they came from.
No record of what was issued
When an RFI or a claim lands, nobody can say which version of the section went out for tender, or on what date.
From project setup to released package.
KrionSE keeps specification development in a deliberate sequence so teams can move from reusable standards to project-specific scope without losing review history or release control.
Project
Create the project context, disciplines, teams and specification requirements.
Template
Start from company standards, a project template or a curated library.
Coded spec tree
Navigate a structured hierarchy with classification codes and section relationships.
Edit / AI / voice
Write directly, insert from the library, dictate requirements or autogenerate content.
Review
Review by categories and sections with comments, status and completeness checks.
Carve packages
Select approved sections and assemble procurement, trade or execution packages.
Release
Issue reviewed snapshots for tender, construction, procurement or coordination.
Connect downstream
Link material, product, timeline, task, BIM and other project information.
Less document chasing. More structured engineering.
Authoring tools are embedded where decisions are made, while codes, products and downstream project links remain visible and reusable.
AI-assisted authoring
Generate draft specification text from design intent and keep relevant codes hyperlinked for fast navigation.
Voice capture
Mic controls inside specification sections convert spoken requirements into editable text where it belongs.
Standards library
Add clauses and codes from reusable company standards without leaving the project specification.
Category review
Review scope by sections and categories before approved content is carved into packages.
Product catalogue links
Connect specification requirements to approved products, materials, brands and supporting catalogue data.
Release snapshots
Preserve the reviewed state of every released package so issued scope stays traceable.
A specification tree that reaches the real work.
Move from the coded system or element down to the actual material, labour, finish and item requirements — then enrich each node with products, tasks and BIM context.
- ✓Hyperlinked classification codes speed navigation between related requirements.
- ✓Project teams can edit manually, insert from the library or generate a first draft with AI.
- ✓Each section can carry notes, linked products, timeline tasks, model relationships and release status.
MAT_01600×600 mm porcelain tileMaterialFIN_02Matt finish · Light grey · R10FinishLAB_03Set out, cut, lay, grout and cleanLabourPRD_04Approved manufacturer / catalogue linkProductQA_05Flatness, joints, adhesion and finish checksQualityBIM_06Room finish / model element associationBIM linkFour ways into the same section.
Type it, pull it from the library, generate a first draft or dictate it on site. Whichever route the content takes, it lands in the same coded structure, carries the same review status and keeps the same links.
Author in the section, not in a separate document.
The editor sits inside the node it belongs to, so a requirement is written against the element it describes. Classification codes can be inserted mid-sentence and stay live.
- ✓Rich text with clause numbering that follows the tree, not the page.
- ✓Internal notes stay with the team and never reach the issued output.
- ✓Every edit is attributed, so review comments have somebody to go to.
Tile: Pr_35_93_96 porcelain, 600 × 600 mm
Adhesive: Pr_20_31_04 cementitious, C2TE
Internal note — confirm slip rating with the client's facilities team before review.
Reuse the clause your firm already agreed on.
Search the company standards by code or title and drop an approved clause into the section. The library stays separate from project scope, so reuse never overwrites what a project has decided.
- ✓Search across codes, titles and clause text in one field.
- ✓Inserted content keeps its source reference for audit.
- ✓Improvements made on a project can be promoted back into the library.
Ss_30_20_15Cement and sand levelling screedClauseSs_30_20_18Flowing calcium sulfate screedClausePr_20_29_05Screed reinforcement meshProductQA_11Screed moisture test before finishesQualityStart from intent, not from a blank section.
Give the design intent and the assistant returns a structured draft for that node — material, finish, workmanship and quality clauses — with classification codes already linked for checking.
- ✓Drafts are written into the section as editable content, never as a locked block.
- ✓Suggested codes are shown as links so a reviewer can verify each one.
- ✓A draft stays in draft status until a person approves it.
→ Material — Pr_35_93_96 porcelain tile, 600 × 600 × 10 mm, water absorption ≤ 0.5 %
→ Finish — matt, light grey, R10 slip resistance
→ Workmanship — set out from lobby centreline, 3 mm joints, full adhesive bed
→ Quality — flatness, joint alignment, adhesion pull-off, final clean
Capture the decision where it is made.
A mic sits inside each section, so a requirement agreed during a drawing review or a site walk is recorded against the right node instead of a notebook.
- ✓Dictation becomes editable text in the section, not a separate recording.
- ✓Works on a tablet or phone for site and client walkthroughs.
- ✓Captured wording is marked as draft for a writer to tidy and structure.
→ Transcribed to section content · draft
→ 2 requirements detected · 1 code suggested
Standards-aware editing, without leaving the section.
The current workflow combines specification content, codes, internal notes, library access and output controls in the same working view.
Search, reuse and evolve your library.
- ✓Search codes and titles across company standards.
- ✓Browse structured classification codes and add new standards when required.
- ✓Keep reusable content separate from project-specific released scope.
Author content with codes, notes and assistive tools in context.
- ✓Insert coded requirements directly into specification content.
- ✓Use autofill and internal notes while keeping the authored section reviewable.
- ✓Export working or released content to customer-ready formats.
Nothing leaves the project until a section is signed.
Review runs by category and section rather than by document, so a discipline lead approves what they own. Everything that is issued keeps a frozen snapshot of exactly what was approved.
Every issue is a version you can go back to.
- ✓A release freezes the approved content, the linked products and the codes as they stood on that date.
- ✓Superseding scope creates a new revision instead of overwriting the last one.
- ✓Changes between two revisions can be listed section by section for the client.
- ✓Draft work continues on the live tree while the issued revision stays fixed.
Draft, in review, approved or released — visible on the tree, not buried in a file name.
Review threads sit on the section they question, with the author, the date and the resolution.
Empty clauses, unlinked codes and sections without a product are surfaced before issue.
Structure, finishes, services and external works can be approved by the people responsible for each.
Carve approved scope into the package each team actually needs.
A package is a selection of reviewed sections, not a new document. The same approved content can go to a tenderer, a subcontractor, a supplier and the site team without being rewritten four times.
Tender package
The full priced scope for a bidder, issued as a frozen revision so every tenderer answers the same document.
- ✓All approved sections for the works, with preliminaries and quality clauses.
- ✓Issued as Word and PDF, with a schedule export for pricing.
EF_25Walls and barriersApprovedEF_30Floor, stair and ramp finishesApprovedEF_35Ceiling finishesApprovedQA_00Testing, samples and mock-upsApprovedTrade package
Only the sections one subcontractor is responsible for, so a tiling contractor is not handed the façade specification.
- ✓Scope boundaries are explicit, which cuts the "not in my package" claim later.
- ✓Interfacing sections can be included as reference rather than as scope.
EF_30_10Tiled floor systemsScopeSs_30_20_15Levelling screedScopeEF_25_10Wall tiling, wet areasScopeEF_30_40Movement jointsReferenceProcurement package
The product and material requirements a buyer needs, with the approved catalogue links attached to each line.
- ✓Product, brand, model and technical requirement travel together.
- ✓A substitution request is raised against the clause that set the requirement.
PRD_04Porcelain tile 600×600, matt, light greyApproved listPRD_07Cementitious adhesive C2TEApproved listPRD_09Epoxy grout, colour to matchOpenPRD_12Aluminium movement profileOpenExecution package
What the site team needs to build and check the work, linked to the programme activities it belongs to.
- ✓Workmanship, tolerance and quality clauses without the commercial content.
- ✓Sections map to timeline tasks, so inspections sit on the programme.
WRK_02Setting out and datum checkTask linkedWRK_05Laying, jointing and groutingTask linkedQA_05Flatness and adhesion checksHold pointQA_09Handover clean and protectionHold pointRelease scope in the format the next team needs.
Export specifications, released scope and packages for design, tender, procurement, construction and planning workflows — without rebuilding the content each time.
A section that knows what it touches.
Specification content is only useful downstream if it carries its relationships. Each node in KrionSE can hold the products, quantities, activities, model elements and documents that depend on it.
Approved manufacturers, models and datasheets attach to the requirement that justified them, so substitutions are assessed against the clause.
Measured scope can be associated with the specification section it prices, keeping the takeoff and the requirement in step through revisions.
Sections link to programme activities and hold points, and export to MS Project or Primavera P6 as structured XML.
Room finishes, systems and element types associate with the sections that specify them, so the model and the written scope agree.
Drawings, schedules and reports referenced by a clause stay attached to it, and travel with the released package.
Comments, approvals and released revisions are part of the section, which is what makes an audit trail possible later.
KrionSE is the scope layer of a connected suite.
It can run on its own, or alongside the rest of the Krion AI Suite so that scope, model quality, quantities, signoff and the common data environment share the same project context.
Specification engineering — structured, reviewed and released scope.
Common data environment and digital twin for construction and infrastructure projects.
Digital signoff and AI intelligence over your CDE, ERP and BIM data.
Enterprise project intelligence for developers and contractors running a portfolio.
Quantity takeoff and pricing straight from drawing packages.
Automated model quality control with model-pinned, assignable issues.
Built for the people who own what gets written down.
Specification work crosses design, BIM, procurement and construction. KrionSE gives each of them the same structure to work against instead of four versions of the truth.
Organisations
Teams that issue scope repeatedly and cannot afford to rebuild it every project.
Roles
The people who write, review, approve or depend on the specification.
Intent, library content and AI drafting replace the blank document at the start of every section.
Clauses improved on one project can be promoted into the standard for the next one.
Packages carry their products and quantities, so buyers are not rebuilding the scope in a spreadsheet.
Every released revision is preserved with its content, links and date for claims and audits.
How it runs, and what teams usually ask first.
KrionSE fits into an existing toolchain rather than replacing it. Authoring, model and document tools stay where they are; the specification becomes the structured layer between them.
Deployment
Chosen with your IT and project governance teams during onboarding.
Common questions
If yours is not here, ask it in the demo request and we will answer it directly.
Build specifications as connected project data — not isolated documents.
See how KrionSE can help your design, specification, BIM, procurement and project teams move from intent to reviewed and released construction scope.
Tell us about the project
Send the details and we will come back with a walkthrough built around your own specification structure.
This opens your email client with the message ready to send. Nothing is submitted from this page.
What happens next
- We reply to agree a time and ask for one live example — a section, a template or an existing specification.
- A 45-minute walkthrough runs against your structure, not a generic demo project.
- If it fits, a short pilot on one live project sets up your library, codes and review roles.