Electrical job documentation works best when the office can connect a customer, a specific installation, the agreed work and the records returned from site. Photos can help explain what the team encountered and did. They do not establish every condition inside an installation, replace inspection and testing, or turn an ordinary job card into an electrical Certificate of Compliance.
This guide describes an administrative workflow for South African electrical contractors. It covers organising records and handing information between the office, field team, customer and responsible registered person. It does not provide electrical testing instructions, a certification checklist or a substitute for the applicable professional requirements. WorkOrderPro supports job coordination and job records; it does not issue a statutory electrical CoC or independently determine whether an installation complies.
Keep the certificate and supporting job record distinct
Regulation 9 of the Electrical Installation Regulations, 2009 restricts issuing a CoC to a registered person and describes inspection, testing and an accompanying test report. That distinction matters when choosing software: completing a digital form, collecting a customer signature or uploading a photograph does not itself satisfy those professional functions. Read the Department of Employment and Labour's published regulations for the authoritative requirements relevant to certification.
The job record answers different operational questions. Who requested the work? Which property and installation did the request concern? What was approved? Which visits occurred? What information is still outstanding? Where can an authorised colleague find the final documents? Clear answers help the responsible people organise their work without making the software responsible for technical conclusions it cannot establish.
Use separate descriptions for separate outcomes. “Site visit completed”, “repair work recorded”, “inspection information awaiting review” and “certificate received” communicate more accurately than one broad “compliant” label. The exact tracking method can be an agreed note or checklist if your software has no dedicated certification workflow. Do not present an internal label as an independent verification of the underlying document.
Start with a precise customer and site identity
Create the record against the person or organisation ordering the work and the physical site where the team will attend. These may differ: a property manager can coordinate several buildings, while a tenant can report a problem in a property owned by someone else. Record those relationships clearly enough that dispatchers do not send documents to the wrong party simply because a name appears first in a contact list.
Add the practical identifiers that distinguish the work location. A street address may need a unit, building, floor, shop number or agreed asset reference. When more than one distribution board is relevant, use consistent descriptions supplied or confirmed by the people responsible for the job. An unexplained label such as “main board” can become ambiguous across a large property or several visits.
Check the site reference before uploading images. Moving a photo after it has been shared creates avoidable confusion, especially when filenames look similar. Make the site name and job number part of the field team's review habit. If the wrong record has already received material, correct the association through the supported process and communicate the correction to anyone relying on the earlier version.
Describe the requested scope before the team attends
A useful request explains the reported issue, the expected attendance and any decision the customer needs from the visit. Distinguish investigation from approved repair work. A customer asking for a quotation, a fault assessment or assistance with documentation may require different preparation, time and personnel. Avoid translating a vague request into a promise of certification before the responsible person has assessed what is involved.
Record access arrangements separately from the technical scope. Include the authorised contact, agreed appointment, relevant site procedures and who can grant entry. Where planned interruption or coordination is necessary, record the agreed communication arrangements without putting operational safety instructions into a generic office template. The competent team must determine the actual working procedure for the installation and circumstances.
Give the technician a concise briefing that can be understood on a phone. Put the immediate request and site identifiers first, followed by useful prior-job references. A long history copied without review can bury the current problem. If a previous document matters, identify the exact version or date and explain why it is relevant rather than attaching a collection of unnamed files.
Decide what each record is meant to communicate
A record pack should have a purpose beyond accumulating files. An arrival image may establish which labelled area was visited. A close-up may illustrate a particular observation. A written note can explain the context that the image cannot show. The person reviewing the job should be able to understand why an item is present without guessing from the camera angle or filename.
The following table is an organising aid, not a statutory list of required electrical evidence. The responsible professional determines the actual inspection and testing records for the work. Use the table to decide how the office will connect supporting material to the right job and avoid treating every uploaded file as equivalent.
| Record | Administrative purpose | Review question |
|---|---|---|
| Customer request | Preserve the reported issue and requested attendance | Does it describe this site and this visit? |
| Agreed scope or quotation | Identify the work authorised commercially | Are later changes linked to an approval? |
| Context photograph | Show the relevant location or labelled area | Can a colleague identify what the image depicts? |
| Observation note | Explain a finding and its context | Is the statement attributed and clearly written? |
| Inspection or test-report reference | Locate the responsible person's technical record | Can an authorised reviewer retrieve the correct document? |
| CoC reference, where applicable | Identify a certificate received for the relevant installation | Is its identity and source clear? |
| Handover record | Record what was supplied and what remains outstanding | Is the customer being given an accurate completion message? |
Capture photographs with useful context
Choose photographs that explain a specific observation or stage of the work. A clear contextual image and a relevant closer view can be more useful than many nearly identical pictures. Capture images only when it is appropriate and safe to do so within the team's actual working procedures. Documentation should never distract someone from an electrical hazard or require unsafe access for a better camera angle.
Describe the subject in plain language. Include the agreed location or asset reference and the reason the photo matters. Avoid asking office staff to interpret an unexplained technical image. If the image relates to an observation that requires professional assessment, attribute that assessment to the person making it instead of treating the picture itself as the conclusion.
Before leaving the documentation step, inspect the image on the device. Check whether the subject is visible, the intended label can be read and the file belongs to the right job. A blurred image may be unusable even when an upload succeeds. Where a retake is no longer possible, explain the limitation in the record rather than presenting an unclear photograph as stronger evidence than it is.
Connect before, during and after records honestly
Where stage-based photography is useful, describe the stage accurately. A “before” photo means it was recorded before the documented change; it does not prove the installation's entire prior condition. An “after” image can illustrate visible completed work without proving hidden conditions or every test result. These limits should shape how staff describe the material to customers.
Keep continuity between the images by using the same agreed subject reference. If a later photograph shows a different board or area, say so. If the job spans multiple visits, explain which visit produced each item. This makes the record easier to review when technicians change or an office colleague prepares the customer handover after the original field team has moved to another job.
Do not overwrite an earlier explanation merely to make a sequence look tidier. Use the available correction or follow-up process and make the reason for a material change understandable. The goal is an accurate account that another authorised person can follow. A perfectly arranged gallery with missing context is less useful than a smaller set of clearly attributed records.
Record scope changes and outstanding decisions
Electrical jobs can reveal work beyond the customer's original request. Record the newly identified issue, who assessed it and what decision is required. Separate the technical observation from the commercial proposal. An observation can exist before the customer approves additional work, and a quotation can remain pending while the original attendance has ended.
When requesting approval, make the proposed addition easy to identify. Refer to the affected job and site, describe the additional scope and state the commercial terms through the appropriate quotation process. If a customer replies in a conversation outside the system, preserve the relevant decision in the authorised job record rather than expecting a future colleague to search personal message histories.
Track unresolved items explicitly. “Awaiting customer decision”, “return visit required” or “document reference outstanding” tells the next person what action remains. Do not close the administrative loop simply because the technician has left the site. Equally, do not describe an unapproved repair as completed or imply that a commercial approval establishes a technical compliance outcome.
Organise inspection and certificate references for retrieval
Use a document naming convention that helps an authorised colleague find the right record. A combination of site reference, job number, document type and issue date is usually easier to interpret than a camera-generated filename. If the formal document already has its own identifier, record that identifier accurately rather than inventing a replacement that could confuse later correspondence.
Keep the original issued document in an appropriate controlled archive. If your work-order setup cannot attach that document type, record its reference and the agreed retrieval location in the job notes. Check access from the account that will actually perform the handover. A link that works only for the person who created it is an unreliable office process.
Define who can add, replace, distribute or correct the record. An administrator may organise files while the registered person remains responsible for the professional document they issue. Make that division clear in training. The Department also advises the public to verify contractor registration; its warning about fraudulent electrical contractors explains why a professional-looking document or software account is not a substitute for checking credentials.
Review the handover pack before sharing it
Review the pack from the customer's perspective. Confirm the customer and site, the work described, the documents actually included and any outstanding action. Check that the cover message matches the contents. Saying “all documentation attached” when a referenced report is still missing creates a misleading impression and an avoidable follow-up conversation.
Keep internal discussion separate from customer-facing material. Pricing preparation, access notes, staff comments and images of unrelated areas may have no place in the handover. Select what the intended recipient needs to understand the work and next steps. Confirm the recipient's authority and address using the agreed customer record rather than forwarding an entire internal conversation.
A customer acknowledgement records the interaction you asked them to acknowledge. It should not be described as a technical inspection, professional certification or blanket acceptance of undisclosed conditions. Use clear wording about what was supplied or explained. If the customer raises a concern, preserve the concern and route it to the appropriate responsible person.
Use a practical office review table
A short office review can make the handover process more consistent without pretending to be an electrical compliance audit. The review should identify missing administrative information and direct technical questions to the responsible person. It should not require an administrator to infer safety or certification from photos, status colours or a completed checklist.
| Office check | Ready for the next administrative step | Needs follow-up |
|---|---|---|
| Site identity | Address and relevant installation reference agree across records | Different unit, building or unexplained board label |
| Scope | Original work and approved additions are distinguishable | Additional work is described without a recorded decision |
| Photo context | Relevant subjects and stages are understandable | Images are blurred, misplaced or unexplained |
| Document references | Referenced records can be retrieved by authorised staff | Missing file, inaccessible link or unclear version |
| Outstanding work | Remaining actions have a responsible person | A vague note leaves the next step unassigned |
| Customer message | Contents and limitations are described accurately | Message claims certification or completion beyond the record |
Plan for weak connectivity and interrupted uploads
A photograph visible on a device is not necessarily available to the office. Treat capture, queued storage, upload acknowledgement and successful retrieval as different stages. During a software trial, check the actual behaviour for the devices and actions your team uses. Do not assume that every screen, attachment or document works offline because one job-note operation does.
When the connection returns, verify that the intended material appears under the correct job and can be retrieved by the authorised office user. If an upload fails, use the supported retry process and confirm the outcome. Repeatedly tapping an action without checking its state can create confusion about which submission succeeded.
Have a documented exception process for device loss, account changes and interrupted attendance. Decide how a technician reports a missing record and who follows it up. Do not rely on personal camera rolls as the only archive or promise automatic recovery without testing it. See the offline field-service app evaluation guide for an action-based trial approach.
Evaluate WorkOrderPro with a representative electrical job
Use a realistic sample job to evaluate the workflow. Create the customer and job site, record a clear problem description, prepare the commercial scope, assign the technician and review the returned notes and photos. Include a change request or missing document reference so the demonstration tests an exception rather than only a perfect handover.
Ask the dispatcher and technician to complete their own steps. The office should be able to identify the job's next action, while the field user should find the correct site and scope without relying on a founder's narration. Check customer-facing material separately from internal records. This shows whether the workflow is understandable to the people who will use it every day.
WorkOrderPro's electrical contractor workflow and job-photo features can support that evaluation. Keep the certificate process explicit: use the responsible person's applicable documentation and an appropriate archive. Confirm any attachment, export or access requirement in the trial before treating it as supported. Compare the full subscription on the pricing page, counting active office users as well as field technicians.
Frequently asked questions
Can work-order software issue an electrical CoC?
An ordinary completed job card or software-generated work summary is not a statutory electrical CoC. WorkOrderPro coordinates work and records; it does not independently certify an installation. Use the responsible registered person's certification process and keep its documents distinct from the operational job record.
Are photographs enough to establish electrical compliance?
No. Photos can illustrate visible observations and provide context, but they cannot establish every condition or replace the relevant inspection and testing. Describe what an image shows and keep the responsible person's technical records identifiable. Avoid presenting a photo gallery as a complete compliance determination.
How many photos should an electrical job have?
There is no universal photo count proposed by this guide. Choose useful images for the actual scope and the responsible team's documentation needs. Check their clarity and context. A fixed quota can encourage repetitive pictures while still missing the one observation the next reviewer needs to understand.
Should every photo be shared with the customer?
Select material appropriate to the intended handover. Internal notes, unrelated areas and sensitive access details may be unnecessary for the recipient. Review the customer-facing selection and message before sharing. Keep the complete authorised internal record available to the staff who need it for their work.
What if the technician has no connection on site?
Check which actions the actual app supports without connectivity and how pending work is shown. Confirm upload and retrieval after reconnection. A locally visible image is not proof that the office has received it. Establish a clear follow-up process when records cannot be submitted during the visit.
Can a customer signature replace the professional certificate?
No. A customer acknowledgement and a professional certificate serve different purposes. Explain what the customer is acknowledging, such as receipt of a handover or a recorded service interaction. Do not describe that acknowledgement as the registered person's inspection, test report or certification decision.
How should documents from a return visit be organised?
Link them to the relevant site, original job and actual visit through the supported record process. Explain whether the new material adds information or corrects something earlier. Keep version references clear so staff do not accidentally distribute an outdated pack or mistake a partial update for the full record.
What should an electrical contractor test before adopting the software?
Test one complete job and one exception with real staff roles. Include site identity, scope approval, technician assignment, photos, missing information, authorised retrieval and customer handover. Verify the separate professional-document process and the full active-team subscription cost. Choose on demonstrated workflow fit rather than a generic promise of compliance.