Fidrel

Fidrel — Drawing and document review software

  • Consultants
  • Engineers
  • Public sector
  • Contractors
  • Architects
  • Developers
  • Project managers
  • Property owners

Review project information in Fidrel. Collect comments and follow the review process with the people involved.

Agree the review scope

The project system of tomorrow. For every discipline.

Identify the document, revision and checks required. Distinguish technical review from formal acceptance.

Describe the issue, location and clarification or correction required, referring to the right information.

Make comments actionable

Talk to us
The Fidrel advantage

Assign the response

Name the recipient and required date. A reply does not necessarily mean a drawing has been corrected.

Compare revised information with previous comments and retain visibility of unresolved items.

Explore the platform

01 / 05

Agree the review scope

Identify the document, revision and checks required. Distinguish technical review from formal acceptance.

View our plans
Fidrel project overview, programme and drawing viewer on a computer, tablet and phone.

Your whole project. Wherever you are.

From planning in the office to drawings on site. Fidrel brings your project documents, programme and information together in the browser – on your computer, tablet and phone. Create your account and bring the team together around the same information, wherever you work.

0+

project participants prepared in one shared environment

0 MB

per document upload

0+

items per structured import

0/7

access to project information

Ready for a clearer project?

Tell us how you work today. We will show you how Fidrel can fit your project and organisation. Together, we map the information flows, responsibilities and the first areas worth simplifying.

Get in touch

Frequently asked questions

When can a review close?+

When the responsible person has assessed responses and agreed how remaining items will be managed.

Does review mean approval?+

No. Any decision about approval or use needs to be clear separately.

What should be agreed before a design review?+

Identify the document, revision and checks required. Distinguish technical review from formal acceptance.

How do you write a clear review comment?+

Describe the issue, location and clarification or correction required, referring to the right information.

How should responses to comments be followed up?+

Name the recipient and required date. A reply does not necessarily mean a drawing has been corrected.