- Location. Location.
Not aligning subcontractor names and locations in SF330 Section C with the locations shown on the resumes (Section E) and projects (Section F) or not including Part IIs for each of the office locations mentioned in C, E, and F. #Protip – crosswalk the firm names and locations in C against the locations for person’s resume in E and each project the subcontractor worked on in F, THEN make sure each location that is included has a Part II. #Protip 2 – order your Part IIs in the same order as shown on Section C. - Relationships that matter.
Not showing all the items required in SF330 Section G. The SF330 is designed to demonstrate relationships among people and firms. To Section G matrix is the main place to show this. Make sure that the correct office location is selected for each project’s or opportunity’s subcontractor or vendor. Match each employee name and role shown in Section E to the same role on a project shown in Section F. #Protip – arrange your personnel by role, not by firm, so the matrix population is mixed across the board, not by chucks for each firm. - Using internal titles not roles in the solicitation.
Use general terms for employee roles, for example, Project Manager instead of Electrical Engineer. Add the more general employee roles to the Employee Role code table. These general roles can be used in the Project Role column in Section F. Likewise, add more general roles for vendors to the Vendor Role code table. These general roles can be used for vendors and consultants in the Role column in Section F. #Protip – use the exact roles from the solicitation for box 13 and repeat that role in the project descriptions on the resume, and in Section G. - Not following instructions for Section H.
The solicitation is usually pretty direct with the information they want in Section H. This is found, generally, in the selection criteria discussion on the solicitation. But don’t just look there, make sure the solicitation doesn’t have hidden requirements in other sections (things such as % involvement of each firm, DUNS numbers, points of contact, etc.). Find these items and populate your proposal checklist with these details so you make sure to put everything where they want to find it! #Protip – don’t add more than what they ask for – follow the criteria they want and give them your best qualifications. - Not capturing data gathered during the writing process to use next time!
So much data is gathered during the writing of and SF330 – client contact information, dates, costs, key personnel… All of that needs to be captured into the company database for future use next time. If that database is a well-organized server directory or something customized like Contract Cloud or Cosential the data you collect must be entered so you can find it easily next time. #Protip – having the data you need at your fingertips makes the next proposal much easier and you can focus on writing to enhance your win themes, not chasing down dates and fees!