PROJECT PROPOSAL DOCUMENT

OUTLINE OF THE CONTENTS OF A PROJECT PROPOSAL

The actual content of the proposal may vary depending on student and supervisor interests but
it must contain as a minimum, the following sections:

PART I: PRELIMARY PAGES

First page = The Title page (which should never be numbered) should contain the following
centred information:-
 University logo
 Name of faculty
 Name of the course/qualification towards which the project contributes
 Unit code and name
 Full title of the project
 Candidate’s name
 Registration number
 Name of supervisor
 The commitment at the bottom of the page

The second page should contain a declaration on originality of work –duly signed

The third page should contain the Table of Contents

The fourth page sgould contain the list of tables (should they be included in the document)

The fifth page should contain the list of figures (should they be included in the document)

The sixth page should contaion the list of acronyms and abbrevaitions used in the document

The senth page should contain the abstaract: which is a 1-2 paragraph summary of the main
document, i.e. the summary of the proposal

NB: preliminary pages ae numbered using roman numbers.

PART II: MAIN DOCUMENT

The main document starts at the eight page, the contents of which should follow the following
outline.

Section 1.0: INTRODUCTION

1.1 Background
This is usually a detailed background information about the project research area and about
the client. It should be clear on what business the client is involved in and how operations are
currently conducted. It sets the stage for the problems that will arise.

1.2. Problem Statement

This is a statement of the problem the project is intended to address. It should clearly show
the problem in the light of the project research and its contribution to the solution. Ideally it
should originate from the way the organization currently performs its functions. Each problem

1 Proposal Guidelines
Prepared by Rachael Kibuku
should be stated clearly with a brief explanation on how it arises from the functions be
undertaken.

1.3. Proposed Solution

This is a high level description of the proposed system touching on major system functionality
or features N.B. this should not be a basic statement of automating a manual system

1.4. Research Objectives

Clear, concise “SMART” objectives should be provided including research and system
development related objectives. They are the basis upon which the success of the project will
be evaluated. Therefore they should basically address each of the problems being faced by the
organization.
1.5: System Objectives
1.6: Justification/significance of the study

SECTION 2.0 :LITERATURE REVIEW

A review and discusion of earlier studies relates to the reaserch problem under investigation.
At three stsudies of cases from the apst highlighting the advantages and weaknesses and gaps
that you identify form the past studies or implementted systems.

SECTION 3.0: METHODOLOGY

This is basically an outline of the plan of action. It encompassess the all-round developmental
methodology driving your entire data collection to system development.
3.1 Indroduction
3.2 Research Methodology
3.2.1 Research Design
3.2.2 Population, sample and the sampling techniques
3.2.3 Data Needed
3.2.4 Data collection method and tools and their justification
3.2.5 Data analyis and presentation
3.2.6 Data interpretation Requirements
3.3: Development Methodology  Justification, description of the stages and the graphical
notations .

SECTION 4.0: BUDGET AND RESOURCES

This should generally address all the envisaged resources and a budget that will enable the
development of the system to succeed. The key items are hardware, software,human and any
other costs that will be incurred.
Table 4.1
S/N ITEM UNIT COST (@) QUANTITY TOTAL

TOTAL

2 Proposal Guidelines
Prepared by Rachael Kibuku
SECTION 5.0. PROJECT SCHEDULE

This is a breakdown of all the tasks that will be carried out in the course of carrying the
project. An estimate of the duration of each task in hours should be done. A work breakdown
schedule should be formulated and a task schedule/Gantt chart prepared.
A sample project schedule is as shown below:

Table 5.1
Task Description Task Subtask Planned Actual Planned Actual Deliverables
No. No. No. of hrs Start Start Completion Completion date
of hrs Date Date Date

PART III: DOCUMENT SUFFIX

References
References should be placed after the results and should be in APA format (make sure you
are familair with it). It is different for books, articles, periodical and newespapers. In case
you read certain material that you did not cite then you may include a list of a bibliograhy.

Appendices
Information that was not placed in the main write up but was refereced e.g. maps, table,
standard documents, etc should be labeled as appendix and placed at the end of the
document.

NB: Since the project deliverables are formal documents; the following specifications must be
observed;
a. The font style = Times New Roman

b. The font size = 12

c. Line spacing = 1½

d. The write up should be fully justified

e. Content of the title page should be in upper case

f. Titles should never be underlined; head titles are in upper case while sub-tittles are
in tile case (Capitalize the First Letter)

3 Proposal Guidelines
Prepared by Rachael Kibuku