Frequently asked questions

Capital projects with many companies on one set of drawings. That covers energy and power, refineries, chemical plants, petroleum projects, onshore and offshore work, oil rigs, solar energy plants, infrastructure development and warehousing.

SetuVault is a Common Data Environment for engineering and construction projects. It holds the controlled record of every drawing and document: numbering, revisions, review, transmittals and the audit trail.

Owners, PMC consultants, EPC contractors, vendors and the document controllers who run them. Each company is a participant on a project and sees only what its role allows.

A revision is a formal issue. A version is a re-upload inside a revision, before it is issued. Only revisions are transmitted. Once issued, a revision refuses further files.

Yes. The numbering pattern is set per project, with a live preview. It is fixed once documents exist, so numbers stay consistent for the life of the project. The other party's own reference is stored and searchable beside ours.

Any file can be registered. Each shows its program's icon, including PDF, Office, AutoCAD, Revit, IFC and others, detected before upload. Drawings open in the browser viewer, with markup tools and side-by-side revision comparison.

Yes. The portal has a phone layout with an off-canvas menu and full-width drawers.

Yes, that is the normal case. The owner, the consultant, the contractor and any vendors each join as a participant and see what their role allows. One person can belong to several projects with a different role on each.

Yes. Each document has one comment sheet with the same columns most clients already use, from serial number and revision to response and resolved. Every row stays open until its author marks it resolved, and the sheet exports to Excel whenever the client asks.

Yes. Projects adopt a catalogue workflow template and keep their own copy. Steps, assignments and outcomes are edited on a screen. Every change is validated and audited.

1 Approved, 2 Approved with comments, 3 Revise and resubmit, 4 Rejected. With several reviewers, the worst code decides the next state.

Set a named alternate for the dates. New reviews go to the alternate automatically, and open ones are moved. A reviewer can also hand over a single review. Both names stay on the record.

Due dates run in working days on the project's holiday calendar. Late reviews are escalated in steps: the reviewer, then their organisation's controllers, then the project administrators. The steps and timings are configuration.

Yes, if the project switches on the comment sheet. It lists every comment, response and resolution across all revisions of a document, and can be exported to Excel by project administrators and document controllers.

Not in the audit trail. It is append-only, enforced in the application and by database triggers, and chained by hash so tampering is detectable. Documents deleted by mistake go to a recycle bin and can be restored.

In object storage with Object Lock for write-once retention. Each upload is hashed during the write and rejected if the size or SHA-256 does not match.

Deny by default, checked on the server for every request. A person only sees projects their company participates in. Row-level security applies in the database as well.

Yes. Users can enrol an authenticator app with recovery codes. A support desk can reset it for a user who loses their phone. The reset needs a reason and is audited.

A platform administrator can view as a project user for support. Project administrators can only do this under a time-limited grant for one project. The person is notified, and every act is audited with the real person named.

It goes to the recycle bin instead of disappearing. A project administrator can restore it with its revisions intact, and both the deletion and the restore appear in the audit trail.

Download the Excel or CSV template, list organisations and members with their roles, check the file, then import. New accounts get a one-time password and must set their own at first sign-in.

Your project administrator raises a support request from inside the portal. It gets a ticket number and a reply due time set by its priority, and you are told as soon as the desk answers. The whole conversation stays on the request.

Yes, without a screen share. With a request open, our desk can view the project as the person who has the problem, for a limited time. That person is told who is looking and why, and everything done is recorded under the helper's own name.

Yes. Project administrators can take a backup. Platform administrators can schedule them and decide whether downloads are allowed. A close-out package is available, and a backup can be restored as a new project.

Handover is planned from the start. The project can be closed out into a package of files, register and audit trail, retention rules keep records for as long as the contract requires, and a backup can be brought back as a project of its own if anyone needs it years later.