ESG commitments live or die on the project record
Plans get submitted, RFIs get raised and non conformances get closed out across separate inboxes and shared drives. When the client or an auditor asks for the evidence, nobody can show the full trail. DocFlow controls correspondence, document issue and review workflows in one system, with the ball in court always clear.
- ✕RFIs on local content and social procurement buried in personal inboxes
- ✕Superseded plans and schedules still in use on site
- ✕Submissions stalled in review, with no visibility of who holds them
- ✕No audit trail of what was issued, to whom and when
Inside DocFlow.
Six elements. The Head Contractor configures them, and every organisation on the project works in them, trade partners and the client included.
Mailbox↓
Project correspondence, RFIs, technical queries, site instructions and non conformance reports between organisations.
Document Register↓
A controlled register of plans and schedules, with revision status and full issue history.
Transmittals↓
Formally issue documents to any organisation on the project, with a record of what went to whom.
Workflows↓
Build review and approval workflows once, then run them on any plan, schedule or submission.
My Actions↓
Your ball in court: what is overdue, due this week, due later and still unread.
Analytics↓
Correspondence, documents and workflows reported by type, status and organisation.
Project correspondence, on the project record.
General correspondence, RFIs on local content, technical queries on recycled materials and non conformances on waste all run between organisations, not personal inboxes. Each item has a type, a thread, a holder and, where a response is owed, a response date.
- General correspondence through to RFIs and Non Conformance Reports
- Documents attached straight from the register
- The Head Contractor controls who can issue each type
Every plan and schedule, with its full revision history.
Environmental management plans, social procurement plans, and waste and materials schedules sit in one controlled register. Every revision stays on record, with who issued it, who received it and the workflow it went through.
- Revision history on every plan and schedule
- Filter by All, My Organisation or Received
- Preview a document without leaving the register
Issue documents, with a record of the issue.
Issue plans and schedules from the register to any organisation on the project. The revisions issued, the recipients and the date stay on record, ready when the client or an auditor asks.
- Issue from the register, one document or in bulk
- Recipients and revisions kept on every transmittal
- Start a review workflow from the same selection
Build the workflow, then run it on any submission.
Set up a review template once, stage by stage: who reviews, in what order and how long they have. Run it on an environmental plan or a social procurement submission, and every outcome stays on the record.
- Stages in order, with parallel steps inside a stage
- Worst Outcome Decides or Final Step Decides
- Total working days and a forecast finish on every template
Your ball in court, in one list.
Nobody has to chase three systems to find what is waiting on them. Overdue items come first, then what is due this week, what is due later and what is still unread.
- Choose All, Mail, Documents, Workflows or Reports
- Click an item to open what it is about
- Monthly reports you have to submit sit in the same list
See what is outstanding, by the numbers.
DocFlow Analytics reports the project's correspondence, documents and workflows by type, status and organisation, using the same statuses the Mailbox, Document Register and Workflows show.
- Mail by Type and Status
- Documents by Discipline
- Workflows by Template
DocFlow, in practice.
How does DocFlow relate to GovAssure?+
GovAssure keeps compliance records current against their obligations. DocFlow goes further into the project's working documents, adding a full register, mail between organisations and review workflows.
Who uses DocFlow on a project?+
The Head Contractor sets it up, and every organisation on the project takes part, the client included.
What types of mail can we send?+
General correspondence, letters, memoranda, requests for information, technical queries, requests for approval, quotation and substitution, and non conformance reports, among others. The Head Contractor can limit who sends each type.
How does a workflow reach its outcome?+
Each template uses one of two rules: Worst Outcome Decides or Final Step Decides. A parallel step waits on every party in it, and the workflow moves on when all have answered.
Can we send documents to another organisation?+
Yes. Select documents from the register and transmit them to any organisation on the project, one at a time or in bulk. The revisions sent, the people they went to and the date stay on record.
Can we see the history of a document or schedule?+
Yes. The register keeps every revision of a document or schedule, with who issued it, who received it and the workflow it went through.
Can other organisations see our mail and documents?+
You see mail you are party to, and documents your organisation holds or has received. Analytics follows the same rule, so mail you are not party to and confidential documents you cannot open are in no figure.