Thank you, Shayla—I appreciate you passing this along to the product team.

For our workflow, the two most valuable additions would be:

1. A dedicated Project Status field.
2. Scheduled Start Date and Time and Scheduled End Time / Date fields.

These would solve two related but separate problems for companies integrating CompanyCam with Salesforce or another CRM.

Project Status

Labels can technically represent a project’s status, but they become messy very quickly. We also use labels for job type, fuel type, paperwork, routing, technician workflow, and other operational purposes. When status is mixed into the same label system, a project can accidentally have Scheduled, Completed, and Cannot Complete selected simultaneously.

A dedicated, single-value Project Status field would prevent those conflicts. Suggested values could include:

• New
• Scheduled
• In Progress
• Completed
• Incomplete
• Cannot Complete
• Waiting
• Canceled
• Closed

Ideally, companies could customize their available status values.

In our workflow, Salesforce is the main office system, and the Work Order Status controls which queues, lists, and follow-up processes contain the job. Our technicians do not have Salesforce licenses; they work from CompanyCam.

We currently rely on the technician applying a matching CompanyCam label, which triggers an integration that updates the Salesforce Work Order. It works, but labels are not the cleanest tool for this. We must determine which label represents the newest status, remove the previous status label, and prevent multiple conflicting status labels from being applied.

A dedicated field would give every project one clear, authoritative status.

Structured status values would also give CompanyCam and its customers much more automation potential. A status change could trigger:

• A webhook update to Salesforce or another CRM.
• A customer completion message.
• An office follow-up task for an incomplete job.
• A parts request when a job cannot be completed.
• A payment request when work is completed.
• Automatic project archiving after a defined period.
• Different required checklists or documents.
• Management alerts and dashboards.
• Movement between project views without creating additional labels.

Labels could then remain available for what they do best: flexible categories such as Wood, Gas, Installation, Cleaning, Warranty, or Route Stop 1. Project Status would describe where the job is in its lifecycle.

For integrations, the minimum useful Project Status implementation would include:

• One current status value per project.
• Customizable status options.
• Read and write access through the API.
• A webhook event when the status changes.
• The user and timestamp associated with the change.
• Visibility and easy editing on web and mobile.
• The ability to filter, sort, and report by status.
• Optional automations based on status changes.

Scheduled Start Date and Time and Scheduled End Time / Date

For scheduling, having both a Scheduled Start Date and Time and a Scheduled End Time / Date would be considerably more useful than having a single date or timestamp.

I would keep the scheduled appointment information separate from the actual time worked:

• Scheduled Start Date and Time
• Scheduled End Time / Date, preferably optional
• Actual Clock-In and Clock-Out through CompanyCam’s Time Tracking feature

The Scheduled End Time / Date should not automatically close the project. Project Status should control whether the project is completed, incomplete, canceled, or closed. The scheduled fields would represent the appointment or arrival window promised to the customer.

Our office schedules a Salesforce Work Order for a particular technician and date. The integration then creates the corresponding CompanyCam project. Salesforce customer information maps very well into the CompanyCam project contact, but the scheduled date and time currently have no structured destination. We can only place that information in the project description or notepad.

That technically displays the information, but it cannot be reliably sorted, filtered, reported on, displayed prominently, or used by automations without parsing free text. The schedule can also become buried among the other project notes.

Our technicians often route the next day’s jobs themselves the night before. Structured scheduling fields could allow CompanyCam to:

• Display today’s and tomorrow’s projects chronologically.
• Show the arrival window prominently on mobile project cards.
• Sort and filter projects by their scheduled date.
• Improve map and routing views.
• Notify technicians when an appointment changes.
• Send appointment reminders or arrival-window texts to customers.
• Push technician scheduling changes back to Salesforce or another CRM.
• Compare the scheduled appointment with actual Time Tracking data.
• Report on travel time, arrival accuracy, job duration, and workload.

For example, a customer could be given an appointment window of September 16 from 9:00–11:00 AM:

• Scheduled Start Date and Time: September 16 at 9:00 AM
• Scheduled End Time / Date: September 16 at 11:00 AM

For a multi-day installation, the Scheduled End Time / Date could instead fall on a later date. Companies that only need a single scheduled time could leave the ending field blank.

The existing contact integration is a good comparison. Because customer information has dedicated fields, it remains structured and useful throughout CompanyCam. We would love project status and appointment scheduling to work the same way.

The minimum useful scheduling implementation would include:

• Scheduled Start Date and Time.
• Optional Scheduled End Time / Date.
• API read and write access.
• Webhook events when either value changes.
• Web and mobile visibility.
• Visibility on mobile project cards.
• Sorting and filtering by these fields.

Together, Project Status, Scheduled Start Date and Time, Scheduled End Time / Date, and Time Tracking would provide a clean progression:

Scheduled appointment → technician arrival → work performed → final project status.

That would make CompanyCam substantially more powerful for companies using Salesforce and other CRMs without requiring CompanyCam to become a full field-service platform. It would also create a strong foundation for customer communications, routing, reporting, payments, and workflow automation.

We would be very interested in beta-testing these features with our Salesforce-to-CompanyCam integration.

Hey Matt! Good news, you can pull this off today!

Every Proposal starts with a default Terms & Conditions section (boilerplate our in-house legal team wrote). Head into the Proposal editor, scroll to Terms and Conditions, and swap that text out for your company's own. Once you edit your T&C, that version carries over to every new Proposal you create after it. So it's really a one-and-done setup — paste yours in once, and you're rolling.

Two quick heads-ups:

• It's set per user, so each person on your team building Proposals will want to paste your company's T&C in on their first one.
• Hang onto the Proposal where you first set them. If every Proposal using your custom terms gets deleted, new ones will fall back to the original stock language. (Pro tip: keep a copy of your T&C in a doc somewhere so it's an easy re-paste if you ever need it.)

Full walkthrough here: Create a Proposal

A true account-level default, where an admin sets the T&C once for the whole company, is exactly the kind of thing our team is exploring with Proposal templates. No timeline I can promise, but I'm passing this along to the Proposals crew because wishlist posts like yours are a big part of how that stuff gets prioritized.

Keep an eye on our News Center too — that's where we post updates as they ship, so you'll see it there first if this one lands.

Thanks for taking the time to write it up!

Hey, Jon!

First off, thanks for sticking with us and sharing what's needed for you and your team to get your jobs done more easily!

Good news: Folders are here. Every project now has a single Documents tab where your Pages, Files, and Reports all live together, and you can create Folders to organize them however makes sense — by visit, by property, by doc type, whatever fits your workflow. It's live on the web app and in the mobile app for everyone, so you should see it next time you open a Project. Just hit + in the Documents tab and choose Folder to get started.

On Checklists specifically — those don't live in Folders yet. You're not the only one asking, and it's something our product team is actively looking at, so I'm making sure your voice gets added to that conversation. I can't promise a timeline today, but it's on the radar!

In the meantime, a couple of things that might take some pressure off:

• Project Groups (only on specific plans) lets you bundle related projects — say every unit at one property, or every job for one client — into a single group with one dashboard showing progress across all of them. If you're managing thousands of photos across a bunch of properties, this is probably the biggest win available to you right now.
• Project Labels are great for slicing your project list by property, client, or job type, and Tags do the same thing at the photo level. Between the two, you can usually get to the right handful of photos way faster than a broad keyword search.

If you want a hand setting any of this up, our support team is at support@companycam.com and they'll walk you through it. We don't want to lose you over organization — that's a fixable problem.

Thanks again for sharing your feedback!

Hey there!

This is a great one, and you laid it out really clearly. Labels can technically work as a status today, that's part of what they're built for, but as you said, that gets messy once you want to use labels for other things too, and there's still no start date/time field outside of jotting it in the notes or description. I hear you on wanting cleaner data to actually hand off to a CRM instead of parsing free text.

I've passed this request along to our product team.

One thing I'm curious about, since it'll help shape what this actually looks like: for the arrival window, is a single date/time enough, or do you need a start and end window to "close out" the Project?

No promises on timing, but the more detail you can give us here, the better. Appreciate you writing it up!

Thank you!

Great points. I think the labels would be helpful as well since we're unable to automatically add labels using the API before the project is created. We're still new to Company Cam and mapping out our company's use-cases. We envision archiving projects / estimates that don't turn to sales and think we'll do this daily. Hope that makes sense and thanks for the quick reply.

Hey! I'm envisioning pulling info from the CRM to create the CompanyCam invoice. That way I can have an invoice premade in CompanyCam ready to go for the PMs before they start the final walkthrough.
My CRM is already integrated with CompanyCam, so the project link is quite simple. On the scheduled install end date I would push client info, project balances, and project descriptions to CompanyCam for invoice creation.

Hey there!

Good news, more of this is possible than you might think. Tags have full support in the API, create, update, delete, all of it, so automating tags based on project criteria is totally doable. Groups are the same story: full create, update, delete support, including managing who's in them.

Labels are close but not all the way there yet. You can add a label and delete one through the API, there's just no update endpoint to rename an existing one in place. That part's a real gap, and I'll get it in front of our product team.

One more thing worth mentioning: we rolled out a new developer portal a couple of months ago. If you've been working off older docs, there's a good chance you're missing some of what's already there. Worth a fresh look before ruling anything out.

Let me know if the label piece is the one actually blocking you. Appreciate you flagging into this!

Hey there!

Creating 20-40 projects a day and then having to archive them one by one can definitely be a pain. Totally get why this one's on your radar, and I've passed it along to our product team.

While I've got you: is archiving the main action you'd want to do in bulk, or are there others, like updating project labels, reassigning a crew member, or deleting, that would save you time too? The more of that we can hand to the product team, the better shot this has at getting built the way you'd actually use it.

Hey there!

This is a smart ask, and I can picture exactly why you want it. Grouping items like panels and breakers, or conduit and fittings, would make the Proposal read a lot more the way you actually think about the job.

That's not something we can do today, but I've passed it along to our product team.

No timeline on it, but keep this kind of feedback coming!

Hey there!

This is a great one, and I want to make sure I route it to the right place. When you say creating invoices from Zapier or the API, are you picturing a CompanyCam Invoice getting created automatically (pulling in that description and payment amount from your CRM), or is the invoice actually living in your CRM, and you just want CompanyCam project info to feed into it?

Right now there's no way to trigger a CompanyCam Invoice through Zapier or the API, so either way this is a real gap. But knowing exactly what you need created, and where, helps me pass along something specific instead of something vague. What does the setup look like on your end?

Hey there!

I hear the frustration, but I don't want you walking away thinking collaboration doesn't do anything here. Collaborators can already create, view, and complete Project Tasks today, so they're not locked out of the workflow entirely.

Fair ask on assigning them to the Task, though, and I've passed it along to our product team.

Curious what's driving this for you; is it more about assigning specific punch list items to a sub, or keeping everyone's outstanding work visible in one place? Either way, appreciate you writing it up!

IT LIVES IN THE DOCUMENTS TAB IN YOUR PROJECT. JUST CLICK THE + DOCUMENT BUTTON.




THEN CLICK NEW DOCUMENT



THE REPORT IS IN THE GRID ON THE UPPER LEFT OF THE PAGE

GREAT WORK AROUND FOR THIS! I'LL BE SURE TO REMIND THE CREW TO USE COMPANYCAM FOR THE VIDEO AND NOT JUST THE PHONE'S PHOTO APP.

Hey Hayley, sorry for taking so long to get back to you, but this is now live in the Web app and will be live on mobile next week.

So, I guess not a totally out there idea, because it looks like someone requested something similar recently.

Emberton Electrical said:

Feature Request: Create a Daily Field Update advanced checklist automatically when a crew member clocks in on a project

I would like to request a workflow improvement for field crews using CompanyCam on active jobs.

A useful feature would be the ability to trigger a Daily Field Update advanced checklist automatically when a crew member clocks in on a project.

Requested workflow​

• Crew member clocks in on a project
• CompanyCam automatically creates a Daily Field Update advanced checklist instance on that project
• The checklist is prefilled with project name, date, crew member name, and clock-in time
• At the end of the visit, the crew completes prompted fields for work completed, materials used, materials required, client changes or requests, tools or subcontractors needed, blockers, and next steps

Why this matters​

Our crews work much better from prompted lists than from open-ended note writing. If the checklist appears automatically when they clock in, adoption would be much higher and field reporting would be more complete and consistent.

• Improves daily field documentation
• Creates a clean place to capture materials used and materials still needed
• Makes outstanding work easier to track
• Reduces missed notes and duplicate entry
• Connects labor activity directly to field reporting

Additional request​

It would also be valuable if time data could automatically flow into the checklist or into a client-facing daily report generated from that checklist.

• Clock-in time prefilled
• Clock-out time available at completion
• Hours for the visit calculated automatically
• Crew members on site tied to the checklist record

For field teams, this would make advanced checklists much more practical as a real daily workflow tool rather than something the office has to chase after the fact.

As always if there is already a function that you can suggest that already does this I would love to hear about it! Thanks!

Click to expand...

Hello! Thank you so much for sharing this detailed feedback. I'm Ana by the way, Product Manager working on Checklists. Your workflow makes a lot of sense. I do have a follow up question - when the crew member is done with the visit how would you expect them to be prompted to complete the checklist? Perhaps when they attempt to clock out? A reminder is sent after certain amount of time? Something else?

Hey there, thanks for flagging this!

Quick context on what you're running into: right now, a single shift caps out at 12 hours. That's an intentional guardrail so a timer someone forgets to stop doesn't turn into a 40-hour shift on your payroll report, but you're not the only crew telling us 12 isn't enough for the way they actually work.

Good news: our team is already revisiting that limit, and we've added you to the feature request ticket so you'll stay in the loop as it moves. No timeline to promise yet, but this is on the radar.

In the meantime, here's the workaround so nobody loses hours: log the day as two shifts instead of one — say 6am–4pm and 4pm–8pm. An Admin or Manager can create and edit those entries from the Time Tracking page on the web app, and they'll roll up into the same timesheet and the same CSV export at the end of the week. Same total hours, same Project, just split across two entries.

Appreciate you taking the time to post this. Keep 'em coming!