How to Approach Project Scheduling Assignment 2: Critical Path, Crashing, Levelling and Memo
A critical path assignment is won on method: a clean forward and backward pass, a float table you can defend, a crash table that always picks the cheapest critical activity and re-checks the network, and a levelling schedule that shows its rules. If your brief also asks for a memo, the memo should turn the numbers into one clear recommendation. For help with the layout of your own tables, see our university assignment help page.
What the brief is really asking
The Project Scheduling Management Assignment 2 question has four parts. Question 1 asks for the network, the critical path, total and free float, and the cost of a five-day reduction against a client benefit of €1,500 per day, with a check for new critical paths at each stage. Question 2 limits two resources (M to 5 units, L to 8 units) and asks for the duration, loading diagrams, levelling and options to meet a 35-day target. Question 3 is a larger resource-constrained table. Question 4 is a risk memo of about 500 words.
One practical warning: the network and crash tables in the original brief are images, so the public page only describes them. Work from the tables in your own copy of the brief, and check every number against it.
The brief also states a limit and a target: resource M is capped at 5 units and L at 8, and the levelling question asks how to reach a 35-day completion. That means the marker expects you to compare your levelled duration with 35 days and to say what you would change if it falls short.
How the words and marks split
The page gives no mark allocation, so ask your lecturer or check the module outline. As a working guide, spend effort in proportion to the number of steps.
| Part | Main output | Suggested effort |
|---|---|---|
| Q1 critical path and floats | Network diagram, ES/EF/LS/LF table, critical path | 25% |
| Q1 crashing | Day-by-day crash table, net benefit, recommendation | 25% |
| Q2 resource levelling | Loading diagrams, levelled schedule, options for 35 days | 20% |
| Q3 resource-constrained project | Duration, cost, problems, options, recommendation | 20% |
| Q4 memo (about 500 words) | Risk, assumptions, consequences, missing information | 10% |
Step-by-step plan
- Draw the network first. Check every predecessor against the table, and mark the start and finish nodes. A wrong link ruins every later answer.
- Run the forward pass. Early start is the largest early finish of the predecessors. Early finish is early start plus duration.
- Run the backward pass. Start from the project finish. Late finish is the smallest late start of the successors. Late start is late finish minus duration.
- Calculate floats. Total float is late start minus early start. Free float is the earliest successor start minus the activity’s early finish. Free float can never be larger than total float.
- List all paths. A path table shows the critical path and the near-critical ones, which is what matters when you crash.
- Calculate crash cost per day. (Crash cost minus normal cost) divided by days saved for each activity, and note the maximum days each can be shortened.
- Crash one day at a time. Pick the cheapest critical activity. When a second path becomes critical, shorten an activity common to both paths or one on each path. Stop when the next day costs more than €1,500.
- Level the resources. State your priority rule (early start, then total float), place activities day by day within the limits, and show the new loading profile and duration.
- Write the memo last. Lead with the recommendation, then the main risk, the assumptions, what happens if they fail, and the extra information you need.
Our report writing help page covers structuring calculation-heavy answers and memos.
A good habit is to build a small check table as you go. After each forward and backward pass, confirm that every critical activity has zero total float, that the longest path equals the project duration, and that no activity has negative float. After each crash step, confirm that the new duration equals the old one minus the days saved. These checks take a few minutes and catch most arithmetic slips before a marker does.
The crash decision is where reasoning shows. The rule is simple: buy a day only when its cost is below the benefit of that day. In the worked example, the cheapest fifth day costs €100 more than the €1,500 benefit, so the recommendation stops at four days. A tied or close call like this is exactly where a marker looks for a clear statement of the assumptions behind the answer.
What markers reward
- Every calculation shown in a table, with the working visible.
- Correct total and free float, with the critical path clearly identified.
- A crash table that re-checks for new critical paths after each day.
- A stated assumption for each crash step, such as linear cost.
- A clear stop point compared with the €1,500 daily benefit, with the net gain calculated.
- A levelling method that is stated, followed and checked against the resource limits on every day.
- A memo that recommends, not just describes.
For the memo, think of a busy sponsor who will read only the first paragraph. Put the decision there, with the key figures, and use the rest of the memo to justify it. Keep the assumptions in a short numbered list so the reader can see at a glance what the answer depends on.
Common mistakes
- Forgetting that the critical path can change during crashing, and continuing to crash the original path.
- Crashing only one of two parallel critical paths, so the project does not get shorter.
- Crashing a non-critical activity, which costs money and saves nothing.
- Ignoring the maximum crash limit of an activity.
- Calculating free float incorrectly by using the wrong successor.
- Levelling without saying what priority rule was used.
- Finishing a levelled schedule without checking the daily loading against the limit.
- A memo that repeats the tables instead of giving a decision.
Student pain points
Keeping track of paths while crashing. Rewrite the path lengths after every crashed day. It takes two minutes and catches most errors.
Choosing between two critical paths. If a shared activity exists, compare its cost with the combined cost of one activity on each path. Pick the cheaper option.
Levelling decisions. Write the rule in one sentence at the top, then apply it without exceptions. Markers care more about consistency than about finding the shortest possible schedule.
Missing data. Where the brief does not give a figure, state your assumption in the answer and say how the result would change.
Time. If the calculations are running over, see how our project writing help works and ask for a scoped quote.
Before you submit, recheck three numbers: the project duration from the forward pass, the total crash cost from your table, and the peak resource load after levelling. If any of these differs between your tables and your written answer, a marker will notice, and the mismatch usually costs more marks than the original slip.
See a worked example
Our worked critical path, crashing and levelling example (for reference only, not to be submitted as your own work) uses an illustrative nine-activity network, not the data from the original brief. It shows the float table, a crash table compared with a €1,500 daily benefit, a levelling schedule and a short memo. If your course also uses operations calculations, the Pizzamatic forecasting and scheduling question shows a related brief.
FAQs
What is the difference between total float and free float?
Total float is how long an activity can slip without delaying the project. Free float is how long it can slip without delaying the early start of any successor. Free float is never larger than total float.
How do I know which activity to crash first?
Among the critical activities that can still be shortened, choose the one with the lowest crash cost per day. Recalculate the critical paths after each day.
When should I stop crashing?
Stop when the cost of the next day is more than the benefit of that day, here €1,500, or when no critical activity can be shortened further. Compare cumulative cost with cumulative benefit to show the net gain.
What if two paths are critical at the same time?
To reduce the project duration you must shorten every critical path. Either crash an activity common to all of them, or crash one activity on each path, and cost both options.
Does resource levelling change the critical path?
It can. Once resources are limited, the longest chain may include resource links between activities that have no logical dependency, and the project may take longer than the unconstrained critical path.
How long should the memo be?
The brief gives about 500 words for the memo. Lead with the recommendation, keep paragraphs short, and cover the risk, the key assumptions, the consequences if they fail and the extra information you would need.
Working on your own network and not sure the numbers are right? Send us your brief for a free quote and a clear view of what can be covered.

Written by
Ireland Assignment Helper Editorial Team
Our editorial team works with students in Ireland and sees the questions they ask most often. This guide is built from those real queries: where students get stuck, what markers look for and how to plan the work step by step.