ScopeSense
About ScopeSense

A scope tool. Not a platform.

We build one thing for electrical and MEP contractors across the EU: a second reader for tender packs that finds the scope a bid is about to miss — and is clear about what it can't do.

Core Engineering Kft., BudapestHosted in the EU · Vienna
scope-checkSample project
Tender pack read · 38 documentsdone
Scope items extracted · 214done
DIN VDE 0100 · IEC 60364checked
EU CPR 2024/3110 clausesreview
Specified, missing from scope

Emergency lighting circuits (C4)

source: Spec E-05 §5.4 · p. 112→ added to RFI report
Findings are decision support, not sign-off.
Why we built it

Built by engineers who priced the bids.

We are electrical engineers and estimators. For years the job was the same: take a tender pack — drawings, specifications, schedules, the contract — and turn it into a bid before the deadline.

ScopeSense started from a specific failure: a commercial bid that lost its margin after award, because the emergency lighting circuits were never in the scope we priced.

Nobody was careless. The requirement appeared once, on one page of a 300-page tender pack read under deadline. That is not a skills problem. It is a reading problem — volume, time pressure and a requirement mentioned only once.

So we built a second reader for exactly that job. It goes through every page, lists the scope items, and puts the gaps in front of an engineer while there is still time to ask the client.

The expensive item is rarely the one nobody specified. It is the one specified once, on a page nobody had time to read.

Design basis for ScopeSense
300
pages in the tender pack

Read under deadline, as they always are.

1
requirement that never surfaced

Emergency lighting circuits — specified, but not in scope.

0
people who were careless

The process failed, not the estimators.

What a scope gap looks like

Three circuits in scope. Four specified.

A gap rarely looks like a mistake. It looks like a complete board schedule — until the specification is read against it.

DB-1 · Single-line diagramSample project
  1. 01

    The board schedule looks complete

    DB-1 lists lighting, small power and HVAC. Three circuits, all in scope.

  2. 02

    The specification asks for more

    Section 5.4 requires emergency lighting on a central battery system, fed from DB-1.

  3. 03

    ScopeSense flags the gap

    C4 is listed as a scope gap with the page it came from, and goes into the RFI report as a question for the client.

Narrow on purpose

What ScopeSense does. What it deliberately doesn't.

A narrow tool can be precise. A broad one has to guess. We chose narrow, and we put the boundary in writing.

ScopeSense does
  • Read the whole tender packDrawings, specifications and schedules for electrical and MEP scope.
  • Extract scope items and flag the gapsWhat is specified but at risk of falling out of scope.
  • Check against standards and EU rulesSelected clauses that change a bid.
    DIN VDE 0100IEC 60364EU CPR 2024/3110
  • Write an RFI reportOpen questions for the client, each tied to its source page.
  • Answer questions in project chatAsk about the tender; answers cite the document and page.
ScopeSense doesn't
  • Manage constructionNo site diaries, programme control or project controls.
  • Do general takeoffIt looks for missing scope, not every quantity in every trade.
  • Give legal advice or certify complianceA passed check is not a certificate. National and local rules stay with you.
  • Replace your engineerOutput is decision support. A qualified person reviews and signs off.

Verify every finding against the original tender documents before you submit.

Data & trust

Where your documents live, and how answers are made.

The questions a procurement or IT reviewer asks before a tender pack is uploaded — answered in one place.

Hosting

Hosted in the EU, in Vienna.

Application servers run at netcup in Vienna, Austria. Every processing location is listed in the DPA.

Sources

Every answer points back to the page.

Findings and chat answers cite the document and page they came from, so you check the original — not a summary of it.

Emergency lighting shall be supplied from a central battery system located in the LV room…
Spec E-05 · §5.4 · p. 112Drawing · E-201Sample project

The same rule applies to the RFI report: every question carries its source.

Cost

Known before you run.

Analysis≈ 45 credits
Chat message≈ 8 credits
Free trial300 credits
Pricing →
Contract

A DPA for every customer.

Named subprocessors and their processing locations, in writing.

Read the DPA →
Confidentiality

Tender documents are treated as confidential client material.

They are processed only to run your analysis and your project chat.

Privacy policy
Company

Core Engineering Kft., Budapest.

ScopeSense is built by engineers and estimators at Core Engineering, an engineering company in Budapest. The standards it checks apply across EU markets, and so does the product.

Registered company details are in the Impressum.

Company
Core Engineering Kft.
Based in
Budapest, Hungary
Market
EU-wide
Hosting
EU · netcup, Vienna, Austria
Product
ScopeSense — tender scope analysis
Stage 1done

Built around one real task

Each workspace starts from a job estimators actually do on a tender.

Stage 2done

Tested on real tenders

It runs against real tender documents until the findings hold up.

Stage 3ongoing

Opened in stages

ScopeSense is live and still being built. Feedback decides what comes next.

Questions, feedback, or a tender we should test against?

Write to the people who build the product.

Contact
Next tender

Find the missing circuit before award.

Run ScopeSense on your next tender pack. The free trial runs 14 days with 300 credits — no card required.

Start free trialSee the productAnalysis ≈ 45 credits · chat ≈ 8 credits