Rule #3 for preventing version-control problems is this:
Pass version control clearly.
Continue reading“Preventing Version-control Problems: Rule #3”
Rule #3 for preventing version-control problems is this:
Pass version control clearly.
Continue reading“Preventing Version-control Problems: Rule #3”
Rule #2 for preventing version-control problems is this:
Have clear rules for handling online files.
Goodness. It sounds simple, doesn’t it?
Continue reading“Preventing Version-control Problems: Rule #2”
An RFP section that lays out the proposed terms and conditions under which the Work will be contracted. Sometimes open for discussion through the question and answer (Q&A) process, but unilateral rejection of any term or condition by a bidder at the time of submission is usually considered grounds for finding a proposal non-compliant. Continue reading“Term: Draft Contract”
Primarily the legal agreement between the client and the contractor that specifies the terms and conditions under which the Work is to be delivered. In some industries, however, it refers to the body of Work executed by the contractor under the contract: what some other industries refer to as a “project.”
See also “draft contract.”
Everyone who works on proposals has a version control story. Well, everyone has a version problem story.
In these days of online document repositories and shared network drives, version control of RFP response documents has gotten trickier, because everyone can usually access everything all the time. But there are simple rules for maintaining version control. Continue reading“Preventing Version-Control Problems: Rule #1”