Capsar.io

Every ISO 19650 document,
one connected platform

Prepare, review and maintain EIRs, BEPs and the plans that depend on them with less effort, in one traceable workflow — with AI on Capsar’s own server or on Google Gemini, your choice. Built by a practitioner on regulated programmes.

Watch it, then open your side.

One recording of the whole workflow, and a live session for each side of the appointment.

Watch it work

The recording · 73 seconds, no sound
The full BEP workflow — 73 seconds, no sound

A project opened, the client’s EIR read by the AI, the plan written section by section and exported as a PDF. Then open whichever session is yours, on the right.

Write an EIR

Exchange Information Requirements · client side

Write the requirements section by section on a sample office project, with the OIR, PIR and AIR they trace back to already filled in and open to edit.

Open the EIR demo no account · app.noeinsolutions.com/demo/eir

Answer with a BEP

BIM Execution Plan · supplier side

Read two finished BEPs for a substation rather than an empty template, then write sections of your own, with the AI suggesting wording field by field.

Open the BEP demo no account · app.noeinsolutions.com/demo/bep

Opening either session asks for an email address and the six-digit code sent to it — no account and no password, but not nothing. From there the session runs on a clock, counted along the top of the screen, and what you write is kept until it runs out. Everything that would carry a project out of the demo is locked — uploads, publishing, sharing, scoring and exports — so it is a test drive rather than a free tier. A workspace that stays, on a project of your own, is what beta access is — that conversation is at the foot of this page.

Why BEPs are still broken

Three problems that every BIM manager and information manager recognises.

2–4 wksof drafting from a blank template

A blank template is not a starting point

An empty template or last job’s copy: neither says what a section needs, or how to answer this EIR.

With CapsarSmart Help on every field says what it needs and drafts it with you.

30–50pages of EIR, with no structure

EIRs are dense PDFs

Pulling out what matters, and tracking whether the BEP answers it, is manual and error-prone.

With CapsarRequirements are extracted, and the Responsiveness Matrix shows what is covered and what is not.

0outside AI providers, on Capsar’s own server

No AI for confidential projects

Generic AI tools send project data to a third party: a non-starter on infrastructure and defence work.

With CapsarYou choose where the AI runs: Capsar’s own server, slower but private, or Google Gemini, faster and under terms where Google does not train on your data.

From EIR to compliant BEP — guided every step

Five steps, built around the way real teams respond to a real EIR. From a blank template a BEP is 2–4 weeks of drafting; through these it is 3–5 days.

01

Upload EIR

Drop the client’s EIR PDF into Capsar

02

AI Extracts

Requirements parsed and structured automatically

03

Guided Authoring

Smart Help on every field with AI-assisted content

04

Gap Analysis

Responsiveness Matrix shows what’s covered and what’s not

05

Export

Professional PDF & editable DOCX deliverables

The demo drops you into the third step, on a project that is already half built. Uploading your own EIR, checking the plan against it and exporting the result are what a beta workspace adds.

Open the demo

One platform, both sides of the appointment

The ISO 19650 process has two sides and six phases between them, and the platform is laid out the way the standard runs rather than as a list of features. Every tool is listed below under its side and phase; pick one to see it running on a worked project. Until you do, the screen walks the exchange itself: the EIR, the BEP that answers it, and the score of one against the other.

If you are the appointing party

The client side of the appointment. You say what the organisation, the project and the finished asset need to know, turn that into requirements a tender can answer, and score what comes back against them.

Define the need

Specify the exchange

Receive and assess

  • CDE FindingsSoon
  • Capability ReviewSoon

If you are the delivery team

The lead appointed party’s side. You answer those requirements and evidence that your task teams can meet them, plan who produces what and when, then check what is produced against the plan you committed to.

Respond to the tender

Plan the delivery

Produce and check

  • Soon
  • Soon
Authoring an EIR — the drafts list, then the ISO 19650 sections

Tried it? Let’s talk about your project

The demo is the whole application on a clock. If it matches how you actually work, the next step is a paid pilot on one live tender of yours, with me beside your evaluator — or a beta workspace, or a partnership if you build in this space too. All three start the same way: thirty minutes, no deck.

Early access — founding cohort

Request beta access

Invites are issued by hand, a few at a time — the app itself has no signup form. Leave an address and I’ll send you a passcode and a short getting-started guide, usually within a working day. Early-access pricing is still to be decided. The teams who join now are shaping what Capsar becomes, and their founding-cohort terms will reflect that.

Request received. I’ll set the invite up myself and email you the passcode with a short getting-started guide.

Used to set up your invite and reply to you about it. No list, no sequence. How your data is handled