How to offer scholarship places at a paid conference

You want people at your conference who can't get there on the standard ticket price. Perhaps they're starting a business, between jobs or paying for professional development themselves. Scholarship places can help, provided you fund the whole promise, explain who can apply and give successful applicants enough time to use the offer. Start with a defined allocation and a clear attendance package, then build the application around the decisions you actually need to make.

The ticket is only one part of that promise. A free pass won't help someone who can't afford the train. A travel reimbursement won't help someone who can't pay for travel first. And an acceptance email isn't much use if it arrives after affordable accommodation has disappeared. Those details can decide whether someone attends or quietly declines the award.

You also need the event to remain financially sound. Scholarship attendees use capacity, meals and staff time. If the conference sells out, allocating a place may mean giving up a paid booking. You can choose to fund that, but the decision belongs in the budget before you announce how many places are available.

This guide walks through that decision, a worked conference budget, a practical application and review process, and the handover into actual tickets. All dollar amounts and planning quantities in the examples are invented USD assumptions. They aren't recommended grant amounts, market prices or results from a Loopyah customer.

Decide what the scholarship is meant to change

Begin with the people you want to help and the obstacle they face. "Make the conference more accessible" is a worthwhile intention, but it doesn't tell your team whether to fund local tickets, overnight travel or a smaller number of more complete attendance packages. You need a purpose specific enough to make those choices.

For a professional conference, you might want independent practitioners without employer funding to attend the main programme. For a technical conference, you might want people entering the field to learn alongside experienced participants. Neither purpose requires applicants to promise that they'll become paying customers later. Treat access as the stated outcome and judge the programme against it.

Be careful with the word scholarship. Some people will read it as an academic award, while others will expect financial assistance based on need. Explain what you mean in the first paragraph of the offer. If relevant experience matters, name it. If the programme isn't a competition for the most impressive career, don't ask questions that turn it into one.

Separate this from a general discount. A lower public price lets buyers choose without asking for assistance. An application-based scholarship allocates limited support using published criteria. Both can be useful, but the second creates work and asks people to share information. Use an application only when those decisions justify the effort for applicants and your team.

The wider ticket pricing strategy still needs to work for the conference. Scholarship places should have an approved funding source rather than depend on a hoped-for increase in regular sales. You can explain the commercial decision internally without suggesting that recipients owe the event publicity, unpaid work or a future purchase.

Write a short purpose statement your reviewers can use. For example, the programme funds main-conference attendance for people working towards a relevant professional goal who lack employer support and would otherwise struggle to attend. Then check every proposed criterion against that sentence. If a question doesn't help you apply the purpose, remove it.

Define the attendance package before counting places

A ticket-only award is a valid offer when you describe it honestly. Say which conference days it includes, whether meals are included and whether workshops need separate booking. A recipient shouldn't have to discover a compulsory extra payment after accepting. Optional activities can remain optional, provided the main experience is complete as described.

Travel support needs its own terms. Decide which journeys qualify, who approves an amount, what evidence is needed and when payment happens. Someone offered a capped reimbursement needs to know whether they can commit to a fare before approval. An instruction to save receipts isn't an approval to spend whatever the journey costs.

Accommodation is another separate commitment. A room booking made by the organizer behaves differently from a fixed lodging allowance or a reimbursement. Explain the nights covered, any sharing arrangement and how someone can raise a practical concern privately. Avoid assuming that every recipient can share a room with a stranger or stay at the same property.

A current example is PyCon DE & PyData's 2026 financial aid programme. It distinguishes tickets from travel and accommodation support, and describes travel reimbursement after the conference. That is one organizer's published arrangement, not a model every conference should copy. The useful lesson is to state each part of the award separately.

For your own programme, ask what happens before the recipient arrives. If reimbursement comes afterwards, explain that prominently. Consider whether an approved direct booking or a different support arrangement is possible for someone who cannot advance the money. Don't promise that exception until finance can deliver it safely and consistently.

Include a private route for accessibility requests alongside the scholarship process. Receiving a scholarship should not become the condition for asking about access. Some requirements concern how the conference operates for attendees generally, and need an event-level response. Your scholarship budget and your broader accessibility responsibilities are related decisions with different purposes.

Give the programme a real budget

Start with costs the organizer will actually pay. For each scholarship attendee, include catering, materials and any other charges that increase with their booking. Then add the work of administering applications, communicating decisions, arranging support and checking payments. Existing staff can do that work, but their available hours still have limits.

Some expenses arrive in steps. A few extra attendees might fit within the existing room and crew plan, while a larger allocation requires another room, more transport or another staff shift. Ask suppliers about those thresholds before multiplying one attendee cost by the number of places. A cheap additional ticket can trigger an expensive additional commitment.

Now separate cash spending from the ticket income you may give up. If there is unused capacity and the recipient wouldn't otherwise buy, the conference mainly incurs the extra cost of serving them. If their place displaces a paid buyer, the event also loses the contribution that paid booking would have made. Those are different forecasts.

Our event break-even guide explains the underlying calculation. For scholarships, keep a separate note of the attendance allocation and the funding allocation. Ten places can mean ten full awards or ten tickets with different support amounts. Don't let one headline count conceal a promise your cash budget cannot support.

Imagine a conference with 300 attendee places available after the organizer has accounted for other capacity commitments. Fixed conference costs are $30,000. A regular ticket leaves $200 after applicable transaction charges and taxes, and serving each retained attendee costs $40. Each paid ticket therefore contributes $160 towards fixed costs and profit.

Without scholarships, the organizer expects 240 paid bookings. Those bookings contribute $38,400, leaving $8,400 after fixed costs. The unused 60 places are available capacity, not a prediction that another 60 people will buy. That distinction matters when the organizer considers reserving some of them for applicants.

Suppose the programme offers 20 ticket-only scholarship places and allows $600 for application administration. Serving 20 recipients costs $800. Together, those direct programme costs are $1,400, reducing the forecast profit to $7,000 if all 240 paid bookings still happen. This forecast assumes every scholarship place incurs the service cost once confirmed, even if somebody later misses the event.

The cash required is manageable in this invented case, but the organizer still needs to approve it. An event with a smaller margin might need fewer places, a sponsor or a different package. Generosity isn't measured by selecting a number before checking whether the event can deliver it.

Check the cost when paid demand is stronger

Now consider a different forecast for the same conference. Suppose the event could sell all 300 places at the regular retained price. With no scholarship allocation, 300 paid bookings contribute $48,000. After fixed costs, the event would make $18,000 under the assumptions already stated.

Reserve 20 places for scholarship attendees and paid capacity falls to 280. The paid bookings contribute $44,800. Subtract $800 for serving recipients, $600 for administration and the same $30,000 fixed costs. The resulting profit is $13,400, or $4,600 below the all-paid case.

That $4,600 consists of $3,200 in paid-ticket contribution given up, plus the $1,400 direct programme cost. Don't add the full $4,000 retained ticket value again. The $160 contribution already accounts for the paid attendee's $40 service cost, and the scholarship attendee's service cost has been included separately.

The decision isn't whether scholarships are worthwhile only when seats would otherwise be empty. You may deliberately reserve access even for a conference with strong demand. The decision is whether the business approves the full trade and has a funding plan for it. A sellout should not force you to withdraw places already promised.

Add travel assistance and the calculation changes again. Suppose eight of the 20 recipients receive an approved $150 travel allowance. That adds $1,200 of spending, taking direct programme cost to $2,600. The original 240-paid-booking forecast now leaves $5,800 profit. The full-demand forecast leaves $12,200, which is $5,800 below the all-paid comparison.

Those allowances are invented for the example. A flat allowance might be too little for one journey and unnecessary for another. You could instead approve actual costs up to a cap, but then forecast the maximum commitment before issuing awards. Unspent allowances are a later saving, not money to promise to another applicant before you know it is available.

Run both demand cases before approving the programme. Also identify when you will stop releasing unclaimed scholarship places and what happens to them afterwards. A place doesn't become available for public sale while an applicant still has an active acceptance window. The allocation record needs to govern every route into that capacity.

Fund the award without selling the recipients

A sponsor can pay for scholarships, but agree what the sponsor is buying before accepting money. A named programme credit, an acknowledgement on the conference site or an aggregate delivery report can be reasonable commitments. Applicant essays, financial details and private contact information shouldn't become an assumed extra benefit.

State whether the organizer or sponsor chooses recipients. My preference is for the organizer to apply the published criteria and keep individual decisions separate from the sponsor's sales interests. If the sponsor has a legitimate role in selection, explain that role before applications open and limit the information shared to what is justified for it.

Use the actual amount available after payment charges and the costs of delivering the sponsorship. A payment described as funding 20 places may also require design work, reporting or an activation. Those costs reduce what is available for attendees. Our guide to pricing event sponsorship packages helps you assess that commitment before quoting it.

Loopyah's event sponsorship tools let organizers create priced packages with defined perks and quantities, including packages that require organizer approval. That can help you sell and track the funding agreement. It doesn't decide scholarship eligibility or turn a sponsorship application into an attendee scholarship application. Keep those responsibilities clear in your own process.

For the worked conference, suppose a sponsor provides $2,000 net of transaction charges and there is another $300 of delivery work. The funding available for the scholarship programme is $1,700. Against the $2,600 direct cost including the eight travel allowances, the organizer still needs to fund $900. Foregone paid-ticket contribution remains a separate consideration in the strong-demand case.

Decide what happens if the sponsor doesn't pay on time. You can make the programme conditional before opening it, secure organizer funding or reduce the offer before anyone receives an award. Once you've made an unconditional commitment, a delayed sponsor payment is your problem to resolve. Don't pass it to a recipient who has already booked their journey.

Ask separately before using a recipient's name, photograph or story in publicity. Declining should not quietly affect their award or access. You can report how many places were used without asking people to explain their financial circumstances in public. Give the sponsor evidence of delivery that respects the promise made to applicants.

Check the costs beyond the ticket

Before writing the application, ask which expenses could still prevent someone attending. Travel, accommodation, care responsibilities and time away from paid work can remain after the admission charge disappears. You may not be able to fund all of them. You do need to explain what your offer covers early enough for someone to decide whether applying is worthwhile.

Loopyah's research gives some wider context for that decision. In the Worth It Event Index, respondents selected unclear details and high price for unclear value among reasons an event didn't feel worthwhile before buying. A scholarship removes a stated ticket charge, but recipients still need to understand the programme and practical arrangements.

Source: Loopyah Worth It Event Index, Q14, Pollfish survey of 500 US consumers, fielded February 11, 2026. These are unweighted respondent shares for three selected answers in a multiple-selection question. They aren't a complete ranking or evidence of conference scholarship demand, applicant circumstances or travel costs.

For an applicant, practical clarity means knowing when the event starts and ends, what the award includes and when a decision arrives. If travel is excluded, say so next to the application link. If only the main conference is included, show which workshops or social events sit outside it. Don't make the offer sound broader to attract more applications.

Use the application window to leave time for real arrangements. Work backwards from travel booking, visa needs where relevant, employer leave and accommodation deadlines. A programme designed around the organizer's final sales push can leave recipients with too little time to attend. Set dates for the people using the award as well as the people reviewing it.

Publish eligibility and selection rules people can understand

Eligibility decides who can be considered. Selection decides who receives support when there are more eligible applicants than awards. Keep those ideas separate. Someone can meet every eligibility condition and still miss out because funding is limited. Explain that possibility without suggesting they failed to show sufficient hardship.

For the example programme, eligibility might require a relevant interest in the conference subject, a financial barrier to attending and no employer funding for the same costs. Specify whether students, unemployed people and self-employed applicants can apply. Employment status alone doesn't tell you someone's ability to pay, so avoid treating it as a complete financial assessment.

Choose selection criteria that serve the stated purpose. You might consider whether the programme is relevant to the applicant's goal, whether the requested support would make attendance feasible and whether other funding is available. A concise explanation of those factors is more useful than asking applicants to write the most moving account of their circumstances.

If you plan to restrict eligibility by age, nationality or another personal characteristic, check the rules that apply to your event and funding arrangement before publishing. Don't copy restrictions from another conference as if they are automatically appropriate everywhere. You can define a focused programme without improvising legal conclusions about who may be excluded.

Publish how ties will be handled. A documented random draw among equally prioritized eligible applicants may be easier to explain than making tiny distinctions between similar applications. If you use that approach, define who runs it and how the result is recorded. Don't switch methods after seeing which applicants would benefit.

Set a correction route for factual mistakes and missed information. That doesn't need to promise a full new assessment whenever somebody dislikes the outcome. Say what the team can review, how to contact them and when the allocation becomes final. A clear boundary is kinder than an open-ended promise your small team cannot honour.

Explain the sponsor's involvement, if any, in the same place. Applicants should know who will see their answers and who makes the final decision. Don't make them infer that from a sponsor logo. The public explanation and the reviewers' instructions should describe the same process.

Ask for the minimum information needed

A useful application is short enough for someone to complete without treating it as unpaid project work. Ask for their name and contact details, their connection to the conference subject, the support requested and a brief explanation of the barrier. Tell them that concise answers are welcome. Strong writing shouldn't become an accidental selection criterion.

The UK's Information Commissioner's Office explains data minimisation as collecting information that is adequate, relevant and limited to what is necessary for the purpose. Its guidance is under review following UK legislation. Apply the rules relevant to your programme, and decide why you need each field before adding it.

Avoid requesting bank statements, identity documents or detailed medical information by default. If a funder genuinely requires evidence, establish the need, access controls and retention arrangements before collecting it. Explain the requirement clearly and provide a safe route. A public upload field isn't a substitute for deciding who should hold those documents.

Health and other sensitive information can create additional obligations. The ICO's guidance on special category data explains that UK processing needs an ordinary lawful basis and an applicable special-category condition. That page is also under review. Don't assume an optional checkbox makes any collection appropriate.

You can often ask a practical question without asking for a diagnosis. "Would any additional arrangement be needed for you to attend? Contact our access coordinator privately" gives someone a route to help. Keep access arrangements separate from the review score unless a justified part of the published funding purpose requires particular information.

Explain the privacy arrangements in ordinary language beside the form. Name the organizer, say why information is collected, identify who can access it and link the full notice. State whether sponsors receive anything identifiable. Keep marketing sign-up separate from the application so a request for assistance doesn't become an unnoticed mailing-list subscription.

Use W3C's accessible forms guidance when checking the application. It recommends clear labels, instructions and feedback, among other measures. Test the actual form with a keyboard and a phone. Make required fields obvious, confirm successful submission and provide a contact route if somebody cannot use the form.

An application confirmation should say that submission doesn't reserve a conference place. Give the decision date and explain how to correct a mistake. Otherwise, someone may book travel believing their application receipt is an acceptance. That confusion is easy to create when the confirmation screen looks like a ticket confirmation.

Use a short application template

Here's an example you can adapt after deciding the programme's rules. It assumes a main-conference ticket award with travel support requested separately. Replace every programme-specific detail before using it. The form should reflect the support you can actually deliver, including any limits that change whether someone can attend.

• Name and email address for application decisions.

• What connects you to this conference's subject, and what would you like to learn or do there?

• Would paying the standard ticket price prevent or materially limit your attendance? Please give a brief explanation; detailed financial documents are not requested in this form.

• Is an employer or another organization paying for the same attendance costs? Explain any partial support so we can assess the remaining request.

• Which support are you requesting: conference ticket only, or conference ticket with consideration for travel support?

• If travel support is requested, what journey would you need to make, what amount are you requesting and could you attend if support were reimbursed afterwards?

• If offered the stated package, do you expect to be available for the conference dates? Tell us if something still needs confirmation.

• Is there a factual detail you'd like us to clarify before deciding? For private accessibility arrangements, use the separate contact route.

After those fields, show the eligibility rules, decision date and privacy notice again in a concise form. Don't require applicants to make a declaration that contradicts what you've asked. For example, someone with partial employer support should be able to describe it honestly rather than tick a box saying they receive none.

A final acknowledgement can confirm that the information is accurate to the applicant's knowledge and that they understand the award isn't guaranteed. Keep agreement to the conference's conduct rules clear and proportionate. Don't bury photography permission, sponsor contact permission or an obligation to post about the event inside that acknowledgement.

Give the contact person a prepared answer for questions about proof. If your published form says documents aren't required, reviewers shouldn't start requesting them casually by email. Any justified additional check needs a consistent process, a clear reason and a secure handling route. Tell the applicant what happens if they cannot provide the requested information.

Consider an alternative submission route for someone who cannot use the form. The team can record equivalent answers without rewarding or penalizing that route. Explain how the deadline applies and who confirms receipt. Accessibility works only when the alternative route reaches the same review process as the standard one.

Review consistently and manage conflicts

Before applications open, appoint the people who will review them and give those people the criteria in writing. Run a practice review using fictional answers. If reviewers interpret a criterion differently, fix the wording before real applicants depend on it. A numerical score cannot rescue a question nobody agrees how to assess.

Keep the first eligibility check factual. Is the application within the stated window? Does it meet the published conditions? Is information missing that the applicant should have an opportunity to correct under your rules? Record the reason for each decision in language another reviewer can understand. Avoid private labels such as "not our kind of attendee."

For eligible applications, assess the agreed selection factors. Two reviewers can reduce reliance on one person's judgment when the programme is large enough to justify the work. For a small programme, a second person can at least check borderline decisions and conflicts. Choose a process the team can finish before the promised decision date.

Ask reviewers to declare relationships with applicants. A colleague, client, friend or family member creates an obvious reason for another reviewer to handle the decision. Record the reassignment and restrict unnecessary discussion. The point is to make decisions defensible without asking applicants to guess which personal connections helped somebody else.

Keep private application answers out of casual team channels. Reviewers need access to the information necessary for their role. The catering lead needs dietary requirements through the appropriate process, while the door team needs a valid ticket. Neither needs the essay explaining why a recipient couldn't afford the conference.

Don't let a sponsor replace the published process with a late list of preferred names. If a sponsor wants additional guest tickets, handle that as a separate allocation within capacity. Scholarship places already promised to an open application process shouldn't quietly become client hospitality. Explain that boundary in the funding agreement before it becomes uncomfortable.

When the budget supports different packages, review both suitability and cost. An applicant might qualify for a ticket but need travel support that has already been allocated. Don't send an award framed as complete attendance support when it leaves a known barrier unresolved. Offer the precise package available and let the person decide without pressure.

Turn decisions into confirmed attendance

Send each successful applicant an offer describing exactly what has been approved. Include the conference days, included activities, any travel amount and its payment method, excluded expenses, the acceptance deadline and the person to contact. If further travel approval is needed, say that they should wait before making the relevant booking.

An acceptance deadline needs enough time for somebody to read the message and check arrangements. Publish the window before applications open and use a specific date, time and time zone in each offer. Send a reminder through the agreed contact route before releasing a place where your process allows it. Don't use a deliberately short deadline to manufacture urgency.

Separate acceptance from ticket issuance in the record. An applicant may say yes but fail to complete the booking step. Someone else may receive a ticket but still need a travel decision. Keep each unfinished task visible so the team can follow up before the event. An award count alone won't reveal those gaps.

Loopyah's ticketing tools support event ticket types and ticket confirmation. Use the verified ticketing route to give each accepted attendee valid admission, while keeping the scholarship decision and private application information in the controlled process you've chosen. Don't assume ticketing automatically scores applications, approves grants or reconciles travel reimbursements.

Test the exact recipient journey before sending offers. Check the ticket's included access, quantity limit and final amount due. A fully funded ticket shouldn't unexpectedly request payment. Verify what happens if a link is forwarded or used twice, and choose a supported way to control issuance rather than trusting a sentence asking people not to share it.

Count scholarships within the same overall attendee capacity as regular tickets. If you hold 20 places, the public allocation must respect that hold. When one offer expires, confirm that it is no longer active before offering the place to someone on the waiting list. An old link that still issues admission can create two promises against one place.

Give recipients the same practical arrival information as other attendees. The badge and check-in experience shouldn't announce their funding status. If support requires a private finance appointment, arrange it separately and discreetly. Receiving assistance shouldn't mean explaining the award again to a volunteer at a crowded entrance.

Handle waiting lists, withdrawals and changes

Tell unsuccessful applicants whether they are declined or still being considered if a place becomes available. Those messages mean different things. A waiting-list message should explain whether any action is needed, when the list closes and that it is not an invitation to book travel in anticipation of an award.

Allocate returned places using the method you published. If timing now matters because a recipient would have to travel tomorrow, explain how that affects feasibility. A late offer might reasonably be usable only by someone local, but you should record the operational reason and avoid claiming the original ranking alone determined the result.

Ask recipients to tell you if they can no longer attend and make that easy to do. Don't impose a penalty simply to discourage honest withdrawals unless a justified, clearly disclosed arrangement requires it. People facing financial barriers may also face uncertain work, care or travel circumstances. A quiet withdrawal is more useful than an unused place nobody felt able to return.

Check what happens to approved expenses after a withdrawal. A ticket can be cancelled while a non-refundable journey remains a cost. The support terms need to explain whose commitments are covered and which bookings require approval. Handle each case against those terms rather than assuming no attendance means no liability or no support payment.

Conference cancellation or a major date change needs its own response. Recipients still need prompt information even if they paid nothing for admission. Identify what happens to organizer-booked travel, accommodation and approved claims. Keep the scholarship team involved in the wider change response so those attendees aren't omitted from a paid-buyer communication list.

If somebody already bought a regular ticket before applying, publish whether they can be considered and whether an award would change that booking. Don't promise an automatic refund or reimbursement unless the policy and ticketing process support it. Resolve the old paid booking and the new award together so the attendee doesn't end up with duplicate admission or an unexplained balance.

Keep one owner for exceptions. They should record the decision, the reason, the remaining funding and any capacity change. This prevents a friendly answer from one colleague becoming an unfunded promise for another colleague to deliver. An exception can be compassionate and still be documented properly.

Review what people could actually use

After the conference, compare applications, offers, acceptances, valid tickets and attendance. Those counts answer different questions. A programme can attract many applications and still have low attendance if decisions arrive too late or travel support doesn't solve the remaining barrier. Don't report the application total as people helped to attend.

For example, suppose 20 offers lead to 18 acceptances and 17 issued tickets, with 15 recipients attending. Report each stage honestly. Investigate the missing ticket and the two issued tickets that weren't used. That doesn't automatically mean the programme failed. It tells you where to ask whether clearer messages or a different support arrangement would have helped.

Reconcile the actual spending as well. Compare approved travel amounts with paid claims, list any outstanding amounts and keep the money available until those commitments are resolved. Confirm whether the $600 administration allowance in the example matched the work involved. A programme funded within its attendee budget can still demand more staff time than you planned.

Ask recipients for optional feedback about the process. Were the application questions understandable? Did the decision leave enough planning time? Were any stated benefits unavailable? Keep the request brief and explain that answering won't affect payment of an already approved claim. Avoid making a testimonial the price of receiving the remaining support.

Report to sponsors using agreed aggregate measures. For a small cohort, even a breakdown without names can identify someone when combined with public information. Use broader descriptions where needed and leave out details that serve no delivery purpose. Our guide to attendee data and sponsor consent covers that wider boundary.

Set record retention by purpose. Application narratives, award decisions, financial records and attendance records may need different treatment. The ICO's storage limitation guidance says UK organizations must justify how long they retain personal data rather than keep it indefinitely. That guidance is under review; check the requirements that apply to your own records.

Keep enough information to resolve claims and explain decisions for the justified period, then delete or anonymise what is no longer needed. Don't retain private hardship accounts because next year's marketing team might want a story. Preserve the useful operational learning separately, such as decision timing, hours required and the gap between offers and attendance.

Write the programme promise before opening applications

Before launch, read the offer as somebody deciding whether they can afford to attend. Can they tell what they will receive, what they still need to pay, when they will hear back and what happens next? Ask a colleague outside the selection team to follow that journey. Fix unanswered practical questions before collecting applications.

Then check it against the event budget and ticket allocation. Name the person authorized to approve support, the money reserved for it and the last date places can move between scholarship and public inventory. Confirm that finance, ticketing and attendee support have the same version. A clear public offer needs an equally clear internal commitment.

You don't need a large programme to do this well. A small number of properly funded places, awarded through a process people can understand and use, is a reasonable starting point. Approve the attendance package and its full cost first. Open applications when your team can deliver the answer it is inviting people to ask for.