Documenting copyright for software and technical works in Kenya starts from a different legal premise than many founders assume, and the assumption itself is the first thing worth correcting. Under the Copyright Act, 2001, copyright in Kenya is not something you apply for and wait to be granted. It exists automatically the moment an original work, including source code, technical documentation, and design files, is fixed in a tangible form. Registration is entirely voluntary. The real question for a business is not whether to seek copyright protection, since that already exists by operation of law, but how to build a documentation trail that actually proves ownership and origination if a dispute ever reaches a courtroom.
What Voluntary Registration With KECOBO Actually Gives You
The Kenya Copyright Board (KECOBO) is required under the Act to maintain a data bank of authors and their works, and it does this through a voluntary registration system run via the National Rights Registry Portal. Registration does not create the copyright, since that already exists from the moment of fixation, but it creates a public record and, more importantly, a certificate that acts as evidence of ownership in court in the event of a dispute. The current registration fee is around KES 1,000 per work, payable by bank deposit or M-Pesa, with a certificate typically issued within five to seven working days of a successful application. Businesses should confirm the current fee schedule directly with KECOBO before budgeting for a registration round, since government fee schedules are revised from time to time and a figure quoted even a year or two ago may no longer be current. Computer programs and software are explicitly covered as a category KECOBO registers, alongside musical, audio-visual, literary, and artistic works.
The certificate is worth more than a formality. Beyond acting as prima facie evidence of ownership, it makes licensing and assignment transactions considerably easier to structure, since a counterparty or investor conducting due diligence can point to an official record rather than relying solely on internal company documentation. Some businesses also use a registration certificate as supporting evidence when seeking financing, since a documented IP asset is easier for a lender to assess than an undocumented claim of ownership.
Why Software Needs a Different Documentation Approach Than a Static Work
A book manuscript or a design file is fixed the moment it is written or drawn, and its authorship is usually straightforward to establish from a single dated copy. Software is different. Code evolves through many hands, many commits, and many versions before it reaches a state worth protecting, and a single KECOBO deposit at one point in time will not, by itself, establish who wrote which part of a codebase or when a particular feature was actually created. For software specifically, the documentation that matters most in practice is often not the registration certificate at all, but the underlying development record: version control history showing authorship and commit dates, code review records, and internal documentation of the development timeline. A business should treat its version control system, properly configured with accurate authorship attribution rather than a single shared commit identity, as part of its copyright evidence strategy, not merely as an engineering tool.
This matters most at the exact moment ownership is most likely to be disputed: when a contractor, a departing employee, or a co-founder leaves and a disagreement arises over who owns what was built. Section 31(1) of the Copyright Act already determines the legal default here, generally vesting ownership of commissioned work in the party who paid for it rather than the contractor, a point covered in more depth in our guide to software development agreements in Kenya. Documentation does not change that legal default, but it is what allows a business to actually prove, rather than merely assert, that a given piece of code falls within it.
Building a Practical Documentation Trail
A reasonably disciplined documentation practice for software and technical works includes maintaining version control with accurate per-developer authorship, retaining signed assignment or work-for-hire language in every contractor and employment agreement rather than assuming the statutory default will cover every situation cleanly, keeping dated records of design specifications and technical documentation separate from the code itself, and registering the most commercially significant works with KECOBO rather than attempting to register every minor update. Registering a major release or a stable, commercially important version, rather than every incremental change, is generally a more sensible use of the process than attempting continuous registration. A cap table or IP schedule prepared for a fundraising round should also reference the specific registered works and their certificate numbers where registration has been done, since investors conducting due diligence will ask what has actually been registered rather than accepting a general assurance that the company owns its own code.
Where a business would rather keep source code and technical processes confidential instead of placing them on the public KECOBO register, trade secret protection is often the more suitable route for that specific material, since a copyright registration necessarily involves depositing a copy of the work. Our guide to trade secrets in Kenya covers when confidentiality protection is the better fit than registration, and the two approaches are not mutually exclusive: a business can register a public-facing release for copyright evidence purposes while keeping the underlying proprietary algorithms or build processes protected as trade secrets instead.
Technical Literature and Design Files Need the Same Discipline
The same principles apply to technical manuals, training materials, and design files, though the practical risks differ slightly from software. A technical manual or a set of design drawings is usually authored in a more linear, single-version process than a codebase, so establishing a clear date of creation is often simpler, but businesses still commonly fail at the more basic step of consistently marking ownership. A copyright notice, the author or company name, and the year of first creation, costs nothing to add and materially strengthens a later ownership claim, yet it is routinely left off internal technical documents and design files precisely because they were never intended to leave the building. Where a manual or design was produced jointly with an external consultant or agency, the underlying services agreement should say explicitly who owns the resulting copyright, since the commissioning default under the Act, while generally favourable to the paying party, is not a substitute for a contract that removes any doubt about which specific deliverables it actually covers.
A Reform Worth Watching
Kenya’s IP institutional landscape may consolidate in the coming years. The proposed Intellectual Property Bill would merge KECOBO, the Anti-Counterfeit Authority, and the Kenya Industrial Property Institute into a single Intellectual Property Office of Kenya. The Bill has faced repeated delays in Parliament, and businesses should not assume the current three-agency structure, and the separate registration processes that go with it, will necessarily remain unchanged over the medium term. In the meantime, the practical guidance in this article, KECOBO for voluntary registration and evidentiary certificates, and version control and contractual documentation for the underlying proof of authorship, remains the safest approach regardless of how the institutional landscape eventually settles.
For advice on copyright documentation strategy, structuring software ownership and assignment provisions, and choosing between copyright registration and trade secret protection for technical works, consult our intellectual property practice. We advise technology and creative businesses across Kenya from our offices at Nextgen Mall, Nairobi.
