How to plan a project: scope, timeline, budget and risks
A one-page plan written before work starts prevents most late and over-budget jobs. Here is how to set the scope, timeline, budget and risks, with a worked RM example.

Plan a project in five steps: write down the scope, including what is excluded; break the work into tasks with owners; build a timeline that allows for supplier lead times, annual leave and public holidays; budget each cost with a contingency of around 5% to 10%; and list the main risks with a plan for each.
Most late jobs were late before they started. The quotation promised a date nobody had checked against the team's other work, the materials were ordered after the deposit cleared, and the long weekend in the middle of the job was forgotten. A short plan, written before the first task begins, catches these problems while they are still cheap to fix.
What is a project plan?
A project plan is a short document that sets out what a project will deliver, the tasks needed, who does each one, when they are due, what it will cost, and what could go wrong. For a small business, one or two pages is enough.
In Bahasa Malaysia this is perancangan projek. The plan is for your team as much as your customer. It turns a quotation into work that people can actually start on Monday morning.
| Part of the plan | Question it answers | Typical format |
|---|---|---|
| Scope | What exactly are we delivering? | A list of inclusions and exclusions |
| Tasks and owners | Who does what? | A task list with one name each |
| Timeline | When is each task due? | Dates, with dependencies marked |
| Budget | What will it cost? | Cost lines with a contingency |
| Risks | What could go wrong? | A short risk register |
How do I write a project scope?
Write a list of what you will deliver, then a separate list of what is not included. The exclusions list is the part that prevents disputes. Base it on the accepted quotation and confirm it with the customer.
A good scope is specific enough that a new staff member could tell whether a request is inside it or not.
- Deliverables: "Supply and install 12 metres of kitchen cabinets, laminate finish, per drawing rev. B."
- Exclusions: "Electrical rewiring, plumbing beyond relocating the sink, and appliances."
- Assumptions: "Site access 9am to 6pm on weekdays. The customer clears the area before day one."
- Acceptance: "The customer inspects and signs the handover checklist within three working days."
When the customer asks for something outside the scope, treat it as a change. Price it, agree the new date, and get written confirmation before starting. A WhatsApp message saying "OK, proceed with the RM1,800 upgrade" is far better than nothing.
How do I build a realistic project timeline?
List the tasks, mark which ones depend on others, estimate each one in working days, and then place them on a calendar that already shows leave, public holidays and supplier lead times. The calendar check is the step most plans skip.
- Break the work into tasks that take one person between half a day and a week. Bigger tasks hide delays.
- Mark dependencies. Cabinets can't be installed until they are delivered, and they can't be delivered until they are ordered.
- Estimate in working days, based on similar past jobs rather than optimism.
- Add supplier lead times as tasks in their own right, confirmed in writing by the supplier.
- Block out non-working days. Under the Employment Act 1955, employees are entitled to paid holidays on eleven gazetted public holidays a year, five of which are fixed: National Day, the Yang di-Pertuan Agong's birthday, the state Ruler's or Yang di-Pertua Negeri's birthday (or Federal Territory Day), Workers' Day and Malaysia Day. Some holidays differ by state, so use the calendar for the state where the work happens.
- Check annual leave. The Act gives 8, 12 or 16 days of paid annual leave a year depending on length of service. Ask the team about planned leave before you commit to dates.
- Add a buffer at the end, not spread across every task, so it is visible and protected.
Remember the limits on hours, too. The Act caps normal working time at eight hours a day and 45 hours a week, so a timeline that only works with constant overtime is not a realistic plan. For capacity planning across several jobs, see how to plan team workload.
How do I budget a project?
List every direct cost the job will incur, add a contingency for the unexpected, and compare the total with the quoted price to check the margin before you start. If the margin is already thin on paper, it will be thinner in practice.
Typical cost lines for a Malaysian SME project are materials, subcontractors, your own staff's time (including overtime and statutory contributions), transport and delivery, equipment hire, and permits or fees. A contingency of around 5% to 10% of the costs is a common starting point for familiar work. Use more when the job is new to you, or when prices of key materials move often.
Example (illustrative): A Penang interior design firm quotes RM85,000 to renovate a small clinic over six weeks.
| Cost line | RM |
|---|---|
| Materials (flooring, partitions, ceiling, paint) | 31,000 |
| Joinery subcontractor | 14,500 |
| Electrical and air-conditioning subcontractor | 9,500 |
| Own staff time, 2 people × 6 weeks | 9,000 |
| Transport, skip bins, equipment hire | 2,000 |
| Direct costs | 66,000 |
| Contingency at 7% | 4,620 |
| Budget including contingency | 70,620 |
| Quoted price | 85,000 |
| Planned gross profit | 14,380 (16.9%) |
If the contingency isn't used, profit rises to RM19,000 (22.4%). If the firm needs at least 20% gross margin to cover rent, admin salaries and other overheads, this plan shows the risk early: it either needs a firmer scope, a better subcontractor price, or a higher quote. Our guides on markup vs margin and break-even analysis explain how to set that minimum.
Plan the cash, not only the profit. If you pay suppliers before the customer pays a progress claim, the job can be profitable and still strain your bank balance. Agree deposits and progress claims that cover your biggest payments to suppliers.
How do I identify and manage project risks?
List what could delay the job or raise its cost, rate each item's likelihood and impact, and write one action for the most serious ones. A risk register with five to ten lines is plenty for most SME projects.
ISO 31000:2018, the international risk management guideline, defines risk as the "effect of uncertainty on objectives". For a project, the objectives are the scope, the date and the budget, so a risk is anything uncertain that could move them.
| Risk | Likelihood | Impact | Action | Owner |
|---|---|---|---|---|
| Imported tiles arrive late | Medium | High | Order in week 1; agree a local alternative | Purchasing |
| Customer changes layout mid-job | High | Medium | Written change form with price and date | Project lead |
| Subcontractor double-booked | Medium | High | Confirm dates in writing; keep a backup | Project lead |
| Building management limits work hours | Low | Medium | Get written approval of hours before starting | Site supervisor |
| Key staff member on leave | Low | Medium | Check leave before fixing dates | Owner |
Review the register at your weekly project meeting. Close risks that have passed, and add new ones as they appear.
How do I turn the plan into weekly work?
Put every task on a shared board with its owner and due date, then review progress against the plan once a week. A plan that lives in a folder nobody opens is soon out of date.
A kanban board, with a column for each stage, makes the plan visible to everyone. Our kanban board guide shows how to set one up. In HumbleBear, for example, a job can be a card in a Space with custom stages, an owner and dates, and the quotation and purchase orders can be linked to the same card so the plan and the paperwork stay together.
During the weekly review, compare actual costs with the budget line by line. Our guide to tracking project costs shows a simple method.
Frequently asked questions
How detailed should a project plan be for a small business?
One or two pages is usually enough. It should cover the scope with exclusions, the tasks and owners, the key dates, the budget and a short list of risks. Add more detail only where a mistake would be expensive, such as long supplier lead times or work that depends on another contractor.
How much contingency should I add to a project budget?
Around 5% to 10% of direct costs is a common starting point for work you have done before. Use more for unfamiliar work or materials with volatile prices. Keep the contingency as a separate line, so you can see when it is being used up.
Should I include public holidays in a project timeline?
Yes. Under the Employment Act 1955, employees are entitled to paid holidays on eleven gazetted public holidays a year, and some holidays differ by state. Mark them on the calendar for the state where the work takes place before you promise a completion date.
What is the difference between a project plan and a quotation?
A quotation tells the customer what you will deliver and for how much. A project plan tells your team how it will be delivered: the tasks, owners, dates, costs and risks. The plan should be based on the accepted quotation and kept consistent with it.
What should I do when the customer changes the scope?
Treat it as a change. Price the extra work, state the new completion date, and get the customer's written agreement before you start. Then update the plan, the budget and the board, so the team works to the new version.

