A due date and an owner at every step of every review.
A review that runs by email has no clock and no owner. In DocFlow, a workflow template sets out each stage, who reviews in it, how many working days they have and which outcomes they can give. Start it on a set of revisions, and every step carries a due date, a responsible party and a record of what was decided.
How it works.
Stages and Parallel Steps
Stages run in order. Steps within a stage run side by side and complete when all, any or the lead reviewer finishes.
Durations in Working Days
Each step gets 1 to 60 working days, skipping weekends and the state's public holidays, with due dates forecast step by step.
Responsible by Name
Name who reviews each step, by person, group, organisation or role, and who is copied in.
Your Outcomes, Your Stamps
Two to six outcomes per template, each with its stamp and the document status it gives.
Final Step or Worst Outcome
Choose whether the last step decides the result, or the worst outcome across the review.
Controlled Flexibility
Decide whether the person starting a workflow can change durations, change reviewers or skip steps.
Every step has a clock and an owner.
Pick a template and the revisions, adjust reviewers and durations where the template allows, and start. Each reviewer gives an outcome for every revision, with a comment and a marked-up file where they have one.
- An outcome for each revision, with comments
- Marked-up files returned with the outcome
- Skip, reassign or terminate, with the reason on record
Every open review, closed out in one place.
See every workflow on the project with its stage, its due date and who it is waiting on. When people change, reassign their steps across up to 200 workflows at once, and send reminders to the organisations holding a step.
- Reassign many reviews at once
- Reminders to whoever holds the step
- In Progress, Completed and Terminated, all on record
Build the workflow your contract describes.
A template is built once and run on any submission. Set the stages, the steps inside each, how long each step has, who is responsible and how the stage completes. Templates can be duplicated, and up to 200 kept per project.
Design Review
- No Comments
- Minor Comments - Proceed
- Major Comments - Revise And Resubmit
- Not Accepted
Shop Drawing And Submittal
- Approved
- Approved As Noted
- Revise And Resubmit
- Rejected
ISO 19650 Acceptance
- A - Authorised And Accepted
- B - Accepted With Comments
- Not Accepted - Return To Work In Progress
Approve Or Reject
- Approved
- Rejected
Inspection And Hold Point Release
- Released
- Released With Conditions
- Not Released
Contract Notice Response
- Acknowledged
- Further Information Required
- Accepted
- Not Accepted
A finished review drafts its own transmittal.
When a workflow finishes, it can draft a transmittal for the person who started it, with the outcome and the reviewed revisions attached, ready to check and send to whoever needs the result.
- Outcomes and revisions attached
- Checked before it is sent
- Numbered and kept like any other project mail
Every approval, with who gave it and when.
Hold points, design approvals and submittals are where quality risk is accepted or stopped. DocFlow records each decision against the revision it was made on, with its reviewer, its date and its reasons.
A Due Date on Every Step
Durations run in working days, so late reviews are visible before they hold up site.
Accountability by Name
Each step has a responsible party, and each outcome records who gave it.
Decisions With Their Evidence
Outcomes carry comments and marked-up files, revision by revision.
Reviews Cannot Be Overtaken
A revision in a running workflow is locked, so it cannot be superseded mid-review.
Why it matters.
Reviews are where design risk, quality risk and program risk meet. When they run by email, a submittal can sit unanswered for weeks with no record of who had it. A DocFlow workflow puts a due date, an owner and an outcome on every step, so late reviews surface early and every approval can be traced back to the person who gave it.
Design and Project Managers
Run every review to one standard, with dates the team can plan around.
Reviewers and Consultants
See what is waiting on you, and return outcomes with mark-ups.
Superintendents and Clients
Release hold points and approve submittals with the record attached.
Workflows, in practice.
What is a document review workflow?+
A set route a submission follows for review: who looks at it, in what order, how long each has and what outcomes they can give.
Can review steps run in parallel?+
Yes. Stages run in order, and steps inside a stage run side by side. A stage completes when all of its steps finish, any one finishes, or its lead reviewer decides.
How are due dates worked out?+
Each step has a duration of 1 to 60 working days. Weekends and the project's state public holidays are skipped, and due dates are forecast step by step when the workflow starts.
What happens when a reviewer is away?+
The person who started the workflow can reassign a step, or reassign steps across up to 200 workflows at once.
Can reviewers mark up drawings?+
Yes. Reviewers can mark up a revision and return the marked-up file with their outcome. Their marks stay private until they submit the step.
What happens when a review finishes?+
The outcome rule decides the result, by the final step or the worst outcome. If the template says so, a transmittal is drafted with the outcome and the revisions attached.
See DocFlow Workflows on a real project.
30 minutes with our team, on live project data.
Book a Demo →