A thesis proposal is not a shorter thesis. It is a feasibility case. The committee reading it is deciding one thing: can this student finish this study, with the time, access, data and skills actually available, and produce something worth examining? Ambition is not what gets a proposal approved; a defensible plan is. This guide gives you the seven sections almost every Malaysian faculty asks for, a mirror test that catches the single most common rejection cause, and the checks to run before you submit.
Step 1: Get your faculty’s proposal format before you write a word
Proposal requirements in Malaysia are set by the faculty, not nationally, and they differ far more than students expect. Undergraduate FYP proposals are often 8–15 pages and reviewed by a coordinator; postgraduate proposals are frequently 20–40 pages and defended in a proposal defence session before a panel.
Before drafting, write down five things from your own handbook: the page or word limit, the required section headings and their order, the citation style, whether a Gantt chart and budget are compulsory, and whether the proposal is defended orally. If your handbook prescribes section headings, use those headings verbatim — reviewers mark against their own checklist, and renaming a section costs you marks for nothing.
Step 2: Write a working title that states variables, population and setting
A proposal title is a promise about scope. The version that survives review usually contains three things: what is being studied, in whom, and where.
Example you can adapt: “The Effect of Remote Work Arrangements on Job Satisfaction Among Executive Staff in Klang Valley Shared Service Centres.” Compare that with “A Study on Remote Work and Employees” — the second version tells a reviewer nothing about feasibility, because it does not say who you can actually reach.
Keep the title working, not final. It should change once your objectives are fixed in Step 4.

Step 3: Open with the problem, not the topic
The first paragraph of a weak proposal introduces a subject area. The first paragraph of a strong one names something that is going wrong, for whom, and with what consequence — then narrows to the specific gap your study addresses.
This section is the same instrument as the problem statement in your final thesis, so build it properly once and reuse it. The funnel pattern, the “already X, but not yet Y” gap formula and the sentence-level examples are in how to write a problem statement for research.
Length guide: in a 12-page FYP proposal, the background and problem statement together rarely need more than two and a half pages. Reviewers read the objectives next, and a bloated background delays the part they are actually assessing.
Step 4: Make objectives and research questions mirror each other exactly
This is the single most common reason proposals come back. Objectives and research questions must be the same list expressed twice — same number of items, same order, same variables. If you have three objectives and four research questions, one of them is unfunded work.
| Research objective | Matching research question | Matching hypothesis (quantitative only) |
|---|---|---|
| RO1: To determine the level of remote work adoption among executive staff. | RQ1: What is the level of remote work adoption among executive staff? | — (descriptive, no hypothesis) |
| RO2: To examine the relationship between remote work arrangements and job satisfaction. | RQ2: Is there a relationship between remote work arrangements and job satisfaction? | H1: There is a significant relationship between remote work arrangements and job satisfaction. |
| RO3: To determine whether the relationship differs by department. | RQ3: Does the relationship differ by department? | H2: The relationship differs significantly by department. |
Two rules that save a revision round. First, use one verb per objective and make it something you can actually do with data — determine, examine, compare, describe — not “to understand” or “to explore the importance of”. Second, a descriptive objective takes no hypothesis; adding one where nothing is being tested tells the panel you copied a template.
Step 5: Compress the literature into a gap, not a summary
A proposal’s literature section is short by design. Its job is to prove that (a) the concepts you will measure already have accepted definitions and instruments, and (b) somebody has not already answered your question.
A workable structure for four to six pages: one paragraph per key concept with its accepted definition, one paragraph per relationship you will test with what prior studies found, one paragraph on the studies closest to yours and exactly how yours differs, and one closing paragraph that states the gap in a single sentence. The full method for building this, including how to move from a reading matrix to prose, is in how to write a literature review for your FYP or thesis.
Reviewers look for one thing here that students often skip: whether the instruments you plan to use are borrowed from a named published source. Saying “the questionnaire will be adapted from Smith (2019)” is a feasibility signal; saying “a questionnaire will be developed” creates work you then have to validate.
Step 6: Specify the method concretely enough to be costed
This is where proposals are won or lost, because it is the only section that tells the panel whether the study can be completed. Write it as decisions already made, not options being considered. Six things must appear:
- Design. Cross-sectional survey, quasi-experiment, case study, and so on — named, not implied.
- Population and sampling frame. Who, how many exist, and how you will reach them. “Employees in Malaysia” is not a sampling frame; “executive staff at three shared service centres where access has been arranged through the HR department” is.
- Sample size with a stated basis. Give the number and how you arrived at it — a published table, a power calculation, or a rule for your analysis. The bases accepted for a Malaysian FYP are set out in how many respondents do I need for my FYP or thesis.
- Instrument. Its source, number of items, response scale, and how validity and reliability will be established. Scale construction and pilot testing are covered in how to design a questionnaire for your FYP.
- Analysis plan. Name the tests, matched to each research question. A panel that cannot tell which test answers RQ2 will ask you in the defence. Use the decision table in which statistical test should I use for my FYP data, and state the software you will run it in — see the statistical software comparison.
- Ethics and access. Which committee approval you need, whether a gatekeeper letter is required, and how consent and confidentiality will work.
The methodology chapter you eventually write is the past-tense version of this section, so drafting it well here saves the work later; the full chapter structure is in how to write the methodology chapter.

Step 7: Add the practical apparatus reviewers check first
Many students treat these as formalities. Panels use them as the fastest feasibility test in the document.
- Timeline. A Gantt chart against your actual semester weeks, not a generic twelve-month plan. Put ethics approval and data collection on it as separate blocks with realistic waiting time; approval is rarely instant.
- Expected outcomes. Two or three sentences on what the findings will let someone do differently. Not “the study will contribute to knowledge”.
- Scope and limitations. State the boundary honestly. A proposal that admits it covers one state and cannot generalise nationally is stronger than one that claims otherwise.
- Budget, if required — printing, incentives, transport, software licences.
- References, formatted in the style your faculty requires and complete. A reference list with missing DOIs is the cheapest possible thing to lose marks on; the rules are in what is APA 7th edition format.
Step 8: Run four checks before you submit
- The mirror check. Count your objectives, questions and hypotheses. Do the numbers match, in the same order?
- The instrument check. For every variable in your objectives, is there a stated way to measure it?
- The calendar check. Add up the weeks in your Gantt chart. Do they fit inside the semester you actually have?
- The stranger check. Give the proposal to a coursemate from another programme. If they cannot say what you will do and to whom after one read, the panel will not either.
Six reasons proposals get sent back
| Reason | What the panel sees | Fix |
|---|---|---|
| Objectives and questions do not match | Unplanned work, or an unclear study | Rebuild both from one list |
| No sampling frame | The data may never exist | Name the access route and who approved it |
| Analysis plan missing or vague | The student cannot analyse the data they will collect | Map one named test to each question |
| Scope too large for one semester | Guaranteed non-completion | Cut one objective, not one respondent |
| Literature review reads as summaries | No gap has been established | End with a one-sentence gap statement |
| Ethics ignored | Data collection will stall | Add the approval step to the timeline |
Reuse the proposal instead of rewriting it
Almost every part of a good proposal becomes part of the thesis: the problem statement becomes Chapter 1, the literature section becomes the spine of Chapter 2, and the methodology becomes Chapter 3 in the past tense. Students lose weeks because those parts live in a separate file that drifts out of step with the thesis as the study changes.
Tesify keeps your work in one place, chapter by chapter, so the proposal text you have already defended stays connected to the chapters that grow out of it — and when your objectives change, you can see everything that has to change with them. You remain the author and remain responsible for every sentence; nothing here replaces your supervisor’s judgement or your faculty’s handbook.
Start building your thesis in Tesify and let the proposal become Chapter 1 instead of a document you abandon.
Frequently asked questions
How long should a thesis proposal be?
Your faculty handbook decides. Undergraduate FYP proposals in Malaysia are commonly 8–15 pages; postgraduate proposals are often 20–40 pages and defended orally. Check the limit before drafting, because cutting a finished proposal is much harder than planning to the limit.
What sections does a research proposal need?
Most Malaysian faculties ask for: title, introduction and background, problem statement, research objectives and questions, brief literature review, methodology, timeline, expected outcomes, and references. Use your handbook’s headings verbatim if it prescribes them.
What is the difference between a proposal and a thesis?
A proposal argues that a study should and can be done, and is written in the future tense. A thesis reports a study that has been done, in the past tense, and adds results and discussion chapters.
How many references should a proposal have?
There is no fixed number, and your handbook may set one. The useful test is coverage rather than count: every concept you will measure and every relationship you will test should have at least one source behind it.
Do I need ethics approval before submitting the proposal?
Usually not before submission, but you almost always need it before collecting data, and the approval step belongs on your timeline. Requirements differ by university and by the kind of data you collect, so confirm with your supervisor early rather than late.
Can my objectives change after the proposal is approved?
Small refinements are normal and expected. Changing a variable or the population is a different matter and usually needs your supervisor’s agreement, sometimes a resubmission. Record the reason for any change; you will be asked about it in the viva.
Should the proposal be written in future tense?
Yes. Methods and procedures are written as what will be done. When the proposal later becomes your methodology chapter, those sentences are converted to past tense.
What happens at a proposal defence?
You present the study in a short slot, usually 10–20 minutes, and the panel questions you on feasibility, method and scope. The commonest questions are why this design, why this sample size, and how each research question will be answered — which is exactly what Steps 4 and 6 above prepare you for.
Can I use a published questionnaire in my proposal?
Yes, and adapting a published instrument is usually viewed more favourably than building one from scratch. Cite the source, state what you changed, and say how you will re-check reliability on your own sample.
What if my supervisor and the panel disagree?
Write down both positions, then ask your supervisor to help you reconcile them in writing before you revise. Silently following one side is what turns a single revision into three.
Is a Gantt chart really necessary?
If the handbook asks for one, yes. Even when it does not, it is the fastest way to discover that your plan does not fit the semester — which is far better to learn now than in week ten.
