Image via WikipediaI dislike templates 'usually' because I've seen too many people ignore defining their requirements and instead 'cutting & pasting'. That being said, templates serve a purpose of consistency and providing some 'legal' protection of the process through the use of standard terms & conditions/administrative requirements for the process.I'm currently assisting a client with developing an RFP template to be used by skilled and experienced procurement staff. Not a difficult assignment since I know the end-users understand the process so will need less 'prompts' in the template. This will be more about making their job easier and more consistent. It's also the first time I'm NOT having a template dictated to purchasing by the legal department!
In past, I've found the legal department develops the template terms and conditions and puts them up-front in the document, leaving procurement to fill in their requirements around it. Legal's point of view is to keep the legal information front and centre. From a technical writing perspective, the MOST IMPORTANT information should be front & centre.
So I ask you, what is more important in an RFP document - legal boilerplate or project scope/requirements? Please comment/email me or comment on twitter - I seek viewpoints from both the buying and selling sides!
No comments:
Post a Comment