We’d Love Your Feedback on Project Status Reports in the Next Experience
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2025 06:12 AM
Hello everyone!
I’m Hayley Alexander, Inbound Product Manager for Project Workspace here at ServiceNow.
We’re continuing to evolve the Next Experience for Project Status Reports, and I’d love to hear directly from you about how you’re currently using them.
Specifically, I’m looking to understand:
-
How your teams are creating, managing, and delivering project status reports today
-
What’s working well in the current experience
-
Current pain-points you're experiencing
Your feedback will help us shape upcoming improvements and ensure the experience fits seamlessly into how your teams work.
If you’re using (or have recently started using) the Next Experience Project Status Reports, please reply to this post. I’ll reach out directly to set up a short follow-up conversation.
Thank you for helping us make Project Workspace even better!
-Hayley Alexander
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @HayleyAlexander
Currently, status report templates cannot be restricted to specific teamspaces (this is what we were told).
This lack of configuration means the global default template is applied to all teamspaces, when the status report is created via the related list.
I would like to request to consider the ability to define template visibility per teamspace / define default template for each teamspace. This would ensure that when a status report is created, only the relevant, team-space-specific template is utilised, maintaining data integrity.
In a summary:
Current State: One-size-fits-all default template.
The Conflict: Teamspaces have unique status report requirements (different fields on the status report)
Thank you
A.
