JCON TO Proposal Development Process-DRAFT

JCON TO Proposal Process
Proposal Development and
Documentation Process and
Procedures
for
JCON Task Order Proposals
Revised January 20, 2004
ManTech Proprietary Page 1 5/26/2016

Section 1 Introduction
The fast-paced environment of responding to JCON Task Order RFPs requires a well-thought-
out process clearly communicated to all participants. The process should support the rapid
development of proposals (5-10-day turnaround). Since many RFPs are similar, we should take
advantage of good content that has already been written (and in some cases used in winning
proposals!). To that end, this Task Order Response Process has been developed. (NOTE: This
process addresses the technical proposal only; price proposal is handled under a separate
process)
Specifically, this process will enhance the team’s ability to:
• Adhere to schedules,
• Keep up with the pace while maintaining a high level of quality – we will accomplish this by
automating as much of the process as possible,
• Develop reusable content, place it on the share and USE it,
• Facilitate the interaction between ManTech and team members during the proposal
development process,
• Effectively communicate the solution by focusing on “how”, and finally,
• Repeat the process WITHOUT Tim when he moves into operational phase
Also this process identifies roles and responsibilities for various specific tasks.
Program Manager – Tim Withers. Overall JCON program responsibility
Deputy Program Manager -
Capture Manager – responsible for marketing activities prior to RFP release to gain insights
into customer that help develop the win strategy. (Jen Connell, Pat Clyne, Carolyn Ryan)
Proposal Manager – responsible for developing schedule, creates team contact list, creates
section templates for proposal; drives schedule; runs review meetings, distributes templates for
resumes and past performance with the content submission instructions to team members (Pat
Clyne, Carolyn Ryan, Cor Johnson, Victoria Fries)
Technical Lead – responsible for developing technical solution (Help Desk – Carolyn Ryan;
Installation – Jim Scammordella; – Wayne)
Technical Writer - Works with technical lead and proposal manager to understand technical
approach, win strategy; gathers reusable content.

The ManTech JCON Team
Name Role Work Phone Alternate Phone Email
ManTech
Section 2 The JCON Task Order Response Process
Is on the following page

Distribute Draft- Distribute Draft-
Figure 1. The ManTech Team JCON Task
Order RFP Response Process (Technical
Proposal Only)
• Capture Mgr
develops:
• Win Strategy
• Risk
ID/mitigation
strategy
• EVM strategy
• JCON Proposal
• JCON PM
• Notifies internal &
external team via email
• Assigns Proposal
Manager
• Assigns Technical
Lead
• Assigns Capture
Manager
Write
Proposal *
• Kickoff meeting
• All participating team
members (internal/external)
• Team validates win strategy
• Tech Lead briefs ConOps
• Writing assignments agreed
on
Withers,
Verna, Connell
confirm team
Proposal
Mgr. holds
Reviews
(Pink, Red,
Final
Production
and
QA/QC***
JCON PM
submits
proposal via
email to
customer
requesting
acknowledgem
ent of receipt
DOJ
acknowledge
s receipt
TORFP
Receive
d by
JCON
PM
CR
s/
DR
s?
CR
s/
DR
s?
JCON PM
decision on
participants Opportunity
Status
updated at
Monthly BD
Meeting
Opportunity
Status
updated at
Monthly BD
Meeting
• Proposal Mgr:
• Places RFP on share
drive
• Develops Schedule
• Develops
Outline/Distributes
Instructions
• Develops Kickoff Agenda
• Tech Lead:
• Develops
ConOps
• Assigns writing to
Team
Print copy of all
TO-related
documentation for
library
Print copy of all
TO-related
documentation for
library
Proposal
Mgr
oversees
Response
JCON PM
submits
CR/DR
Response via
email to
customer
requesting
Process Complete
Award Pending
Process Complete
Award Pending
DOJ
acknowled
ges receipt
Proposal Mgr.
records on
consolidated
schedule
Proposal Mgr.
records on
consolidated
schedule
• ManTech internal
notification
• Decide on TO
Lead, Notify
Team Members,
and Request
Intent to
JCON PM
designates
lead for
anticipated
task and mails
out Conops
template
Lead company
meets with
customer to
develop Conops
Create A CD Copy of Final
Proposal for Library and Log for
anyone checking them out
Distribute Draft-
Red Team
Distribute Draft-
Pink Team
Distribute Draft-
Blue Team

Section 3 Shared Drive Directory Structure
and Documentation Control/Architecture
In the dynamic JCON environment in which the Government allows very little turnaround time for proposals, it
is extremely important to work efficiently to ensure minimal overlap and/or duplication of effort. Files must be
accessible to all but with ‘restrictions’. Those who access the files must use extreme caution and communicate
clearly with others as to what has taken place in the file or whoever might have a need to access the same files.
No more than one person at a time should be in the same file as this prevents any type of file corruption or lost
data.
At the same time, we cannot afford to ‘re-invent the wheel’ for each proposal. Proposals must be customized for
the customer in order to meet their requirements and have a winning proposal. We will use ‘boilerplate’ or
previously written content as much as possible as a framework for creating new proposal responses, making
special use of content from the JCON BPA proposal and sample tasks.
The following paragraphs discuss the procedure for managing configuration control of documents.
Major Objective:
Any person working on a Task Order (TO)/Proposal should be able to pick up at any point in the
proposal process and complete the proposal response.
1Main Objective:
Create a standardized format easy for everyone to use, increase productivity/turnaround time
and generate revenue.
Goal:
Decrease amount of time in duplicating efforts, create a more organized structure for proposal
responses/task orders, and increase productivity to be more efficient.
A shared drive has been set up for all TO proposal development work. It is crucial that this structure be
utilized. The structure is as follows:
Proposal Development (Directory –Writing)
• There will be a primary author identified for each proposal effort normally the Proposal Manager and a
backup person normally a writer. This person usually the Proposal Manager will be the keeper of the
“master” document and input while being the focal point for pulling all sections together into a cohesive
document. The primary author is the ONLY person authorized to work in the master file unless other
authorizations are communicated.
• Other contributors (authors or reviewers) can access the master file for reference purposes but should NOT
alter the file unless specifically requested by the primary author; at which time a new version should be
Notes:
* It is critical that authors use the directory structure described in Section 3 of this
document.
** See Section X for description of review process
*** See Section X for description of final production process

created and the older version saved into SAMPLE: K:Task_OrdersEOUSAJCON EOUSA Equipment
RepositorySourceBackup Copy.
• Other contributors should save their (interim) work in separate files as INPUT using the following naming
convention:
TOxxxx_Section <#>_<Author’s initials>_<mmddyy>_<time> and save it into
EXAMPLE:
Task_OrdersEOUSAJCON EOUSA Equipment RepositorySourceInputPartner Name-
Date
• Independent Contributors and Team Members should notify the primary author (Proposal Manager) and
CC: Capture Manager and assigned Writer (via email or in writing) indicating in a separate WordPerfect
document that they have NEW Input and/or section/question number of their changes should be identified
either as a complete replacement and/or a change in a different colored font such as blue or red. The
primary author will copy all relevant sections and/or changes to sections into the master file as appropriate.
• The Proposal Manager will be responsible for managing the directory for that proposal effort and the
proposal status. He/she will copy or move files as appropriate. The Proposal Manager is responsible for
communicating the process to all team members and must set the expectations of following these procedures
to ensure that the process becomes effective in preventing duplication of work and version control.
• During the development process it is critical to always have a back up copy of the file and place it into the
Sourcebackup copy folder and at the end of each day as well as a backup copy after every pink, red and
blue team review. This ensures that we do not have to recreate or rewrite sections. However, it may become
necessary for sections to be rewritten. In that event, the primary author will copy and paste relevant sections
and provide to the appropriate contributors.
• CONTRIBUTORS SHOULD NOT WORK FROM OLD VERSIONS THAT THEY MAY HAVE
STORED ON THEIR DESKTOPS OR EMAILED COPIES OR OTHER “UNOFFICIAL”
LOCATIONS AT THIS POINT. THEY MUST WORK FROM THE VERSION PROVIDED BY
THE PRIMARY AUTHOR AND IT IS ONLY FOR REVIEWING PURPOSES—NO CONTENT
CHANGES SHOULD BE MADE IN ANY DISTRIBUTED DOCUMENT OUTSIDE OF THE
ORIGINAL MASTER FILE.
Proposal Manager must communicate this clearly to the team to ensure that they receive the input
and changes to input in a usable file format. If it is not received according to the instructions then a
written request must be sent out by the Proposal Manager requesting the information be sent in the
originally instructed format.
• A copy of all review versions of the files shall be placed in Sourcebackup copy folder by the Proposal
Manager and the file should be named with the following convention:
<TOxxx>_<JCON Division>_<Color Review>_<mmddyy_time>
Final Deliverable (Directory – Final Deliverables)
• When the primary author has finalized the file for submission, he/she will notify the proposal
manager and the technical writer. The file name should follow the convention:
<TOxxx>_JCON Division>_Ready for Final>_mmddyy_time>
• The Technical Writer will finalize the document by completing an edit and performing the items in
the checklist in Section 7 of this process

• The Technical Writer will rename the file using the following convention and notify the Proposal
Manager that it is ready to be delivered.
<TOxxx>_JCON Division>_Final Deliverable>_mmddyy_time>
• The Proposal Manager will move the final deliverable files to the directory labeled “Final
Deliverables” NOTHING SHOULD BE PLACED IN THIS DIRECTORY EXCEPT THE
FINAL FILES AND ONLY THE PROPOSAL MANAGER SHOULD PLACE FILES IN
THIS DIRECTORY
File Folder Architecture For Proposals
Folders should be set up the same day that the task order/proposal is kicked off either by the
proposal manager or Cor Johnson. Below is a sample of the proposed structure on the left side
of this screen shot for the team's to use.
Proposed Folder Definitions of Use:
TASK ORDER
Task Order Name File folder with Date
EXAMPLE: K:Task_OrdersEOUSAJCON EOUSA Equipment Repository
Admin - Contains all pertinent information to the task order, team contact list, assignment
matrix, and copies of important email.
Solicitation solicitation files, addendums if any
Q&As Q&As
Boilerplate - Contains information for the team to use as a framework for crafting and
customizing the proposal's solution.

Input -
Team Member folder w/date - create an individual folder for each teaming
member/company and insert all received content for the
proposal.
Backup Copy - At the end of each review create a backup copy to be placed in this folder.
Writing (PM and Editors)- Contains only 1 version of the most up-to-date copy of the
proposal broken down by section. Only person in these files or have rights to these
files is the Proposal Manager and Writer/Editor. The proposal manager will decide
on designated production day whether or not to combine the sections into one
document or not depending on the file size to prevent corruption of files.
Appendices or Attachments folder - This folder should contain only files that will be
considered attachments or appendices.
Final Deliverable - Contains only the final proposal documentation submitted to the
customer.
EXAMPLE:
JCON
Task_Orders
<Division Name with Task Order number>
Background Information
<Division Name_TOxxxx_project name> (could be multiple folders here)
Admin – (contains schedule, outline and contact list)
Notes and Customer Info
Solicitation
(all information received from customer placed here)
Q&A;s
Pricing (Restricted)
Final Deliverables
Boilerplate
Input
Team Member(s) Input Folder
Back Up Copy-contains copy of pink, red, blue team and
copies of proposal as changes are made
Writing (PM and Editors)-Contains most recent copy of the
proposal at all times.
Obsolete-all old or files that are not usable should be inserted
here

File Folder Architecture For Archived Task Orders and Boilerplate
Boilerplate Content (Directory – K:jcon shared driveBoilerplate)
As previously noted, the automation of this process relies heavily on the reuse of valuable content as a
framework for customizing bid responses. To facilitate this, the following content is being developed and
inserted into template format and placed in the following directory structure has been established:
Below is a visual sample structure for the Task Order and Boilerplate archives.
JCON
Boilerplate-Boilerplate
BoilerplatePast Performances
BoilerplateApplication Design-Development
BoilerplateCable Plant
BoilerplateHelp Desk
BoilerplateImplementation-Rollout
BoilerplateNetwork Server Administration
BoilerplateOffice Automation
BoilerplateRequirementsAnalysis-Design
BoilerplateTechnical Approach
BoilerplateTraining
ManTech_Standard Operating Procedures
ManTech_Plans
Program Management Plans
Installation Plans
Transition Plans
Training Plans
Resumes
Help Desk

Performance_Service Level Agreements
Risk Mitigation
Bids Archive For Previous Year
At the end of six months bid responses will be moved to the current years “Bids Archive Folder” this
will allow future boilerplate to be created and to have bid responses that are completed moved to a
different location than current bid responses being worked on. A sample of the structure is below:
Discussion/Action Items/Training
1) Finalizing standardized templates for all documentation in WordPerfect and Presentations: title
page, table of contents, main proposal section, past performance/qualifications, resumes, and
cover pages for individual sections where necessary.
A. Need to be breaking sections for the document to prevent file corruption, allowing more
than one person to insert and edit content and easier recovery of files to prevent loss of
documentation.
2) Need WordPerfect Representative at the Advanced or Expert Level for training of the advanced
features of the application to facilitate productivity and no duplication of work or to have the
training cds.
3) Train the team on proper formatting and acceptable procedures for crafting and completing
proposals.
4) Need to acquire all necessary software to facilitate the process for completing quality
proposals, conducting changes in live reviews and developing an internal website to allow for
accessible bid resources.

Section 5 - Document Process
All communication and information relative to the proposal should be communicated in writing to the
team including changes, updates and inserting content to files. Proposal Manager and Writer/Editor are
the only ones to have rights to the files in the writing folder.
**Need Teaming Partner Procedures for submitting content and changes throughout the proposal
process.
• All content should be submitted in a newly created document using only WordPerfect.
• All Changes must be submitted in a separate document indicating the change and submitted
electronically where possible.
• All graphics/diagrams etc. to be sent in their originally created file format as available. Notify
Proposal Manager where not available
Capture Manager –
• Win Strategy
• Risk ID/mitigation strategy
• EVM strategy
• Assist in providing SME support to the team to continue facilitating the proposal process.
Proposal Manager-
• Creates Outline.
• Creates Proposal Folders according to the required structure.
• Creates Blank Sections in the required format including a table of contents and adhering to the
distributed outline.
• Creates Contact List.
• Copies important email into the admin folder throughout the process.
• Received content is inserted into the source/input folder by teaming partner and subject matter
expert with the date in the file name.
• Creates Schedule, sets expectations to the team on how the proposal is to be structured, how
content should be submitted, and assigns proposal sections/questions using a matrix.
• Distribute Past Performance and Resume Templates to the team.
• Manages the revision process and version control to eliminate duplication of work efforts and
corruption of files.

Contract Summaries/Past Performance References
Project Date Last
Validated
Program
Management
Help Desk Installation Training # Users Geographic
Locations
Software
Maintenance
Hardware
Maintenance
Deskside
Support
Technology
xxx 24 x 7
M_F; 9-5
Sa, Su; 10
Level 1; 15
Level 2
2000 PCs per
year for 6 years
Classroom,
CBT
20000 15 locations
worldwide
Resumes
Name Program
Management
Software
Skills
Hardware
Skills
Help Desk Installation Training
xxx 15 years PM
with NASA
Windows (95,
ME, 2000,
XP), MS
Office Suite,
Project
Scheduler,
Level 2 and 3
support for xx
help desk for 2
years supporting
xxx applications
N/A Classroom, CBT

Section 6 - 1Instructions for Submitting New Content and Content Changes
from All Content and Team Member Contributors
• All content must be created in a WordPerfect document to help the team avoid having
corrupted documents and maintain version control.
• Proposal Manager will maintain an original version of the proposal using the sections
created at kickoff and insert content from source documents submitted by team
members.
Revised Proposal Process
Ideally, the process of submitting changes needs to be simplified to allow the proposal manager
and other members assisting him or her in a quick turn around of revising the proposal.
Depending on the team members familiarity and comfort level with WordPerfect will
determine, which of the following methods they will use:
• Any team member can submit changes in either of the following formats. Using the
reviewer function in WordPerfect identifying the changes made and these will be
inserted into the main document.
• For any team member not familiar with the reviewer function in WordPerfect they can
either submit changes in a separate document using a different colored font or
indicating that the change is a replacement referencing the section/question it is for or
use the redline/strikeout method in the font menu for deletion and use red or blue font
for additions.
• Please name the file with the associated section and SME initials to allow us to track
content files and maintain version control.
• All graphics must be sent in their original file format where possible and where not
possible contact the proposal manager.
• If you have files that were originally created in MS Word and you want to reuse the
same information, please contact the proposal manager for instructions.
• For All Pink, Red, and Blue Team Reviews, any changes where possible will be
submitted in electronic format only, if you have hard copy changes please notify the
proposal manager.
• All content must be submitted directly to the proposal manager: XXXXX, Proposal
Manager, AND CC: XXXXX, Capture Manager and Tim Withers.
• Please use the templates for Resumes and Past Performance and limit them to 2-3 pages
only depending on solicitation requirements and page count limitation.
***Please note that this is the new procedure any deviation from the above requires notification and
agreement from the proposal manager.
Page 14

Completed Bids
Notification to the team of any new information that should become boilerplate, success stories or
failures.
Future Proposed Procedures:
Laptop for All Reviews for changes to be made live during the review to speed up the productivity.
Will be creating a Style Guide for everyone's use and to have a standardized process.
Page 15

Section 7 Formatting and Editing of Proposal Documentation
1Style Sheet For Proposal Main Sections
Editing proposals consistently across the team is important to sending the appropriate message
to our customers. The following styles have been created to keep the consistency and professional
image of the proposals.
Main Body of Proposal
All proposal text is 11 point font, Times New Roman flush left for when page count is an issue
and when page count is not an issue use F7 and indent the proposal response in the sections. Spacing
between heading and main body of text should be 6 point. Option 1 is preferred, however, sometimes
the space is needed to meet the page count requirements, in these cases only, use the Option 2
formatting.
Sample:
OPTION 1
1.0 BACKGROUND
The ManTech Team
OPTION 2
1.0 BACKGROUND
The ManTech Team
Level Heading 1 15 POINT FONT, TIMES NEW ROMAN, SMALL CAPS
Level Heading 2 14 point font, Times New Roman, Bold
Level Heading 3 12 point font, Times New Roman, Bold, Italics
Level Heading 4 11 point font, Times New Roman, (no bold)
Level Heading 5 10 POINT FONT, TIMES NEW ROMAN, SMALL CAPS, (NO BOLD)
Level Heading 6 10 point font, Times New Roman, Bold
Level Heading 7 10 point font, Times New Roman, Italics, (no bold)
Sub Heading 1 12 point font, Times New Roman, Bold, Italics
Sub Heading 2 11 point font, Times New Roman, Bold
Sub Heading 3 10 POINT FONT, TIMES NEW ROMAN, SMALL CAPS
11 point font, Times New Roman, Bold, Italics
Call out Boxes or Win Theme Captions
Bullets
Bullets and bullet spacing should be 3 points and should look by the sample style below:
Page 16
111 point font, Times New Roman, Bold,

# Bullet 1 Square bullet, 11 point font, Times New Roman, Navy Blue
• Bullet 2 Round bullet, 11 point font, Times New Roman, Black
! Bullet 3, Hyphen bullet, 11 point font, Times New Roman, Black
Headers and Footers
Headers and footers should contain specific information pertaining to the task order response.
Please refer to the samples below:
Header
[NAME OF TASK ORDER DIVISION] THE MANTECH TEAM
Style for header is 10 point font, Times New Roman, Small Caps, Navy Blue and must include
the above information and horizontal line, Navy Blue.
Footer
[Centered Page Number] 14 January 2004
Style for header is 10 point font, Times New Roman, Navy Blue and must include the above
information and horizontal line, Navy Blue.
Figures, graphics, and tables should be number consecutively throughout the proposal,
i.e. figure 1, 2, 3... and table 1, 2, 3. Using the following styles will assist in formatting of the
proposal.
Tables
Table titles should be 11 point font, Times New Roman, Bold. Tables should have black 100%
Fill and in the Table heading only, using 12 point font, Times New Roman, White, Bold. Table text
should be 11 point font, Times New Roman. Table Subheadings should be 11 point font, Times New
Roman, Bold, Italics.
Graphics
Graphics should be requested and obtained in their original file format where at all possible and
converted to a JPEG or GIF compressed file and inserted into the proposal.
Figure Captions
Should contain the following information. Figure XX. [Title of Figure identifying use or meaning].
The appropriate style is: 11 point font, Times New Roman for the word Figure and Figure number, and
italics of the figure title no bold.
Please use the resume and past performance templates located on the JCON drive under
Template_FormsWordPerfect Templates. Styles for past performance and resumes are below.
Page 17

Resumes
NAME OF PERSON, 15 point font, Times New Roman, Bold, Small Caps
In the box containing required information, the styles are:
Response to requested information is 11 point font, Times New Roman. What information that is being
requested, i.e., Title, Education, Responsibilities, Citizenship, etc., is 11 point font, Times New Roman, Bold,
Small Caps.
Body of the resume should follow the following styles:
Technical Experience should be 12 point font, Times New Roman, Small Caps, Bold and the same for the main
headings of the resume. Subheadings such as company name should be 11 point font size, Times New Roman,
Bold Small Caps and the and job title should be 11 point font, Times New Roman, Small Caps, No Bold. All
resume position/responsibility information should be broken into a bulleted style format. The same bullet styles
apply in the resumes, that are in the main proposal.
Past Performance
Styles have been set up in the template. The proposal text should be 11 point font, Times New Roman and all
headings should be 12 point font, Times New Roman, Bold, Italics. Depending on the proposal
requirements will dictate whether or not a seven item or eight item past performance is used.
Page 18

Section 8 Proposal Reviews
Pink Team (1st
Draft) Review
• The Pink Team Review is a status check to ensure that we are getting off to a good start. During this
review the Proposal Manager checks for “planned” compliance with SOW requirements and for
consistency across sections.
• The Proposal Manager will emphasize and communicate the instructions for submitting changes to
ensure that version control is maintained. Since the document will be a detailed outline at this stage,
check the author’s notes re: the content that WILL BE in each section of the document.
• Reviewers should be able to identify the overall strategy and approach, even though the sections won’t
be complete at this point.
• Reviewers are the authors and may include management. Usually the document is broken up and
authors review each others’ sections (but not their own). Map the planned content to the compliance
matrix and note any holes or discrepancies.
Red Team Review (how much better are we than we were at Pink?)
This is a critical review, as it gives the team an opportunity to “get well” with sufficient time to recover if
necessary. At this point the document should contain data for each section. There should be no holes.
Red Team review is primarily a compliance review. Select reviewers who have NOT participated in the
proposal development. This will provide an objective view.
Provide each reviewer with the RFP and any Q&As as early as possible so they can become familiar with the
requirements. Since there will be a short time allowed to read and review the document, any preparatory work
they can do before receiving the proposal will help ensure a thorough and more meaningful review.
To the extent that they are available, the following individuals should be Red Team reviewers:
Help Desk – Carolyn Ryan
Installation – Jim Scammordella
Blue Team Review (how much better are we than we were at Red?)
This is the final formal review and is another critical step in the process. This review simulates the government’s
evaluation process as closely as possible. Reviewers should check for the following:
1. Compliance with RFP; discussion of each RFP topic
2. Clear presentation of plans, approaches, policies, procedures
3. Compliance with proposal instructions; logical and compliant organization of sections
4. Justification of any exceptions being taken
5. Use of customer’s language vs. ManTech or industry lingo; giving them what they want
Page 19
All changes must be completed electronically in a separate WordPerfect document indicating
the section/change and submitted in writing to the Proposal Manager CC: Capture Manager
and Tim Withers.
and Tim Withers.

6. Overall effect of proposal; the document is a good selling tool; best possible presentation of the
ManTech Team
7. Proposal is clear, convincing, compelling
8. Strategy is clear; justification/substantiation of claims
9. Effective use of theme statements, headings, action captions – they communicate clear and convincing
messages
10. Presence of BENEFITS as well as FEATURES (being careful to distinguish the two); clarity of WHY
and HOW the features will benefit the customer
11. Demonstration that ManTech really wants to work with the customer and intends to provide what the
customer wants/needs
12. Understanding of customer’s technical and fiscal limitations; absence of arrogance
13. Effective ghosting of competition
14. Effective use and clarify of visuals
15. Crisp and clear writing style
16. Overall “believability” of proposal
Provide each reviewer with the RFP and any Q&As as early as possible so they can become familiar with the
requirements. Since there will be a short time allowed to read and review the document, any preparatory work
they can do before receiving the proposal will help ensure a thorough and more meaningful review.
Rating System for Blue Team Review
Blue (Exceptional)
• Proposal fully complies with or exceeds RFP requirements and provides convincing detail
• Superior understanding of needs, problems – offers sound, realistic solutions
• Clearly superior technical approach – offers advantages in scope, feasibility, design
Green (Satisfactory)
• Proposal complies with RFP requirements and includes sufficient detail for thorough evaluation
• Demonstrates understanding of nature and scope of requirement
• Technical approach is sound and has sufficient supporting evidence
Yellow (Marginal)
• Proposal barely or partially meets RFP requirements
• Requirements are misunderstood
• Technical approach is risky or marginally compliant
Red (Unsatisfactory)
• Proposal does not address requirement or does not include sufficient detail to permit thorough evaluation
• Offeror misunderstands nature or scope of requirement
• Technical approach is incompetent and would not meet requirement
Page 20
and Tim Withers.

Section 8 Final Document Preparation/Quality Checklist
• Document conforms to established format guidelines (1st
level heads, font type and
size, etc.) Please see Victoria Fries for standardized styles and guidelines.
• Header includes program name on left and the words “The ManTech Team” on
right
• Footer includes page number in center and date in format “dd Month, Year” on right
• Spell check has been run
• Globals have been run
• Acronyms are spelled out on first occurrence
• Figures are called out before figure occurrence
• Figure titles/captions are presented in the format Figure X. This is a Great Figure.
A style guide will be created to accompany the process along with standardized templates.
Page 21

Appendix A Acronyms and Globals for JCON Task Order Proposals
Acronyms
DOJ – Department of Justice
JCON – Justice
BPA – Blanket Purchase Agreement
TO – Task Order
Globals
ManTech Team
JCONII (vs. JCON2)
Page 22

JCON TO Proposal Development Process-DRAFT

Recommended

Recommended

More Related Content

What's hot

What's hot (11)

Similar to JCON TO Proposal Development Process-DRAFT

Similar to JCON TO Proposal Development Process-DRAFT (20)

JCON TO Proposal Development Process-DRAFT