Guide navigation 28 of 44
What this page helps you accomplish
Coordinate startup eligibility, evidence, materials, stakeholders, scheduling, and follow-up for demo day.
Scope and authority
Access to the appropriate authenticated workspace through My Batoi Authority for the records, action, or decision involved
Event Readiness
Coordinate startup eligibility, evidence, materials, stakeholders, scheduling, and follow-up for demo day.
Observable business result
Demo day participation is supported by reviewed readiness evidence and coordinated stakeholder responsibilities.
A startup lacks evidence, consent, or approval close to the event.
Recommended recovery: Do not bypass the gate. Record the missing item, owner, and deadline, or remove the startup from the published schedule.Who should use this article
This article is for programme managers who are authorized to complete or review the task in the intended workspace. The person making a consequential operational, commercial, academic, care, access, or compliance decision remains accountable for the result.
Before you begin
- Access to the appropriate authenticated workspace through My Batoi
- Authority for the records, action, or decision involved
- Use a sanitized demonstration record for practice and confirm the intended workspace, role, scope, and responsible owner before changing operational records.
- Do not place passwords, connection secrets, personal data, regulated information, private documents, or payment details in notes, prompts, screenshots, or exports.
Workflow overview
Complete the workflow
- Confirm the workspace and responsibility. Enter the authorized workspace through My Batoi. Confirm the workspace name, your current role, the record or review period, and the person accountable for the result.
- Open the current product area. Open Incubation Centre and Events and Demo Days. Select the programme, cohort, intended event, audience, and accountable event owner.
- Check prerequisites and source records. Make sure the required capability, connection, status, relationship, approval, and safe information boundary are ready. Search before creating a new record.
- Perform the task. Define readiness criteria, collect the permitted startup evidence, complete reviews and consent checks, and prepare the schedule, materials, audience, and follow-up.
- Review the result. Check pitch and product readiness, claims, confidentiality, consent, investor or guest access, timing, dependencies, decision authority, and post-event ownership.
- Verify and retain the outcome. Each participating startup has a supported readiness decision and the event has an authorized audience, schedule, owner, and follow-up plan. Record every exception and follow-up with an owner and review date.
Verify the result
- The workspace, role, record, period, and Industry Pack still match the intended scope.
- Demo day participation is supported by reviewed readiness evidence and coordinated stakeholder responsibilities.
- The visible status, source evidence, owner, exception, and next action agree with the completed work.
- An authorized reviewer can understand the result without relying on hidden assumptions or information outside Flex.
Troubleshooting and recovery
| What you see | What to check | Safe next action |
|---|---|---|
| A startup lacks evidence, consent, or approval close to the event. | Workspace, role, entitlement, source record, status, ownership, required fields, and approval evidence. | Do not bypass the gate. Record the missing item, owner, and deadline, or remove the startup from the published schedule. |
| The expected page or action is missing. | Current role, team scope, Industry Pack availability, workspace subscription, record state, and prerequisite setup. | Stop and ask an authorized Owner or Admin to review access. Do not use another person’s account or bypass the control. |
| The result conflicts with evidence or another register. | Source ownership, date range, status definitions, duplicate records, latest update, and correction history. | Do not mark the task complete. Return it for correction or escalate it to the accountable owner. |
Safety and governance
Do not copy authenticated page addresses, record identifiers, connection details, browser notifications, account information, or unrelated workspace content into public documentation or external communication.
Use Batoi Intelligence safely
Next step
Continue with the next verified article in this Product Guide, or return to the Batoi Flex Product Guide.