ER:LC communities run on structure. Police, fire, EMS, civilian operations, dispatch — each with its own requirements, its own training and its own leadership. Trying to run all of that through one Discord form and a pinned message never survives contact with a growing community.
No card required · Free plan available · Set up in an afternoon
Emergency Response: Liberty County
Roleplay
Also searched as
Emergency Response Liberty County · Liberty County · ERLC roleplay · Police Roleplay Community
A different Google Form for every department, all with different questions
No way to require the general application before a department application
Denied applicants reapplying the next day, every day
Guildbase gives your ER:LC community a proper intake system: one branded portal, a separate application for each department, exams before certification, interview stages, and Discord roles applied automatically when someone is accepted.
Every one of these is its own template with its own questions, requirements, reviewers and workflow. Build the ones you need and ignore the rest.
The base application everyone completes before applying to a department, covering rules, roleplay experience and expectations.
LEO intake with radio procedure, traffic stop scenarios and a required interview before certification.
Fire and medical intake with scenario questions and its own reviewer team and certification exam.
Intake for civ roles, including scenario ideas and an understanding of what makes civilian roleplay work for everyone else.
Recruit session moderators and administrators, with situational judgement questions and an exam on your rules.
Recruit the people who run sessions and hold dispatch, with availability and past hosting experience.
The features that matter when you are running intake for Emergency Response: Liberty County, not a generic form builder.
Require an accepted community application before a PD, fire or EMS application can be submitted, so departments only review people who already passed the basics.
Attach a timed exam covering radio codes, traffic procedure or your community handbook, with question pools so the answers cannot be passed around.
Add a required interview step to any workflow, with a reviewer assigned to run it and a record of the outcome attached to the application.
Accepted applicants get their department role automatically, with the applicant role removed and their nickname set to your callsign format.
Set a cooldown after a denial so applicants have to wait a fixed period, and block second applications while one is still pending.
Give each department command team permission to review only their own applications, with internal notes that applicants never see.
See the full platform feature list, or compare what is included on each plan on the feature comparison page.
Sign up with Discord, Google or email, create your community and connect your Discord server.
Drag your questions into place, or start from a community template someone has already built for ER:LC.
Decide who can apply, add review, interview and exam stages, and choose which Discord roles get applied at each one.
Post your public page in Discord and your server listing. Applications land in a queue your whole staff team shares.
Browse community templates to start from a form someone else has already built and tested.
Steal these. They are the questions that separate applicants who will stick around from applicants who wanted to see what was behind the form.
Yes. Each department gets its own application template with its own questions, requirements, exam, reviewer team and Discord role on acceptance. You can require an accepted general application before any department application is opened.
Yes. Attach an exam to the application and require a pass before it proceeds. Question pools rotate the questions between applicants, and anti-cheat options are available on paid plans for higher stakes certification.
Yes. Any workflow stage can require an interview, with a reviewer assigned to run it. The outcome is recorded against the application so the rest of the command team can see what happened.
Set an application cooldown of, say, fourteen days after a denial. You can also block applicants who already have a pending application and add requirements based on the outcome of a previous one.
Yes. Workflow actions add and remove Discord roles and change nicknames when an application changes stage, so acceptance and department access happen together.
Yes. The free plan covers one community with two application templates and a small staff team. As you add departments you will want more templates, which is what the paid plans unlock.
Still stuck? The help centre covers setup step by step, or ask in our Discord.
Group, staff and division applications for Roblox communities, with Discord verification and proper review workflows.
Whitelist, department and staff applications for FiveM roleplay servers, with Discord roles and in-game apply built in.
Enlistment, section and specialist applications for Arma 3 milsim units, with basic training exams and rank roles.
Free to start, no card required. Bring your Discord server and your first form can be live today.