Fidrel — Document review software for technical consultants
- Consultants
- Engineers
- Public sector
- Contractors
- Architects
- Developers
- Project managers
- Property owners
Review issued documents in Fidrel. Keep comments, revisions and questions for other disciplines together in the project.
Define the review appointment
The project system of tomorrow. For every discipline.
Identify the documents and revisions being checked. A review comment should state the observation and the correction or response required so that the recipient can act.
Compare responses with the resubmission. A technical recommendation may require a separate project decision; Fidrel retains the exchange without replacing professional judgement or engineering calculations.
Check the revised information
Talk to usExplore the platform
Define the review appointment
Identify the documents and revisions being checked. A review comment should state the observation and the correction or response required so that the recipient can act.
View our plans
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.