How to Run an Internal Review Workflow Before Sending a Submittal

Your team has just finished a batch of shop drawings. The lead engineer glances at them, nods, and you fire off the transmittal to the consultant. Two weeks later, the response comes back: Revise and Resubmit on half the package. The consultant found title block errors, mismatched revision numbers, and a drawing that referenced an outdated specification. Every one of those issues could have been caught internally — if you had a proper review workflow in place.

Internal review before external submission is one of the most effective quality gates in construction document control. Yet on many projects, it is either skipped entirely or handled through a chain of emails that nobody can trace afterwards. This article walks through how to set up a structured internal review workflow using Mowafeq, so your documents are vetted before they ever leave your organisation.

Why Internal Reviews Matter More Than You Think

When a submittal gets rejected by the consulting engineer, it does not just delay that particular document. It triggers a cascade: the resubmission resets the review clock, downstream procurement waits, and your team loses credibility. On large projects with hundreds of submittals, a high rejection rate can push an entire programme off schedule.

An internal review workflow acts as a filter. Before any document is packaged into a transmittal and sent externally, it passes through one or more reviewers inside your own organisation. These reviewers check for completeness, technical accuracy, compliance with project standards, and simple errors like wrong reference numbers or missing signatures. The goal is straightforward: catch problems while they are still cheap to fix.

The challenge is doing this in a way that is structured, trackable, and does not slow you down. That is where a dedicated workflow inside your document control system becomes essential.

Setting Up a Review Workflow in Mowafeq

Mowafeq supports two approaches to internal review workflows: preset templates and dynamic workflows. Both achieve the same result — routing documents through internal reviewers before external transmission — but they suit different situations.

Preset templates are ideal when your review process is standardised. For example, if every structural shop drawing must be checked by the senior structural engineer and then approved by the engineering manager, you create a template with those two steps. Any time someone initiates a review for a structural submittal, the template is applied automatically. No need to pick reviewers each time.

Dynamic workflows give you flexibility. When a document does not fit a standard template — perhaps it requires input from a specialist or an additional quality check — the initiator can define the review steps on the fly, selecting reviewers and setting the sequence as needed.

In both cases, each step in the workflow is tracked. The document moves from one reviewer to the next, and at each stage the reviewer can approve, request changes, or add annotations directly on the PDF inside the browser.

In-Browser PDF Annotation During Review

One of the most practical features of running reviews inside Mowafeq is the ability to annotate documents without leaving the platform. When a reviewer opens a document assigned to them, they can mark up the PDF directly in the browser — highlighting issues, adding comments, drawing attention to specific areas.

These annotations stay attached to the document and are visible to subsequent reviewers and the original author. There is no need to download the file, open a desktop PDF editor, save a marked-up copy, and email it back. The entire feedback loop happens in one place, and every annotation is part of the audit trail.

For document controllers, this means less chasing. You can see exactly where a document is in the review process, who has commented, and what issues were raised — all from the document registry.

The Review-to-Transmittal Flow

Once a document clears the internal review workflow, it is ready to be included in an outgoing transmittal. In Mowafeq, this connection is explicit: documents that have completed their internal review can be selected for transmittal packaging, and the system maintains the link between the review outcome and the transmittal.

This creates a complete trail. If a consultant later questions why a particular document was submitted, you can trace back through the internal review — who approved it, when, and with what comments. On projects that require ISO 9001 compliance or similar quality management standards, this kind of traceability is not optional; it is expected.

The flow looks like this in practice:

1. A document is uploaded or a new revision is created.
2. An internal review workflow is initiated (using a preset template or dynamic steps).
3. Reviewers annotate and approve or request changes.
4. Once approved, the document is added to a draft transmittal.
5. The transmittal is finalised and sent to the external party.

Each of these steps is recorded, timestamped, and visible in the document history.

Common Mistakes to Avoid

Even with a good workflow tool, internal reviews can go wrong if the process is not designed well. Here are the most common pitfalls:

Too many review steps. Every additional reviewer adds time. If a drawing needs to pass through five people before it can be submitted, your cycle time will balloon. Keep the workflow as lean as possible — typically two steps (technical reviewer + approver) is enough for most submittals.

Unclear review criteria. If reviewers do not know what they are checking for, the review becomes a rubber stamp. Define a simple checklist: correct title block, right revision number, compliant with the referenced specification, proper file naming convention. Share this with all reviewers so expectations are aligned.

Skipping reviews under time pressure. When deadlines loom, teams often bypass the internal review to speed things up. This almost always backfires. A rejected submittal costs far more time than a two-day internal review. Protect the workflow.

Not using annotations. Verbal feedback or separate emails defeat the purpose of a structured review. If a reviewer has a comment, it should be recorded on the document itself so there is a clear, traceable record.

Getting Started

If your team is currently reviewing documents through email chains or shared folders, moving to a structured workflow does not have to be a big-bang change. Start with one document type — shop drawings are usually the best candidate because they have the highest volume and the most rejections. Set up a two-step review template, run it for a few weeks, and measure whether your rejection rate drops.

Mowafeq makes this straightforward to configure. You define the workflow template, assign the default reviewers, and every new submittal of that type automatically follows the process. No training needed for reviewers — they see their pending items on the dashboard and can act directly from there.

If you are managing document control on a multi-company construction project and want to see how internal review workflows work in practice, take a look at Mowafeq.