When the way you work is written down and built into NextCrew, the right thing happens whoever is working. New staff are useful in their first week, and clients get the same experience every time.
Summary
A process is just the answer to "what do we do when this happens?" Most agencies have the answers, but they live in a few people's heads. This guide shows you how to list the moments that repeat, write each one in a few lines, and then build it into NextCrew: what you say goes in message templates, what you record goes in note templates, who does what goes in tasks, and what each person checks goes in a shared view. What usually goes wrong is writing a long manual nobody opens, or writing nothing and relying on the one person who knows.
How to do it
- List the moments that happen again and again in your agency.
- Write each one in five to seven lines: what starts it, who owns it, by when, and what "done" looks like.
- Build each line into NextCrew with the tool that runs it.
- Give every role a shared view to open each morning, and an owner for every process.
- Train your team on it, then review it once a month.
That's the whole method. Everything below is for when you want the reasons, the tools for each step, and a full example.
On this page
- Why it matters
- Where it usually breaks
- Step 1: List the moments that repeat
- Step 2: Write each one in five to seven lines
- Step 3: Build it into NextCrew
- Step 4: Give every role a daily view and an owner
- Step 5: Train the team, then review monthly
- What runs on its own
- Where CrewPilot AI helps
- A worked example: the no-show process
- A one-page process template
- You're set up when…
- If something isn't working
- Questions people ask
- Other ways people ask this
- Related guides
Why it matters
- Clients trust you when the experience is the same whoever answers the phone. They notice when it changes with the person.
- Crew stay loyal when they get the same clear messages, the same paperwork and the same follow-up every time.
- Your team builds relationships instead of asking each other "how do we do this again?" A written process means nobody is the single point of failure.
There's one more reason. NextCrew's automation and CrewPilot AI can only follow a process that exists. If the steps are only in someone's head, the system can't help.
Where it usually breaks
- The process lives in one person's head. When they're off sick or leave, it goes with them.
- It's written down, but in a long document nobody opens.
- It's written down, but not built into NextCrew, so people still type every message and note from scratch.
- Everyone owns it, so nobody does.
- It was written once and never checked again, so it no longer matches how you work.
Step 1: List the moments that repeat
Start with the moments that happen every week. Most agencies have these:
- A new applicant applies.
- A new hire needs their paperwork.
- A client sends a new order.
- A Crew Member doesn't show up.
- A timesheet has a problem.
- A new client signs on.
- A Crew Member's credential is about to expire.
- A Crew Member leaves.
Add your own. Then pick the three that cause the most trouble today and start there. You don't need all of them on day one.
Step 2: Write each one in five to seven lines
Keep each process short enough to fit on one page. If it needs more than seven lines, it's probably two processes.
| Line | What to write |
|---|---|
| Starts when | The moment that sets it off. For example, "a Crew Member hasn't clocked in." |
| Owner | One role, not "everyone." For example, "operations." |
| By when | How fast it has to happen. For example, "within 15 minutes of the start time." |
| Steps | Three or four short steps, in order. |
| In NextCrew | The template, task, view or form that runs each step. |
| Done when | What has to be true to call it finished. For example, "the job is covered, the client knows, and the record is updated." |
Write it in plain words, the way you'd explain it to a new starter. If a step says "use judgment," say who decides.
Step 3: Build it into NextCrew
Each line of your process has a tool in NextCrew that runs it. Build it once, and the next person follows the same steps without having to remember them.
| Process step | The tool that runs it | Guide |
|---|---|---|
| What you say | Message templates. Save the message once, tick Shared, and use macros for the first name, so everyone sends the same words. | Create and Share Message Templates |
| What you record | Note templates, with a Note Category. Every note is dated and shows who wrote it. | Add Notes to a Record and Use Note Templates |
| Who does what, by when | Tasks, each with one owner, a Due Date and a Priority, linked to the job, order, client, Crew Member, timesheet or offer. | Create and Track Tasks |
| What each person checks every morning | Saved list views, shared with the team. A view keeps its filters, columns and sort order. | Save and Share Your Own List Views |
| Forms and policies people sign | Form packages. Mark fields Required, add a signature field, and track who has finished. | Build and Send Form Packages |
| Hiring paperwork | Onboarding workflows. NextCrew tracks each form, creates a task for each document, and sends reminders. | Track Onboarding in Workflows |
| The job team's conversation | Channels. One group conversation for the job, with Crew, your team and, if you choose, the client. | How Channels Work: Group Conversations for a Job or a Team |
| What already happens on its own | NextCrew's built-in automation. Don't write steps for what the system already does. | What NextCrew Automates for You |
A tip on names. Name each template and view after the moment it's for, such as "No-show: where are you?" or "Scheduler: jobs not full." Then people find it when they need it.
Step 4: Give every role a daily view and an owner
A process only runs if someone opens it. Give each role one shared view to start the day with, so the work comes to them.
| Role | What they open first | What it shows |
|---|---|---|
| Recruiter | A shared view of candidates | New candidates waiting for the next step |
| HR | The Crew Members list grouped by HR Status, saved as a view | How many people are at each hiring stage |
| Scheduler | A shared view of orders | Orders with open spots |
| Operations | Daily Pulse | Today's timesheets, with counters for no-shows and late clock-ins |
| Timesheets | A shared view of timesheets | Timesheets that need a correction |
Then give every process one owner:
- Tasks name one person. A task can't have two owners, so "I thought you had it" goes away.
- Assigned Roles on each client's Overview show who works the account and what they handle. The Account Manager still owns the client. See Add a New Client.
- The Staffing Manager and Recruiter on each Crew Member's record show who looks after that person.
Step 5: Train the team, then review monthly
Train it.
- Walk each person through the processes they own, using real work, not a test.
- For your Crew, send one welcome message and then each guide as the moment comes up. Put one person on Crew questions each day, and save common replies as templates. See Train and Support Your Crew in the NextCrew App.
- For your clients, walk the person who books through one real order, and the approver through one real timesheet. See Orient New Clients to Use NextCrew.
Review it once a month. Book 30 minutes with the owners and ask three questions:
- Where did a process break this month? Look at the Violation Report, your open tasks, and the notes on jobs that went wrong.
- Is the one-page process still how we really work? If not, change the page.
- Does every template, task and view still match the page? If not, change those too.
What runs on its own
These run on rules your agency sets. They're workflow automation, not AI. Leave them out of your written steps, and build your process around them. See What NextCrew Automates for You.
- Applicants: reminder emails to applicants who haven't finished.
- Onboarding: the onboarding package goes out, each document is tracked, a task is created for each one, and reminders go out on day 3, day 5 and day 7.
- Crew records: Crew are reminded before a credential expires, and a note is added when an HR status changes.
- Filling jobs: open jobs are offered to Crew who fit and are nearby, skipping anyone already booked.
- Before the job: the assignment notice, a reminder 24 hours before, clock-in and clock-out reminders, and a notice to confirmed Crew when the job changes.
- Repeat work: recurring orders create the next order on schedule.
- Timesheets, payroll and invoices: timesheets are built from clock-in and clock-out, overtime is calculated for employees, timesheets are marked Paid on export and Invoiced when billed.
Some steps always stay with your team: moving someone to Hired, confirming who works a job (unless Auto-Confirm is on), approving timesheets, running payroll, and sending invoices. Those are the steps your processes need to cover.
Where CrewPilot AI helps
CrewPilot suggests, finds and drafts. Your team makes the calls. See How CrewPilot AI Works: Your AI Command Center, AI Ticker and Assistant.
- Ask in plain words for the list a process needs, such as "show me open jobs for this week," and open the records it shows. See Ask CrewPilot: Get Answers About NextCrew and Your Data.
- Turn a client's emailed order into a job draft. Paste the email, check the draft and save it.
- Check timesheets before you approve. Select up to 100 timesheets and ask CrewPilot to check them. It shows which are ready and which need attention. Nothing changes until you apply the approval.
- Draft the day's reminder. In Send Message, the AI menu drafts a job reminder. You check it and send it.
- The AI Command Center shows what CrewPilot has flagged, and clicking an item opens the record. Rolling out gradually. We're enabling the AI Command Center one account at a time. It will appear in your workspace as we activate it for your agency, with no action needed on your end.
A worked example: the no-show process
An example of one process, start to finish. Not a real client.
The one-page process
| Line | What it says |
|---|---|
| Starts when | A Crew Member hasn't clocked in at the start time. |
| Owner | Operations. |
| By when | First message within 15 minutes of the start time; job covered within the hour. |
| Steps | 1. Message the no-shows. 2. Rule out a false no-show. 3. Backfill and tell the client. 4. After the job, record it. |
| In NextCrew | Daily Pulse, the "No-show: where are you?" message template, the job's Invite, a note template, a violation. |
| Done when | The job is covered, the client knows who is coming and when, and the record shows what happened. |
How it runs on the day
- Spot it. Operations opens Daily Pulse and clicks No Shows. The job's assigned user also gets an email 15 minutes after the start time. See See Today's Timesheets with Daily Pulse.
- Message them. Tick everyone listed, choose Send Message, and pick the shared template. Call anyone who doesn't reply.
- Rule out a false no-show. If someone is on site but couldn't clock in, select them and choose Clock-In. Don't record anything against them.
- Backfill. Open the job and choose Invite. Use the Available and Worked For Client filters, then Request or Confirm a replacement. See Handle No-Shows & Backfill.
- Tell the client the replacement's name and arrival time.
- Record it. After the job, set the missing Crew Member's timesheet to Not Completed (don't delete it). Add a violation with the category and the facts: the job, the start time, and how you tried to reach them. Violations can't be edited, so check before you click Add. See Record Violations and Spot Problems Early.
- Look back monthly. Run the Violation Report and look for the same person or the same site coming up again.
The result: a new operations hire can run a no-show on their first Saturday, because every step is written down and every tool is already set up.
A one-page process template
Print this, or copy it into a document, and fill one in for each process.
Process name: ____
| Line | Your answer |
|---|---|
| Starts when (the moment that sets it off) | |
| Owner (one role) | |
| Backup owner (when the owner is out) | |
| By when (how fast) | |
| Step 1 | |
| Step 2 | |
| Step 3 | |
| Step 4 | |
| In NextCrew (template, task, view, form or Channel for each step) | |
| Done when (what has to be true) | |
| Last reviewed (date and by whom) |
Before you call it finished:
- ☐ It fits on one page.
- ☐ One role owns it.
- ☐ Every message in it is a shared message template.
- ☐ Every note in it has a note template.
- ☐ Every hand-off is a task with an owner and a due date.
- ☐ The owner has a shared view that shows when it's needed.
- ☐ Nothing in it repeats what NextCrew already does on its own.
You're set up when…
- ☐ Your three most painful moments each have a one-page process.
- ☐ Each process has one owner and a backup.
- ☐ The messages in each process are shared templates.
- ☐ The notes in each process have note templates and categories.
- ☐ Hand-offs are tasks with owners and due dates.
- ☐ Every role has a shared view to open each morning.
- ☐ New staff are trained on real work, using the one-page processes.
- ☐ You review your processes once a month.
If something isn't working
| What you see | Most likely cause | What to do |
|---|---|---|
| People still type messages from scratch | The template isn't shared, or its name doesn't say when to use it | Tick Shared and rename it after the moment it's for |
| A teammate can't find a saved view | It wasn't shared | Open the view and turn on the Shared switch |
| A task fell through the cracks | It had no owner, or it was outside the date range on the Tasks list | Give every task one owner and a due date; widen the date range |
| Notes are hard to find later | No category, or everyone writes them differently | Use a Note Category and a shared note template |
| Two people handled the same no-show | The owner wasn't clear | Name one owner on the one-page process |
| The process no longer matches what people do | It hasn't been reviewed | Update the page, then the templates, tasks and views |
Questions people ask
We're a small agency. Do we really need written processes? Yes, and it's quicker for you. Start with three, each on one page. When someone is out, the work still gets done.
How long should a process be? Five to seven lines. If it needs more, split it into two.
Who should own a process? One role, with a backup. "Everyone" means nobody.
Do I need to write steps for reminders and notices? No. NextCrew already sends them. Write your process around what it does. See What NextCrew Automates for You.
Can my whole team use the same templates and views? Yes. Tick Shared when you save a message template, note template or list view.
Can a task have two owners? No. Each task names one person. Use the task's Permissions to give others access.
Is the automation AI? No. Reminders, notices and timesheet building are workflow automation, running on rules your agency sets. CrewPilot is the AI part, and it suggests and drafts while your team decides.
How often should we review our processes? Once a month, for 30 minutes, with the owners. Change the page first, then the templates, tasks and views.
Other ways people ask this
- How do I write an SOP for my staffing agency?
- How do I stop everything depending on one person?
- How do I train new staff faster?
- How do I make sure everyone sends the same message?
- What should each person check every morning?
- How do I handle no-shows the same way every time?
- How do I set up templates in NextCrew?
Related guides
- Create and Share Message Templates · Add Notes to a Record and Use Note Templates · Create and Track Tasks · Save and Share Your Own List Views
- Build and Send Form Packages · Track Onboarding in Workflows · How Channels Work: Group Conversations for a Job or a Team · What NextCrew Automates for You
- Train and Support Your Crew in the NextCrew App · Orient New Clients to Use NextCrew
- See Today's Timesheets with Daily Pulse · Handle No-Shows & Backfill · Record Violations and Spot Problems Early
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article