A ChatGPT Business Standard seat costs $25 per month on monthly billing or $20 per month equivalent on annual billing, before local pricing and tax. Premium costs $125 or $100 respectively. To cut seats safely, identify unused paid capacity, move finished work into business records, remove only the right members, then schedule a seat reduction for the next billing cycle.
A seat is paid capacity, while a member is a person assigned to it. Removing a member ends that person's access but leaves the seat on the subscription until an owner reduces it. On an annual plan, added seats remain committed to the end of the current annual term. Treat renewal as an access and work-handover audit, not simply a headcount subtraction.
Read three counts before deciding who leaves
Open the intended Business workspace, then Workspace settings > Members and Billing. Record the number of paid Standard seats, paid Premium seats and people occupying them. Include unassigned paid seats. OpenAI says a pending invitation does not reserve a seat and an unused paid seat may be reassigned without another purchase. The gap between paid and occupied capacity is your first possible saving; it is not evidence that a person should lose access.
Use a ledger with columns for member, role, seat type, occupied or vacant, principal tasks, last useful output, shared project ownership, manager, action and renewal date. This is a business record, not an OpenAI report. Ask each manager to confirm whether a person actually needs the workspace next term. Usage analytics can help locate questions, but OpenAI says they do not give owners automatic access to private chat transcripts. A quiet account may be doing a monthly critical task; a busy account may be producing drafts that nobody uses.
An illustrative removals firm has six paid Standard seats on monthly billing but only four current members. At OpenAI's USD list rate, the subscription is $150 a month, while four Standard seats would be $100. Scheduling two reductions would lower the next full-cycle list total by $50 a month, or $600 over twelve full months if rates and demand stayed the same. Those are arithmetic examples before local price, tax or credits. The saving begins at the next cycle, not on the day the owner clicks Remove member.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowFind the work that cannot vanish with access
Before removing a member, distinguish three kinds of work. A finished customer-facing document should already be in the firm's normal document store. A shared project may contain instructions and files that colleagues need to continue. Private chats are personal to the member within the workspace and are not automatically readable by an owner. OpenAI says removal reassigns projects and GPTs to an owner, but that ownership change does not transfer the former member's private conversations and files into the owner's view. Do not plan a handover that depends on reading those chats afterwards. Custom GPTs need a separate plan as well: OpenAI's retirement FAQ says they are scheduled to retire on 11 December 2026, with migration to plugins, so a reassigned GPT is not a lasting home for a process.
Ask the departing person to identify active tasks and produce a handover while they still have access. For each task, capture the business purpose, current status, approved prompt or instructions, source-document location, reviewed output, next action and accountable colleague. Put the final material in a controlled business repository. If a project is shared, check that a remaining staff member can open the necessary instructions and files. Where a conversation contains useful reasoning, ask the member to create a concise, checked summary for the work record rather than rely on a raw transcript.
Illustrative handover entry: “Supplier quote comparison, five quotes received, four checked; final comparison sheet in the purchasing folder; missing delivery surcharge on quote 5; next owner: operations manager; due: next Tuesday. AI draft is not approved as an order.” The entry is useful even if the private chat later cannot be viewed by others. In contrast, “all the work is in ChatGPT” gives no status, source or permission trail. This is the operational reason to hand over before the access change.
OpenAI's current retention help says a removed Business member's chats, files and canvas documents are retained indefinitely and restored to the member if they are re-added, while project and GPT ownership moves to a workspace owner on removal. Retained does not mean accessible to the remaining team. Do not promise permanent recoverability or rely on re-adding a former employee as the firm's records strategy. A member's personal workspace is separate again. If they merged it into Business earlier, leaving or removal does not move those chats back to personal.
Separate vacancy, downgrade and removal decisions
A vacant seat can be retained for a confirmed new hire, reassigned now, or scheduled for reduction. A busy member on Premium might be moved to Standard if their recent work fits Standard limits; that changes usage, not role. A member who no longer needs the workspace should be removed once their work is handed over, with the billable capacity reviewed separately. These are three different actions. Mixing them causes invoice surprises and unnecessary access disruption.
| Finding | Operational action | Billing action | Check |
|---|---|---|---|
| Paid seat vacant, replacement approved | Assign the existing seat to the replacement | No new seat purchase | Paid count unchanged |
| Paid seat vacant, no replacement | Leave it unassigned | Schedule reduction | Pending reduction and effective date shown |
| Member leaving | Complete handover, then remove member | Reduce vacated seat if not reused | Access ends; future count falls |
| Premium user needs less capacity | Move to Standard after testing limits | Schedule downgrade if no spare Standard seat | Pending downgrade or immediate reassignment |
OpenAI's billing guide says that if an unused Standard seat is available, a Premium member can move to it immediately; the old Premium capacity remains paid until separately reduced. If no Standard capacity is free, the Premium-to-Standard downgrade is scheduled for the next cycle. Swapping Standard and Premium between two members can be immediate without changing total capacity. Review pending changes before performing another seat move: OpenAI says a seat with a scheduled downgrade or removal must have that pending change cancelled before it can be assigned, reassigned or swapped.
A tutoring centre illustrates the distinction. It has three Standard seats and one Premium seat. The Premium tutor now only drafts two short weekly updates and has never reached a useful limit. If there is a vacant Standard seat, move the tutor there and schedule removal of the vacant Premium seat. If all Standard seats are occupied, schedule a Premium-to-Standard downgrade for the next cycle instead. Do not buy another Standard seat merely to avoid the pending state; compare the current and future bill first.
Calculate the renewal bill before touching membership
Use the seat type and billing cadence in the current workspace, not the price you remember from an older receipt. OpenAI's current USD list is $25 monthly or $20 annual-equivalent for Standard, and $125 or $100 for Premium. For annual billing, multiply each monthly-equivalent rate by twelve to find the term price. Local checkout amounts and tax can differ, so use the actual billing screen for approval. The currency and tax comparison covers the local invoice question.
Work through an illustrative independent bookshop with five Standard and one Premium seat on an annual plan. Its USD list renewal would be five times $20 times twelve, plus one times $100 times twelve: $1,200 plus $1,200, or $2,400. If the Premium user can work on Standard and one Standard seat is unoccupied, a six-Standard renewal would be six times $20 times twelve, or $1,440. The $960 difference is a list-rate illustration, not a refund on the present annual term. It depends on actually scheduling the right changes before renewal.
Now suppose the shop removes the unused Standard capacity as well, leaving five Standard seats. The next annual USD list total becomes $1,200. That is a further $240 below the six-Standard plan. The owner should check whether a seasonal staff member will return during the next term. If so, retaining one Standard seat may be worth $240 of annual list capacity to avoid a later prorated addition and repeated onboarding. This is a business judgement, not an automatic rule to minimise every empty seat.
Credits and seat fees should be separate rows. A Premium seat with higher included limits is not the same as a blanket authorisation to buy unlimited extra usage. If the workspace has flexible pricing, inspect credit purchases and automatic top-up settings. Add only expected, approved credit spending to the budget. Ask the heavy user for two or three tasks that require the higher limit, and compare their reviewed outputs with the seat difference. The whole-workspace cost guide provides broader seat-mix arithmetic.
Schedule the count change in the owner account
Only a workspace owner can buy, reduce, assign, reassign or change paid seat types. The current OpenAI guide directs owners to Workspace settings > Members > Users > Manage seats for the count and to Billing for the next invoice and pending changes. First reduce the number of occupied seats if necessary; OpenAI says you cannot reduce paid capacity below the occupied count. Then set the new count, review the effective date and confirm. Save the confirmation and check that Billing shows the scheduled change.
A reduction starts at the next billing cycle. For monthly billing, that means the next monthly boundary; for annual billing, the next annual term. It does not ordinarily create a refund for an unused portion of the present term, though legal rights or approved exceptions may apply. If an annual seat was added partway through the year, OpenAI says it was billed prorata at addition and remains committed through term end. That is why the renewal audit should start early enough to collect handovers, test Standard usage and review the pending change before the charge date.
Illustrative calendar: an annual workspace renews on 30 November. The owner asks managers for the seat ledger by 1 November, collects handovers by 10 November, tests the Premium downgrade by 15 November and confirms the pending seat changes by 20 November. Those dates are a planning example, not a vendor cut-off promise. The actual workspace's renewal date and checkout terms govern. A late decision can leave the organisation paying another term for seats it meant to remove.
Reconcile removal with access and privacy
Removing a member is an access decision. OpenAI says it revokes workspace access immediately; billing capacity remains. Before clicking it, verify the right account, a completed handover, the status of connected apps, shared project membership and whether the person is the last owner. Admins have some removal permissions, but an owner should control the billing follow-through. When removal is done, ask a remaining colleague to open the handed-over project and confirm the needed files and instructions are available.
For a landscaping company, a departing estimator may have a private chat that drafted a quote. A remaining employee should not assume that reassigning the estimator's seat gives access to the old chat. The proper handover is the checked quote in the estimating system, source measurements in the job folder, and a note of assumptions such as surface area and labour hours. If the estimator used a connected account, revoke access at the source service as well as in the AI workspace where applicable. Seat reuse is not data transfer.
Where export matters, check the actual Business workspace before removal. OpenAI says members cannot self-export Business data through Data controls; another help page says owners may export a member's data if an Export data option is available. The general FAQ is less specific. These pages do not establish that every owner can export every item on demand. Record which option is visible and contact support if the handover needs something the UI cannot supply. Keep the firm's final records outside chat so a disputed export does not halt operations.
Check whether the change really saved money
After the cycle boundary, compare the new invoice with the scheduled seat ledger. Check each paid seat type and count, any prorated additions, credits, currency, tax and total. A lower active-member count alone proves nothing. If the invoice still lists an empty paid seat, check whether the reduction was confirmed, whether it was scheduled for a later annual date, or whether another invitation bought replacement capacity. Keep the confirmation screenshot and invoice number for support.
An illustrative before-and-after review shows why this matters. Before: five people, six paid Standard seats, $150 USD monthly list. The owner removes one inactive member and assumes the next bill will be $100. After: four people, still six paid seats, still $150, because no capacity reduction was scheduled. The corrected action is to check remaining occupancy, schedule two seat reductions and verify the next-cycle count of four. The cost target is then $100 USD monthly list, subject to the actual invoice.
Review the work side too. Ask the new task owner to produce one normal output from the handed-over instructions and compare it with the approved format. Check that documents referenced in the handover open under their own account, that no unresolved customer request was stranded in a private chat, and that a saved prompt contains no old staff name or obsolete policy. A cheaper bill with a broken process is a false economy. For a fresh workspace, use the owner's admin checklist before seats are first allocated.
Keep a short renewal decision record
Finish with a one-page record: current paid capacity, occupied capacity, named changes, handover status, planned capacity next term, list-rate arithmetic, actual checkout or invoice currency, effective date and owner approval. Note any person who still needs a seat for a low-frequency critical task. That record lets a later manager understand why an apparently unused seat was kept or why a Premium seat became Standard. Revisit it at the next renewal rather than starting from memory.
The decision is simple once the columns are separate: preserve the work before removing access, reduce paid capacity after the member change, and verify the next invoice. If the organisation is considering moving to another assistant entirely, compare data terms and migration effort before cancelling the workspace; the alternative-plan comparison shows the questions to ask about contracts, processing and retained content.
Handle the awkward two-seat floor
A very small team may discover that its desired count is below the usual two-seat minimum. OpenAI's overview still describes two paid seats as the normal Business requirement, with any mix of Standard and Premium. A newer help page says a single-seat configuration is available to some new workspaces and may remain available to eligible existing ones, but it is limited. The owner should inspect Manage seats for the minimum actually offered to that workspace. Do not create a second workspace solely to chase an eligibility that OpenAI has not promised.
Illustrative case: a two-person tutoring centre loses one tutor, leaving the owner as its only active member. On monthly Standard billing the usual floor is two seats, a $50 USD list subscription. If Manage seats offers reduction to one, the future list total would be $25, but only from the next cycle; the current period is not automatically refunded. If it does not offer one, the owner can keep the second seat for a genuine new colleague, or compare an individual plan and the implications of leaving Business. Before any cancellation, copy approved teaching resources to the centre's normal records and check what the change does to workspace access.
Further reads
- ChatGPT Business vs Claude Team: Seat Costs for a Small Consultancy — See a rival team's seat model.
- ChatGPT Business for One Person: Plus, Pro or the Two-Seat Minimum? — Understand the smallest eligible seat count.
- ChatGPT Business Trial: What to Test Before You Pay — Test whether seats earn their place.
- ChatGPT Business for Law Firms: Seats, Privacy Settings and Cost — What ChatGPT Business costs a small law firm at three sizes, the privacy and sharing settings to fix before the first prompt, and what it cannot provide.
- Free ChatGPT for Accountants: When Client Work Needs a Paid Plan — What free ChatGPT gives an accountant, why ads and training defaults matter for client data, and the rule for moving client work to a paid business plan.
- ChatGPT Business or Enterprise: When a Small Firm Should Upgrade — A practical upgrade test for small firms comparing seats, identity controls, retention, support and the true cost of an Enterprise quote.
- ChatGPT Work Usage Limits and Credits: What a Business Plan Allows — A five-person usage calculation shows where Business seat allowances stop, how workspace credits begin and what owners can control.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: OpenAI Business pricing; ChatGPT Business overview; Managing billing and seats in ChatGPT Business; Managing members, seat types, and roles in ChatGPT Business; Data retention when a member is removed from a workspace; Managing data, sharing, and privacy in ChatGPT Business, checked 5 November 2026.