Tech Project Management - The Proposal Document

  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

The Proposal Document, which may be referred to as the Business Case, explains the problem together with a description of how the problem will be solved and includes a high-level estimate of what it will cost to develop and deploy the solution.  

Editor's Note: This article is excerpted from chapter 3 of Fundamentals of Technology Project Management, by Colleen Garton and Erika McCulloch.

For an external project, the proposal planning will begin for the development company after they receive a Request for Information or a Request for Proposal from a prospective client. The client company will have completed the Project Concept and will have been through an internal approval process before sending out the RFI or RFP documents to prospective vendors. For an internal project, the Project Proposal will be based on the approved Project Concept.

The Project Proposal Document will include a high-level description of the project and the proposed solution. The Proposal will be submitted to senior management (or to the client) for approval to move on to the project definition stage of planning, where the Project Charter and Marketing Requirements Document are created. A Project Proposal can be a very detailed document, or it can be a very high-level, conceptual document with a lot of open issues that will need to be addressed later in the planning phase. The accuracy of the estimates and costs are contingent upon the level of detail contained in the proposal. An external project will require a much more detailed proposal than an internal project. The client (whether internal or external) will be unable to approve the project to move ahead without a pretty good idea of the time, cost, and effort involved in the project. If you are asked to submit estimates for a RFP document, be sure to document the accuracy of your estimates and any assumptions used to come up with the estimates. If a disclaimer is necessary, include it. For instance, if you are not sure how you will be able to solve a specific problem due to the immaturity of the technology being proposed, clearly state this on the proposal. If the client is not told that no one else has solved this problem yet, they may go into the project with unrealistic expectations! Don’t try to tell them what they want to hear just to get the contract. It will come back to haunt you. Remember that the key to keeping your clients happy is to under-promise and over-deliver.

The following information will typically be included in a Project Proposal Document:

  • Executive summary
  • Corporate and cultural information
  • Previous projects and clients
  • Client references
  • Development methodologies and processes
  • Quality assurance and testing processes and procedures
  • Development environment
  • Assumptions
  • The problem
  • Proposed solution(s)
  • Constraints, limitations, and risks
  • Proposed project phases
  • Milestones and deliverables
  • The proposed project team
  • Costs and payment details
  • Terms and conditions
  • Proposal submission and questions
  • Proposal acceptance and approval

Some sections of the document will not be required for internal projects, such as corporate and cultural information, previous projects and clients, client references, and terms and conditions.

Executive Summary

For external projects where proposals are submitted in response to RFPs, an executive summary is very important. If the company requesting the proposal has never worked with your organization before, the reviewers will need some compelling data that compares you favorably with your competitors. The executive summary should include a brief history of the company together with some high-level financial information. The executive summary is a key input into the decision-making process as many of the proposals are likely to be similar in solution and costs. If a company is investing a substantial amount of money in a project, the decision makers need to feel confident that they are working with a high-quality, reputable company.

Corporate and Cultural Information

This section will contain additional information about your company and the technical department(s) that will be involved in the project. It should include a corporate overview and some information about the company culture. For example, it could include operating values or mission statements for the engineering department.

Explain whether the company has a casual, informal culture or a disciplined, formal one. This information could be very important to the client’s selection of a vendor and will ensure that there are no misconceptions should the project be approved and awarded to your company.

Previous Projects and Clients

This section will contain descriptions of previous clients and projects that were similar to the project the client is proposing or that will demonstrate your

organization’s expertise and experience in project management and development.

For reasons of confidentiality, you may not be able to cite the names of some of your clients or too much detail about the projects you implemented for them. High- level information with a description of the market space that the client operates in, together with a synopsis of the success of the project(s), will be sufficient.

Client References

Here you should list some of your clients who have agreed to give references regarding projects you have implemented for them. Include contact names and titles as well as a brief description of the project(s) you worked on for each client.

Development Methodologies and Processes

This section will include an overview of the project lifecycle and the documentation that is produced during each phase. It should also include information about processes and procedures for such things as configuration management, quality management, source control, security, and any other standard processes used during the development of projects.

Quality Assurance and Testing Processes and Procedures

Quality assurance processes, procedures, and methodologies should be outlined together with an overview of the documentation produced at each step of the lifecycle. There may be testing outside of the quality assurance team that also needs to be accomplished (e.g., performance testing, security testing, product verification/acceptance testing).

Development Environment

This section includes a brief description of the development environment. This will include details about the hardware platform for development, including operating system, design packages, programming software, unit test software, and so on.


This section should contain both organizational assumptions and technical assumptions. Organizational assumptions would include such things as the expectations the vendor has from the client (or the project team will have from the internal client or sponsor) as far as involvement in the project, client responsibilities such as testing or documentation, or client representatives for the project (project manager, for example). Technical assumptions will include items such as the client’s existing hardware, systems, and software that will be used for the project; specific technology that will be used in the development of the product; or consultants who will be engaged for specific areas of development requiring specialized knowledge or skill sets. A lot of assumptions will need to be made to create a Project

Proposal Document. It is important to document assumptions so that there are no misunderstandings later on.

The Problem

This section includes a brief description of the problem. This can be taken directly from the RFP or the Project Concept or can be elicited from the client via phone conversations or meetings.

Proposed Solution(s)

This section contains details about the proposed solution or solutions. There may be more than one way to solve the specified problem, and if this is the case, give the client some alternatives. Different solutions should not be presented if they are just variations on the same theme. For example, do not present the same proposed solution with just one or two details changed. These specific options can be discussed and finalized later if the client decides to go ahead with the project. If you present 350 possible solutions, you will overwhelm the client with too much information, making it impossible for them to make a decision.

Constraints, Limitations, and Risks

Note any known constraints, limitations, or risks that are currently known. This can include things such as the timeline for starting the project. You may need to complete another project before you would be available to work on this one. Any limitations that your company has with regard to technology, knowledge, and skill sets should be identified together with a proposal for how you would manage them should you be awarded the project. Risks are things that are obvious to you based on the information that the client has already furnished. It is important to ensure that you and the client are on the same page with what you consider to be constraints, limitations, or risks for the project.

Proposed Project Phases

The project may need to be developed and delivered in phases either because the client has requested it in the RFP or because you feel that the size and/or complexity or the project warrants it. For example, the project may consist of three distinct products that need to be developed consecutively because of dependencies between them. You may propose that the project be delivered in three phases, with one of the products being delivered in each.

Milestones and Deliverables

High-level project milestones and deliverables are detailed here. These would include the project phases, if relevant. At this early stage of the planning phase, the milestones may be confined to approximate dates for completion of specific documents for the planning phase and a high-level timeline for when each of the subsequent lifecycle phases will be concluded. It should be obvious from the RFP and the solution section whether there are other key milestones or deliverables that should be specified.

The Proposed Project Team

The proposed project team will include the specific roles/positions needed together with some high-level qualifications and skill sets. Individuals do not need to be identified at this point. If it is known who the sponsor and the project manager will be, then name them. If you are not sure, you can specify that you have three project managers, all of whom have at least six years of project management experience, and that one of those managers will be assigned as soon as the project contract is awarded and timelines are finalized.

Costs and Payment Details

This section will contain high-level estimates based on the initial estimates created for the Project Concept or the budget information contained in the RFP. Payment details will contain the payment terms. For example, payment for creating the remaining planning documents may be required prior to the project kickoff. Payment for development may be in installments. Some companies ask for 50 percent up front and 50 percent on completion of the project.

Terms and Conditions

This will include some legal jargon that will most likely be supplied by the legal department. It will contain some disclaimers related to the accuracy of the information contained therein, together with contractual requirements for the approval to move forward with the project.

Proposal Submission and Questions

This section will include the contact information of the proposal preparer, the date and time that the proposal was submitted, and the method of delivery. It will also include any questions the preparer has about anything in the RFP that was not clear. There may be some updates needed to the proposal before it can be finalized and approved if there are open issues/questions at the time the proposal is submitted.

Proposal Acceptance and Approval

By signing this document, everyone involved is in agreement that the Project Proposal Document is accurate and complete and is approved to move forward.

The client (or requester) will typically have a standard process for awarding the project contract to the chosen vendor.

Want to learn more about project management best practices now?  Pick up your own copy of Fundamentals of Technology Project Management, by Colleen Garton and Erika McCulloch - available and on sale at the MC Press Bookstore today!

Colleen Garton

Colleen Garton is a highly respected and experienced writer, consultant, and speaker. She is the author of two management books: Fundamentals of Technology Project Management and Managing Without Walls. Recognized internationally as an expert on virtual and global management, Colleen is an experienced and in-demand public speaker for numerous events and conferences around the world. She is also author of the blog Working With or Without Walls.

 Colleen has extensive management and training experience in the United States and internationally, with more than two decades of practical experience in traditional and virtual management spanning multiple industries. She is the owner of the Garton Consulting Group. Before founding the Garton Consulting Group, Ms. Garton held senior management positions at some major U.S. corporations.

You can follow Colleen on Twitter at @ColleenGarton and on Facebook.

MC Press books written by Colleen Garton available now on the MC Press Bookstore.

Fundamentals of Technology Project Management Fundamentals of Technology Project Management
Master the specific project management issues that technology professionals must face.
List Price $69.95

Now On Sale

Managing Without Walls Managing Without Walls
Optimize the effectiveness of your matter where they are.
List Price $37.95

Now On Sale

More Articles By This Author


Support MC Press Online





  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things

    Read Node.js for Enterprise IBM i Modernization Now!


  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!


  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.


  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline



  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.


  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact


  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using as a pre-built development environment



  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.



  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.



  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails


  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.



  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.