Hey @JoMaughan, thanks for raising this - I like this idea! 

Have you added your vote to the existing feature request linked below? 

I also encourage you to add some more context as to how you’re using monday.com <> SafetyCulture on the request so our Product team can get a better understanding of how they could make this work? I can see that one of our Product Managers responded to the request a few months ago and I’d be happy to raise this again with Austin 

Use Labels instead of Statuses: As you mentioned, SafetyCulture allows modifying labels. You can leverage labels for the actual status representation and map those to Monday.com statuses. This way, Monday.com reflects the desired information even though the underlying SafetyCulture status names remain static.

Third-party Integration Tools: Tools like Zapier or Workload can connect Monday.com and SafetyCulture. These platforms allow you to build automated workflows based on triggers and actions. You can potentially set up a Zap that pulls data from SafetyCulture based on labels (which you can modify) and populates Monday.com statuses accordingly.

Custom Integration with API: If you have some technical resources, consider a custom integration using the SafetyCulture API. This would allow you to potentially manipulate the actual status names within SafetyCulture, although it requires development expertise.

Here are some additional points to consider:

Feature Request with SafetyCulture: While you've submitted a feature request, it's good to manage expectations. Implementing new functionalities takes time for vendors.
Monday.com Statuses vs. SafetyCulture Statuses: Ensure your Monday.com statuses accurately reflect the intended meaning behind SafetyCulture's labels. Clear communication between teams using monday and invoice maker is crucial.
By exploring these options, you can achieve a workable integration between Monday.com and SafetyCulture for your client, even with the current limitations of status name changes in SafetyCulture.