---
title: DRE
description: Upload a PDF document and receive a structured requirements table ready for DOORS or Relatics within minutes. The DRE reads concepts, not sentences.
---

[![Logo basewise](https://basewise.ai/hubfs/Logo%20basewise.svg "Logo basewise")](https://basewise.ai/en/home?hsLang=en)

[![Logo basewise](https://basewise.ai/hubfs/Logo%20basewise.svg "Logo basewise")](https://basewise.ai/?hsLang=en)

- [Applications](https://basewise.ai/en/applications)
- [About Basewise](https://basewise.ai/en/about-basewise)
- [Insights](https://basewise.ai/en/insights)
- [Contact](https://basewise.ai/en/contact)

More results

En

- English
- [Nederlands](https://basewise.ai/nl/dre)

[Request your demo](https://basewise.ai/en/demo?hsLang=en)

[Request your demo](https://basewise.ai/en/demo?hsLang=en)

- [Applications](https://basewise.ai/en/applications)
- [About Basewise](https://basewise.ai/en/about-basewise)
- [Insights](https://basewise.ai/en/insights)
- [Contact](https://basewise.ai/en/contact)

[Book free demo](https://basewise.ai/en/demo?hsLang=en)

![Upload documents and automatically extract structured text and requirements with INCOSE compliance checking.](https://basewise.ai/hs-fs/hubfs/DRE.png?width=400&height=263&name=DRE.png)

 LIVE - demo.basewise.ai

# 75% profit preparation

Capability-driven The Document Requirements Extractor automatically pulls requirements from PDF documents. Either verbatim or rewritten to the INCOSE standard, split at concept level and enriched with an ID and paragraph reference. Exportable to Excel with a single click.

[Back to applications](https://basewise.ai/en/applications?hsLang=en)

## From PDF to structured requirements in minutes

Requirements\_Spec\_N307\_Viaduct.pdf

Programme of Requirements  
N307 Reconstruction — Markerwaard Viaduct

§ 3.1 Structural requirements

The carriageway width per direction shall be at least 7.20 metres, excluding pavements and cycle paths.

The viaduct shall provide a minimum clearance height of 4.50 metres above ground level, measured along the centreline of the carriageway.

§ 3.2 Load requirements

The structure shall withstand traffic loads in accordance with load class 60 per NEN-EN 1991-2, including dynamic load factors.

§ 3.3 Environmental requirements

It is expected that residents in the vicinity experience minimal disruption during the construction phase.

The contractor shall limit noise nuisance to a maximum of 65 dB(A) measured at the facade of adjacent residential properties during daytime hours.

Extract as requirement? + Add

Human-in-the-loop mode active

Requirements table

| ID | Requirement | § | Type |
| --- | --- | --- | --- |
| DRE-001 | Carriageway width per direction min. 7.20 m, excl. pavements. | §3.1 | Requirement |

1 requirement extracted

GET STARTED

# Ready to accelerate your SE workflow?

 Request a free demo or start a pilot program. Our consultants guide you from onboarding to your first results.

[Request your demo](https://basewise.ai/en/demo?hsLang=en) [Contact](https://basewise.ai/en/contact?hsLang=en)

How it works

## Two passes. One consistent result.

The DRE processes every document in two steps — ensuring that even large, complex documents are handled quickly and completely.

PASS 01 · STRUCTURAL SCAN

Understanding the document before extraction begins

The first pass scans the document globally and determines context before a single requirement is extracted.

- Document type: technical spec / EMVI / contract / PvE
- Language detection: Dutch or English
- Paragraph structure and requirement segments marked

PASS 02 · PARALLEL EXTRACTION

Every segment processed in parallel via Claude Vision

Every segment from Pass 1 is processed simultaneously — fast even for documents of 50+ pages.

- 5–10 simultaneous API requests per document
- Per segment: record with ID, source, text, scope and type
- Incrementally saved — no data loss on interruption

Output

## Seven fields. Fully traceable.

Every record contains everything needed for direct import into DOORS or Relatics — including source reference and context information.

ID

Source

Requirement text

Type

DRE-001

§3.2.1

The system shall have a structural fire resistance of at least 60 minutes.

REQ

DRE-002

§3.2.3

The contractor assumes a load-bearing capacity of 500 kg/m².

ASSUMPTION

DRE-003

§4.1.0

The floor area per building level shall be at least 350 m² net usable area.

REQ

DRE-004

§2.0.0

This document describes the programme of requirements for the office building.

NOT A REQ

DRE-005

§5.3.2

The façade shall have a thermal transmittance coefficient (Rc) of at least 6.0 m²K/W.

REQ

Export: .xlsx

Export: .csv

DOORS-ready

Relatics-ready

Split logic

## Concepts, not sentences.

The DRE splits documents at concept level. Three sentences about the same building element become one requirement — not three separate lines. This is a deliberate choice to prevent requirements list noise.

Source document (fragment)

This document describes the technical requirements for the project.

The crash deck structure shall withstand an impact load of 250 kN.

The crash deck shall be constructed in reinforced concrete with a minimum compressive strength of C30/37.

The structural height of the crash deck shall not exceed 400 mm including finishing.

The contractor is responsible for the detailing.

= same concept → will be merged

DRE  
split logic

Output — 1 requirement, not 3

DRE-012 · TYPE: REQ · SCOPE: Crash deck structure

The crash deck structure shall withstand an impact load of 250 kN, constructed in reinforced concrete C30/37, with a maximum structural height of 400 mm including finishing.

**Result:** one complete, coherent requirement instead of three separate lines that would need to be split and manually merged in DOORS.

Human-in-the-Loop mode

## Manual selection. Full control.

In addition to the automatic mode, the DRE offers a HitL mode where you select text directly in the live PDF and decide what gets added as a requirement.

01

PDF view on the left

The original document is displayed on the left with live text selection. You navigate through the document as usual.

02

Mark a text segment

Select a text fragment you want to add as a requirement. The selection is immediately highlighted in the document.

03

"Extract?" popup

Upon selection, a context popup appears with the option to add the text to the extraction table.

04

Verbatim or rewritten

Choose whether the selected text is copied exactly or rewritten into INCOSE structure for direct usability.

DRE · Human-in-the-Loop

Document

Extract as requirement?

Extract

Extraction table

DRE-001 · REQ

The system shall be resistant to...

DRE-002 · REQ

The structure shall have a minimum service life...

DRE-003 · new...

Will be added after selection

**When to use HitL?** Ideal for documents with irregular structure, mixed language, or when specific sections need to be deliberately skipped.

Use cases

## Proven in practice.

The DRE has been tested on a wide range of document types in construction, infrastructure and energy — from EMVI texts to technical installation specifications.

Construction · EMVI

Courthouse EMVI documents

Extraction from EMVI documents covering security passages, crash decks and dust screens. Actor determination critical due to tenderer context.

DRE testing successfully completed

Energy · Technical spec

Energy system specifications

Extraction from technical requirements for energy systems — heat pumps, installations and sustainability requirements with quantitative performance values.

RQA coupling directly deployable

Infrastructure · PvE

Heat-cold project Holten

Programme of Requirements for a district heat-cold supply. Extraction of functional requirements, constraints and performance indicators.

Demo document platform

Infrastructure · UAV-GC

UAV-GC contract documents

Complex contracts where obligations, assumptions and requirements are intertwined. TYPE classification is particularly valuable here.

REQ / ASSUMPTION / OBLIGATION split

Universal

Large documents (\> 50 pages)

Thanks to parallel processing, the DRE efficiently handles extensive specifications and planning documents. No manual pagination required.

\< 3 minutes regardless of document size

Future

API integration (roadmap)

Direct API integration with Relatics and DOORS is on the roadmap for the dedicated platform — no manual import required.

Dedicated platform · 2026

[Back to applications](https://basewise.ai/en/applications?hsLang=en)

#### BASEWISE

**Basewise** provides modular AI solutions and applications for process optimisation.

Basewise Consultancy B.V.  
Chris Schutweg 3  
3632JK Loenen aan de Vecht  
The Netherlands  
KVK-number 98925717

<https://x.com/><https://github.com/Basewise/framework>

[Applications](https://basewise.ai/en/applications?hsLang=en)

- [Platform](https://basewise.ai/en/platform?hsLang=en)
- [DRE](https://basewise.ai/en/dre)
- [RQA](https://basewise.ai/en/rqa?hsLang=en)
- [REF](https://basewise.ai/en/ref?hsLang=en)

[Company](https://basewise.ai/en/about-basewise?hsLang=en)

- [Contact us](https://basewise.ai/en/contact?hsLang=en)
- [AI Disclaimer](https://basewise.ai/en/ai-disclaimer?hsLang=en)
- [Terms and Conditions](https://basewise.ai/en/terms-and-conditions?hsLang=en)
- [Privacy policy](https://basewise.ai/en/privacy-policy?hsLang=en)

 Copyright © 2026 basewise.ai