Post the job, work the applicants, and put them on a site.
It is February, you need a camp host couple for April, and last year you found them in a forum thread you had to keep checking.
Compose the posting
Workamper, seasonal, year round, part time or contract, with the comp model that fits.
Try the line about families, then publish. The database will stop you.
boards from one posting
checks that will refuse to publish
accounts an applicant has to create
date that ends their access for you
Hiring for a season is not hiring for a job.
They arrive in April, live on your property, hold keys to your office, and leave in October.
Once they are on, they are on the schedule.
A workamper is on the same shifts, time cards and certifications as the rest of your crew, so nobody is tracking half your seasonal team in a different place from the other half.
Certifications sit on the person, so when somebody calls out on a Saturday you know who can actually run the register before you ask them.
See housekeeping and the crewOpen a status dropdown and walk a site through to clean.
Access that ends when the season does.
Front desk and housekeeping access is dated to October 15 and lapses on its own, rather than sitting live in December because nobody remembered to remove it.
Build the rest of it yourself: the reminder before their end date, the offboarding checklist, the note on the site they were seated on.
See workflowsRun history
Nothing has run yet. A test run walks every step for real and sends nothing.
Press test run and watch it walk the steps.
February to October, in six moves.
The whole arc of hiring somebody who is also going to live with you.
Workamper, seasonal or contract, paid as a site, an hourly rate, a stipend, or a mix.
A pay range required in your state, and a line about children blocked outright as a fair housing problem.
Your own park board on a real address, and the network board workampers already read.
No accounts created, attachments straight into private storage, consent stamped with the time it was given.
A standalone link, an ID scan and a selfie. The check is on you, never on them.
Site 41 held April to October with no nightly charge, and access that lapses on October 15.
Eighteen things that stop living in an email folder.
Postings, applicants and the last hundred feet of getting somebody onto your property.
18 things listed right there. Ask about any of them and we will show you it working on your own park, not on a slide.
Publish once and it lands on your own board and the CampGuide network board, where workampers already look.
When you publish, CampGuide checks the wording against fair hiring rules and stops you if it would get you in trouble.
They verify on their own phone before they arrive, and the check is on you, never on them.
What you get.
Compose and publish
Say what the job is and what they get, add the questions you actually need answered, and publish it.
The checks that stop you
Post hourly in a pay transparency state and CampGuide wants both ends of the range. Mention families and it refuses outright.
Applicants without accounts
They apply straight from the posting with no account to create, and CampGuide stamps what they consented to and when.
Verify, seat, and date the access
Verify them, park them on site 41 for the season with no nightly charge, and give them access that ends when the season does.
How operators actually use it.
Short walkthroughs of a real situation, start to finish.
Questions operators ask.
Who can see an applicant's contact details?
Contact details are a manager tier permission. Front desk and marketing can see that a posting exists and how it is doing, not who applied.
Does the workamper pay for their own identity check?
No. An invited worker verification is always on the operator, and the worker opens a standalone link with no account to create.
What happens to their access at the end of the season?
Access is dated to the season, so it ends on its own rather than sitting live until someone remembers to remove it.