EIZ firm registration needs 3 separate checks: the organisation’s membership category, the EngRB firm application, and the practising evidence of the people responsible for engineering work. An employee’s individual membership is not the company’s registration. The current EIZ constitution and its linked firm form describe different stages, so their staff requirements should not be collapsed into one universal rule.
By Spout Team. AI-assisted drafting by Codex, grounded in the linked EIZ primary documents.
Are you preparing individual membership, organisation admission or firm registration?
Start with the applicant named on the record. An individual’s qualification documents, an organisation’s incorporation evidence and a firm’s application to the Engineering Registration Board concern different subjects. A company profile containing an engineer’s membership number does not establish that the company has obtained its own applicable registration. Likewise, a company application does not make each person on its staff professionally registered.
EIZ’s 2025 constitution distinguishes Engineering Organisation membership from Engineering Unit membership. The latter concerns an operational entity of a non-engineering organisation that provides engineering services internally in support of the organisation’s core activities. This distinction matters for a business whose main activity is outside engineering but which has an internal engineering function. Describe the actual entity and activity before selecting an application route. EIZ Constitution 2025, Article IV.
For admission as an Engineering Organisation Member, the constitution describes a body involved in engineering with at least one staff member who is a certified member, professional member or Fellow. For an Engineering Unit Member, it identifies at least one staff member who is an Incorporate Engineer, Professional Engineer or Fellow. These are the constitution’s admission conditions for the respective categories; neither sentence should be rewritten as a complete firm-licensing checklist. The constitution also states prior Association of Consulting Engineers of Zambia registration requirements for the consulting organisation and consulting unit cases described there. EIZ Constitution 2025, Article IV.
The linked EngRB form is a separate application headed “Registered Engineering Organisation or Engineering Unit”. It asks the applicant to identify engineering disciplines, engineering employees and business offices or project locations. Its staff section asks for two employees registered to practise engineering in Zambia who control the listed engineering activities, with their signatures and valid practising licences. The EIZ company-registration FAQ also lists two valid EngRB practising licences for employees responsible for engineering operations. That is the evidence requested by these firm-registration materials, not a reason to erase the constitution’s distinct admission wording. EngRB firm application, EIZ FAQ.
The form carries a July 2018 validity label and remains linked from EIZ’s journal page. Treat that date honestly: current availability of the PDF does not make every detail a newly issued instruction. Ask EIZ to confirm the applicable firm class, current form and route for your circumstances before submission, particularly where a consulting or foreign-organisation case is involved. This guide does not assign your class or establish that a particular team satisfies the applicable conditions. EIZ journal downloads.
Use the following original evidence map to keep the stages distinct. It helps identify the question to put to EIZ when a colleague says simply, “We already have EIZ.”
| Record or question | Evidence to locate | What it does not establish by itself |
|---|---|---|
| Individual membership | Named person’s membership record and relevant qualifications | Organisation admission or firm registration |
| Organisation or unit admission | Applicant entity, actual activity and constitution category | Completion of the separate EngRB firm application |
| Firm application | Current applicable EngRB form and entity documents | Approval merely because the form has been completed |
| Responsible engineering employees | Actual role, signature and valid practising evidence requested by the firm materials | Permission to name people who do not control that work |
| Company identity | PACRA record and company profile | A professional entitlement for every activity in the profile |
| Official outcome | EIZ or EngRB response applicable to the applicant | Coverage of a different entity, class or future project |
What should the company evidence folder contain before submission?
Begin with a company profile that explains actual engineering activities. The linked form asks for industrial activities related to engineering and disciplines appropriate to them, as well as the organisation’s incorporation year and registered business address. A marketing list of services is a poor substitute for a coherent description of what the applicant does. Reconcile the profile with the application so that responsibility and scope remain intelligible. EngRB firm application, Part A.
Next, assemble the entity evidence requested by the current company FAQ: PACRA certificate of incorporation and computer printout, valid ZRA tax clearance certificate, company profile and the stated practising licences. The older linked form uses “certificate of share portfolio” in its PACRA list. Keep that wording difference visible and confirm the accepted current registry output rather than silently assuming that every PACRA document is interchangeable. EIZ FAQ, EngRB firm application, registration requirements.
Create a responsibility sheet for the named employees. Record the engineering activities each person controls, the licence identifier and the document supplied. The form expressly asks employees to sign in their own handwriting and attach valid practising licences. A membership certificate, a CV and an unsigned list of names answer different questions. Obtain the correct evidence from the actual responsible people; do not describe a borrowed name as operational supervision.
For the submission record, keep the completed form, attachments and correspondence together. The form includes an applicant declaration that the particulars are true to the best of the applicant’s knowledge and belief. Review factual inconsistencies before signing: different company names, an old registered address or a profile describing a different activity should be resolved rather than hidden by a polished PDF. Retain the version actually submitted so that a later request can be answered against that version.
Do not turn the FAQ’s processing-time statements into a promised completion date. This guide has not lodged an application, received approval or verified a particular firm’s live status. If you need to establish registration for a tender or project, obtain the relevant current official record and check that its applicant, class and scope answer that requirement. A submission acknowledgement should remain labelled as an acknowledgement until the issuing body supplies the applicable outcome.
For a public website, use the same discipline. Describe engineering services and registration status only as the business can substantiate, with permission to publish any personal details. Spout’s web development service is a relevant route for discussing how to present the business clearly. Use /get-started/ to outline the site requirement, keeping private identity and practising documents out of public page content.