Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
How-to guide

How to Create an Evaluation Console in an ERP: Rubrics, Panels and Fair Startup Scores

For incubator managers and programme officers: set up a panel that scores every application on the same rubric, keeps conflicts out, and hands you a shortlist you can defend.

Two panellists at a table reading application folders and placing scoring tokens

Knowing how to create evaluation console scoring properly matters the week an incubation call closes. Two hundred applications arrive, six panellists are available, and the selection committee wants a ranked list by Friday.

Most incubators run this on a shared spreadsheet with one tab per panellist. Weights are typed into a formula, a mentor scores a startup she advised last year, and nobody notices that one panellist marks every team two points lower than the rest.

This guide explains what an evaluation console needs, walks through an illustrative selection round at a Bhubaneswar incubator, and shows how Apragya's incubation app sets one up.

How to create an evaluation console, step by step

An evaluation console is the place where a selection panel scores applications against a fixed rubric. It needs four parts: criteria with weights, a way to assign each application to named panellists, a scoring card per panellist with room for comments, and a rule for combining cards into one score.

The combining rule matters more than it looks. A simple average lets one harsh or generous panellist tilt the list, which is why each application should have at least two or three cards. Conflicts of interest should be declared on the card and the card left out of the average, while staying on record.

Finally, fix when scoring closes. Once the committee has decided, scores should no longer change, or the reasoning behind a selection can quietly shift.

  1. Define the criteria and the weight of each.
  2. Decide how many panellists score each application.
  3. Limit each panellist to the applications assigned to them.
  4. Collect a score and a comment for every criterion.
  5. Record conflicts and exclude those cards from the average.
  6. Rank on the mean weighted score and review borderline cases together.
  7. Close scoring once the application moves past interview.

An example: a Bhubaneswar agritech incubator picks its cohort

Take an illustrative university incubator in Bhubaneswar selecting twelve agritech startups from 140 screened applications. The committee wanted five criteria: problem, team, technology readiness, market and social impact, with team weighted highest.

One application, scored by its panel

Application under evaluation

Passed screening, panel assigned.

  • Panellist one

    Scores five criteria with comments.

  • Panellist two

    Scores the same rubric independently.

  • Panellist three

    Declares a conflict; card left out.

  • Weighted totals

    Each card totalled on the programme weights.

  • Mean score

    Taken over the cards without conflicts.

  • Shortlist position

    Ranked against the other applications.

The conflicted card stays on record but never moves the mean.

Twenty applications had a declared conflict, most of them from mentors who knew the founders. Those cards were kept for the record and excluded from the averages. The committee met with a ranked list, read the comments on the borderline teams, and chose its twelve in one sitting.

Twelve ribboned seedling pots in a row with folders set apart under a paperweight
Twelve teams chosen from a ranked list, with the conflicted cards kept aside rather than counted.

Scoring by spreadsheet, and scoring in a console

Evaluation console

  • Each panellist sees only the applications assigned to them
  • Criteria and weights sit on the programme
  • A declared conflict is recorded and left out of the mean
  • The shortlist sorts itself on the mean weighted score

How to build a startup evaluation rubric in Apragya

Step 1 of 6

Write the criteria

Name each criterion and its weight on the programme, or use your organisation-wide rubric.

  1. Write the criteria: Name each criterion and its weight on the programme, or use your organisation-wide rubric.
  2. Assign panellists: Pick evaluators for each application once it clears screening.
  3. Scope what they see: An evaluator role limited to their own cards shows only assigned applications.
  4. Score with comments: Each panellist rates every criterion and explains the rating.
  5. Record conflicts: A declared conflict is noted on the card and kept out of the average.
  6. Read the ranking: Applications sort on the mean weighted score across submitted cards.

Incubator application scoring: sheet, form tool or console

Online form tools collect scores well but know nothing about the programme, the applicant's history or who has a conflict. A console inside the incubation app scores the same application record that later becomes a cohort member, an award and a set of milestones, so the selection reasoning travels with the startup.

Ways to score applications, compared with Apragya

FeatureSpreadsheet or form toolApragya evaluation console
RubricRebuilt for each callStored on the programme, with a fallback
What a panellist seesUsually everythingOnly assigned applications
ConflictsHandled verballyRecorded and excluded from the mean
RankingPasted togetherSorted on the mean weighted score
Late score changesPossible any timeAccepted only while the application is being evaluated

Checked against public information on 16 September 2026.

What sets Apragya apart as a jury scoring sheet for startups

One startup record

Scores sit on the application that becomes the cohort member.

Scoped evaluators

External jurors see their own queue and nothing else.

Rubric per programme

Each scheme keeps its own criteria and weights.

Audit log

Who scored, and when, is kept against the application.

AI you can add

An agent can summarise panel comments for the committee to read.

Score from anywhere

Panellists can work in a phone browser between sessions.

The console sits between startup applications and cohorts. Selected startups join programmes you set up by following how to create incubation programmes. See the evaluation console feature.

Setting up your first scoring round

  1. Agree four to six criteria and their weights with the committee.
  2. Enter them on the programme before the call opens.
  3. Create an evaluator role scoped to assigned cards.
  4. Assign two or three panellists to each screened application.
  5. Ask for conflicts before scoring starts, not after.

A rubric written before the first application arrives is the easiest way to show the selection was fair.

What it costs to start

INR 7,999
Pro, a month
Up to 25 users, with Incubation Management and every enterprise app
5,000
AI Credits a month
Included on Pro
Free
Up to 3 users
CRM and HR, to try the platform first

Creating an evaluation console, answered

Can different programmes use different criteria?
Yes. Criteria live on the programme. When a programme has none, the organisation-wide rubric is used.
How is an application's score worked out?
Each card gets a weighted total, and the application takes the mean of the submitted cards that have no declared conflict.
Can external jurors take part without seeing other applications?
Yes. Give them an evaluator role scoped to their own cards, and they see only what is assigned to them.
Can a panellist change a score after selection?
No. Scores are accepted while the application is under evaluation, shortlisted or at interview.
What does it cost to start?
Incubation Management comes with the Pro plan, INR 7,999 a month for up to 25 users, which includes every enterprise app, 5,000 AI Credits a month, single sign-on and audit logs. The free plan covers up to 3 users with CRM, HR and Vendor Onboarding if you want to try the platform first.

Run your next selection on one rubric

Write the criteria, assign the panel and let the shortlist rank itself.