Evaluation Panels and Scoring
Selecting a cohort is the decision your centre is judged on. This page covers how to put people on a panel and the permission that lets them score. It also shows what a panel member sees, how the scores are worked out and listed, and how to send a shortlist to the committee.
What you will learn
- What must be true before someone can be assigned to a panel, and before they can score
- How to assign evaluators to a whole program or to one batch
- What a panel member sees and how scoring works
- How the total, the average and the score % are worked out
- How to send a shortlist to the Evaluation committee, and what each panel member then sees
- How panel groups split who scores which applications, and how scoring days set when
- How to carry groups into the next intake, or start new ones
- Who can see the scores, and who can give them
- How to review an application and ask for changes or documents
Why panels are worth setting up properly#
Without a panel, selection comes down to whoever read the application and how they felt that day. With one, several people score the same application against the same criteria. The result is a number you can defend - to a founder who asks why they were not selected, and to a funder who asks how you chose.
Good to know
The scoring sheet itself - the questions, their answers and how much each counts - is built when you create or edit the program. See Creating a Program. This page is about who does the scoring and what happens when they do.
Before you can assign anyone#
Two things must be in place before someone appears in the assign list, and a third before they can actually score. If either of the first two is missing, the dialog simply shows an empty list with no explanation.
- 1
The person must exist as a portal user
External evaluators are not a separate kind of account. Add them in Users & Permissions like anyone else. Give them a deliberately narrow role - an outside investor does not need to see your funding figures.
Tip: A new person counts toward your plan's staff limit, like any colleague. Making someone already on your team a panel member adds nothing.
- 2
Their Panel Member switch must be on
On their user profile there is a Panel Member toggle, separate from their role. That switch is what makes someone appear in the list of people you can assign to a panel. Without it, they are invisible here no matter what their role says.
Tip: This is the single most common reason the assign list comes up empty. If you cannot find a colleague, go to Users & Permissions, open them, and check that switch.
- 3
A role with Evaluation - or no role at all
Seeing scores comes with the programme, but giving them is the Evaluation permission (it used to be called Panel). Tick View and Create on the Evaluation row of their role: View opens the scoring screen and Create submits the scores. Without it the Evaluate button shows a padlock for them, with the reason.
- A panel member may have no role (14 Nov 2026). Their seat then lets them score the programme they sit on: they land on My evaluations, see only that and their programmes, and every other page takes them back there.
- Admins can score any application at the Evaluation committee. Colleagues working on the programme (its People on this programme) can score its applications without a panel seat, as long as their role has Evaluation.
Assigning people to a panel#
Open the program, stay on the Program Info tab, and scroll to the bottom. Panel Members is the last section on that screen, with a count of how many are currently assigned.
- 1
Press Assign Panel Members
Search by name or email. Only people with the Panel Member switch enabled will appear.
An empty list means nobody has the Panel Member switch turned on yet - not that something is broken. - 2
Decide the scope: whole program or one batch
The 'Assign to Batch' dropdown defaults to 'All batches (program-level)', which means this person evaluates for every intake of this program, now and in future. Choose a specific batch instead to limit them to that one cohort.
- Program-level suits your own staff, who will be involved every year.
- Batch-level suits a guest evaluator brought in for one intake - a sector specialist for a themed cohort, say.
- Batch-level decides which applications they are asked to score, and can score. It does not hide the rest of the programme: any seat, programme-level or batch-level, lets them read the programme's page, registrations, evaluations and scores, read-only.
Tip: Default to batch-level for anyone outside your organisation, so they are only asked to score the intake they were brought in for - and remember that a seat lets them read the whole programme.
Not seeing Panel Members?
The Panel Members section needs Evaluation View on your role; without it the section only says to ask your admin. If your plan does not include Evaluation, it says panel members can't be assigned - your team then moves applications to Evaluated from each registration once it has assessed them. Assign and Remove from a programme need Programs Edit on that programme; admins always can.
What a panel member sees when they score#
A panel member signs into the same portal, and with a narrow role their menu is short; with no role it holds only My evaluations, their programmes and Notifications. My evaluations lists what waits for their score. Evaluate opens the application and your scoring sheet side by side.
- Each question shows what it is worth ('up to 10 pts') and each answer its real points. Your guidance for the panel sits under the question.
- With tracks, the screen names the application's track and shows only that track's questions and the shared ones.
- Every question has its own comment box, so a scorer can explain a low mark rather than leaving you guessing.
- A running total sits at the bottom against the best possible - 'Total: 42 of 60'.
- A General Remarks box captures an overall view of the application.
- Submit stays disabled until every question has been answered - nobody can submit half a scorecard.
- If they cannot score an application - it is not at the Evaluation committee, they are not on its panel, or their role can only view evaluations - the screen says which.
- Once they have scored it, they see their answers and Edit my evaluation. They can change it while the application is still being evaluated; the score is worked out again and the change goes on the application's history.
Tip
Guidance written on the question - '1-2: needs work, 3: meets the bar, 4-5: well above it' - is what keeps two evaluators marking alike.
My evaluations#
Each person's own list of what waits for their score. An application leaves it when they score it, never when someone else does, or when it moves past evaluation. Seated on, at the top, says which programmes and batches they sit on.
- Waiting for me - at the Evaluation committee (or Evaluated, in a batch that uses it) and not yet scored by you.
- Scored by me - every application you have scored; See my evaluation opens it to read or change.
- A batch seat lists only that batch's applications; a whole-programme seat lists every batch of that programme, and no other.
- When staff send applications to the committee, each seated panel member gets one notice: '10 applications in KIET Incubation 2026 are waiting for you.'
- With panel groups, you see your groups' applications and anything sent to everyone. Each card names its group, and Show narrows the list to one group.
- With scoring days, the first tab is Today: what you can score today, under one heading per session. Upcoming shows later dates and counts, never startup names.
How the total score is worked out#
Each question adds the points of the chosen answer: its score times how much the question counts. The points added together are that panel member's total for the application.
- Average - the mean of every panel member's total, shown over the best total: '42.5 / 60'.
- Score % - each evaluation over its own best total, then the mean. It is fair across tracks with different questions, and across a question added half-way.
- A score from staff without a panel seat counts in both, and shows apart in Evaluated by ('6 of 8 +1 staff').
| Question | Answer chosen | Score | Counts | Points |
|---|---|---|---|---|
| Strength of founding team | Exceptional | 5 | ×2 | 10 |
| Size of the market | Adequate | 3 | ×2 | 6 |
| Technical feasibility | Strong | 4 | ×1 | 4 |
| Social impact | Limited | 1 | ×1 | 1 |
| Total | 21 of 28 |
Careful
Counts is not a percentage and nothing has to add up to 100. To make one question matter twice as much as another, set it to ×2.
Scores in the Registrations list#
From the Evaluation committee tab on, the Registrations list shows the scores and puts the best first. Founders never see any of it.
- Order switches between Best score first and Newest first.
- The same numbers are in Export CSV, in the Registrations sheet (Score %, Evaluated by) and on the application's own page.
| Column | What it shows |
|---|---|
| Evaluated by | '6 of 8' - panel members seated for its batch who have scored it, of all seated. Staff without a seat show as '+1 staff'. |
| Average | The mean of the panel's totals over the best total of its track's questions - '42.5 / 60'. |
| Score % | Each evaluation over its own best total, averaged. 'so far' until every seated member has scored. |
| Rank | Score % high to low; a tie goes to more evaluations, then the earlier submission. With a track filter, rank is within the track. |
Sending a shortlist to the Evaluation committee#
Tick the applications on the Registrations list and press the first button in the bar. It names where they go - Send to Evaluation committee. The panel then sees those applications and nothing else.
- Each application moves one stage on its own batch's stages, never past the one before Finalist.
- Each seated panel member is told once for the whole send, not once per application.
- Pressing twice - or a colleague sending at the same time - moves nothing further: the window reports 'It moved meanwhile'.
- Make finalists, from the evaluation stages on, takes an amount for each, capped by the startup's track and batch. Reject… asks for one reason every founder reads.
- Applications you didn't tick stay where they are.
- When the programme has panel groups, the window asks who scores them and, optionally, on which days. Both are explained in the next two sections.
Panel groups: some applications to one group, others to another#
A panel group is a named set of people from the programme's panel, such as Committee A. An application sent to a group is scored by that group's members only. Programmes without groups work exactly as before.
- Make one with New group on Program Info: a name, its members, and optionally a default track. Members are picked from people already seated on the programme.
- One person can be in several groups. They see every group's applications in one list, and get one notice per send.
- A default track means sending 'by each one's track' gives that track's applications to the group. A track is the default of one open group at most.
- In the send window, choose By each one's track, Everyone on the panel, or one group. Without tracks, you pick the group for each send.
- Evaluated by counts the group's own members: '3 of 4'. Rank within one group by choosing it under Panel on the Registrations list.
- Change panel group, on the registration page or the list's bulk bar, moves an application to another group until its first score.
- Founders never see groups. The trail line 'Panel: Committee A' is for your team only.
Tip
Groups never seat anyone. Someone in a group who isn't seated for an application's batch won't see it, and the send window names them with Seat them on this batch.
Scoring days: when the panel scores#
In the same send window you can set Scoring days, for example 20 to 21 Nov. The chosen panel can open and score those applications on those days only, in India time.
- Before the first day, panel members see the date and how many, not the startups. Opening one says when it opens.
- On the days, they read, score, and can change their own score.
- After the last day, they can read but not score. The page says to ask the programme team to extend the days.
- Admins and the programme's managers are not held to the days.
- Program Info lists each Evaluation session: who scores, the days, how many are fully scored, and its state.
- Change days or Extend works before, during or after the days. Only people who haven't finished are told, once. The change is kept with your name.
- Moving an application on while its days are open is allowed. The window first says how many have scored it.
Good to know
No reminder is sent on the morning of the day. The notice sent when you send, or change the days, already names them.
The next intake: keep your groups, or start new ones#
Groups belong to the programme, not to a batch, so a new batch uses them as they are. You only act when the people change.
- A closed group can't be chosen for new sends. Its applications, members and scores stay, and it can be reopened.
- Create Batch shows Panel for this batch. Members seated on earlier batches only are named, with Seat them on this batch too.
| When | What to do |
|---|---|
| Same people | Nothing. The groups and their default tracks carry over. |
| A few people change, and the last batch is finished | Open the group and press Change. Past scores stay. |
| A few change while the last batch is still being scored | Press Duplicate, edit the copy, and tick Close. The old group finishes its own applications. |
| An entirely new panel | Seat the new people, make new groups, and close the old ones. |
Reviewing an application yourself#
Before an application reaches your panel, someone on your team usually reads it. Open any application from the Registrations tab and you get the whole picture on one screen. Sector, stage, founding year and location sit under the name; funding requested and its purpose are called out at the top.
- Change status, top right, is the one place to move one application: the next stage (for example Move to Shortlisting), Move back to an earlier stage, Reject application, or Reopen application once it was rejected. Each opens a window to confirm.
- To ask the startup for changes or documents, open Changes & Requests and press New Request.
- 'At Other Incubators', under Program History & Funding, is quietly useful - it tells you whether this startup is applying everywhere or has chosen you deliberately.
| Section | What it holds |
|---|---|
| Overview | Funding requested and its purpose, funding received from you, its programmes and other applications here, and team size. Program History & Funding adds one short line for each programme at another incubator: the programme, joined or applied, and any funding. |
| Company profile | The startup's company profile, as it was submitted with this application. |
| Files & Docs | Everything an onboarded startup has sent you - pitch deck, certificates, financials. It appears once the startup is onboarded; before that, ask for things under Changes & Requests. |
| Evaluations | Every evaluator's answers and scores for this application once they come in, and the summary. |
| Changes & Requests | The history of what you have asked for and what they sent back. |
Asking for changes before you score#
If an application is not good enough to judge fairly, send it back rather than marking it down. Under Changes & Requests, New Request lets you raise several specific points in one go rather than one vague note.
- Each request has a title and a description, and is tagged with its type - a general change, or a request tied to a specific field or file.
- 'Add Another Request' stacks up more; the counter on the right tracks how many you have written.
- The send button tells you exactly what you are about to do: 'Send 3 Change Requests'.
- The application keeps its phase and shows as awaiting the startup until they respond; their answer then waits for your review.
Tip
Raise every point in one round. Three separate requests over three days reads as disorganised to a founder, and each round adds days to your own timeline.
Common questions#
Nobody at your centre has the Panel Member switch turned on. Go to Users & Permissions, open the person you want, and enable Panel Member on their profile. Their role is a separate thing and does not control this.
Yes, and it is common. Add them as a user with a role that has only Evaluation ticked (View and Create), turn on Panel Member, and assign them to a specific batch. They can score what you assign them and read that programme, and nothing else. They count toward your plan's staff limit like any colleague.
Their role does not include Evaluation. Edit their role in Users & Permissions and tick View and Create on the Evaluation row - or, if Evaluation is not on your plan, the programme's Evaluations tab says so and new scores cannot be recorded.
It is now called Evaluation, and it covers scoring applications, the panel members list and the pending evaluations list. Seeing evaluations and scores moved to Programs, so anyone who can see a programme can read its scores without Evaluation. Putting someone on a programme's panel, or taking them off, needs Programs Edit on that programme.
No. Counts is a multiplier, not a percentage: ×2 counts twice as much as ×1. Totals differ between programmes; Score % is what compares applications fairly, even across tracks.
Submit stays disabled until every question has an answer selected. Ask them to scroll back up and look for a question they have skipped.
Anyone who can see the programme: Programs View on their role, View set for them in that programme, or a seat on its panel. The programme's Evaluations tab lists every application waiting for evaluation or through it. Each registration's Evaluations tab shows every evaluator's answers and the summary. Scoring is separate: it needs Evaluation Create on the role and a seat on the programme's panel (or a place among its People on this programme). On a plan without Evaluation, scores already recorded stay visible.
Yes. Admins can score any application at the Evaluation committee. Otherwise you need Evaluation on your role, and either a seat on the programme's panel (Panel Member switched on, then assigned) or a place among the programme's People on this programme. Many centre heads do exactly this.
Program-level means they evaluate every intake of that program, including future ones. Batch-level limits their scoring to a single cohort; either way they can read the whole programme. Use batch-level for guests and program-level for your own staff.
Yes, in as many as you like. They see each group's applications in one list, each named, and score each application once. A send reaching both their groups sends them one notice.
It was sent with scoring days that haven't started. They can see the date only until then. To open it sooner, change the days on Program Info under Evaluation sessions.
Open Evaluation sessions on Program Info and press Extend on that session. Set a new last day; the people who haven't finished are told once and can score again.
Some panel members haven't scored. Evaluated by on the Registrations list says how many have - '5 of 8'. Chase the rest, or move it on once you have enough scores.
