Audit trail
When a revision, a status or an amount is questioned, the team needs to see who changed what and when. “Audit trail” sounds like one list, but in a project it is several, and each answers a different question. This page says what Fidrel records in plain terms: the project’s activity list, the history inside each record, the status history of a document, and the trail of a transmittal. It also says where a name appears and where it does not.
30 days free · No long-term contract.
A revision is questioned in a meeting, but the change happened in an email, a folder or a spreadsheet. When the history lives in several tools, answering takes a search through all of them, and some of the trail is simply gone.
If an amount or a status can be edited without a trace, the final figure is all anyone has. The dispute is then about memory, and the person who remembers best is not always the one who is right.
A single log of every click answers every question and no question quickly. The useful trail is short, tied to the record it belongs to, and tells you in one glance what happened and who did it.
Activity & history is introduced as an automatic, read-only log of important project changes. It lists documents and their versions, reviews and markups, RFIs and issues, change orders and NCRs, cost changes and saved schedule baselines, with the verb for each: created, updated, changed status, moved to the recycle bin, restored, received a new revision, answered. Entries for risks, tasks, transmittals, forms and time follow the same pattern. Each entry links to the record, so the list is a way into the project rather than a dead end. It does not name the person; that is on the record.
Documents, drawings & models
A change order, an NCR or a daily report keeps its own history. Each event carries a date, a person and a label, and the fields that changed are listed, so a quantity or a due date can be traced to the edit that set it. Only a project administrator approves a change order or enters its approved cost. A daily report cannot be deleted, and every change is logged field by field with name and time. In the costs, the History tab lists each action with its date and the person, and the values from and to.
Step 1
Open Activity & history in the project. Each entry names the kind of record, its title, what happened, such as received a new revision or changed status, and when. A status change shows the old and the new status. Choose an entry to go to the record.
Step 2
For a drawing, the Versions tab lists every version with its upload date, size and change note. Under Details a version shows when it was uploaded, its version and revision, and its Checksum, and where it came from if it was imported.
Step 3
Under a version, Status history lists each status with the date and the person, and a comment if one was written. Approved, Issued for construction and Record (as-built) can be set only by an administrator or a document controller.
Step 4
On a change order, an NCR or a daily report, open Activity & history in the record. Each event shows the date and the person, and the fields that changed. A comment can be added there.
Step 5
The transmittal register shows what was issued, to whom, and whether it was opened and confirmed. In the project’s costs, the History tab lists each change with who performed it and a From and a To side.
A new file with an existing number becomes a new version, and earlier versions are kept with their date and change note. A status change is written to the status history with the person and an optional comment. Deleted files and folders are moved to the recycle bin and can be restored for 30 days, and the activity list records both the move and the restoration. The schedule keeps its own history, which notes that a baseline was saved. Together, these cover the questions people ask most often.
The Activity & history page lists the project’s 100 most recent entries, so an older change is found in the record’s own history. The Versions tab gives the date, size and change note of each version, and the person appears in the status history. Fidrel does not claim that these records satisfy any legal or evidentiary requirement, and it has no signing feature. Treat the trail as a working record of the project, and ask your own advisers what a dispute would need.
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.
The project system of the future connects people, documents and decisions. Discover the thinking behind Fidrel.
Read more
On site, answers need to be close at hand. Fidrel displays DWG drawings in your mobile browser, within the project’s document structure.
Read more
When everyone can see the next step, moving the project forward becomes easier. Fidrel brings activities, dates and reported progress together in a shared Gantt view.
Read moreThe record of who changed a document or a related record, what changed and when. In Fidrel it is spread over the activity list, each record’s history, the document status history and the transmittal trail.
Open the document and its Versions tab for the dates and change notes, and read the status history under a version for the person, the date and any comment. The project’s Activity & history list shows when the revision arrived.
No. Every change is logged field by field with name and time. A daily report cannot be deleted, and only a project administrator approves a change order.
Yes. Deleted files and folders can be restored for 30 days, and the activity list records the deletion and the restoration.
No. Fidrel has no signing feature and makes no claim that its records meet a legal or evidentiary requirement. The trail shows who did what and when, as a working record of the project.
