The judging invitation was not the whole record

My EB-1A petition included two judging roles.

I judged the Soyoye Pitch Competition at King's College London in February 2018. I also judged the pitch session at UCL HackMed on February 23, 2020.

At first, each role looked like one line on a resume:

**Judge, event, date.**

That line was accurate. It was also incomplete.

An invitation could show that an organizer asked me to judge. It could not explain the whole event, show what I evaluated, and connect the role to my field at the same time.

The judging section became easier to draft when I stopped treating the title as the evidence and reconstructed the sequence around it.

The record started with why I was invited

For each role, the invitation was useful because it answered a question that the event page could not:

Why did the organizer ask me?

The letter connected the selection to work the inviter knew.

For the King's College London competition, the inviter described my work with Founders of the Future and why that experience was relevant to evaluating young entrepreneurs.

For UCL HackMed, the inviter connected the request to my experience supporting entrepreneurial talent and evaluating competitions.

Those details mattered more than the word **judge**.

The title named the role. The reason for selection connected the role to the career record.

Without that bridge, the judging entries could have looked like two isolated events that happened to appear in the right section of the petition.

The event source established the setting

The inviter's letter had direct knowledge of the invitation and my role.

It was not the only source I used.

For the Soyoye Pitch Competition, the record also included a King's College London page about the 2018 technology innovation scholarships and the competition's winners.

For UCL HackMed, it included a University College London page describing the 2020 event.

Those public sources helped establish the setting around the judging work:

• the institution connected to the event
• the event's purpose
• the date or edition
• the participants or projects being evaluated
• the broader program in which the judging took place

This was a different evidence job.

The public page did not have to explain every detail of why I was invited. The letter did not have to replace the public event record.

Each source could stay inside its own boundary.

Participation needed verbs, not just a title

The word **judge** is a label.

The record became more specific when it described what the label meant in practice.

At the King's College London competition, the judging involved evaluating entrepreneurial projects across factors that included innovation, feasibility, business models, and presentation.

At UCL HackMed, I evaluated pitches for innovation, practicality, and potential impact.

Those verbs made the activity visible:

• reviewed
• evaluated
• assessed
• compared

That was more useful than repeating that I had served as a judge.

A reader could see what kind of work was placed in front of me and what I was asked to do with it.

The section no longer depended on the title carrying an undefined amount of meaning.

The field connection kept the roles from floating

My field in the petition was community building in technology and entrepreneurship.

The two judging roles were not identical.

One involved an entrepreneurship competition at King's College London. The other involved medical technology projects at UCL HackMed.

The field connection did not come from pretending the events were the same.

It came from the work I was asked to evaluate and the experience that led the organizers to select me.

The petition could explain that relationship directly:

1. My prior work involved identifying and supporting entrepreneurs.
2. The organizers asked me to evaluate entrepreneurial or technology projects.
3. The judging activity used experience connected to the field described in the petition.

That sequence was stronger than attaching a broad field label to the event after the fact.

It also gave me a test. If I could not explain why a judging role belonged in the same field as the rest of the case, the title alone would not solve the problem.

Prestige did not replace the sequence

King's College London and University College London gave the events recognizable institutional context.

That context helped the reader understand where the roles occurred.

It did not answer the other questions.

A university name could not show why I was selected.

An event page could not automatically show what I personally evaluated.

An invitation could not make the participation details unnecessary.

This kept the section from becoming a list of impressive nouns.

The institutions, events, dates, selection reasons, and judging activity had to connect in a readable order.

Prestige was part of the setting.

The sequence was the record.

Build the judging record in three passes

If you are organizing a judging role, start with three short notes before writing the paragraph.

Under **Selection**, record:

1. Who invited you.
2. Why they selected you.
3. Which source can verify that reason.

Under **Setting**, record:

1. The event and institution.
2. The date or edition.
3. What the event asked participants to produce or present.

Under **Participation**, record:

1. What you evaluated.
2. Which criteria or questions guided the evaluation.
3. Which source confirms that you performed the role.

Then add one field-connection sentence.

Do not start by writing that the event was prestigious. Start with the facts that make the judging work traceable.

That is what my resume line could not do.

The invitation opened the record.

The event source established the setting.

The participation details showed the work.

Only when those pieces were visible did the title **judge** become useful.