Roblox Early Testers First Indie Preview Lab Worksheet 2026

If you searched roblox early testers preview after the October 12, 2026 DevForum announce, you do not need another “invite ten friends and tweet soft launch” thread. You need a fill-in worksheet that locks six decisions before Discord invents a public launch:

1. Experience + age-check lock — named experience; creator age-checked 9+
2. Playtest audience honesty — Manage Audience is Playtest, not Public claimed
3. Roster ≤10 — friends (individual) or Group members with early-tester role rules
4. Safety guardrails — similar age / Trusted Friend / parent-block notes
5. Watermarked preview smoke — at least one tester joins; watermark + feedback note
6. Decision latch — LAB_PREVIEW, HOLD, or PLAYTEST_ONLY — refuse PUBLIC_CLAIM

This URL is that worksheet. It is not the live Stop Treating Roblox Early Tester Invites as Your Public Launch (refusal CapEx). It is not the live discovery measurement Stop. It is not the Custom Quick Words chat lab worksheet. Those own launch refusal, analytics measurement, and chat labs. This URL owns the first indie early-testers preview lab evening.

Why this matters now

On October 12, 2026, Roblox published A Simpler Path to Publish, Plus Invite Early Testers: age-checked creators 9+ can invite up to 10 friends or Group members to preview before Public. Previews carry a watermark. Guardrails include similar-age or Trusted Friend rules and parental controls. Studio path: Collaborate → Early testers tab. Creator Hub path: Configure → Permissions under Collaborators. Audience choice includes Playtest (replacing Private/Limited) versus Public.

October 2026 is when studios either (a) confirm Playtest, build a ≤10 roster with guardrail notes, run one watermarked join, capture feedback, and file a receipt, or (b) invite Discord at random, post “we launched,” and rage when Trusted Friend blocks hit. Without a worksheet, teams skip Manage Audience honesty and confuse early testers with Kids/Select admit.

Direct answer: Fill Sections A–F this week. Confirm Playtest. Cap the roster at 10. Note guardrails. Smoke one watermarked preview. Latch LAB_PREVIEW, HOLD, or PLAYTEST_ONLY. Read the public-launch Stop if Discord is mid-PUBLIC_CLAIM.

Who fills this worksheet

Time: 45–90 minutes first lab (Trusted Friend / parent approvals may add wait — latch pending honestly).
Honest limit: DevForum + Creator Hub are authorities. Do not invent ways around age check, watermark, or the 10-person cap.

Non-repetition

Pair community paste with 25 free game development Discord servers.

Official facts you must quote (not invent)

From A Simpler Path to Publish, Plus Invite Early Testers:

1. Early testers: up to 10 friends (individual-owned) or 10 Group members (Group-owned).
2. Creator must be age-checked and 9+.
3. Preview happens in the Roblox App before the game is public.
4. Every preview carries a watermark; Community Standards + reporting still apply.
5. Early testers must be similar age or Trusted Friends (parents approve Trusted Friend for under-13).
6. Parents of users under 16 can turn off / block early tester access.
7. Studio: Collaborate → Early testers tab → add → Save (notification + optional copy link).
8. Creator Hub: Configure → Permissions → Collaborators early tester list.
9. Group games: one early-tester role (new role or existing role with under 10 members).
10. Playtest vs Public are distinct Manage Audience options; Playtest replaces Private/Limited.
11. Early testers ≠ legacy playtester role (larger groups after ratings / Kids+Select requirements).

Pasteable diligence line:

We are labbing Roblox early testers on a Playtest audience with a ≤10 roster, age/Trusted Friend notes, and a watermarked preview smoke. We refuse PUBLIC_CLAIM. Kids/Select and Public remain separate decisions.

Section A — Experience + operator lock (fill in)

A-gate: If the owner is not age-checked 9+, latch HOLD — do not invent a workaround. Read the Stop before marketing any invite count.

Section B — Playtest audience honesty (fill in)

B-gate: If Manage Audience is blank or you plan to market “live” while on Playtest, fail B. Public is a deliberate flip — not a side effect of ten invites.

Why Section B comes before invites

Discord starts at “add friends.” Diligence starts at “what can strangers on Roblox play?” Writing Playtest first makes the lab a controlled preview, not a silent Public claim.

Section C — Roster ≤10 + path (fill in)

C-gate: Count >10, non-friends on individual games, or “whole group” without a ≤10 role fails C.

Studio path checklist

1. Open Studio on the experience.
2. Click Collaborate (upper right).
3. Open the Early testers tab.
4. Add up to 10 friends (individual) or Group members (Group).
5. Save. Confirm App notification / optional copy link.

Creator Hub path checklist

1. Creations → Experiences → your game → Configure → Permissions.
2. Under Collaborators, manage the same early tester list.
3. Keep count ≤10; sync with Studio if both paths used.

Group role honesty

Section D — Safety guardrails (fill in)

D-gate: Empty guardrail notes with a mixed-age Discord roster fails D. Roblox FAQs list age check, Trusted Friend, Preview setting off, content restrictions, parent blocks, and unsupported regions as join blockers.

Guardrail cheat sheet (from Roblox FAQs)

Section E — Watermarked preview smoke (fill in)

E-gate: “Invites sent” without a join + watermark note is not a lab. Fail E if you only filled the roster. Cropping watermarks for “launch” stills fails E and the Stop.

Tiny smoke ideas (pick one)

Section F — Decision latch (fill in)

F-gate: You may not check PUBLIC_CLAIM as a pass. Pair with LAB_PREVIEW, HOLD, or PLAYTEST_ONLY only.

Gates G1–G8 (developer checklist)

All eight green before you paste “preview lab complete” in Discord.

CapEx four-liner (diligence zip cover)

1. Scope — free early-tester preview under Playtest; ≤10 watermarked joins; not Public launch CapEx.
2. Cost — creator time for roster, Trusted Friend loop, and feedback — invites are free; false launch claims are partner risk.
3. Evidence — Sections A–F + G1–G8 + receipt JSON + optional screenshots.
4. Owner — named LiveOps / tech lead who freezes “soft launch complete” until the Stop honesty ladder also passes.

Beginner first path (45–75 minutes)

1. Confirm you are age-checked 9+ (Section A).
2. Set / confirm Playtest on Manage Audience (Section B).
3. Add ≤10 early testers via Studio or Hub (Section C).
4. Note age / Trusted Friend / parent risks (Section D).
5. Have one tester join; confirm watermark; take feedback (Section E).
6. Latch LAB_PREVIEW or HOLD (Section F).
7. File the receipt. Stop. Do not announce Public launch.

Common beginner mistakes:

• Marketing “we launched” while on Playtest.
• Inviting more than 10 Discord pals.
• Skipping Trusted Friend for mixed ages.
• Ignoring parent Preview settings.
• Treating early testers as the legacy playtester role.
• Using this worksheet as a substitute for the Stop.

Developer depth — failure taxonomy

Anti-patterns (reject in review)

• “Ten invites = soft launch.”
• “Watermark is optional for trailers.”
• “Playtest is Public with friends.”
• “Skip Trusted Friend — Discord is enough.”
• “Legacy playtester docs are dead — use early testers for 50 people.”
• “This worksheet replaces the Stop.”
• “Kids/Select unlocked because friends joined.”
• “Crop watermark for the storefront.”

Worked example (fictional studio evening)

Studio North Gate wants feedback on spawn and a short obby.

1. Section A: Experience North Gate Obby Lab, operator Ava, age-checked Y, goal LAB_PREVIEW.
2. Section B: Manage Audience = Playtest; Public claim refused.
3. Section C: Studio Early testers tab; 7 friends; count 7.
4. Section D: Five similar-age; two Trusted Friend; one under-16 parent note.
5. Section E: Bea joins; watermark Y; feedback: “spawn faces wrong wall; first jump too hard.”
6. Section F: LAB_PREVIEW; PUBLIC_CLAIM refused.

Friday Discord says “Playtest preview with seven early testers” — not “we launched.”

Company diligence appendix

45–90 minute schedule

If age check or parent blocks stop joins, latch HOLD — do not fake E.

Discord shortlist (paste)

Roblox early testers preview lab:
1) Creator age-checked 9+; Manage Audience = Playtest
2) ≤10 friends/Group members via Collaborate or Hub Permissions
3) Similar age / Trusted Friend / parent risks noted
4) One watermarked join + feedback bullets
5) Decision: LAB_PREVIEW / HOLD / PLAYTEST_ONLY
6) Refuse PUBLIC_CLAIM — see public-launch Stop
7) Receipt: roblox_early_testers_preview_lab_receipt_v1.json
Sources: DevForum Oct 12 early testers · create.roblox.com

How this worksheet pairs with the public-launch Stop

QA script (15 minutes after LAB_PREVIEW)

1. Re-open Manage Audience — still Playtest if that was the latch.
2. Confirm early tester count ≤10.
3. Re-join as a tester — watermark still visible.
4. Confirm Discord has no “we launched” claim.
5. Confirm Kids/Select ticket was not closed solely because invites landed.
6. If drifted, flip to HOLD and re-file receipt.

Replace-Public checklist (do before any Public flip)

If any row is N, you are not flipping Public — you are still in LAB_PREVIEW / PLAYTEST_ONLY.

Night-of runbook (Discord says “just invite everyone”)

1. Freeze the claim. Paste: “≤10 early testers on Playtest only — not Public.”
2. Open Section B–C. If audience or count is wrong, stop.
3. Offer this worksheet, not a Public flip.
4. If someone already posted “we launched”: correct the post, latch HOLD or PLAYTEST_ONLY, file receipt.
5. File the receipt the same hour.

Quality ladder

Outsiders can cite the gate table when they need a fillable early-testers preview lab — not a screenshot of ten invite notifications alone.

Receipt — roblox_early_testers_preview_lab_receipt_v1.json

{
  "receipt_type": "roblox_early_testers_preview_lab_receipt_v1",
  "operator": "",
  "experience_name": "",
  "creator_age_checked_9_plus": false,
  "manage_audience": "Playtest|Public|other",
  "ownership": "Individual|Group",
  "path": "Studio|CreatorHub|both",
  "early_tester_count": 0,
  "early_tester_cap_ok": false,
  "guardrails_noted": false,
  "watermark_smoke_pass": false,
  "feedback_bullets": "",
  "decision": "LAB_PREVIEW|HOLD|PLAYTEST_ONLY",
  "refused": ["PUBLIC_CLAIM"],
  "timestamp_local": "",
  "notes": ""
}

decision: LAB_PREVIEW with early_tester_cap_ok: false, manage_audience: Public while marketing claims launch from invites, watermark_smoke_pass: false, or empty feedback_bullets is an invalid receipt.

Key takeaways

1. October 12, 2026 shipped early testers: ≤10 friends/Group members, watermarked preview.
2. Lab on Playtest — do not claim Public from invites.
3. Use Studio Early testers tab and/or Creator Hub Permissions.
4. Age / Trusted Friend / parent controls are part of the lab.
5. Smoke requires a watermarked join + feedback — not invites alone.
6. Latch LAB_PREVIEW, HOLD, or PLAYTEST_ONLY.
7. Refuse PUBLIC_CLAIM.
8. Early testers ≠ legacy playtester ≠ Kids/Select admit.
9. Pair with the live public-launch Stop.
10. File the JSON receipt.
11. Primary keyword: roblox early testers preview.
12. Discovery-measurement honesty stays on its sibling Stop.

FAQ

How do I add early testers in Studio?

Collaborate → Early testers tab → add up to 10 → Save (DevForum).

Can I manage them from Creator Hub?

Yes. Configure → Permissions → Collaborators early tester list.

Does this make my game Public?

No. Confirm Playtest on Manage Audience. Public is a separate decision.

Why can’t my friend join?

Age check, Trusted Friend, Preview settings, parent blocks, content restrictions, or unsupported region — see Roblox FAQs and Section D.

Is the watermark required?

Yes. Every preview carries a watermark. Expect it in smoke notes.

How is this different from the public-launch Stop?

The Stop is the refusal. This worksheet is the fill-in lab with gates and a receipt.

Can Group games invite more than 10?

No. Still capped at 10 via one early-tester role.

What primary keyword does this page target?

roblox early testers preview — first indie preview lab worksheet intent.

Where is Creator Hub?

https://create.roblox.com/dashboard/creations.

Related reading

• Stop Treating Roblox Early Tester Invites as Your Public Launch - 2026 — policy refusal
• Stop Comparing Roblox Discovery Metrics Across Oct 12 Without a Measurement Note - 2026 — analytics sibling (live)
• Roblox Custom Quick Words First Indie Chat Lab Worksheet 2026
• Stop Expecting Roblox Custom Quick Words Without Policy Review - 2026
• Roblox Guide
• 25 Free Game Development Discord Servers

Primary sources: A Simpler Path to Publish, Plus Invite Early Testers · Roblox Creator Hub.

Conclusion

Roblox early testers are real — when you lab them. Confirm Playtest. Cap the roster at 10. Note guardrails. Smoke a watermarked join. Latch LAB_PREVIEW, HOLD, or PLAYTEST_ONLY. Refuse PUBLIC_CLAIM. Keep invite wallpaper out of the launch calendar.

Print Sections A–F. Paste Discord. Treat early testers as measured preview craft — not announce-day soft launches.