Technical activity, product scope, benchmark, data protocol and corporate evaluation documentation for R&D products.
In KOSGEB work I made the technical activities, product scope, research approach, benchmark logic and corporate outputs of healthtech and AI-supported products ready to present to the evaluation committee. The work was especially heavy on products like TercüMed AI that involve health data and AI.
In KOSGEB and R&D reports it is not enough to write what the product does. The report has to say what technical problem the product solves, which activities were run, which outputs were produced, and which methods were used. Weak or marketing-flavored or vague report language drops the product's credibility.
I built KOSGEB work around technical activity and decision-support documentation. The technical activity report, R&D activity description, product scope, benchmark analysis, local LLM evaluation framework, data collection protocol, consent form, health data security, KVKK / GDPR perspective and technical evaluation were the main headings.
In the report language I stayed away from overclaim. Completed activities were written as completed. Areas still in productization or integration were written as they actually are.
KOSGEB outputs became more than reports. They turned into decision-support materials that clarify product scope, tighten technical claims, surface the sensitivity of working with health data, and fit the format of committee evaluation.
Technical activity report, TercüMed AI evaluation document, local LLM benchmark report, data collection protocol, consent form, corporate report language, technical scope clarification, and making product decisions reportable.