The report starts on the day the work happens
At the end of an internship period, a total number of hours cannot explain what happened. It leaves out tasks, questions and the context that gives the work meaning. Practicora starts with that gap between experiencing a day and later needing to describe it accurately. Useful details are easier to record while they are still available.
The daily journal is the starting point. An entry brings together hours, context and professional notes; the calendar, history, goals and reports build on that information. I want to preserve the thread of a working day and make it useful later, without asking someone to enter everything again when a report is due.
A form has to earn the time it takes
Asking for too much detail immediately can discourage an entry. Asking for too little leaves a journal that is hard to use. Progressive forms and automatic drafts aim for a workable middle ground: start writing, keep unfinished content and return to complete it. An imperfect entry can be more useful than a page that never gets filled in.
For a fictional example, “fixed a form” names a task but says little about the work. Adding the observed problem, the approach and what still needs checking gives the note future value. The product can support that structure without requiring a long essay every day or producing the student’s reflection on their behalf.
Show missing information without deciding what it means
The calendar and history make documented periods and gaps visible. That visibility needs careful wording. A day without an entry does not prove an absence from the internship; it shows that information is missing from the tool. A label can turn incomplete data into an unjustified conclusion, so the language belongs to the design discussion.
Goals and skills add another layer. Connecting a task to a skill helps find examples, but the number of entries does not automatically measure ability. I want the analysis to lead back to the relevant days. Someone can then read the context and decide what the available evidence actually supports.
Build a report from selected evidence
The report studio brings recorded days, tasks and skills together to prepare a summary before export. Selection matters: a useful report is not necessarily the complete journal copied into a new format. It should help explain progress, a significant problem or a decision, with concrete material that remains available for someone to consult.
Finding a note and explaining its significance are different tasks. A tool can gather the material; the student still needs to connect the experience to their goals and recognise its limits. That distinction guides the product. I want to reduce the effort of remembering and selecting while leaving interpretation to the person who experienced the internship.
Make room for each person involved
Practicora uses Next.js, React, TypeScript and Supabase. Alongside student screens, its foundations cover organisations, programmes, cohorts, invitations, roles and placements. Those relationships make permissions part of the workflow design. A student documenting a day and an institution organising placements need different information and different levels of detail; the same navigation will not necessarily suit both.
Those layers stay connected while serving distinct needs. The project is in active development; institutional foundations do not mean it has been adopted by schools. My reference point remains the documented day. If an administrative feature makes that basic action more difficult, its place in the product needs another look.