Incubation Portal

Running a Program Day to Day

Once your program exists and applications start arriving, everything happens on one screen with six tabs. This page explains what each tab is for and how to move an application from arrived to onboarded. It also covers who on your team can do what inside a programme, and the setup step without which you cannot create a batch at all.

15 min readWritten for: Program Managers, Incubation Managers

What you will learn

  • What each of the six tabs on a program is for
  • How to open an intake with a batch - and what blocks it
  • When a new or reopened batch counts toward your plan's programme limit
  • What the application phases mean
  • How to ask a startup for changes or extra documents
  • Who can do what inside a programme
  • How to collect forms and files from a whole cohort at once

The six tabs#

Open any program from All Programs and you land on a screen with six tabs across the top. Everything about that program lives here - you rarely need to go anywhere else once a cohort is running.

Program Info. The counts next to Questions tell you how many evaluation and application questions the program has.
TabWhat it is forHow often you will use it
Program InfoThe public description, objective, benefits, eligibility rules and question counts. There is a Preview button to see it as an applicant would.Occasionally - mostly to check or correct wording.
BatchesYour intakes. Each batch has its own dates, slot limit and funding. Without an open batch, nobody can apply.Once per intake.
StartupsThe startups accepted into this program.Weekly.
RegistrationsEvery application received, with its status. This is where most of your work happens.Daily while a batch is open.
EvaluationsEvery application waiting for evaluation, and every one your panel has scored, with the scores.During shortlisting.
Data CollectionRequests for forms and files from startups already in the program.Monthly or quarterly reporting.

Opening an intake with a batch#

A program is the scheme; a batch is one intake of it. Applications attach to a batch, not to the program, which is why nothing can arrive until you have created one and its dates have opened.

The Batches tab. Search, filter by status, and use a batch's Change status menu to open or close an intake.
  1. 1

    Press Create Batch and name the intake

    Name it something that will still make sense in three years - 'Cohort 1, Jan–Jun 2026' rather than 'Batch A'.

    • Batch Code is a short reference like SMA-2026-C01. It appears under the batch name in lists. Each code is used once across your whole incubator, in any programme - capitals and spaces do not make a new one - and the dialog says straight away if the one you type is taken, and by which batch.
    • Application Opens and Application Closes control when the apply button appears to startups.
    • Max Slots caps how many you will take. Leave it blank for unlimited.
    Creating a batch. The line under Batch Code says when it can still be changed.

    Tip: Decide your batch code format before your first intake and stick to it. It is fixed once applications open, and a consistent format makes your records far easier to read later.

  2. 2

    Fill in the funding details

    Every batch must have funding attached - this is not optional. You set the amount allocated to this batch and the most one onboarded startup can get. Then choose the funding type and say which of your funding sources the money comes from, and how much from each.

    • Funding types: Grant, Equity, Debt, or Mixed.
    • Amounts are in your incubator's currency, shown beside the amount. Change it in Settings.
    • Most one onboarded startup can get is required. Founders see only this figure, never the batch's total. They can ask for up to it, and onboarding approves up to it, within what the batch has left.
    • When every open track of the programme sets its own limit, the batch's is optional; when both are set, the lower one wins.
    • On the Batches tab, a batch with that limit shows 'Up to' and the amount, each, under its total.
    • Funding Sources is a list of the sources you have already set up, with a box to say how much this batch draws from each.
    Tick the sources this batch draws from; each shows what it still has. Test source names are blurred here.

Set up your funding sources first

You cannot create a batch until at least one funding source exists, because every batch needs funding and the funding must come from somewhere. If the Funding Sources box says 'No funding sources found' and the Create Batch button is greyed out, that is why. Go to Funding, add your source - a government grant, your own corpus, a CSR partner - and come back. This catches almost everyone the first time.

Good to know

Batches move through Draft, Upcoming, Open, Closed, Under Evaluation, Completed and Archived. Each row's Change status menu lists only the moves open to that batch, in plain words; picking one asks you to confirm, because opening a batch tells founders. The same menu has Edit batch, Graduate cohort (once it is completed) and Delete (while it is a draft). Use it rather than editing dates when you simply want to stop accepting applications. A batch whose closing date has passed can't be opened: move the closing date later first. A batch moved to Under Evaluation by mistake can go Back to Closed. Archived puts a finished batch away: it can no longer be edited, and the Batches tab hides it unless you choose Every status.

A new batch can count toward your plan

Your plan may limit how many programmes you run at once. A programme counts while it is new with no batch yet, or while any batch is Draft, Upcoming, Open or Under Evaluation. Once every batch is Closed, Completed or Archived, it stops counting, like a programme imported from your past records. Creating a batch on such a programme, or moving a Closed batch back to Open, makes it count again. At the limit, Create Batch and that move are locked with the reason. Below it, the Create New Batch and Change Batch Status dialogs warn you first - for example: 'This programme isn't running now, so it doesn't count toward your plan. A new batch runs it again: you will have 4 programmes of 5 on your Silver plan.' Moving a Closed batch on to Under Evaluation, or completing it, is never locked: that finishes an intake that has already happened.

Working through applications#

The Registrations tab is where you will spend most of your time. It shows every application with its current status. The line under the heading counts the whole program - every batch - and each status filter carries the colour its applications show, so the list explains itself.

The counts under Applications cover every batch - how many applications, how many onboarded, how many rejected. Export CSV gives you the lot as a spreadsheet; Sheet shows them as one. Startup emails are blurred here.
  • Filter tabs across the middle jump straight to one stage - New application, Shortlisting, Evaluation committee and so on. Only the stages your batches use are shown. The Waiting on menu narrows the list to applications waiting on the startup, on you, or on nobody.
  • Search by startup name, and filter by date or by batch if you are running more than one intake. With tracks, a Track filter and a Track column appear.
  • Tick several applications to act on them together: send them on (the button names the next stage), make them finalists, reject them, ask for documents or collect data.
  • From the Evaluation committee tab on, the list shows Evaluated by, Average, Score % and Rank - see Evaluation Panels and Scoring.
  • Export CSV is the quickest way to answer a funder who wants the whole list.
  • Sheet, next to Export CSV, shows the same applications as a spreadsheet - see The Registrations sheet below.

The Registrations sheet#

Switch the Registrations tab from List to Sheet to see this programme's applications one per row. Each row shows the startup, programme, batch and status, who the next step is waiting on, what the startup still owes, and when it was submitted and last changed.

One row per application. Waiting on and Still owed come from the requests themselves, so they are never out of date.
  • Keep an internal note, a follow-up date and who is handling it beside each application. Founders never see them.
  • Add columns of your own for anything else your team tracks - interview done, shortlisted, a score from an outside round.
  • Status is not typed into a cell. Clicking it explains why and opens the application, where the change is made and the startup is told.
  • Tabs are saved views, such as Waiting on your team or Finalists, and every programme's sheet shares them.
  • Export turns the tabs you choose into an Excel workbook of this programme's applications.
  • Tick applications to move them together. Next phase moves each one stage on its own batch's stages, never past the one before Finalist. Reject asks for one reason that every founder reads. Onboard takes an amount for each, capped as for one application - no more than the startup asked for, or the most one startup can get from the batch - with the batch's money used row by row. The dialog first says how many move and which cannot, and why.

Good to know

An exported Registrations sheet is for reading. Changes made in the file do not come back by upload - keep notes and your own columns in the sheet itself.

The Startups sheet, and every registration at once#

A programme's Startups tab opens on a sheet of every startup with a place in the programme: active, completed and offboarded. Its money comes first: Approved, Paid, Remaining, Last paid and the funding sources it was paid from. Above it, the programme's funding: what was allocated to it, what has been paid, what is in progress and what is not yet paid out.

  • Paid is the completed payments recorded to the startup's place, the same number as its Funding tab. Remaining shows only where an amount was approved.
  • A startup in two batches of the programme is one row adding both up; open it with the '2 places' button to see each batch's own dates and money.
  • Its tabs - All, Active, Completed & offboarded, Funding - are shared by every programme's Startups sheet. A startup removed from the programme is left out of them; filter In the programme to Removed to see it.
  • List, next to Sheet, is the table it always was: every place with its batch and founder, 25 a page. Its Export to Excel downloads every startup in the programme; with Audit Reports, Export in Audit Center takes its place.
  • Export on this sheet can give a startup in two batches a line for each - its own batch, standing and money on each line - with One line per place.
  • Asking the startups for a field from this sheet puts the request on their application to this programme, or on the startup itself when it has none here. So it counts as still owed on the registration, and only this programme's team and the startup's own page see it.
  • Programs > All registrations lists every application to every programme, as a list you can search and filter, or as the Registrations sheet.

Who can do what inside a programme#

Everything inside a programme is one permission, Programs. Anyone whose role has Programs View sees every programme's page, its batches, its registrations and every evaluation and score; opening a startup from a programme shows that startup's record in that programme. Create, Edit and Delete add the work below. Creating a new programme is separate: the Create new programs switch on the role, which opens only the Create Program wizard.

  • Someone assigned to a programme does what that programme's own access says - set on their page under Program Assignment, or by an admin under Program Info > People on this programme. It starts from their role and can give more or less there. With Programs Create they create batches in that programme. With Edit they edit its details, move applications on and ask for documents and changes. With View there, it shows under Programs in the menu, every evaluation and score in it can be read, and its startups' pages open within it, even without Programs on their role.
  • Creating a new programme, merging two, and recording money stay with the roles that have them, whatever is set for one programme.
  • Scoring is not part of Programs. It needs Evaluation on the role and a seat on the programme's panel - see Evaluation Panels and Scoring.
  • Changing a startup's cells in a programme's sheet needs Startups & Sheets Edit.
  • A button you cannot use is shown with a padlock rather than hidden; hover over it, or tap it, to see why.
Programs tickWhat it lets someone do in a programme
ViewSee the Programs list, a programme's page and info, its batches, its registrations (All registrations too) and every evaluation and score.
CreateCreate a batch; add startups to a programme; ask or remind startups from a sheet; data collection.
EditEdit details, scheme and evaluation questions; edit, open or close a batch; graduate a cohort; move a phase; ask for changes or documents; review answers; seat or remove panel members.
DeleteDelete a batch or an evaluation question; remove a startup; merge a duplicate programme.
The same chart is in the role editor, under What each Programs tick opens. Admins can do everything.

What the stages mean#

An application moves through the stages its batch uses, one at a time, and can be rejected from any of them. Every incubator sees the same names. A batch can skip Shortlisting, Evaluation committee, Evaluated or Verified; New application and Finalist are always used.

A live cohort. Each row shows the startup, its phase, what it still owes, when it was submitted and when it last changed.
  • Leaving the evaluation stage needs at least one score, on a plan that includes Evaluation.
  • Applicants see their stage is set per batch (new batches copy the programme's). Switched off, founders read 'Application received' until they are a Finalist or not selected. The status window says when the startup won't be told.
  • With tracks, an application's page shows its track and Move to another track - until the first score. Its answers stay, and the founder is told unless the batch hides stages.
StageWhat it meansWhat you do next
New applicationJust arrived. Nobody has looked at it.Read it and move it to Shortlisting.
ShortlistingYour team has read it and it is worth progressing.Send the best to the Evaluation committee.
Evaluation committeeWith your panel for scoring. Each panel member sees it on My evaluations.Chase panel members if it stalls.
EvaluatedScored. Used only by batches that keep this stage; the first score moves it here.Check their documents and decide.
VerifiedDocuments checked and accepted.Make them a Finalist.
FinalistAccepted into the program. They now appear under Startups.Nothing - they are in.
RejectedNot accepted - possible from any stage.Nothing. The record stays, and a rejection made by mistake can be reopened.
RemovedTaken out of the program after joining.Nothing.

Tip

If applications are piling up at one stage, that is usually a person, not a process. Evaluation committee stuck for two weeks means panel members have not scored - Evaluated by says how many have.

Your own selection pipeline#

A batch can use the standard stages above, or a pipeline of your own: stages you name, each doing what its activities say. New application is always first and Onboarded always last; everything between is yours - for example Round 1 selection, Review startups (a video call and the evaluation committee), Round 2 selection, Finalist. Choose it in the batch window under Selection pipeline, or on the programme so its new batches start with it. Founders read your stage names when the batch shows them their stage, with a message you can write per stage.

  • Each stage also counts as one of the standard stages, so counts, reports, places and funding keep working. 'Show what each stage is kept as' in the builder shows which.
  • A batch can switch between standard stages and its own pipeline only while all its applications are at New application.
  • You can rename a stage any time. A stage that holds applications - or has scores - can't be removed or moved, and can't gain or lose the evaluation committee: move the applications first.
  • Save a pipeline you like with 'Save as a pipeline' and start other batches from it.
  • Make one saved pipeline your default under Profile > Settings > Default selection pipeline (admins). Every new program starts with it - Create Program shows it on the selection step, marked (default) under Start from - and a program or batch can still change its own. Existing programs are not changed.
  • Registrations show one tab per stage for a batch with its own pipeline. Moving back needs a reason the startup sees; Not selected keeps the stage, so Reopen puts it back where it was.
  • A committee stage can have its own questions: in Edit Program, Evaluation Questions, open a question and tick the stage under Asked in (it lists the committee stages of the programme's batches). A stage with its own set asks only those; the card says where each question is asked.
ActivityWhat it does at a stage
ShortlistingYour team reads and picks who goes on. Applications move on one stage at a time.
Evaluation committeeYour panel scores here. Scores are kept per stage, so a startup can be scored again at a later committee stage. Moving on needs at least one score in this stage.
Video callCall days with the startups at this stage, one at a time. It needs Selection calls on your plan, and the EcoSync team switches it on for your organisation; until then it is shown greyed out, saying which is missing.
LabelsNames your platform admin adds, such as Site visit. They mark what happens; they don't change any rule.

Selection calls#

On a stage with the Video call activity, Program Info shows Selection calls. Plan a call day: the day, the window and the time per startup - the window shows how many fit, and the rest go to the next day you add. Each startup gets a time, a notice and an email with a calendar invite, and a reminder on the morning of the call. On the day, open the call room and start it.

  • Startups wait in a waiting room on their application page. You see who is here. Let in one at a time: each turn gets its own private room, and the panel waits in its own room between turns - your page follows by itself.
  • Finish · let in next ends a turn and starts the next. +5 min gives the turn longer and moves the rest of the day's times.
  • Not here yet: Later today moves the startup to the end of the day; No-show tells it, and it can be given a new day.
  • Panel members see a Live now card on My evaluations: join the call, or score without joining. The score form sits beside the video, for the startup in the call.
  • Admins and people who can edit the programme run the call room. Calls are not recorded.

Tip

If two of you press Let in at once, only one moves the day on - the other sees 'Already moved on'.

Asking a startup for something#

Two things you will do constantly, both from an application's own screen. Both notify the startup. Neither changes the application's phase: what they owe shows beside it - 'Awaiting startup · 1 doc' - until they answer, and their answer then waits for your review. You can still move the application on in the meantime; nothing is blocked by an open request.

Request changes

For when an answer is thin, wrong or contradicts something else. Give it a short title and describe what you need. The application shows as awaiting the startup until they respond.

Request documents

For when you need a file they did not submit - incorporation certificate, financials, a signed undertaking. Name the document and describe the requirements. It shows as awaiting the startup until they upload, then as waiting on you until you approve the file or ask for another.

Tip

Be specific in the description box. 'Please clarify' generates another round trip; 'Your revenue figure for FY24 does not match the figure in your pitch deck - which is correct?' gets you an answer first time.

Tracking evaluation progress#

The Evaluations tab lists every application in this programme that is waiting for evaluation or has been through it, whoever scored it. Two counts sit at the top - Waiting for evaluation and Evaluated - with Waiting and Evaluated buttons to switch between the two lists. Anyone who can see the programme can see this tab and every score in it.

Evaluated is open: each application with how many evaluations it has, and Open to read them.
  • 'Waiting' is what your panel still owes you. An application appears here once it is sent to the Evaluation committee. Each panel member's own list is My evaluations.
  • 'Evaluated' is what has come back with scores. Each row shows how many evaluations it has.
  • Open takes you to that application's own Evaluations tab, with every evaluator's answers.
  • Evaluate opens the scoring screen. It needs Evaluation on your role and a seat on this programme's panel; without Evaluation it shows a padlock, with the reason.
  • If your plan does not include Evaluation, the tab says so. New scores cannot be recorded, and scores already recorded stay listed. Once your team has assessed an application, it moves it on from the application itself.
  • Building the scoring sheet itself happens when you create or edit the program - see Creating a Program.
  • Assigning who sits on the panel is covered in Evaluation Panels and Scoring.

Collecting information from a cohort#

Data Collection is for startups already in the program, not applicants. Use it when you need the same thing from everyone - a quarterly progress report, updated headcount, a compliance document.

Data Collection. Requests can be filtered by status and by batch once you have a few.
  • Create a request describing what you need and by when.
  • Startups see it in their own portal and respond there.
  • Filter by status to see who has replied and who has not.
  • Filter by batch to chase one cohort without bothering the others.

Good to know

This is the difference worth remembering: document requests chase one applicant during selection; data collection requests chase your whole cohort after they are in.

Common questions#

You have no funding sources set up. Every batch needs funding attached, and that funding has to come from a source. Go to Funding, add at least one source, then come back and the button will work.

This programme is not running - all its batches are Closed, Completed or Archived - so it does not count toward your plan's programme limit, and you are at that limit. A new batch would make it count again. Close out another programme's finished batches to make room, or an admin can move to a bigger plan.

Anyone who can see the programme: Programs View on their role, View set for them in this programme, or a seat on its panel. Scoring is separate - it needs Evaluation on the role and a seat on the panel.

Edit the batch and change the code - you can until applications open. After that it is fixed; if it is badly wrong, create a replacement batch with the correct code before anyone applies to it.

Check the Batches tab. Either there is no batch, or the batch status is not Open, or today's date is outside the application window. All three produce the same symptom.

Registrations is everyone who applied, at every stage including rejected. Startups is only those you actually onboarded. An application appears in Startups once its status reaches Onboarded.

Yes. Export CSV at the top of the Registrations tab gives you the current list, respecting whatever filter you have applied.

That means a panel member has not submitted their scores. Check the Evaluations tab to see what is pending, then chase the individual. Changing the status manually would lose the scoring.

Yes. Create two batches with overlapping dates. The Registrations tab has a batch filter so you can work through them separately.

Open the copy and use Merge into another programme, next to Edit. Choose the programme to keep and you see what will move - memberships with the registrations your team or an import made for them, batches, allocations, payments and funding requests - before anything changes. A batch whose name the kept programme already uses is kept apart with '(from ...)' added. The copy stays as an empty, unlisted programme that says when it was merged and by whom. A programme that took applications from founders, or has evaluations, managers, panels or announcements, cannot be merged. Merging needs Programs Delete on your role.

Ready to Join
the Ecosystem?

Book a demo

EcoSync is a product of Opernova Technologies LLP.

Running an incubator or accelerator? EcoSync for incubators

© 2026 Opernova Technologies LLP. All rights reserved.