RFI language

Status
Not open for further replies.

e57

Senior Member
For those of us who have to write RFI's (Requests For Information) to various parties like GC, Arch's and Designers et al. Some of the general terminology has become a language of its own... e.g. "Please Advice" = many things... It could mean one of a few polite ways of saying, "Sort out the details - and do your job before you dole out this cartoon you call a set of plans"

Anyway, I was thinking of coming up with a dictionary of RFI terminology - just for fun, and wondered if anyone had any good ones to add.
 
Please advise "ASAP" =
maybe you will have an answer by 99% completion
(OK my bad, should have wrote "advise by noon Friday")

Please advise "3rd floor" =
answer will include 1st, 2nd, 4th, 5th, etc. floors

Please advise "use revision dated 7/15/08 or revision dated 8/15/08" =
answer include revision dated 2 years ago that you never saw.
 
jeremysterling said:
Please advise "ASAP" =
maybe you will have an answer by 99% completion
(OK my bad, should have wrote "advise by noon Friday")

Lately I have been using "Please reply in most timely manner possible" = Long lingo for dopes who obviously did not get what "ASAP" meant in the first and second RFI on tha same topic.... :rolleyes:
 
I usually try to hint asap by adding "Thank you for your help with this time sensitive matter" before my name at the bottom
 
If it is really time sensitive I usually put something in about how a delayed answer will result in additional costs. This has usually worked for me.
 
I have found a lot of subs and even a few of my own PMs don?t know how to write an RFI or maybe don?t understand that the key to a good RFI is getting the answers you want, and getting them quickly. To do this here are some simple tools I use to that end.

1) Be very specific with plan page numbers, detail number and specification section references down to the actual paragraph in the specs. The easier you make it for them to look up, the faster it will get done.

2) Include your own sketches, pictures, diagrams and cut sheets, the more info at their immediate disposal the better. Don?t drown them in documents, but do attached all the appropriate information.

3) Most RFIs you submit to the GC will be retyped in their RFI form to send to the architect and or engineer. Make it easy on the GC and send your RFI in an email so they can just cut-n-paste it in their form. If there is a specific form you have to use, fill it out, make a PDF, attach it, but make sure to include the ?cut-n-paste? version in your email.

4) State the problem, or ask the question, then offer one or more possible solutions, to answer to your question. Make it easy for them to say, ?We accept your proposed solution?. The more of their work you do for them the better chance you have of getting the answer you want fast.

5) If you have a relationship with the PE then call him and let him know the RFI is on the way and let him know what is going on. This is not always appropriate unless you have a working relationship with the PE but when you do it makes a big difference.

6) NEVER point they were wrong in any way, if an engineer gets his pride involve it will be at your expense. Even if they are way wrong make sure you give them an opportunity to save face with the solution you prefer. (This one is one of my trade secretes, I really had to think about whether or not it should be shared.)

Basically, you do not want to dump the problem on them or point out their mistakes, but you do want to give them the tools they need to answer it quickly and solve your mutual problem. One line vague questions will typically get the same attention you put in writing them, while detailed specific questions and references, posed with possible solutions will get better results and if you did a good job selling the solution it will be the results you prefer.

Just to be clear on this, the results you prefer are the ones that either make you money or save you money.
 
Status
Not open for further replies.
Top