Spark HouseWhere Creativity WorksVolunteer Sign InSpark House volunteer field guide
Use your care, curiosity, and ChatGPT to create something another person can check, improve, and use.
Public learning guide · September 2026 · No private records needed
01Choose a contribution
Agree on one task and a named reviewer. Observations and suggested wording are useful contributions, even without repository access.
Find a public instruction that leaves you wondering what to do next.
Improve this one instruction for a new volunteer. Preserve the approved facts. Show the original, your suggestion, and anything that needs checking.
Try a public page on a small screen or using only a keyboard.
Turn these observations into a clear issue report. Include steps, expected behavior, and actual behavior. Do not invent a cause or claim a test was run.
Check a citation, date, or statement against its original source.
Check this claim against the approved source. Identify what supports, qualifies, or challenges it. State exactly what you read and preserve uncertainty.
Take an assigned, bounded change with a result someone can test.
Make this assigned change in the canonical SparkHouseMN/sparkhouseplatform repository. Preserve permissions, concurrent work, and license notices. Update the relevant documentation and changelog. Run relevant checks and explain what changed and what remains unverified.
Repository access is a separate maintainer decision. Send your work to your coordinator if you do not have approved repository access.
02From idea to reviewed addition
Your designated reviewer checks the proposed change. Adoption, publication, access, merge, and release follow their existing approval processes.
One visible result
Name the audience, deliverable, coordinator, and reviewer. Agree on what finished means.
Only the needed context
Check your account, workspace, host, written role, and approved sources. Practice with fictional records.
One coherent draft
Reuse existing pages and records. Keep independent tasks separate and give a shared document one writer.
Evidence before confidence
Verify facts, links, rights, and privacy. Try the result. Record what you checked and what you could not.
A reviewer can take over
Save the artifact in its approved location. Include decisions, checks, uncertainties, and the next action.
“The link opens the correct guide” gives a reviewer something concrete to check. Use that level of clarity when defining your task.
03Plans at a glance
Personal and organizational plans serve different needs. Compare who manages the work separately from how much Work and Codex usage is included.
One person chooses their own subscription.
$0/ month
Explore the tools
Check the current included limits.
$8/ month
Light use
Check the current included limits.
$20/ month
Regular individual work
The 1× comparison baseline below.
From $100/ month
More individual capacity
Choose a 5× or 20× option; verify its price.
People, administration, and the organization’s agreement.
$20/ user / month, billed annually
$25 per user on monthly billing. Minimum 2 users.
Essential administration, SAML SSO, MFA, and no training on business data by default.
Contact sales
Additional organization controls, including SCIM and role-based access. Allowance and billing depend on the agreement.
Published USD prices checked September 22, 2026. Confirm regional checkout, taxes, and current seat terms. Official pricing.
Each filled square is one unit of the published comparison index.
A larger Personal Pro allowance can explain the difference you feel. Standard Business matches the Plus estimates. Business buys organizational features; its name alone does not promise more usage.
This index is not quality, speed, context size, credits per dollar, or guaranteed messages. Free and Go have no comparable index here. The Business $100 option uses Pro 5× estimates; verify eligible seat terms. Enterprise varies by agreement. Source and current limits.
04Organize people and work
Start with one Spark House Business workspace and projects for approved work areas. Add another workspace when independent ownership, administration, or funding calls for it.
Membership, seats, administrators, and the applicable budget.
One named identity for each volunteer.Keep related approved sources together. Give each distinct outcome its own chat.
Project names do not enforce access.Use the approved host and connected account for the task.
Device and source permissions are separate.This diagram describes activity within the selected account/workspace; it does not pool Personal and Business balances. Remote pairing requires the same account and workspace, plus host and source permissions. Remote setup · Usage rules.
These are suggested work areas, not existing grants or promised Business features.
Active volunteer status, written roles, training, and administrator decisions govern Spark House operations. A workspace seat does not grant portal, GitHub, Drive, or Metricool access.
A shared connection may use an account with broader permissions than your own. Confirm which identity supplies access and what it is approved to do.
Read the OpenAI access boundariesPersonal
Personal can mean Free, Go, Plus, or Pro. Keep personal learning and experiments separate from restricted Spark House work. Review your current Data Controls.
Business
Business adds membership and administration, SAML single sign-on, multi-factor authentication, and no training on business data by default. Granular Enterprise controls are not all included.
Keep private work in approved organizational systems even if a Personal allowance is larger. Before merging or migrating workspaces, verify what moves, reversibility, ownership, and departure/export options in the current account.
Check the current plan comparisonRemote connections help you reach approved files and tools, continue a task away from a desk, and use a dedicated workstation. Pairing requires the same ChatGPT account and workspace; workspace membership does not automatically let colleagues control your host.
Remote does not turn ChatGPT into an offline AI service. More devices do not multiply an account’s allowance.
Read current Remote setup instructions05Make time and credits count
Judge a workflow by useful outputs accepted by reviewers, clear evidence, and manageable rework. A longer conversation is not the measure of success.
Start with the correct comparison
Check the active workspace and actual seat tier. Then compare equivalent tasks, model settings, and reporting periods.
Compare the plan tiersThe recurring plan charge for each licensed person.
Included usage or an eligible workspace allocation. Other eligible activity may draw from that pool.
Your agreement, purchases, and billing controls determine what is charged.
API-key work has a separate bill. Platform API usage follows API pricing and billing. A ChatGPT subscription does not make it free.
Consuming committed credits does not automatically add the same amount to an invoice. Work usage and cost · API-key authentication.
Assume an identical task would use 20 credits at Standard speed. Switch the setting to see the 2.5× credit rate for supported GPT-5.6 Fast mode.
This changes the illustration only. It does not change your model, speed, subscription, or billing.
Illustrative budget 100 credits
example tasks covered
at the assumed cost
Real task cost varies with tokens, tools, context, and caching. This is not a message quota, balance lookup, invoice estimate, or guaranteed speedup. API-key rates differ. Current speed rates.
Read the exact message first. Then follow the matching path.
“Limit reached” or a reset / balance message
Check the plan, reset time, balance, other activity, and any administrator cap.
If a reset time is shown, wait for it. For exhausted credits or an administrator cap, ask the budget owner to review approved capacity.
Starting another chat does not refill this meter.
A thread length or context warning
Save the verified result, decisions, source references, and next action.
Continue in a focused new chat with that handoff and only the necessary sources.
Compaction summarizes; it is not unlimited verbatim memory.
Host unavailable, upload rule, or permission message
Check host availability, file requirements, the connected identity, and permissions.
Resolve the specific connection or access issue with the responsible person.
More credits may not fix this problem.
No universal “Business threads are smaller” rule is established here. Record the app, model, workspace, time, and exact warning without private content. Context and compaction · Troubleshooting.
Compare the same sample task, model, reasoning, speed, environment, and reporting period. Check actual usage, concurrent work, and billing settings before buying capacity.
Understand usage and billing · Check speed ratesCheck the active plan, reset time, credit balance, shared activity, and any administrator cap. A new chat does not refill the allowance.
Save a verified handoff and continue in a focused chat with only the needed sources. Compaction summarizes older context; it is not unlimited verbatim memory.
Check the file rule, host availability, and tool permissions. Purchasing credits may not address the cause.
There is no verified universal rule here that Business threads are smaller than Personal threads. Record the exact warning, model, app version, workspace, time, and attachments. Keep private content out of support examples.
Read about context and compactionUse named accounts and approved seats for the people doing the work. A scanning station is not a shared volunteer identity. Track seats, active assignments, renewal dates, device custodians, and budget owners in the existing account inventory.
Illustrative eight-seat budget: at the September 21, 2026 standard Business prices, eight seats are $1,920 per year on annual billing ($160 monthly equivalent), or $200 per month on monthly billing. Variable credits, API usage, provider licenses, and taxes are separate. Confirm current checkout and renewal terms before purchasing.
Start with a small pilot. Review outputs alongside consumption, remove obsolete access when roles change, and preserve approved deliverables before departure. Supported alerts notify; they are not spending caps. Separate workspace credit controls from Platform API billing.
Seat options and administrative controls vary. Do not assume a new Business workspace can use Codex-only seats or Enterprise custom roles.
Current prices · Seat eligibility and departure06Make the next step easy
A useful handoff lets another volunteer continue without reconstructing your whole conversation. Use this outline in the approved record system.
Use fictional examples. Keep private submissions, account records, credentials, private notes, and dissertation file references out of public outputs.
For research, use Spark House’s established foundations, identify the relevant question or hypothesis, and distinguish supporting, qualifying, and challenging evidence. Citation metadata is not a full-text reading.
Save new or changed publication snapshots and reading assessments in the existing pending review process. Content and insight permissions stay separate.
Drafting, publishing, sending, granting access, and enabling an integration are distinct decisions.
07Keep the full reference
Eight benefits, workspace comparisons, device guidance, credit diagnosis, licensing examples, and joining and leaving checklists.
Plan, allowance, and speed visuals were checked September 22, 2026. Other handbook sources were checked September 21, 2026. Verify current plan settings before procurement. Team structures and budgets are recommendations; existing Spark House administrator decisions remain authoritative. The reported Business billing settings and exact thread warning were not inspected.
This public guide grants no role or private access. Begin assigned work through the volunteer portal, or learn about volunteering.