Features
Projects
People hub Projects—group related jobs, filter the schedule by project, and know when a project beats a stack of one-off jobs.
Overview
Projects in Bounty CRM sit in the People hub alongside Contacts and Team. A project is a container for related jobs—typically a multi-visit engagement such as a remodel phase, multi-system install, or staged service plan—so you can talk about “the Oak Street HVAC upgrade” as one initiative instead of a loose pile of calendar entries.
Projects do not replace jobs. Jobs remain the schedulable units of work. Projects group those jobs, make them filterable on the schedule, and give office and field a shared label for “everything under this engagement.” Projects are a separate folder from the strict 1:1 document chain (job / estimate / invoice / contract)—see /docs/guides/document-linking. One-off service calls usually do not need a project; multi-day or multi-crew work often does.
What it allows you to do
- Create a named project tied to a customer engagement.
- Attach multiple jobs to the same project so history stays grouped.
- Filter the Jobs schedule by project to see only that engagement’s work.
- Coordinate office and field language—everyone references the same project name.
- Decide deliberately when a project adds clarity vs when a single job is enough.
How it impacts your workflow
Without projects, complex work tends to become a trail of similarly named jobs that are hard to isolate on a busy week calendar. With projects, dispatch can filter the schedule to one engagement during a planning meeting, and techs can see how today’s visit fits the larger plan.
Projects also change how you estimate and invoice over time. You might still create separate estimates and invoices per phase, but the jobs under the project give you an operational spine: rough-in, trim, start-up, punch list. That spine is what the schedule filters against.
When not to use a project: a single diagnostic visit, a one-hour repair, or a quick warranty check. Over-projecting one-off work adds navigation without benefit. Use projects when you expect multiple jobs, multiple days, or multiple people asking “where are we on X?”
Key screens & actions
Web: People hub → Projects. From Jobs, filter the day/week/month/list views by project when you need a focused board. Mobile surfaces related job context in the field; project management is most comfortable on web.
Project list & detail
- Browse projects in the People hub with search and filters.
- Open a project to review and manage the jobs grouped under it.
- Keep naming consistent—“Customer + site + scope”—so filters stay meaningful months later.
Schedule filtering
On Jobs & Dispatch, apply a project filter to hide unrelated work. This is especially useful during morning dispatch for a large install, or when an owner wants a status pass on one engagement without scanning the entire company calendar.
- Decide whether the engagement will span multiple jobs or days.
- Create a project with a clear, searchable name.
- Create jobs under that project (or attach existing jobs).
- Schedule and assign techs as usual on the Jobs calendar.
- Filter Jobs by project when planning or reviewing that engagement.
- Close out remaining jobs as phases complete; keep the project as historical grouping.
Connections
- ContactsCustomers remain the people records; projects group work for those customers.
- Jobs & DispatchJobs are the schedulable units living under a project when needed.
- EstimatesPhase estimates often convert into project jobs.
- InvoicesBill by phase or visit while operational work stays project-grouped.
- Document linkingProjects vs the 1:1 job/estimate/invoice/contract chain.
- First workflowEnd-to-end path from customer to scheduled work.
Permissions & plan notes
Projects ride with your Jobs & Contact workflows on core plans (Starter, Professional, Business). Access still follows role permissions for creating and editing related jobs. If a user cannot see Jobs, project-filtered scheduling will not help them.
- Starter includes jobs/dispatch and contacts—enough for project-style grouping on small teams.
- Professional and Business add capacity (more seats/jobs) which matters when many concurrent projects are on the board.
- File storage (Professional+) helps when project jobs carry photos and attachments.
Tips & common questions
- Name projects for search: “Nguyen — 12 Oak — heat pump install,” not “Install 1.”
- Prefer fewer, clearer projects over dozens of tiny ones.
- One-off jobs do not need a project—skip the extra click.
- Use project filters in week view when coordinating multi-crew installs.
- If two jobs feel related but are for different sites, they are usually different projects (or just separate jobs).
- Unsure whether to project-ize a job? Ask: “Will we still talk about this as one thing next month?” If yes, create a project. Questions: customerservice@praevisio.co.
Projects organize jobs; they are not a substitute for contracts or memberships. Long-term service agreements live under Contracts (/docs/features/contracts).