It looks like this engineer decided to break from his usual boilerplate spec...
That can be good and bad.
The good news is that you should hopefully have a clear picture on what you need to provide. Hopefully the contradictory specifications have been edited out.
The bad news is that very specific project specifications can be difficult to respond to in a universal way that makes sense for library storage.
For example, take this specification:
Since each job is unique and could be potentially located anywhere, how could you know in advance that your service center is within 300 miles of the job location?
What can you do?
There is no right way to handle this situation, but the following are a few suggestions:
Add a Quote Considerations note to tell the spec reviewer that this must be checked prior to providing a compliance statement. This does not fully automate the spec review, but helps you add guardrails to the specification review to ensure a higher level of accuracy:
As shown above, this will show up in your Quote Considerations list to make sure you don't miss this manual action.Add your very specific project response, but don't save the responses to your library. Not every specification can be automated, and that is okay. Leave the super specific response alone, especially if there is no logical manual "check" as described in the last step.