30 Jun 2026

Organizing Theoretical-Physics Seminars, Workshops, Schools and Conferences in Indian Colleges

A detailed institutional manual for designing, approving, funding, governing, conducting and closing scientific events, including arrangements suitable for remote and teaching-focused colleges.

theoretical-physics academic-events seminars-and-workshops conference-organization indian-colleges event-administration

← Series map · Previous: funding theoretical-physics research in Indian colleges

A scientific event is temporary research or teaching infrastructure. It brings a defined group of people, scientific questions, facilities and funds together for a stated purpose. The academic programme, institutional authority, participant system, financial record and post-event output are therefore parts of one activity—not separate ceremonial and administrative layers.

This chapter is an organizer-facing manual. Module 8 maps meetings from a participant’s perspective, Module 9 explains how meetings support collaboration, and Module 10 maps the wider funding system. The present module describes how an Indian college can turn an event idea into an approved, scientifically coherent, accessible and auditable institutional activity.

Seminar, workshop, school, symposium and conference are not interchangeable labels. The format describes what participants will do. A sequence of invited talks does not become a workshop merely because it is advertised under that name, and participation by one overseas speaker does not by itself make an event an international conference.

The reference date is 30 June 2026. Funder rules, application windows, admissible rates, visa processes and institutional delegations of financial power can change. The current call, portal, sanction letter and host-institution rules always prevail over this general manual.

1. Choosing the correct event format

Scientific-event names are not standardized perfectly across agencies, but the following operational distinctions are useful.

Format	Primary purpose	Normal academic structure	Typical scale or duration	Appropriate output
Research seminar	Communicate one piece of current work	One talk, questions and technical discussion	60–120 minutes	Discussion record, references and possible follow-up contact
Colloquium	Explain a field or major result to a broad physics audience	Accessible lecture with a longer conceptual introduction	60–90 minutes	Wider departmental awareness
Seminar series	Maintain regular contact with current research	Recurring talks under a stable theme or calendar	Weekly, fortnightly or monthly	Public calendar, talk archive and durable network
Symposium or discussion meeting	Compare several views on one sharply defined subject	A small number of invited contributions and substantial discussion	Half day to two days	Synthesis, open-problem list or research agenda
Lecture workshop	Strengthen understanding of a defined topic	Extended lectures, questions and sometimes tutorials	Commonly two or three days	Learning material and participant feedback
Focused workshop	Work actively on methods or problems	Tutorials, calculations, coding, problem groups, posters and collaboration time	Two to five days	Notes, notebooks, tested calculations or working groups
School or refresher course	Teach a coherent body of material in sequence	Prerequisites, linked lectures, tutorials, exercises and assessment or feedback	Several days to two weeks or longer	Demonstrable learning and reusable course material
Conference	Present and discuss recent research across a field or subfield	Plenary, invited and contributed talks, posters, and parallel sessions only if justified	Two to five days is common	Research exchange; an abstract book or proceedings only when separately arranged
Long research programme	Create a temporary research community	A light formal schedule with seminars, visitors and protected collaboration time	Several weeks or months	New calculations, collaborations, preprints or proposals
Public lecture or outreach event	Explain science beyond the specialist community	Non-technical presentation and moderated public questions	One session	Public understanding rather than specialist training

The ICTP event-format descriptions distinguish pedagogical schools, specialized advanced schools or workshops, conferences on recent results and extended collaborative workshops. The ICTS programme guidelines similarly emphasize scientific interaction and pedagogy rather than an ordinary talk-heavy conference. These are useful design models even when an event is not proposed to ICTP or ICTS.

The audience determines the format. Undergraduate students may need a colloquium or syllabus-connected lecture workshop; MSc students and beginning PhD scholars may need a school with prerequisites and exercises; active specialists may need a small workshop with unscheduled research time. A programme advertised simultaneously for school students, undergraduates, doctoral researchers and international specialists usually has no clearly defined intellectual level.

2. A staged event system for a remote department

An institution does not need to begin with a large conference. A credible event system can grow in stages.

Stage	Minimum viable activity	Administrative load	Scientific value created
1	Monthly online or hybrid seminar	Official page, speaker consent, moderator, recording choice and attendance record	Regular exposure to active researchers
2	Half-day regional discussion meeting	Institutional approval, small programme, nearby speakers and local participants	Connects departments within practical travel distance
3	Two-day focused lecture workshop	Committees, itemized budget, participant call, hospitality and final report	Establishes a visible thematic node and an event record
4	Multi-institutional school or funded symposium	External proposal, selection system, finance file, travel, accommodation and formal closure	Builds advanced training and national participation
5	Recurring school, network or long programme	Stable partnerships, demonstrated past closure and multi-year academic continuity	Converts isolated events into a research community

For a remote venue, travel time from the nearest railhead or airport, power reliability, bandwidth, accommodation safety and local transport are part of scientific design. A programme that begins before participants can realistically arrive, or loses remote speakers whenever the connection fails, is not operationally complete. Useful low-resource provisions include locally cached slides, a second mobile-network connection, UPS or generator support, a tested conference speakerphone, an offline copy of notebooks and a nearby university or institute as a scientific partner.

3. Institutional ownership and three separate approvals

Organizing a scientific event involves at least three distinct decisions:

1. Academic approval accepts the theme, purpose, audience, speakers and proposed programme.
2. Administrative and financial approval authorizes the institution to host the event, constitute committees, use facilities, collect any approved fee, receive funds and incur expenditure under specified rules.
3. External funding sanction approves only the agency’s contribution and conditions. It does not replace the host institution’s approval.

An event should therefore have a file or controlled digital record before public announcement. Depending on the institution, it may contain:

• the concept note and departmental recommendation;
• approval of the Principal, Director, Registrar or other competent authority;
• an office order constituting the committees and naming the convener;
• approved dates, venue, mode and capacity;
• expenditure sanction and the institutional finance or purchase route;
• the authorized institutional bank account, ledger or cost centre;
• permission to collect and account for a registration fee, if any;
• venue, IT, guest-house, transport and security permissions;
• on-duty or leave arrangements for employees and students; and
• funder sanction, partner letters and later amendments.

No speaker, hotel or vendor should receive a financial promise before the person with the required institutional authority has approved it. A scientific committee can recommend expenditure; it normally cannot override procurement, taxation, audit or delegation-of-power rules.

The internal contact sequence

In a college without a conference office, the following sequence makes responsibility visible:

Question	First institutional contact	Decision or information required
Is the scientific idea suitable?	Head of Department and proposed scientific co-organizer	Theme, audience, format, dates and academic ownership
May the college host and represent the event?	Principal, Director, Registrar or other competent authority	Administrative approval and authorized signatory
Is the institution eligible for the named scheme?	Research cell, IQAC or designated grants office, with the scheme guideline	Recognition, affiliation, accreditation, appointment and document tests
How will money be received and recorded?	Accounts or finance officer	Institutional bank details, ledger/cost centre, interest and audit route
Who may approve a purchase, hotel or vehicle?	Finance and purchase/stores section	Delegated power, quotations, order, tax and payment procedure
Can the proposed rooms and services be supplied?	Estate, IT, guest house, transport, security and medical units as applicable	Written availability, costs, access and emergency arrangements
Who handles access and conduct issues?	Disability/access officer, Internal Committee and competent administrative authority	Named event contacts, referral route, confidentiality limits and emergency escalation
Is a funder rule unclear?	Programme contact shown on the current official scheme page	A short written question quoting the exact clause and event facts

External speakers and partners can be approached for scientific interest while approval is developing, but the message should say that dates and financial support remain subject to institutional and funding sanction. Only the authorized officer commits the institution.

4. Organization structure and responsibility

There is no single committee structure mandated for every Indian college. The event’s scale, the host’s statutes and the funder’s rules control. The following functional structure is sufficient for most academic events:

Head of Institution / competent authority
                    │
       Convener or scientific director
          ┌─────────┼─────────┐
          │         │         │
 Scientific     Local      Finance and
 programme    organizing    accounts
 committee     committee       lead
          │         │         │
  theme, speakers,  registration, venue, travel,
  abstracts, chairs hospitality, IT, safety,
  and programme     communication and records

Function	Main responsibility	Records controlled
Head of Institution or competent authority	Gives institutional authority, accepts grants or agreements and designates financial signatories	Approval, endorsement, sanction acceptance and institutional certification
Convener or event director	Integrates the scientific, administrative and reporting work; is the principal contact	Concept note, master action register, correspondence and completion report
Scientific Organizing Committee (SOC)	Defines scope and prerequisites; selects speakers; reviews applications or abstracts; appoints chairs	Scientific programme, review criteria, decisions, conflicts and minutes
Local Organizing Committee (LOC)	Runs the venue, registration, accommodation, transport, catering, signage, IT, volunteers and help desk	Supplier and participant operations, room plans and run sheet
Finance and procurement lead	Checks admissibility, sanctions, purchasing, payments, ledger and closure	Budget, quotations, orders, invoices, claims, payment evidence, SoE and UC
Secretariat and communications lead	Maintains the official email, website, versioned programme and notices	Applicant register, mailing record, invitation and decision letters
Speaker and travel liaison	Confirms titles, biographies, travel plans, support terms and documents	Speaker status sheet, itinerary, reimbursement checklist and consent
Registration and selection team	Receives applications, assigns IDs and implements recorded decisions	Applications, abstracts, waitlist, acceptance and attendance records
Venue, AV and hybrid-production lead	Tests projection, blackboards, microphones, internet, platform access and backups	Technical checklist, rehearsal record and failure plan
Accessibility, safety and conduct contacts	Receive access requests; communicate safety and conduct routes; coordinate with authorized institutional bodies	Restricted access-needs record, incident route and emergency contacts
Session chair	Introduces speakers, keeps time, moderates questions and enforces the code	Chair sheet and session notes
Rapporteur or archive lead	Records scientific content, feedback and authorized materials	Session summaries, report, archive permissions and follow-up actions
Student volunteers	Perform narrowly assigned desk, escort, timekeeping or technical tasks under supervision	Duty roster and shift handover

In a seminar, four or five people can combine several functions. In a larger conference, the SOC and LOC should be distinct enough that scientific selection is not displaced by hospitality work. The finance officer should be an institutional function, not a ceremonial “treasurer” collecting money into a personal account.

An office order should state names, roles, authority, reporting relationship, event dates and the life of the committee. It should also identify who may approve speakers, participants, travel support and purchases. Long lists of patrons, honorary advisers and chief guests do not substitute for these responsibilities. Some schemes prohibit such decorative lists: the Science Academies’ Lecture Workshop manual, for example, specifies Convener and Coordinator roles and asks organizers to avoid patrons and management names in its publicity.

5. Whom to conduct the event with

The partner should supply a real scientific or administrative function. A logo without an agreed role is not a collaboration.

Need	Appropriate partner	Possible documented role
Subject depth and active speakers	Nearby state or central university, IISER, IIT, NIT, national laboratory or research institute	Co-organizer, SOC member, resource person, tutorial leader or follow-up mentor
Academy-supported college teaching event	A Fellow of IASc, INSA or NASI with relevant expertise	Convener of a Science Academies’ Lecture Workshop or Course Director, subject to its rules
DAE-aligned nuclear, particle, plasma, accelerator, quantum-sensor or related topic	Relevant DAE unit or BRNS community	Scientific partner or resource person; a BRNS event proposal must satisfy BRNS subject rules
Mathematical physics	Mathematicians and mathematical physicists with genuine subject fit	Programme design, review and a possible NBHM-aligned event
Astronomy, cosmology or gravitation	IUCAA faculty, Associates or relevant Resource Centre, where programme terms fit	Recurring local activity, resource persons or a continuing student link
Advanced thematic programme	ICTS scientific community or other programme centre	A reviewed programme proposal hosted under the centre’s own arrangements
Low-resource international teaching connection	ICTP Physics Without Frontiers, under its current call	Volunteer-scientist school, course, roadshow, seminar series or faculty support
Formal doctoral participation	Affiliating university or recognized research centre	Approval, scholar participation, supervisor network and follow-up activity

Speaker selection should begin with required topics, not famous names. Each speaker or instructor should have a defined function: foundation lecture, research lecture, derivation tutorial, computational laboratory, problem session, student-feedback session or research discussion. Current publication and group pages show subject fit; teaching clarity and willingness to engage show format fit. A balanced programme normally includes more than one institution and career stage and does not sell scientific slots to sponsors.

For the Science Academies route, the subject-wise list of INSA Fellows, the other Academies’ directories and the Joint Science Education Panel can help identify a scientifically relevant person. An initial approach can attach a one-page concept note containing the local academic need, intended participants, narrow topic, tentative dates, host facilities and requested role. The named programme’s formal rules still determine who may act as Convener or Course Director.

6. The one-page scientific concept note

The concept note is the common source for institutional approval, partner discussions and the later funding proposal. A compact template is:

Working title and event format:
Host department and institution:
Narrow scientific theme:

Scientific context:
What body of theory, current problem or educational gap does the event address?

Purpose:
What will be different after the event—knowledge, methods, calculations,
research connections, teaching capacity or a defined collaborative output?

Audience and prerequisites:
Career stage, expected prior courses or methods, geographic reach and capacity.

Academic structure:
Lectures, tutorials, exercises, posters, discussion or collaboration blocks.

Proposed scientific team:
Convener, co-organizers, possible speakers/resource persons and their roles.
Mark each person as proposed, approached, interested or confirmed.

Dates, mode and venue:
Include the realistic arrival/departure window and hybrid requirements.

Expected outputs and follow-up:
Notes, notebooks, reading group, seminar series, open-problem record or collaboration.

Preliminary budget and sources:
Host contribution, requested agency support, other requested support and fee, if any.

Institutional requirements:
Approvals, account/cost centre, facilities, procurement and external clearances.

The title should identify a coherent subject—such as Open Quantum Systems: Methods and Applications or Geometric Methods in Quantum Theory—rather than combine every branch of modern physics. The programme should then make the title true.

7. Planning timeline

The following schedule is an operating model, not a substitute for a funder’s deadline.

Time before event	Academic work	Administrative and operational work
12–9 months	Need assessment, format, theme, possible partners and anchor speakers	Obtain preliminary institutional approval; examine venue, accommodation and likely funding routes
9–6 months	Form SOC; draft learning or research outcomes and tentative sessions	Form LOC and finance team; build the source-wise budget; submit schemes with long lead times
6–4 months	Record speaker interest; prepare public scope, prerequisites and review rubric	Finalize website, official email, brochure, forms, risk plan and sponsor requests
4–2 months	Review applicants and abstracts; create waitlist; confirm programme	Book authorized services; plan travel, rooms, access arrangements and international clearances
8–4 weeks	Issue final titles and chair assignments; circulate preparatory material	Send joining instructions; collect itineraries and permitted financial documents; test hybrid system
Final 2 weeks	Freeze programme except necessary corrections; brief chairs and rapporteurs	Reconcile lists; create run sheet, desk packs, signage, emergency sheet and offline backups
Event days	Protect scientific time, discussion and participant access	Record attendance, consent, claims, invoices, schedule changes and incidents
1–2 weeks after	Compile feedback, scientific report, materials and follow-up actions	Settle claims and vendors; reconcile every budget head and archive the controlled records
Funder deadline	Report scientific outputs	Submit SoE, UC, audit documents and unspent-balance action; obtain formal closure

ANRF Seminar/Symposia currently requires an application 60–180 days before the start date; the Science Academies say that Lecture Workshop and Refresher Course proposals should preferably arrive at least four months ahead; NBHM specifies longer advance periods for national and international conferences; and BRNS indicates a multi-month appraisal process. These are different clocks. Publicity should not start on the assumption that a pending grant will be approved.

8. Designing the academic programme

The opening questions are: What must participants know before arrival? What should they be able to explain or do at the end? Which session produces that change?

A research seminar

A useful 90-minute structure is 5 minutes for the introduction, 50–60 minutes for the talk, 20–30 minutes for questions and a short closing notice about references or follow-up. The chair protects the technical discussion from a prolonged ceremonial introduction.

A two-day theoretical-physics workshop

One possible structure is:

Day	Morning	Afternoon
1	Common notation and foundations; one extended research lecture	Guided derivation, computational notebook or problem groups; poster discussion
2	Two connected advanced lectures	Open-problem groups; group reports; references, follow-up seminar dates and closing scientific synthesis

A school or refresher course

Lectures should form a sequence rather than a collection. Each unit states prerequisites, notation, core results, exercises and reading. Tutorials, blackboard calculations, problem solving or computing are part of the timetable. A feedback or diagnostic exercise can measure learning without turning the event into an examination unless formal assessment was announced.

A conference

Plenary talks provide common reference points; contributed talks and posters bring new work into the programme. Parallel sessions are justified only when attendance and topic breadth make them necessary. Breaks, poster periods and unscheduled discussion are scientific programme elements, not empty spaces to eliminate. A “talk marathon” leaves little opportunity for comprehension or collaboration.

9. Speaker invitations and status control

The internal speaker sheet should mark each person as proposed, approached, interested, formally invited, accepted or withdrawn. Only accepted speakers should appear as confirmed. A reusable invitation contains:

Subject: Invitation to contribute to [exact event title], [dates]

Institution and organizers:
Scientific purpose and intended audience:
Requested contribution: [lecture/tutorial/problem session/panel]
Proposed topic and duration:
Physical, online or hybrid format:

Financial terms:
Travel class or ceiling, lodging, local hospitality, honorarium if admissible,
reimbursement method, required evidence, and whether support is sanctioned
or still subject to approval.

Publication and media terms:
Abstract, slides or notes requested; separate choices for photography,
streaming, recording and later public release.

Please confirm by:
Please supply by:
Official contact and institutional webpage:

“Invited to speak” and “fully funded” are different statuses. The invitation must not promise airfare, hotel, honorarium or reimbursement outside the approved budget. Reimbursement instructions should precede ticket purchase and specify permitted class, route, booking evidence, tickets, boarding documents, local-transport evidence, bank form and submission deadline under the applicable rules.

10. Call for participation, abstracts and selection

The public event page or call should state:

• exact scope and topics;
• intended audience and prerequisites;
• dates, venue, mode and capacity;
• invited lecture, contributed talk, poster and attendance-only categories;
• application and abstract fields;
• selection and conflict-of-interest principles;
• what financial support is available, to whom and under what ceiling;
• fee, payment route, cancellation and refund policy, if any;
• accommodation and local-travel arrangements;
• accessibility, dietary and conduct information;
• deadlines and decision dates;
• photography, streaming and recording choices;
• data-use and retention information; and
• an official institutional email and authoritative webpage.

Registration, abstract acceptance, oral presentation, accommodation and travel support are separate decisions. A clear decision letter lists each status separately.

A documented review rubric

Criterion	Question recorded by reviewer
Scope	Does the application or abstract fit the announced scientific theme?
Preparation	Does the applicant have the stated prerequisites for this format?
Scientific content	Is the question, method and claimed result intelligible and credible at abstract level?
Contribution fit	Is a talk, poster, working group or attendance place appropriate?
Likely benefit	Is the event likely to supply knowledge or access not readily available to the applicant?
Representation	Does the final cohort serve the stated institutional, regional, career-stage and inclusion aims?
Feasibility	Can the event accommodate the requested technical, travel or access support?

Reviewers should disclose conflicts and recuse. Selection minutes record the rubric, reviewers, recusals, capacity, decision and waitlist. Scientific selection should not be sold through a sponsorship package. A fee may support genuine event costs; it should not buy an invited or contributed presentation.

For a larger meeting, Indico’s official organizer documentation explains programme tracks, calls for abstracts, reviewer roles, registration, timetables, privacy, surveys and documents. Indico is open-source software; an institution still needs an authorized hosted instance or another controlled system. A small event can use an institutional form and access-controlled register, provided the same records and decisions are maintained.

11. Data, communication and records

One event webpage and one institutional email should be authoritative. Messaging groups are useful for short operational notices but are not a replacement for official decisions, current programmes or financial instructions.

The application system should collect only information necessary at that stage. Passport data, bank details, identity or category documents and access requirements should be visible only to authorized personnel and should not be placed in a general volunteer spreadsheet. Every application receives a unique ID and acknowledgment. The event declares how long records will be retained and which public items—such as name, affiliation, title or abstract—will appear online.

Programme versions should display a revision date. A late change is recorded once and propagated to the webpage, chair sheet, room display and participant message from the same source. Funder and partner logos are used only after authorization. “Supported by,” “sponsored by,” “in collaboration with” and “hosted by” describe different relationships and should be used accurately.

12. Budget architecture

A budget contains both uses and sources. Estimating only expenditure conceals the funding gap.

Cost head	Calculation basis	Funder requested	Host contribution	Other confirmed/requested source
Invited-speaker travel	Eligible people × realistic approved fare
Participant travel support	Supported participants × ceiling
Accommodation	Room nights × approved rate
Working meals and refreshments	Eligible persons × sessions/days × rate
Local transport	Authorized trips or contracted vehicle basis
Venue and AV	Only if not supplied in kind by host
Hybrid platform or production	Licensed service or approved technical cost
Printing or event material	Quantity × unit cost; only if admissible
Accessibility arrangements	Captioning, interpretation or other approved provision
Honoraria	Named eligible roles × scheme rate, only when allowed
Contingency	Scheme-defined basis, not an unrecorded reserve
Total uses

The source table also lists institutional in-kind facilities, registration income and sponsorship. Every external source should be disclosed to each funder. The same invoice or journey cannot be claimed twice. A shortfall scenario states which costs will be reduced if a partial award is made; it must not quietly transfer an unannounced burden to participants.

For theoretical physics, scientific access normally has priority over decorations, gifts, elaborate inaugurations and publicity objects. Capital equipment, furniture, alcohol, sightseeing, mementos, international airfare, honorarium, venue hire or publication costs may be inadmissible under a particular scheme even if useful elsewhere. Only the current guideline and sanction letter determine admissibility.

13. Financial control and audit trail

Event money should move through the authorized institutional account and books, never a convener’s personal bank account, personal UPI ID or informal cash pool. The finance record normally includes:

• institutional approval and external sanction;
• approved head-wise budget and every approved revision;
• grant receipt, registration-fee and sponsorship registers;
• a separate ledger or cost centre;
• quotations, comparative statement, purchase approval and work or supply order where required;
• invoice, receipt, proof of delivery and proof of payment;
• travel approval, ticket, journey evidence and signed claim;
• advances and their adjustment;
• attendance or service evidence supporting the expense;
• applicable GST, TDS and other institutional tax treatment;
• head-wise reconciliation, bank reconciliation and interest record;
• Statement of Expenditure, Utilization Certificate and audit certification; and
• return or adjustment of unspent funds and formal closure.

The sanctioning agency’s conditions and the institution’s finance, procurement and delegation rules must be read together. Government institutions should consult the current Department of Expenditure manuals and General Financial Rules as incorporated into their own rules; a general web article cannot decide local quotation thresholds or signing powers.

14. Indian support and programme routes

The routes below fund different objects. Some transfer partial event support to the institution; others approve an event under the programme centre’s own arrangements.

Route	What it is	Key organizer information	Official manual or page
ANRF Seminar/Symposia	Partial support for eligible scientific events held in India	Regular eligible convener; current 60–180 day submission window; event normally 2–5 consecutive days; institutional receipt and closure	Live scheme page
Science Academies’ Lecture Workshop	Joint IASc–INSA–NASI education programme for local UG/PG students and teachers	Two or three days; Academy Fellow as Convener; host faculty Coordinator; local participation; college supplies facilities	Overview and detailed manual with budget formats
Science Academies’ Refresher Course	Longer teacher-development course	Seven to fourteen days under current detailed guide; sequenced curriculum, tutorials and national selection	Overview and detailed manual
BRNS Symposium/Conference support	Support for events relevant to DAE/BRNS subject areas	Online application and BRNS-specific forms; allow several months; complete older event accounts before another proposal	Process page, forms and manuals, symposium user manual
NBHM conference support	Support for a meeting genuinely within mathematics or mathematical physics	Advance submission; complete organizer credentials and academic programme; do not submit the same event simultaneously to both NBHM and BRNS	Conference-support page and form
ICTS programme proposal	Reviewed scientific programme hosted as an ICTS activity	Usually at least two organizers; strong scientific case, proposed speakers, participant plan, interaction and inclusion	Programme guidelines and proposal template
ICTP event proposal	Proposal for an ICTP scientific-calendar or outside activity	Format, international value, training, directors, participants and local contribution are reviewed; not a general cash grant	Propose an ICTP event
ICTP Physics Without Frontiers	Call-based support for physics capacity in low-resource settings	Local organizer required for in-person activity; possible schools, courses, roadshows, seminars or faculty support	Application route and activity models

14.1 ANRF Seminar/Symposia: application anatomy

The live ANRF page currently describes partial support for national or international scientific events held in India. The convener is an Indian citizen residing in India and holding a regular position at an eligible recognized institution. The application is submitted through the portal 60–180 days before an event of two to five consecutive days.

The proposal contains the event identity, objectives, keywords, venue, dates, estimated expenditure and institutional bank information. Current mandatory material includes the convener certificate, Head of Institution endorsement, announcement brochure, session-wise technical programme with chairs or co-chairs, and keynote-speaker information. ANRF’s official files include:

• technical proposal and budget template;
• convener certificate;
• Head of Institution endorsement;
• post-event completion report; and
• Statement of Expenditure and Utilization Certificate.

The displayed support heads include domestic travel for Indian scientists, pre-conference printing and contingency or incidental working expenses under the scheme. It does not support international-participant airfare. The award is released to the Head of Institution or other authorized organizational head, not to the convener personally. Private colleges have additional institutional documents on recognition, governing-body authority, prior accounts and specified registrations or undertakings. ANRF’s logo should not be used before approval. The current page and portal must be rechecked because the displayed eligible event window rolls with time.

14.2 The Science Academies’ route for a college

The Joint Science Education Panel’s Lecture Workshop is unusually well matched to a college outside a major centre. Its official manual states that proposals from less-endowed institutions may receive preference without compromising merit and quality, and it seeks geographical diversity. If the usual number of Academy Fellows is unavailable in a remote area, the Coordinator or Convener may seek special permission by supplying the backgrounds of proposed non-Fellow resource persons.

The standard structure is specific:

• a Fellow of one of the three Academies acts as Convener;
• a faculty member at the host institution acts as Coordinator;
• the event lasts two or three days and primarily serves local UG/PG students and teachers;
• the host contacts nearby colleges and supplies the hall, audiovisual facilities, reliable power and service space;
• the academic plan uses a small number of resource persons for extended lectures and interaction; and
• the proposal is preferably submitted at least four months in advance to the Joint Science Education Panel.

The current manual contains the actual budget heads, rates, instalment method and after-event account format. Rates should be read from the live manual rather than copied into a future plan. It also contains non-obvious programme rules: the activity is called a Science Academies’ Lecture Workshop rather than a national conference; publicity avoids lists of patrons and management; and formal participant certificates are ordinarily replaced by an attendance letter if needed. The report, expenditure statement, supporting vouchers, programme, participant list and authorized photographs are due under the manual’s post-event process.

The longer Refresher Course route is intended chiefly for teacher development. Its detailed guide supplies proposal fields, course structure, resource-person expectations, participant selection and sample budget formats. A theoretical course should contain tutorials, questions and problem-solving rather than only lectures.

14.3 BRNS and NBHM

BRNS accepts symposium, conference, seminar and workshop proposals in areas relevant to its DAE mandate. The BRNS activity process and downloads page describe registration, online submission, required documents and closure forms; the official symposium user manual gives screen-level instructions. An online application and any required signed institutional copy form one process, not alternatives. A retained portal page does not remove the need to check current subject, document and dispatch instructions.

NBHM supports national or international conferences, workshops and seminars that genuinely belong to mathematics. Its conference-support page publishes the current lead times, ceilings, organizer credentials, form and closure conditions. It also states that the same event should not be submitted to both BRNS and NBHM. Mathematical notation alone does not make a general physics meeting an NBHM meeting.

14.4 Hosted-programme routes are not ordinary grants

An approved ICTS proposal becomes an ICTS programme under the centre’s reviewed arrangements; it is not simply a grant transferred to a college for an independent conference. ICTS asks for a timely scientific theme, clear objectives, participant and speaker plans, expected interest, interaction, diversity and justified duration. Faculty at educational or research institutions can propose a programme, normally with co-organizers.

ICTP similarly reviews scientific-calendar and outside-activity proposals under its own programme conditions. Physics Without Frontiers is particularly relevant to departments with little local research access, but it works through calls and a jointly designed capacity-building activity rather than unconditional event finance. These routes can create deeper scientific contact than a one-time sponsorship, but their institutional object must be described correctly.

15. Venue, travel and remote-location logistics

Participant instructions should include:

• the full postal address and map coordinates;
• routes from the nearest rail, bus and air points, with realistic travel times;
• safe arrival windows and the last practical public-transport connection;
• authorized pickup points and a named contact;
• accommodation address, check-in rules, room sharing and distance from venue;
• venue accessibility, toilets, quiet or prayer space and dietary arrangements;
• weather, clothing and local health information where material; and
• reimbursement rules and documents sent before the journey.

The venue check covers capacity, sight lines, equation-readable projection, blackboard or writing tablet, microphones, power backup, ventilation, fire exits, drinking water, first aid, nearest medical facility and safe transport after evening sessions. Food allergens should be labelled. An access-needs question should be asked during registration, not at the door.

A simple risk register records the hazard, likelihood, impact, owner, prevention, response and escalation contact. Relevant hazards include speaker withdrawal, transport disruption, unsafe crowding, power or network failure, medical emergency, extreme weather, food or water problem, data breach, harassment report, vendor failure and event cancellation.

16. Hybrid and online operation

A hybrid session needs three roles: the scientific chair, the platform moderator and the technical producer. One person cannot reliably present, admit attendees, monitor chat, operate slides, troubleshoot audio and moderate scientific questions at the same time.

Minimum controls include:

• a rehearsal with each remote speaker;
• wired internet where possible and a second-network backup;
• separate room and remote microphones so both audiences can hear questions;
• direct screen sharing rather than a distant camera view of equations;
• captions where feasible and advance access to readable material;
• an access-controlled link and a defined late-admission rule;
• one moderated question queue across both audiences;
• offline slides, speaker phone number and a failure decision tree; and
• a clear notice about chat, screenshots, photography and recording.

Recording requires explicit permission. The form should distinguish live streaming, recording the talk, recording questions, publishing slides and permanent public release. A speaker can consent to one and decline another. Participants must have a usable no-photo or no-record route.

17. Conduct, inclusion, accessibility and safety

A written code of conduct should cover lecture rooms, online platforms, accommodation, transport, meals and social activity. It defines prohibited harassment, discrimination, intimidation and disruption; names at least two approachable contacts; explains confidentiality limits and possible immediate measures; and connects the event to the institution’s competent authority, Internal Committee and emergency process. Event volunteers should not improvise an investigation beyond their authority.

Session chairs set the discussion standard: concise questions, no hostile monologues, no discriminatory remarks, respect for unpublished material and time for participants who are less likely to interrupt. The IOP Inclusive Conference Guide supplies a practical checklist covering advance access questions, accessible venues and documents, breaks, dietary labelling, quiet or prayer space, caring needs, scheduling and balanced participation. The IOP Conference and Event Guide covers planning, risk, budgets, venue, registration and evaluation. APS session-chair guidance provides a useful model for introductions, timekeeping, question moderation and conduct.

Where minors attend, safeguarding, supervision and consent requirements need a separate institutional plan. Accessibility and safety costs should be budgeted rather than treated as unexpected favors.

18. Day-of-event operating manual

The master run sheet has one row for every operational change:

Time	Activity	Responsible person	Location or link	Equipment/document	Dependency	Fallback
08:00	Desk and AV open	Registration and technical leads	Foyer / Room 1	Lists, badges, QR/manual attendance, projector, microphones	Power and room access	Printed list, UPS and spare laptop
09:00	Opening scientific orientation	Convener	Room 1	Programme and conduct slide	Key organizers present	Co-convener delivers briefing
09:15	Session 1	Chair and AV lead	Room 1 / online link	Chair sheet, slides, timer	Speaker and connection	Offline slides or substitute discussion
11:00	Break and claim desk	Hospitality and finance staff	Foyer	Dietary labels and claim checklist	Vendor arrival	Sealed backup refreshments
17:00	Daily close	Convener, LOC and finance lead	Office	Issue log, attendance and expenditure log	Team leads	Short online reconciliation

The desk pack contains the current programme, accepted-participant list, emergency contacts, access arrangements known to the desk, room map, transport sheet and escalation chain. Sensitive bank, passport or conduct information is kept elsewhere with authorized staff.

The session-chair sheet states the speaker’s correct name and affiliation, allotted talk and question times, warning cards or signals, pronunciation, recording status, conduct reminder, AV contact and fallback plan. The rapporteur records scientific points and follow-up actions, not a transcript of private discussion.

At the end of each day, the Convener, LOC, technical and finance leads reconcile programme changes, missing participants, next-day travel, access issues, collected claims, new invoices and unresolved risks.

19. Certificates, materials, recording and proceedings

Different event objects must not be confused:

Object	What it certifies or contains
Programme	Planned schedule; not proof that every session occurred
Attendance record	Verified presence under the stated event rule
Abstract book	Accepted summaries; not peer-reviewed full papers unless explicitly subjected to such a process
Lecture material	Slides, notes, exercises or code shared with author permission
Recording	Audiovisual record under explicit speaker and participant consent
Proceedings	Separate scholarly publication with editors, full-paper criteria, review and publisher agreement
Journal special issue	Journal-controlled submission and peer-review process; conference acceptance does not guarantee publication

Certificate wording should distinguish attendance, paper or poster presentation, invited-resource-person service and organizing service. Verification comes from the attendance and session records, and corrections are entered in a certificate register. Certificates should not be issued before the activity or merely in exchange for a fee. Scheme-specific rules prevail: the Science Academies’ current Lecture Workshop manual ordinarily permits an attendance letter rather than a formal participant certificate.

Recording, slides and photographs remain subject to permission. An abstract or attendance certificate is not a journal publication. Proceedings should not be advertised with an ISBN, DOI, journal title, indexing claim or “Scopus” label until a legitimate publisher has formally agreed to the exact volume and its editorial process. The IOP proceedings author guidance illustrates the additional author and publication layer. For many focused theory workshops, edited lecture notes, verified notebooks and an open-problem report are more useful than rushed proceedings.

20. International speakers and events in India

Foreign participation creates a distinct visa and clearance workstream. Before final travel assurances are issued, the host’s international office or competent authority should examine the current conference-visa, political-clearance, security-clearance and restricted/protected-area rules.

The Ministry of Home Affairs Conference Visa FAQ explains when prior reference to MEA and MHA is required, while the MHA International Events portal and its organizer user manual describe the event-clearance system. The MEA political-clearance portal handles the political-clearance process described by MHA. Requirements depend on the organizer, participant nationality, event subject and location; the live portal and relevant Ministry instructions are authoritative because a static manual may lag a portal change.

An invitation letter should state only confirmed facts and support. Foreign guests may need adequate lead time for a Conference Visa and, in specified cases, prior governmental authorization. Calling a meeting “international” also creates expectations about participant composition, review, communication and administration; it should not be used as a promotional adjective for a local event with a single online guest.

21. Post-event report and financial closure

Closure is part of the event, not optional work after it. The file normally contains:

1. final programme, including actual changes;
2. participant, speaker and contribution lists;
3. attendance and certificate or attendance-letter register;
4. concise account of lectures, tutorials, posters, problems and discussion;
5. feedback summary and response to significant issues;
6. consent-cleared photographs or materials;
7. outputs and follow-up actions with responsible persons and dates;
8. head-wise expenditure, source-wise income and reconciliation;
9. original or certified invoices, claims and payment records as required;
10. SoE, UC, audit or institutional certificates in the prescribed form;
11. interest and unspent-balance calculation and return or adjustment; and
12. funder acknowledgment and formal closure correspondence.

The scientific report can use this structure:

Event identity, dates, venue and approved purpose
Organizers, partners and support sources
Target audience, applications, selection and actual attendance
Final academic programme and principal scientific content
Tutorials, posters, computations, discussions and participant outputs
Access, conduct or operational issues and how they were handled
Feedback evidence and learning/research outcomes
Public materials and permissions
Follow-up actions, owners and dates
Financial summary and list of submitted closure documents

ANRF publishes its event completion-report and UC/SoE templates on the Seminar/Symposia page. BRNS supplies a symposium closure form through its downloads page. NBHM describes its conference closure record on the conference-support page. The sanction letter’s deadline controls.

22. Measuring scientific success

Attendance, inauguration photographs, dignitary names and certificate counts are administrative or publicity facts. Scientific success is better described by:

• whether the intended audience and prerequisite level were reached;
• the completeness of the lecture, tutorial or problem sequence;
• quality of questions, posters and contributed work;
• solved exercises, tested code, notes or references produced;
• later correspondence between participants and speakers;
• new visits, reading groups, seminar invitations or joint calculations;
• continued participation by nearby institutions;
• repeat activity under a stable scientific theme; and
• accurate, timely financial and documentary closure.

A small event can therefore be more successful than a large conference. Scale is not a substitute for a coherent intellectual outcome.

23. Common failure modes and what they reveal

Failure	Underlying control that was missing
Event announced before approval or funding	Approval gate and status-controlled publicity
“International conference” with no real international programme	Accurate event classification
Theme covers all of physics	Audience and outcome definition
Famous but unconfirmed speaker list	Speaker status register and consent
Long inauguration and continuous talks	Academic programme ownership by the SOC
Participant later discovers that travel is unsupported	Separate, explicit support decision
Fees or grant received in a personal account	Institutional account and finance authority
Sponsor receives a talk slot	Separation of scientific selection from sponsorship
No record of why abstracts were accepted	Rubric, conflict declaration and minutes
Projector, internet or power failure stops the event	Rehearsal, offline copy and backup plan
Photographs or recordings made without permission	Granular media consent
Certificate or abstract presented as a publication	Clear distinction among event records
Accounts remain open after the event	Named closure owner and deadline

24. Reusable organizer document pack

The following compact set is sufficient to create an auditable event system:

1. one-page scientific concept note;
2. institutional approval and committee office order;
3. responsibility and contact matrix;
4. dated action, decision and risk registers;
5. tentative and final scientific programmes;
6. speaker invitation, status sheet and media-consent record;
7. public call, application form and abstract template;
8. review rubric, conflict declaration, minutes and waitlist;
9. source-wise budget and funder-specific proposal;
10. procurement, travel and reimbursement checklists;
11. venue, access, safety, AV and hybrid checklists;
12. versioned participant instructions and route guide;
13. master run sheet, chair sheet and volunteer roster;
14. attendance, contribution and certificate registers;
15. feedback form and issue log;
16. scientific completion report; and
17. financial reconciliation, SoE, UC, audit and closure dossier.

25. Core official manuals and portals

Source	What it supplies
ANRF Seminar/Symposia	Live eligibility, timing, admissible support, application path and completion documents
Science Academies’ Lecture Workshop manual	College-oriented format, Convener/Coordinator structure, budget norms and post-event procedure
Science Academies’ Refresher Course manual	Longer course design, participants, resource persons, sample budgets and reporting
BRNS activity process and downloads	Event application, portal process, forms and closure material for BRNS-relevant subjects
NBHM conference support	Mathematical-event eligibility, lead times, form, ceilings and closure conditions
ICTS programme guidelines	Scientific case, organizer team, programme design, participants, diversity and centre-hosted proposal process
ICTP event-proposal guide	International school, workshop, conference and extended-programme models
ICTP Physics Without Frontiers	Call-based physics capacity-building route for low-resource settings
Indico organizer documentation	Registration, abstract review, programme, timetable, documents and survey workflow
IOP Conference and Event Guide	General organizer manual for outcomes, timelines, venues, risk, finance and operations
IOP Inclusive Conference Guide	Accessibility and inclusion checklist
MHA International Events portal, FAQ and user manual	Current Indian conference-visa and event-clearance route for foreign participation; live instructions override the static manual
Department of Expenditure manuals	Current central financial and procurement reference; host-institution rules determine local application

The most important practical distinction is between an organizer manual, a funding guideline, a programme proposal and a sanction letter. The first explains good operation, the second defines a possible award, the third asks a centre to host or support a programme, and the fourth legally controls an approved event. Reading one cannot replace the others.

Return to: Journal and Paper Publication System for Quantum Physics