I’m starting this thread of discussion based on talking with several specifications writers about our concerns and experiences with providing specifications to clients (architects/engineers), project owners, construction managers and contractors.
What are the issues in giving specifications to others in an electronic format?
What file formats are most suitable for transmitting and publishing (printing or placing on a website)?
John,
The issues about giving specifications electronically are liability and not having an informed client.
What I mean by “an informed client” – Recently I had a new client call to say they wanted me to write the specs and they wanted them electronically because they would be writing the addenda.
In my opinion, if we do not take the time to educate our clients as to the assets of our services, not just producing a spec, then we are missing the point of this profession.
If we send the project manual electronically for the client to print and collate, what will stop them from making changes. I know people that this has happened to, and they were required to take the time to review each section and prove they did not produce it.
How do we protect ourselves, and stay in touch with the electronic changes?
If clients claim they do not intend to change the electronic files they are requesting, and that they only want an electronic archive that can be printed for future reference, then offer them a PDF file.
Acrobat PDF files can be created that only allow viewing and printing. They are digital images of the originals, and they can be printed on the client’s system printer.
Acrobat Reader is a free application, so any client can obtain it from Adobe’s website. However, the Acrobat program to create the PDF files will cost you between $230-250. Instead of printing your file to a hardcopy printer, you print to the Acrobat Distiller. It is that easy, and you can print multiplle files at one time. Note the use of the term “print”. It is not the same as “converting” or “save as”. There should be no loss of format if the settings are correct.
I’m not aware of any risks at this point, but I will let you know if any develop. I have already delivered four major projects entirely in PDF format (one of which was from a small hill town in Italy last month).
The other obvious benefits include a shorter delivery time, especially when working at a distance. In fact, I can send the PDF files at noon and get them to my client three time zones away at 9 am. Another benefit is lower shipping costs. This comes from agreeing to provide your services in only one format.
There are certain coordination issues because you have to educate your client how to assemble the final project manual, especially if you want double-sided pages in chapter format. With experience will come recommendations and standards.
In summary, there shouldn’t be any electronic changes. However, if specifiers wants to stay in touch with the electronic age, they should try Acrobat.
I agree with John Regener. I just got Acrobat, the whole program and have been playing with it. I have one contract for a structural engineer to do the structural specs. for a fussy architect who has exact formatting requirements. I wrote in my contract that I would give them the files in PDF format - put that in small print,they will never see it, then they can’t complain, you are just fulfilling your contract.
I have downloaded a fresh copy of Acrobat Reader, which I am going to include on every disk with the specs. so that the client can’t say he (she) can’t open it. The tool will be right there.
This is all fine and dandy, but we use the internet to interact with our clients, get them to READ the specs (quite a feat in itself as most of you know) and actually use the TRACK CHANGE feature of Word to all agree on the content of a Section. We find that this is why the internet was created and how it will be used in the future. You can do this in Acrobat but what’s the point?
The Section is then finalized and printed. However in the interim there are incomplete versions of the document floating around and there’s nothing we can do if a client wants to use them either “as is” or in a modified version.
I understand the liability issue, but I don’t know how it can be resolved except by keeping every version of the “authorized” section if one has to go to court.
Gerard:
We also have clients who want specs in disk format, (as well as drawings) and one way to handle the change issue is to have a set of disks run as the record copy and then have them sealed at the time of distribution. They can be professionally sealed and labled and kept as your archive copy. (or you can burn a CD that has the specs and drawings on it and archive that.) I have had clients change stuff once they get the set, but I’ve never had an argument about the content with them – they have always acknowledged the change.
With another client, a major university, we provide specs in PDF format.
We also do the same as you with having the Owner and consultants use the “track changes” utility. I don’t think we see this as a very big problem – even hard copy can be scanned in now, or retyped.
I agree with you. We decided to keep all the issues sent to the client and his/her consultants as “records copies.” It uses a lot of disk space, which can be reduced by zipping the files, but at least we sleep nights.
The method we use is to create subdirectories, with the date of issue, in the main project directory. When we archive the project, we then have a complete history of what we’ve produced.
One problem we are encountering is that some consultants are reluctant to give us an electronic copy of their files, but even the reluctant ones are coming around.
I have less concern about the liability issue than I do with the mechanics problem. I consider my client as being the party ultimately liable for the specifications and work hard to fully engage them in the decisions process. Why would I want to deny them the opportunity to change “their” specifications.
The mechanics of the issue is what drives me nuts. Every client has a different competency level. Some are way out in front of me and others way behind. This makes every project a problem of what they can handle; .PDF ,rtf .sec and .doc.
It is getting worse. With so many opting for the supposed universality of “Office” I find much less competency in dealing with the mechanics of data management, i.e. codes, extensions printer interface. More and nmore clients expect me to solve their “WORD” problems. Since I never made the switch I just can not help them.
Just have to use the hard copy I sent them. Another good reason to not send Bill Gates any more money.
“If clients claim they do not intend to change the electronic files they are requesting, and that they only want an electronic archive that can be printed for future reference, then offer them a PDF file.”
MASTERSPEC subscribers can get a free add-in for either MS Word or WordPerfect called MasterWorks which can perform a translation to PDF. New versions of WordPerfect include this feature, also.
I don’t think that software will work if the PDF is saved as an encrypted file. I have had to fight with some PDF files from manufacturers that lock the spec file.
If you password protect the PDF files, the conversion software won’t convert them. If you don’t, anyone, even dumb me, can convert the PDF files to writeable format using the PDF program.
Password protecting is slow though, at least I have only figured out how to do one file at a time.
The full version of Acrobat includes a feature called “batch processing.” You can set up a sequence to set security parameters for all .pdf files within a directory.
To me the primary issue is that ALL bidders receive ALL Addenda.
There can be claims that the electronic version was not received [how do you disprove that?]
But then one can claim that the snail-mail never arrived [how do you disprove that?]
Registered mail with return receipt, FedEx or other trackable delivery may show that at least delivery was made-- reading and understanding is yet another matter. Personal service and reading out loud to each bidder does seem a little difficult if not remote!
Bottom line, is the need [best advised, not mandated] that the bidding playing field be “dead level” for all.
your email program can be set up to register (ack to sender) and send a reply when it is read and opened – at least the Outlook program has that as an option. that way, you have an electronic “receipt” for the document. for faxed addenda, I have typically included a cover sheet that requires a signed return faxed back – and we keep those in the file as the receipt. I do… however… remember when last minute addenda were sent by telegram to all registered bidders..
Addenda can be sent any way that it has been ‘agreed upon’ to send them. That is, technically it should be outlined in the Instructions to Bidders about how, when and why addenda will be issued.
Even if it is not defined well, the Owner can inform the contractors how he intends to issue addenda and that’s that.
Now - that is per the private sector. Enter the public or the government sector, and then it still can be however it is defined, but, it has to be defined, and if not, an addenda issued in the traditional paper manner that then does define it.
That is the only issue that relates to things like addenda. However, publishing and distributing the book itself devolves to copyright rules and previous legal decisions.
There have been some advances in copyright, I think its about caught up to the 1950s now, maybe even the 70s.
Legal though, that goes by the rule that “its not legal until there has been a decision based on it, whether it is a law or not”, and the corallary, “everything is legal until there has been a decision based on it.”
Regarding Outlook and reply when read or received, that does not work if the system on the other end is not compatible. I used to send out all my emails that way, with other outlook users, I got the notification. And with some other systems I also got a notice. However, of all emails sent out of the office, less than 10 percent generated the reply when read. Someone can even have outlook and on the exchange server side disable that reply function, so an organization’s IT person or group can kill that function.
Virtually every bid form I recall seeing had a specific place for each bidder to acknowledge each addendum by number and date (with blanks to fill in on the form). That provides a record, but doesn’t make sure everyone has received them all before its too late. What may be important is that, with any system used, some followup be done for anyone not acknowledging receipt before bid time, in time to make doubly sure it’s received, and acknowledged in some recordable way, by all bidders.
Electronic communication has arrived and is here to stay. There is no stopping owners, consultants, contractors from taking full advantage of the technology. I remember a project on which I worked on in the mid 1980s where the contractor stole the Architect’s seal off a set of permit drawings. This goes to show that if someone is determined, they will alter a document in virtually any format.
That said, we are making increasing use of FTP sites like Buzzsaw to post drawings and specs, especially for fast track projects and those with multiple bid packages. Sometimes the owner pays for the site, sometimes we do, depending on the project, the schedule and if there is an overall project coordinator. The specs are posted in PDF format. Each section of the manual is “printed” in the manner described by David Lorenzini. Administrators for the better maintained sites send an e-mail alerting me to changes and new posts.
One thing I have not had time to investigate is how to create electronic copies of AIA documents. I suppose one could scan a hard copies and name the files so they follow the order of the manual. There are also copyright issues here.