Skip to main content Accessibility help
×
Hostname: page-component-77c89778f8-m42fx Total loading time: 0 Render date: 2024-07-19T19:13:44.105Z Has data issue: false hasContentIssue false

Chapter 8 - Finishing off

Published online by Cambridge University Press:  11 August 2009

Paul Coombs
Affiliation:
IT Project Estimation Limited
Get access

Summary

VALIDATING COMPLIANCE

You must do what the customer asks. If you are responding to an Invitation to Tender, Request for Proposal, or similar document, you must check that you have complied with all its requirements. These fall into two groups:

  • The physical requirements, which may include the expected format of the proposal, a list of sections to be included, how prices are to be presented, how many copies are needed and so on.

  • The technical requirements defining the system for which you are bidding.

The best method is to draw up a Compliance Matrix. On the left-hand side this lists the requirements from the customer, sentence by sentence, in the form of a cross-reference, the text itself, or both. The right-hand side shows how your proposal addresses each requirement. The result will be something like Table 8.1.

As you complete the matrix, you should be asking yourself if your response to each requirement is adequate, and presented in the manner asked for. You must provide a response to all the requirements in the Invitation to Tender, no matter how repetitive or pointless they may seem. So don't just respond with “As before”, “See the attached” or “Compliant” – give a full answer to each question asked.

You may choose to include the Compliance Matrix as an appendix to your proposal, either because the customer has asked for one, or because you would like to help them with their evaluation process.

Type
Chapter
Information
IT Project Proposals
Writing to Win
, pp. 113 - 120
Publisher: Cambridge University Press
Print publication year: 2005

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

  • Finishing off
  • Paul Coombs
  • Book: IT Project Proposals
  • Online publication: 11 August 2009
  • Chapter DOI: https://doi.org/10.1017/CBO9780511541339.009
Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

  • Finishing off
  • Paul Coombs
  • Book: IT Project Proposals
  • Online publication: 11 August 2009
  • Chapter DOI: https://doi.org/10.1017/CBO9780511541339.009
Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

  • Finishing off
  • Paul Coombs
  • Book: IT Project Proposals
  • Online publication: 11 August 2009
  • Chapter DOI: https://doi.org/10.1017/CBO9780511541339.009
Available formats
×