Fidrel

Role guide

Construction document controller: what Fidrel handles and what stays with you

A construction document controller receives, registers, distributes and archives the project’s documents and keeps superseded sheets out of use. This page follows that day task by task and says which part Fidrel does, which part it supports and which part stays with you.

30 days free · No long-term contract.

Project documents in Fidrel on a laptop, tablet and phone, showing a PDF drawing and its revisions

Where the role gets squeezed

The old revision that is still in someone’s hand

A revised sheet goes out, but a foreman keeps working from the printout or the attachment already on the phone. The controller hears about it when the work does not fit, not when the revision was issued.

No proof of who received what

Months later a recipient says a sheet never arrived. Without a record of the exact revision sent, to whom and when, the controller has an email thread to point to and little else.

A register that is a second job

When the drawing index lives in a spreadsheet beside the files, every upload is entered twice, and the index is only as current as the last person who remembered to update it.

The role, task by task

Receiving and registering is the part Fidrel does most of: one folder structure, a revision history on every document, and a drawing register that lists number, title, revision, status and revision date by discipline. Reviewing is shared with the team, since reviews and RFIs run in the same project. Distributing is the transmittal, with a number such as TR-001, a purpose, a list of recipients and the documents at the revision that was current when it went out. Archiving is a status, Archived, plus the folder structure itself; a file deleted by mistake can be restored for 30 days.

Documents, drawings & models
The drawing register in Fidrel with number, title, revision, status and revision date, grouped by discipline and showing the current revision

Who may approve, and what is recorded

The approved statuses, Approved, Issued for construction and Record (as-built), can only be set by a project administrator or by a member who is a document controller. Everyone else sees them greyed out with a note. Each change can carry a comment, and the status history shows the status, the date and the name for every step, so an issued-for-construction sheet can be traced to the person who released it.

Fidrel’s transmittal register with numbered transmittals, their purposes, recipients and the documents sent

A document controller’s day in Fidrel

  1. Step 1

    Receive and register

    Drop incoming files into the right folder with Upload. Fidrel reads the number, title and revision from the file name, so a file with an existing number becomes the next revision of that document, and an identical file is skipped.

  2. Step 2

    Set who can open what

    Lock a folder or a single document to selected people. Everyone who can open a file gets a notification when it is uploaded, and an email unless they have turned that off.

  3. Step 3

    Set the status

    Open the document and choose its Status, from Working and For review to Approved, Issued for construction or Record (as-built). Add a comment on the change if you like; the status history keeps every step.

  4. Step 4

    Distribute with a transmittal

    Choose New transmittal, pick the documents, add the recipients and a purpose such as For review, and issue it. The transmittal locks, and each recipient gets a personal link that needs no account.

  5. Step 5

    Follow up and retire

    Watch the log for Opened and Not opened, open Who holds which revision to see who still has the old sheet, and use Tell the recipients their revisions were replaced when a newer revision goes out.

Keeping superseded sheets out of circulation

The drawing register can show the current revision only or all revisions, with earlier ones marked Superseded, and two revisions of a PDF or image can be compared as an overlay or side by side. A transmittal takes only shared or published revisions, so work in progress stays in the project. When a revision is replaced, the log shows which recipients still hold the old one, and Fidrel can email them that their revisions were replaced. It cannot reach a printout somebody already pinned to a wall.

What stays with the controller

Fidrel does not route a document through automatic approval chains, and there are no sequential approval steps. There is no e-signature, so a signature collected on paper or in another tool stays outside Fidrel. Fidrel has no scanning or printing workflow: a transmittal prints from the browser, and paper copies are yours to log. Fidrel does not decide who ought to approve a document either: that is a call for you and the project administrators.

One project. One subscription. The entire platform included.

Your trial applies to your first own project and starts when that project is created. No card required. Afterwards, choose card or invoice to continue.

  • 30 days free
  • Unlimited participants
  • No minimum term

Role guide

Frequently asked questions

Anything else on your mind? We are happy to help.

Talk to us

No. A review has participants and a deadline, and each participant approves or requests changes, but there is no chain in which one step releases the next. The status of the document is set by someone who may set it.