Recording coaching sessions has never been clearer
- Structured approach to tracking progress across sessions
- Complete audit trail from initial intake to final report
- Templates designed by practitioners who manage real client loads
How a recordkeeping frustration turned into a structured system
The spreadsheet mess
Serhiy Dubovyk started coaching leadership development clients while juggling files across three platforms. Session notes lived in one place, client goals in another, progress tracking nowhere consistent.
Building what we needed
After losing track of a client milestone buried in an email thread, we designed templates specifically for tracking multi-session coaching relationships. Forms that reduced admin time from 18 minutes per client to under 6.
Sharing the system
Other coaches asked how we maintained such detailed records without drowning in paperwork. We refined the templates based on feedback from practitioners managing 15-30 active clients simultaneously.
Continuous refinement
BranDuleks evolved from personal necessity into a resource used by coaches who need defensible documentation without sacrificing time with clients. The templates still reflect real session workflows, not theoretical ideals.
The people maintaining this resource
Serhiy Dubovyk
Spent eight years as an executive coach before building the first version of these templates in frustration.
Still maintains an active coaching practice in Ternopil Oblast, which keeps the documentation requirements grounded in what actually happens during sessions rather than what sounds good in theory.
Tetyana Lysenko
Background in organizational psychology with a focus on measurement frameworks that practitioners will actually use.
Designs the structure behind intake forms and progress tracking sheets, testing every field against the question: will a coach filling this out at 9 PM after a full day understand what it's asking?
Olena Shevchuk
Manages the feedback loop between coaches using the system and the development priorities.
When someone emails asking why a particular field exists or how to adapt a template for group coaching, Olena either provides the context or flags the question as a sign the design needs reconsideration.
What guides how we build this system
Usability over features
A form that takes 4 minutes to complete beats a comprehensive template that coaches abandon after the second client.
Realistic time budgets
Documentation requirements assume you're managing 20+ active clients, not spending your week on administrative perfection.
Audit trail clarity
Every template creates a defensible record of what was discussed, when, and what actions followed.
Feedback integration
When coaches report a workflow issue, we investigate within 48 hours and update templates based on confirmed patterns.
No vendor lock-in
Templates export to standard formats. Your data remains accessible regardless of whether you continue using this system.
Regional accessibility
System designed to function reliably across Ukraine's varying internet infrastructure without requiring constant connectivity.
Active practitioners
Avg. minutes per client record
Template variations available
User rating from feedback
How we decide what belongs in the system
Every field in a template exists because its absence created a documentation gap in real practice. We don't add complexity for theoretical completeness.
When testing a new form design, we run it through a simulation of 8 consecutive client sessions in one day. If the documentation burden feels excessive by client 6, we simplify before release.
Template updates follow a quarterly review cycle based on aggregated feedback patterns. Individual feature requests get logged, but changes happen only when multiple practitioners report similar workflow friction.
Development priorities balance three factors: time savings for high-volume coaches, audit trail defensibility for regulatory review, and compatibility with existing practitioner workflows that can't be completely restructured.