Tracking Mentor Sessions in Accelerator Cohorts

A mentor session that goes well and never gets written down might as well not have happened, at least from the program's point of view. The founder benefits. The two people in the room remember it. Everyone else, the program manager, the next mentor, whoever takes over the cohort mid-program, has nothing.

This is specifically about what to capture after a session ends, not about scheduling it in the first place.

Quick answer

Short answer: log a short, consistent record after every session, who met, when, what was discussed, and what the founder does next. Done right, it takes under two minutes and gives the program a shared record instead of scattered private notes. Overengineer the form and it gets abandoned within a few weeks.

Why session tracking matters more than it seems

It's the only record that survives staff turnover

A program manager who inherits a cohort mid-program, or takes over after someone leaves, needs to reconstruct what's already happened with each founder. Without logged sessions, that reconstruction is a series of guesses.

It feeds every downstream report

Mentor engagement, one of the harder things to measure in a program, is really just a rollup of individual session logs. Techstars sets an expectation that lead mentors meet with a company roughly weekly, with general mentors checking in closer to once a month. Whatever your program's own cadence expectation is, you can only tell if it's being met by looking at the logged record, not by asking mentors informally.

It catches problems before demo day

A founder who's had zero logged sessions in three weeks is a visible flag, if someone's actually looking at the log. Without it, that gap is invisible until it shows up as a missed milestone.

What to actually capture

Keep the fields short enough that a mentor will realistically fill them out after a tiring session.

The essentials

Date, mentor, founder, and a one or two sentence summary of what was discussed. That's the floor. Anything beyond this needs to earn its place, because every extra required field is a reason a busy mentor skips logging altogether.

Worth adding if it doesn't slow things down

A single action item the founder is expected to follow up on. This is the single highest-value addition, since it turns a conversation into something trackable, without requiring a formal write-up.

What to leave out

Detailed transcripts, formal evaluation scores, or anything that takes more than two or three minutes to complete. Programs that ask for too much upfront tend to see logging compliance drop within the first few weeks.

Where the log should live

A shared system that the whole program team can see, not a personal notebook or a mentor's own files. It doesn't need to be sophisticated. A shared spreadsheet works at a small scale. What matters is that it's visible to more than the two people in the room.

Common mistakes

Making the form too long

The moment logging a session takes longer than the mentor is comfortable with, compliance drops. A form that takes thirty seconds gets filled out. A form that takes ten minutes gets skipped after the second week.

Treating logs as evaluation, not documentation

If founders sense session notes are being used to judge them rather than support them, they'll be less candid in the sessions themselves, and mentors will soften what they write down. Frame logging as continuity, not assessment.

Never reviewing the logs

A log nobody reads is just as useless as no log at all. Even a light weekly scan for gaps, founders with no recent entries, is enough to make the practice worth the effort.

How this connects to broader progress tracking

Session logs are one input into a fuller picture of founder progress. If you're building out tracking that also includes curriculum completion and funding milestones, see how to track founder progress across an accelerator program. If you're specifically trying to catch founders who look fine on curriculum but are missing mentor sessions, or the reverse, how to connect coaching and LMS progress covers that specific pattern.

Frequently asked questions

What's the minimum information a mentor session log needs?

Date, mentor, founder, and a short summary of what was discussed. Add a single action item if it doesn't slow the process down. Anything more detailed risks lowering how consistently mentors actually log sessions.

Where should mentor session logs be stored?

Somewhere visible to the whole program team, not a mentor's personal notes. A shared spreadsheet is enough at a small scale. The requirement is visibility, not sophistication.

How often should mentors meet with founders?

There's no universal rule, but a common benchmark from established programs is roughly weekly for a small group of lead mentors, with less frequent, ad hoc sessions for a wider mentor pool.

Should session logs be used to evaluate mentors?

Not directly, and not in a way founders or mentors can sense. Logs work best as a continuity record. Using them primarily for evaluation tends to make both sides less candid in what gets written down.

What happens if mentors stop logging sessions?

It usually means the logging process has become too burdensome. The fix is almost always to simplify the form, not to remind people more often to fill out a long one.

Can session tracking happen without dedicated software?

Yes, at a small scale. A shared spreadsheet with a few required fields works fine for a single cohort. It becomes harder to maintain once a program is coordinating many mentors across multiple simultaneous programs.

About the Author

Samuel Adeyemo is Head of Marketing at AcceleratorApp, where he leads demand generation, outbound, and brand awareness for the company across the accelerator and incubator markets it serves. He writes AcceleratorApp's guides on running structured, data-informed startup programs.

Ready to keep mentor sessions on the record?

Book a demo to see how AcceleratorApp attaches session logs directly to each founder's program record.