Fidrel — Collaboration software for construction project teams
- Owners
- Engineers
- Public agencies
- General contractors
- Architects
- Developers
- Construction managers
- Subcontractors
Connect construction project teams in Fidrel. Keep messages, questions, documents, and responsibilities in a shared project workspace.
Agree where questions belong
The project system of tomorrow. For every discipline.
Use messages for discussion and RFIs for questions requiring an assigned recipient and deadline. A common process helps new participants follow the work without old private email threads.
Refer to the location, document and revision when responding. Record formal decisions in the appropriate project record and confirm who will implement the change before closing the discussion.
Leave the next party a usable answer
Talk to usExplore the platform
Agree where questions belong
Use messages for discussion and RFIs for questions requiring an assigned recipient and deadline. A common process helps new participants follow the work without old private email threads.
View our plans
Your whole project. Wherever you are.
From planning in the office to drawings on the jobsite. Fidrel brings your project documents, schedule 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 organization. Together, we map the information flows, responsibilities and the first areas worth simplifying.
Get in touch
Frequently asked questions
When are direct messages useful?+
For a focused exchange that the wider project team does not need to follow.
Can chat serve as a formal notice?+
Use the project’s agreed procedure; some communications need separate handling.
How do you choose the right recipients for a project message?+
Separate people who must act from those who need an update; avoid sending every message to everyone.
How do you give a message the right context?+
Reference the project, location and supporting document so a short message still makes sense later.
When should a discussion be recorded as a decision?+
Move significant conclusions into the decision record or formal request workflow when traceability requires it.