The Rejection Report
Crossing 4's report-back — what happened when you asked, yes or no, told exactly as straight as it landed
A “no” is data, not a verdict — that’s the line Crossing 4 is built to test, and this is where you find out if you actually believe it once you’re standing in front of the room saying what happened.
In the room#
Report the ask itself first — what you actually said, to whom, and why that moment — then the answer, however it landed. A yes doesn’t excuse you from the report; the room still wants to know what you risked to get it. A no doesn’t need softening either: say what was said, not a version where it stung less than it did.
What gets asked#
The follow-up usually lands on the ask, not the answer: what you’d change about how you asked, whether you’d have pushed back on a no, what you’d have lost by staying quiet instead. See Crossing Participation for how the live report and reflection are marked.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- you report, live, exactly what you asked for and what the answer was
- a yes gets the same honest account as a no — no skipping the ask because it happened to work
- you can name what you'd change about the ask itself, not just the answer you got
Crossing 4 · Week 8 · 28 September 2026
Teaching team
- Dora De Exploré — tutor