source image : gemini generative image

When lecturers ask BINUS RTT why their Impactful IP claim was not approved, the answer is rarely that the implementation was not real. More often, the documentation did not demonstrate the implementation clearly enough for an independent reviewer to confirm it. The community group used the software, the training module was adopted by an NGO, the design was in production — but the evidence file did not prove it in a form that survives evaluation. That gap between real-world activity and reviewable documentation is where most Impactful IP claims succeed or fail.

Understanding what RTT is actually looking for — and why each requirement exists — is the fastest way to close that gap before the 6 December annual cut-off.

The first condition is foundational and binary: the IP must be officially granted or registered by DJKI in the claim year. For Patents and Industrial Designs, the application must have been registered within the year; full grant is not required, but the DJKI record must exist. For Copyright, the certificate must have been issued. No amount of strong implementation evidence overrides a missing or pending registration. If the certificate has not arrived, the claim cannot be submitted — and waiting until December to check is a common and entirely avoidable source of missed claims.

The second condition is external implementation, and this is where nuance matters most. The implementing party must be external to BINUS: a community group, an industry partner, a government body, an MSME (UMKM), or an alumni organisation. The organisation must have more than ten members. The implementation must be active — the IP is being used or promoted by that party in a meaningful, ongoing way, not merely showcased. A seminar presentation to external guests does not qualify. A community that has integrated your instructional video into their regular training cycle does.

Evidence must allow a reviewer who was not present to understand and verify what happened. For Copyright — the most common IP type and the most relevant for non-STEM lecturers — valid evidence includes: a photograph showing members of the partner organisation using the IP in context (for example, a training session where your module is visible on a projected screen, or a workshop where participants are working with your printed guide); a screenshot of a digital platform, application, or website showing the IP actively deployed; or a verifiable link to an online environment where the implementation is visible. The photograph must show people, not just the IP. A shot of a screen with no visible users does not establish that the implementation reached the required number of members.

For Patents and Simple Patents, the evidentiary standard is similar in format but higher in substance. Implementation typically involves physical or industrial use — a product incorporating the patented invention being manufactured or actively deployed by a partner — and documentation should combine visual evidence with a formal partner letter or MOU that identifies the relationship, its terms, and the implementing organisation’s size and nature. For Industrial Designs, evidence should show the design as implemented in a product actively used or sold by the partner, not merely prototyped or displayed.

The written implementation description is the component that lecturers most consistently underestimate. HKI Apps requires a 25–100 word account of how the IP is utilised. This is not a formality — it is the reviewer’s interpretive guide, and the difference between a passing and a failing submission often comes down to its specificity. “Used in a training workshop” tells a reviewer almost nothing. “A digital financial literacy module (Copyright No. EC00XXXXXXXX) was integrated into a weekly training series for 38 MSME owners in Tangerang, facilitated by Koperasi Usaha Bersama Mandiri, with eight documented weekly sessions from September to November 2025” gives the reviewer everything needed to confirm the claim without additional follow-up.

One timing rule is worth inlining: Impactful IP claims must be submitted within one year after the certificate is issued, but implementation that preceded the certificate by up to one year is still eligible, provided the implementation genuinely occurred. This means a lecturer whose IP was granted in January 2025 but whose community implementation happened in mid-2024 may still qualify — as long as the claim is submitted before the December 2025 cut-off.

The strongest submissions combine a clear photograph with identifiable users, a formal partner letter, a specific written description, and a completed HKI Apps entry before the deadline. RTT consultation is available through the tech transfer portal to review evidence packages before submission. For a complete guide to the Impactful IP process from registration to validated claim, visit the Impactful IP page at BINUS Technology Transfer.

#ImpactfulIP #HKIApps #IPEvidence #RTTReview #BINUS #HKI #DJKI #TechTransferIndonesia