Specification Markups
Create the ability to markup spec sections just like drawings. Many markups apply to both drawings and specs.
Connor McVein
shared this idea
AdminJenn Howard
(Team Lead, Strategic Product Consultant, Procore)
responded
We wanted to take a minute to share more as this request is our top rated and we’re so grateful for the continued input that each of you provided. At Procore, our vision is to improve the lives of everyone in construction. Building software to improve the lives of all roles within construction is so important to us and we continue to pursue this every day. The opinions each of you share here is critical to helping us understand if we’re heading the right direction. So, thank you!
We know this will be a very valuable feature and this is something that we’re actively working towards. There is some underlying technology that we need to improve before we feel confident to deliver a feature like this at the scale of supporting various roles and project types in construction. So while we may not yet be able to update this ticket to “Started” quite yet, know that we are working towards making this functionality available.
139 comments
-
Jaime Thomas
commented
This needs to be an added function. By the time it gets incorporated, it will be too late on my current project.
-
Craig Hanus
commented
Woot! We did it.
Thank you for responding @Jenn Howard
-
Stephen Talaber
commented
Agreed , we need this added in !
-
Yuxin Zhao
commented
Markups in specifications can be very helpful. Please add that in.
-
Chris Sharrard
commented
Voting first time for those that have been paying for PROCORE for years and still have not been heard....our company just recently launched PROCORE and we are still learning - but when we get up to spelled - we do not want to be hindered nor add more waste to an already cumbersome industry. I agree with A LOT of the comments below.....C'MON PROCORE team! Give your CUSTOMERS what they know they need!
-
Kara Gill
commented
Agreed - The amount of ideas that I've supported and have eventually been marked as "Reviewed - Not Prioritized for Implement" is disheartening. (Maybe a new idea should be posted regarding this since it seems this thread has gotten a bit off topic.)
Specifically in regards to the specification markup tool, this feature is clearly in high demand and would prove so helpful. For instance, an addendum will be added to the specifications. The addendum will include references to changes throughout the specifications. In situations where only a paragraph or small portion of a spec section is changed (no matter how crucial), a revised spec is not provided. The Architect only includes the change description within the addendum. The ability to markup the impacted specifications, to either link back to the addendum, or to call out the specific changes within the specification itself, is essential.
-
Craig Hanus
commented
Thanks Dan!
-
Dan Seelman
commented
Just posting to add onto the comment number
-
Bart Sontag
commented
@Chase - agreed! There are so many simple things that could be refined to add great value for current users. We're not ready to walk away from Procore just yet, but it sure feels like a pivot has taken place away from the core and towards increasing customer base. I'm sure that has nothing to do with their IPO...
-
Craig Hanus
commented
@chase, all they have to do is focus on cleaning up the service for a year. Just like Apple used to do with their OS. Every couple of years they released a version that focused on performance with only a few new functions. That's what Procore needs to do now. Halt dev on new functions and just go through this list.
-
Jesse Amezquita
commented
While we are venting they need to fix the search function. It's completely unreliable to use
-
Chase Hallstrom
commented
@Craig - I've come to the conclusion that Procore doesn't pay attention to the customer feedback
@Bart - I agree with your analogy, and wish we could painlessly switch to another management software. Procore's business model seems to push the latest ostentatious feature out, ignore polishing the existing features, and get sales off of the flashy new bell or whistle. Once switched over to Procore, it's a pain to switch out and relearn a new system and most customers will do little other than grumble.
If I had a vote that counted, I'd scrap any 'new' developments and focus on getting some of the simple ideas implemented, regardless of how showy they may be. Everything from marking up specifications to bulk distributing submittals to posting videos in the photo tool.
-
Bart Sontag
commented
@ Dan - that has been our workaround so far and after our Buildr experiment will likely become our default. But why must the client go through those gymnastics for the amount of $$$ we spend on this application? If I pull a report of unsubmitted items, it will pull closeout items as well and skew the numbers. So then create a custom report as a workaround. Again, why must we do all the gymnastics?
Procore is supposed to increase our efficiency and accuracy. Our Sr. Project Asst. recently told Procore in a support call, “every time you folks roll out a so-called improvement, my productivity level drops significantly”.
We purchased a Ferrari, rationalizing that our staff and our clients are worth it, but are starting to get the performance of a Porsche (sorry for the analogy Porsche fans...). Hoping it doesn't start running like a Chevy (not sorry for the analogy Chevy fans).
-
Jason Catalano
commented
Looks like this suggestion is finally getting some heat. I'd love for this to be addressed soon.
-
Dan Steele
commented
@Bart - why couldn't you use the submittal module as a closeout module? Just create a custom type as "Closeout" with due dates toward the end of the project or whenever you want them. Create the closeout requirements the same time you create the rest of the submittal log. We also use the export app for the information dump at the end of the project which we think helps the closeout process.
-
Bart Sontag
commented
@Brian - we are using Buildr's BuildrCloseout tool. Oddly enough, it was created by former Procore employees (go figure - wonder if Tooey's getting a cut). While the sales pitch was slick, it's pricey. $3500 to try it on a single project and then ROM $12K on $40m volume. We've been using it to close out one job as a test, forcing our project coordinator to learn yet another application. We're 4 months into the process and still not closed (likely due in great part to workload). I'm not getting ringing endorsements so far.
It has boggled my mind that this wasn't part of the original Procore offering, such a glaring omission. There are a multitude of related requests in the user forum. I have been obnoxious in my requests to them to provide a closeout module - people have seen my graffiti at Groundbreak 2017 and 2018. I can't imagine it's much more complicated than copy/paste the Submittal module and change "Submittal" to "Closeout". But I'm just a dumb GC, what do I know?
-
Craig Hanus
commented
Perhaps if we left all left a new comment every hour their team would notice the traffic and get the point? If there's 50 of us on here, that's almost one per minute.
-
Brian Traylor
commented
@Bart - what separate product are you using for closeout documentation? This is a need we have that Procore doesn't support. Still needs to get done...
-
Russell Voigt
commented
I have to agree, also. Well said, everyone!
It has been shocking to me that such an elementary need to the industry has taken a back seat to some of these other flashier features like the BIM module that aren't nearly as scalable as a simple spec markup capability. -
Bart Sontag
commented
@Jeff, you show incredibly poor taste. But the feeling is mutual