Englishไทย
FPEP Enterprise

SOFTWARE BY FPEP ENTERPRISE

E1 Trace

Construction claims evidence and programme analysis software

Search project records using exact words and controlled synonyms, review highlighted passages, and prepare source-linked chronologies, timelines and programme reports.

E1 Trace by FPEP Enterprise

Software for your own project team

E1 Trace is a Windows desktop application for working with construction project records. This public website introduces the software; it is not a signed-in project workspace.

Contact us to discuss a demonstration, availability, licensing and installation. If you need professional support with an assignment, you can engage FPEP separately.

EXPLORE E1 Trace

Four connected areas of work

Choose an area of work. Expand a feature to inspect the screen and its explanation. Examples use demonstration records.

Records & search

Start with a separate case

Start with a separate case

Choose an existing case, connect a database or create a case. Original-resolution screenshot supplied in the development-story brochure.

Start with a separate case — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
See the case position

See the case position

Check document totals, date completeness and evidence quality before choosing the next review task.

See the case position — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Bring records into the case

Bring records into the case

Import documents, folders, email and programme data, with OCR profile and source controls visible. Microsoft connections depend on permissions and configuration.

Bring records into the case — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Find relevant evidence

Find relevant evidence

Search exact words and related terms. This demo shows 54 results, with document dates, match information and review checks alongside the selected record.

Find relevant evidence — E1 Trace DEMO_250
Demonstration project using fictional records.Open full screenshot ↗

Evidence references identify records; document dates describe their timing. These search results are sorted by relevance, not chronological order.

Read the underlying document

Read the underlying document

Inspect the source preview and highlighted wording alongside match navigation. The displayed spreadsheet preview states its layout limitations.

Read the underlying document — E1 Trace DEMO_250
Demonstration project using fictional records.Open full screenshot ↗

Evidence references identify records; document dates describe their timing. These search results are sorted by relevance, not chronological order.

Evidence & events

Carry the source into the narrative

Carry the source into the narrative

A source-linked extract retains the supporting passage, citation and verification context. Original image from the development-story brochure.

Carry the source into the narrative — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Follow the source reference

Follow the source reference

Inspect the evidence ID, original filename, source location and recorded review decisions in one traceability view.

Follow the source reference — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Review event and claim suggestions

Review event and claim suggestions

Inspect a suggested event beside its source evidence. The demo contains suggestions awaiting human review; no suggestion was accepted during capture.

Review event and claim suggestions — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Review site submissions

Review site submissions

Optional field capture provides a submission inbox and human review before event promotion. This configuration view has no submissions and its gateway is stopped.

Review site submissions — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗

Programmes & progress

Assess programme quality

Assess programme quality

Review DCMA and P6 checks with distinct pass, fail and review outcomes. Demo figures are illustrative; checks do not establish causation or entitlement.

Assess programme quality — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Turn exceptions into review actions

Turn exceptions into review actions

The programme-quality view groups recorded exceptions and recommended actions for investigation and correction in the source programme. Brochure image.

Turn exceptions into review actions — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Compare programme progress

Compare programme progress

Compare programme revisions, progress curves and changes in completion dates using the current demonstration report.

Compare programme progress — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗

Reports & review

Choose the report you need

Choose the report you need

Choose a report purpose, define its scope, review the evidence and resolve readiness checks before generation. The current workspace includes case summaries, chronologies, programme progress and evidence readiness.

Choose the report you need — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Define scope before generating

Define scope before generating

Choose the report purpose, search terms, evidence dates and detail level before previewing the supporting records. Original image from the development-story brochure.

Define scope before generating — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Inspect the evidence behind a report

Inspect the evidence behind a report

The report evidence view displays source rows, supporting text and inclusion controls. This brochure screenshot shows processing in progress, not completed approval.

Inspect the evidence behind a report — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Check readiness before issue

Check readiness before issue

The Evidence Readiness preview makes missing and unverified dates visible before controlled issue. These demonstration checks remain unresolved; no report was approved or issued.

Check readiness before issue — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗
Keep review and approval visible

Keep review and approval visible

Use the review queue, date actions and case governance routes to address outstanding work before handover.

Keep review and approval visible — E1 Trace DEMO_250
Select the image to inspect the detailOpen full screenshot ↗

IMPORT & CONNECT

Bring your records into the review

Start with local project folders or select records from Microsoft document libraries. Keep the source context alongside the imported evidence.

01 / LOCAL RECORDS

Import project folders

Bring PDFs, Word files, Excel workbooks, MSG or EML emails, P6 XER and Microsoft Project MPP programmes, and drawing files into the project workflow. Retain source records alongside the review.

02 / MICROSOFT LIBRARIES

Connect SharePoint, Teams & OneDrive

Sign in to discover available libraries and select files for controlled local copies. Access depends on your Microsoft account permissions and your organisation’s connection setup.

03 / SOURCE TRACEABILITY

Retain the reference

The connector records source links, file metadata and integrity hashes alongside the intake snapshot. Remote-change checks help identify records that need further review.

Microsoft connections use read-only access and controlled snapshots. They do not edit the source library or provide continuous two-way synchronisation. Confirm connector availability and configuration for your E1 Trace deployment.

Discuss your import and connection requirements →

Explore field capture and site submissions ↓

Reports with a route back to the evidence

Explore chronology, timeline and programme outputs. Historical examples are labelled with their originating version.

OPTIONAL WORKFLOW FOR LIVE PROJECTS

Capture on site and review as the project develops

For teams working on active projects, add field capture to bring site observations and supporting records into FPEP while work is under way. Keep the source context as the team considers events, change and potential impacts.

When to choose this option. Use it when a live project team needs a consistent route for recording observations on site and passing them to the people responsible for review. FPEP can also be used to review existing project records without adding this field-capture workflow.

How it works. The site team submits an observation and attachments through the configured gateway. A reviewer checks the submission in the inbox, returns it for clarification or accepts it, and arranges evidence registration or event promotion as appropriate. The reviewed information then supports notice, programme and commercial review.

01FPEP Field Capture

Record an observation with its location, date and supporting attachments. Keep the field account available for the reviewer.

02Secure Sync Gateway

Transfer submissions through the configured project gateway. Secure remote access requires an appropriately configured HTTPS deployment.

03Field Submission Inbox

Review incoming observations. Accept, return or reject a submission, retaining the review decision before event promotion.

Evidence Register

Bring supporting records into the evidence workflow, retaining their source references and review status.

Proposed Case Event

Consider whether the observation should become a case event. Accepted submissions can be promoted following review.

Event & Claim Intelligence

Review the event alongside its supporting evidence, then identify the further assessments and actions required.

Variation / MOC / Notice

Consider variation, management of change (MOC) and notice requirements, including the responsible person and next action.

Programme Impact Review

Examine the relevant activities, dates and programme context to assess potential time implications.

Commercial Assessment

Use the reviewed event and supporting records as inputs to an assessment of commercial implications.

Optional live-project workflow. Select a stage to learn more. The arrows show the review route; a field submission does not automatically establish a claim, programme impact or commercial entitlement.

Discuss the option for your project. Agree the participating site team, reviewer responsibilities, gateway and device access, and how accepted submissions enter the case. Availability, deployment and any associated licensing or service scope are confirmed before setup.

Discuss the live-project option →

PRACTICAL QUESTIONS

Getting started with E1 Trace

Do I need to log in to this website?

No. This is a public information website. E1 Trace is a separate Windows desktop application, so there is no website account to log out of.

Where does the software run?

E1 Trace is a Windows desktop application. Contact us to confirm installation and system requirements for your deployment. The website and screenshot tour can be viewed on other devices.

Confirm your Windows environment, organisation’s installation policy and intended workload before deployment. This page does not promise native Mac, iPhone or iPad application support.

How is it set up?

The current build guide describes extracting the complete package and starting its included launcher. A separate Python installation is not required. During an access discussion, confirm the package, permissions and any additional tools needed for your file types.

Where are the records stored?

The demonstrated workflow uses a case database and evidence files in the local working environment. Microsoft-library imports create controlled local snapshots with source references. Plan storage access, backups and retention with your organisation before importing client records.

The public website does not provide project-file upload. Agree a suitable transfer method separately for a professional-services assignment.

What is needed for SharePoint, Teams or OneDrive?

Microsoft connections require account access to the relevant libraries and your organisation’s connection setup. They use read-only access and controlled snapshots rather than continuous two-way synchronisation. Confirm permissions and any administrator involvement with your IT team.

Will every imported file be fully searchable?

Searchability depends on the source format and the quality of extracted text or OCR. MPP programme conversion and native drawing handling may require additional tools or suitable exports. Use a demonstration to check representative files and any limitations; see Import & connect.

How do access and pricing work?

Contact us to confirm E1 Trace availability, licensing, setup requirements and terms. There is no software checkout on this website.

Professional-service scope, deliverables and fees are agreed separately before an assignment begins.

Can I use MPP programmes and CAD drawings?

Programmes: P6 XER files use the programme importer. MPP files are converted to XML using Microsoft Project. If automatic conversion is unavailable, you can prepare an XML export in ProjectLibre. Original programme files are retained.

Drawings: DWG, DXF and DWF files are retained and opened in a compatible application. Retaining a drawing does not automatically extract its CAD content.

Can you help prepare a response to a claim?

Yes. The proposed scope can support claim preparation, review or response through evidence organisation, factual chronology and referenced supporting documents. The engagement will define the questions to address and responsibilities for conclusions.

Can a programme check identify the cause of delay?

A quality check identifies findings in the programme. A revision comparison shows recorded changes. Establishing the cause of delay requires further assessment of the programme, events and supporting evidence.

Ask about your setup →

Arrange a demonstration

Tell us about your role and project records. We can show you relevant features and discuss availability, setup and licensing.

Request a demonstration ↗