Why Your Schedule Matters on JKR Projects
On Jabatan Kerja Raya (JKR) and other public sector construction projects in Malaysia, the contractor’s work programme is far more than a document for submission. It is the baseline against which progress is measured, delays are assessed and extension of time claims are evaluated. A poorly built schedule can lead to repeated resubmissions, disputes over progress, and difficulty proving the impact of delays.
Yet many schedules are still prepared just to satisfy the submission requirement. They look complete on paper, but they lack proper logic and do not reflect how the work will actually be built. This article explains what a good, JKR-compliant schedule in Microsoft Project looks like, and the common mistakes to avoid.
Planning vs Scheduling: Know the Difference
Planning decides what needs to be done, how, and in what order: the construction methodology, work packages and sequence. Scheduling turns that plan into a time-based model, with durations, dependencies, resources and dates. A strong schedule always starts with a strong plan. If the methodology is not thought through, no amount of MS Project skill will produce a realistic programme.
The JKR 6-Step Planning Model
A structured approach helps you build a schedule that is both realistic and compliant. The JKR 6-Step Planning Model guides you from scope to a submission-ready programme. In practice, this means working through:
- Defining the project scope and breaking it into manageable deliverables
- Developing a deliverable-based Work Breakdown Structure (WBS) aligned with how the work will be built
- Defining activities and estimating realistic durations
- Sequencing activities with proper logic links and dependencies
- Assigning resources and costs to the schedule
- Reviewing, baselining and preparing the schedule for submission and progress monitoring
What Makes a Schedule Compliant?
JKR scheduling guidelines include a self-audit checklist (Appendix B) that reviewers use to assess the quality of a submitted schedule. Before you submit, check that your schedule:
- Has a clear WBS that reflects the project’s deliverables and construction methodology
- Is fully logic-linked, with every activity (except the start and finish) having at least one predecessor and one successor
- Avoids hard constraints such as “Must Start On” dates unless genuinely required, since they block the schedule from responding to changes
- Uses realistic durations that can be justified by quantities and production rates
- Shows a clear critical path from start to completion
- Includes key milestones such as site possession, sectional completion and practical completion
- Is resource- and cost-loaded, so progress can be measured in value, not just time
Common Mistakes in MS Project Schedules
- Typing in dates instead of using logic. Entering start and finish dates manually creates hidden constraints. The schedule looks right today but will not update correctly when progress changes.
- Too many open ends. Activities without successors make the critical path unreliable.
- Summary tasks with links. Linking summary rows instead of the actual activities makes the logic hard to read and check.
- No baseline. Without a saved baseline, you cannot compare actual progress with the plan or prove delays.
- Activities that are too long. Very long activities make progress hard to measure. Break them into shorter, measurable pieces.
Using the Schedule to Monitor Progress
A good schedule is used throughout the project, not just at submission. With a cost-loaded schedule in MS Project, you can:
- Update actual progress regularly and see the impact on the completion date
- Produce S-curves comparing planned and actual progress
- Apply Earned Value Management (EVM) to measure schedule and cost performance objectively
- Carry out variance analysis to identify delays early and plan recovery actions
- Generate clear progress reports for JKR, consultants and management
This turns the schedule into a practical management tool and gives you solid evidence if delays or disputes arise.
Frequently Asked Questions
Do JKR projects require Microsoft Project?
Microsoft Project is the scheduling software most widely used by JKR officers and contractors, which makes it the practical choice for preparing and reviewing work programmes. Always check the specific requirements in your contract documents.
What is a logic-linked schedule?
A schedule where activities are connected by dependencies (such as finish-to-start), so that a change to one activity automatically updates the dates of the activities that follow.
Why does my schedule keep getting rejected?
The most common reasons are missing logic links, too many constraints, an unclear critical path, and a WBS that does not reflect the construction methodology. A self-audit against the Appendix B checklist before submission helps avoid this.
Master JKR Scheduling with MS Project
Our 3-day Advanced Scheduling Mastery: Project Schedule Development Using MS Project for JKR Compliance course takes you through the JKR 6-Step Planning Model, from WBS to a submission-ready, cost-loaded schedule, including progress updating, S-curves and EVM. New to MS Project? Start with our Microsoft Project – Professional Scheduling course. Both are HRD Corp claimable. Contact us for in-house training for your project team.
