How automation reduces approval and document chaos in building projects

The approvals stage of a Kenyan building project involves preparing submissions for the county planning department, the building department, NEMA, NCA, and the fire department — each with its own document list, its own format requirements, and its own sequencing rules. A typical residential project in Mombasa generates 40 to 60 individual documents across these submissions: drawings, structural calculations, title documents, consultant appointment letters, EIA reports, NCA registration forms, fire engineering drawings, and more.

The chaos does not come from the regulations. It comes from the documents themselves. The structural engineer issues drawings at Revision B while the architect has already updated to Revision C. The QS produces a cost estimate based on Revision B quantities. The EIA consultant references an earlier site layout that no longer matches the submitted planning drawings. No single person has a full view of which document version is current, which authority has received which version, and what is still outstanding.

This is not a compliance failure. It is a document management problem — and document management problems are precisely what automation solves. A system that templates documents, enforces version control, links submissions to an ERP audit trail, and surfaces outstanding items in a checklist removes the manual tracking that consumes project management hours and creates the gaps that cause rejection.

REDM's document management tools address this directly. Approval submissions are built from templates that pre-populate standard information — project name, plot reference, owner details, consultant team — so that every document carries consistent identifiers. Version control ensures that when the architect updates a drawing, any linked documents that reference it are flagged for review. The ERPNext integration logs every submission and every response in an audit trail that the client and consultant team can access in real time.

Each approval authority in Kenya has a defined list of required documents. The county building department's e-DAMS portal, for example, requires architectural drawings at specified scales, structural drawings stamped by a registered engineer, title documents, proof of land rates payment, and a completed application form. NEMA requires the EIA report in a prescribed format with specified appendices. NCA requires the contract sum, contractor registration certificate, and project registration form.

The documents required for each submission are knowable in advance. What varies from project to project is the content, not the structure. A document template system captures the required structure — the headings, the standard clauses, the required signatures, the reference numbering — and populates the project-specific data from a central project record.

The practical benefit is consistency. When the planning application, the building plan application, and the NCA registration all reference the same project name, the same plot number, the same owner details, and the same consultant team, the approval authorities process the submissions faster because there is nothing to query. Inconsistencies — a different project name on the EIA report than on the planning application, or a different architect named on the building plan than on the NCA registration — are the most common cause of requests for clarification, each of which adds days or weeks to the approvals timeline.

REDM templates standardise these identifiers across submissions. The project record is the single source of truth; every document pulls from it. Changes to the project name, address, or consultant team are made once and propagate to all linked documents.

Construction documents change. Drawings are revised in response to planning comments, structural design iterations, and client decisions. When the architect revises a drawing from Revision B to Revision C, the structural engineer, the QS, and in some cases the EIA consultant need to know that the reference document has changed — and they need to know what changed.

Without version control, this coordination happens through email. The architect sends a PDF. The structural engineer may or may not open it before issuing their next drawing. The QS may price Revision B quantities for two weeks before learning that Revision C exists. The client is not aware of any of this until the submission package goes in and the planning department identifies a discrepancy.

Version-controlled document management links all submissions to a project document register. Every document has a revision status, a date, and an author. When a document is revised, linked documents are flagged for review. The project manager — and the client — can see at a glance which documents are current and which have dependencies that need attention.

For approval submissions specifically, version control prevents the most expensive mistake in the approvals workflow: submitting an outdated document to an approval authority. A planning submission made with Revision B drawings when Revision C has been issued will be returned — not for a planning objection, but for a completeness check failure. The time lost is entirely avoidable.

REDM's document management platform integrates version control into every submission package. The submission checklist confirms, before lodgement, that every document in the package is the current revision.

Most project teams track approvals in spreadsheets or — worse — in their heads. This works on a single small project with one approval authority. It fails on any project that requires multiple submissions across multiple agencies over a several-month period.

An ERP-integrated approvals record does three things. First, it logs every submission: date, document list, recipient authority, and submission reference number. Second, it logs every response: approval, conditional approval, or request for further information, with the response date and any deadline for the next action. Third, it surfaces outstanding items: submissions that have not yet been acknowledged, responses that are overdue, and deadlines that are approaching.

The audit trail matters for two reasons. Contractually, it protects the consultant team — and the client — by establishing what was submitted when and what was outstanding at any point. Operationally, it allows the project manager to manage approvals actively rather than waiting for notifications and then reacting. If the county has not acknowledged a submission within its stated processing window, the project manager knows to follow up.

REDM's ERPNext integration builds this audit trail automatically. Every submission and every response is logged against the project record. The dashboard shows a live view of approval status across all authorities. Clients can check the status of their project's approvals without needing to call the architect or the county office.

The automation approach applies differently to each of the main approval authorities in Kenya.

County planning and building plan submissions (via e-DAMS in Mombasa): automation handles the document checklist — architectural drawings, structural drawings, title documents, proof of rates payment, application form, and any special consents. The checklist confirms completeness before lodgement. Version control ensures all drawings are current. The ERP log tracks submission status and response deadlines.

NEMA EIA submissions: the EIA report is a substantial document package prepared by a licensed NEMA expert. Automation manages the EIA tracking milestones: consultant appointment letter, scoping report, draft EIA, public participation records, final EIA submission, and NEMA clearance certificate. The ERP record links the EIA timeline to the overall project programme so the project manager can see whether the EIA is on track relative to the design milestones.

NCA project registration: this is a comparatively simple submission — contract sum, contractor registration certificate, completed registration form, and levy payment. Automation ensures that the NCA registration is not overlooked and that the registration certificate is logged against the project record before construction begins.

Consultant appointment letters: every approval submission requires evidence that the named professionals are appointed to the project. Automation templates these letters — architect appointment, structural engineer appointment, QS appointment, EIA expert appointment — and links them to the relevant submissions so they are never missing.

The submission checklist is the simplest automation tool and the one with the highest return. Before any submission is lodged with an approval authority, the checklist confirms that every required document is present, in the correct revision, signed by the correct professional, and consistent with the other submissions.

REDM's submission checklists are built from the current requirements of each approval authority — county e-DAMS, NEMA, NCA, and fire. When requirements change — a new form, an additional document, a fee revision — the checklist is updated centrally and applies to all projects. This removes the risk that a project team submits based on a checklist that is six months out of date.

The checklist also assigns ownership. Each document has a responsible party — architect, structural engineer, QS, client — and the checklist shows who has signed off and what is outstanding. This makes the submission preparation visible to the whole team and removes the ambiguity about who is responsible for what.

For the client, the checklist provides a single-page view of submission readiness. Instead of asking the architect whether everything is ready, the client can see the checklist status directly.

The approvals stage is not technically complex — the requirements are documented and the sequences are known. What makes it chaotic is the volume of documents, the pace of revisions, and the number of parties involved. Automation does not change the regulatory requirements. It changes the management of the documents that satisfy them.

The practical outcome for a developer is this: instead of discovering, two days before a planning submission, that the structural engineer's drawings are the wrong revision and the EIA report references an outdated site plan, the system flags these discrepancies continuously. The submission goes in complete and consistent the first time. The approval authority processes it in its standard timeframe. The ERP log records the response. The next submission starts from that record.

This does not shorten the regulatory processing time — the county takes as long as the county takes. What it shortens is the lost time between submissions: the time spent chasing documents, reconciling versions, and resubmitting after rejection for completeness failures. On a project that requires four or five approval submissions, this saved time can represent weeks or months.

REDM's approvals workflow, integrated with ERPNext and document management, is built to deliver this consistency. The project check at /feasibility/wizard maps the approvals path for your specific site; the document management platform then manages the submissions through to clearance.