This is the screen you tap at the table. Open a session with venue, stake and buy-in, start the clock, and keep playing. Cash-out, rake, tips and marked hands come later, in the cool-down. The whole interaction is designed so logging never pulls you out of the game.
Venue, stake and buy-in at the table, then start the clock. That is all you need live. Net result, hourly and win rate by stake all build from those few fields, so the fast path still feeds every higher stat.
What you add in the cool-down
Cash-out, rake, tips, travel, notes and marked hands can wait for after the session. The at-the-table flow stays short, so logging never slows the game or makes you the person buried in a spreadsheet.
Finding a session later
Find any session by venue, note or tag, and save the views you use most. The log is searchable from day one, so it works as both a record and the raw material for review.
What you get
→Log the essentials in seconds, finish the detail later.
→Net, hourly and win rate by stake build from the log.
→Search and filter by venue, note or tag.
→Synced across web and Windows desktop.
How this fits the review loop
This feature earns its place only if it makes the next session cleaner. The Overshove loop is deliberately small: log the session, read the number beside the sample, mark the useful hand or leak, then carry one action into study. If a feature cannot support that loop, it stays out of the way.
Judge it with your own data. A strong feature should reduce skipped sessions, make a cost visible, stop a bad stake decision, or give your coach a cleaner packet. Pretty charts are optional; a decision you can defend is the point.
Questions
Will logging slow down my game?
No. The at-the-table step is a few fields and a clock; everything else waits for the cool-down.
Can I log a session from memory later?
Yes. A rough entry with the core fields beats a gap in your sample, so log it as soon as you can.