Relationship reports
The gathering creates the signal. The report turns it into action.
Attendance is not the outcome. Movement is the outcome. Every BiggerBite program ends with a practical relationship report: who came, who engaged, what mattered, what surfaced in feedback themes and host notes, and what should happen next, with next actions by owner.
A dinner without a record is an expensive evening. A dinner with a record is the start of a program.
Illustrative report module
24
Invited
16
Accepted
14
Attended
11
Survey responses
Feedback themes
Referral handoffs feel slow after the first call
7 of 11 mentions
Wants clearer scheduling contact for urgent cases
5 of 11 mentions
Asked about a smaller session for their team
4 of 11 mentions
Next actions by owner
- Visit three dormant referrersLiaison, Within 2 weeks
- Send care pathway summary to attendeesMarketing, Within 5 days
- Book follow-up call with two guestsPractice lead, Within 10 days
Sample figures for illustration only. Not based on real client data.
What the report includes.
The report is written by a person using data your program produced: invitation and RSVP workflow records, check-in, host notes, and survey collection. It is short enough to be read in one sitting and specific enough to assign work from.
Important note
Report examples on this page are illustrative. They are written to show the structure and are not based on real client data or client results.
- 01
Attendance and RSVP summary
The invitation list next to what actually happened, so nobody has to reconstruct the evening from memory.
- Invited, accepted, declined, no response, and attended
- Walk-ins and late cancellations captured at check-in
- Attendance grouped by company, account, practice, or partner tier
- Invited people who have now declined twice, flagged for a different approach
- 02
Guest feedback and survey themes
Short surveys sent while the conversation is still fresh, then grouped so you read themes instead of raw comments.
- Response rate and who responded
- Repeated topics, ranked by how often they came up
- Direct quotes kept intact where the wording matters
- Questions and requests that need an answer from your team
- 03
Relationship signals
Observations from host notes and check-in that suggest where a relationship stands. These are signals, not scores.
- Who engaged with hosts and who stayed on the edge of the room
- Guests who brought a colleague or asked to be invited again
- Accounts that sent a junior stand-in instead of the decision maker
- Relationships that look dormant across several invitations
- 04
Follow-up opportunities
The specific openings created in the room, written down before they fade.
- Materials, introductions, or answers promised during conversation
- Referral source conversations that should continue
- Sponsor and partner opportunities raised by guests
- Customer feedback that belongs with product, service, or success teams
- 05
Recommended next actions
A short list of what we would do next, written as tasks rather than advice.
- Outreach that should happen in the first week
- Meetings worth scheduling in the first month
- Guests to add to, or remove from, the next invitation list
- Internal fixes that would improve the next gathering
- 06
Ownership and accountability
Each action carries a named owner and a date, because unowned follow-up is the usual point of failure.
- Next actions by owner, with a due date
- A single relationship owner per key guest or account
- Items handed to your CRM so the record lives where your team works
- Open items carried into the next program review
- 07
Next-program recommendations
What the evidence suggests you should host next, and who should be in that room.
- The audience that warrants the next gathering
- The format that fits the goal, from dinner to roundtable to council
- Timing relative to conferences, renewals, or planning cycles
- Whether this should become a recurring program
Why this matters after the room clears.
Most gatherings fail in the week afterward, not in the room. People remember the evening fondly, the notes stay in one person's phone, and the follow-up is left to whoever happens to remember it.
A written record changes the default. Attendance is known, feedback themes are grouped, and every action has an owner and a date. Nothing depends on recall three weeks later.
It also makes the next program better. You know who to invite again, which topics landed, and which relationships need a different kind of room. Reports do not guarantee referrals, revenue, partnerships, clients, or funding. They make follow-up possible.
Where reports fit in a program.
Reporting is part of every service, not an add-on.
One gathering
A single event delivers one report with follow-up recommendations. This is the shape of a Relationship Growth Pilot.
A recurring rhythm
Reports compound across gatherings, so themes and relationship coverage can be compared over time. That is a Connection Operating System.
The invitation and RSVP workflow, check-in, and survey collection behind these reports run on our own software. See the platform, the gathering formats, or how a program runs end to end.
Questions about reporting.
When do we get the report?
Is the report automated?
Does this replace our CRM?
Do you score our relationships?
Can our team see the raw responses?
Get the record, not just the evening.
Tell us the audience and the goal. We'll run the gathering and hand you the report, the themes, and the next actions by owner.