actual resource TILOS

Why Resources Don’t Update Automatically in TILOS When Using Split Progress

A common stumbling block in TILOS training — and the exact settings you need to check before touching the progress update dialog.

VA

Virgil Andrei PMP®
Senior Planning Engineer & TILOS Trainer

7 min read

During a recent TILOS training session, we hit a wall that I see trip up almost every group: we’d dutifully ticked the progress checkboxes on activities, chosen Split Progress as the update method, run the update — and the resource quantities sat there, completely unchanged. No actual quantities updated. No histogram shift. Nothing.

It looks like a bug. It isn’t. It’s a configuration choice TILOS makes you set explicitly, and once you understand the logic behind it, it makes complete sense. Let me walk through exactly what is happening and how to fix it.

How TILOS Progress Update Works (the short version)

TILOS gives you three progress methods, each behaving differently when you hit the Update Progress button:

MethodWhat TILOS does to the activityResources auto-update?
Percentage CompleteRecords a % done figure; shifts the remaining durationNeeds setting
Split ProgressPhysically splits the activity at the data date into a done part and a remaining partNot automatic
Actual Dates (start/finish)Moves the activity bar; no splitNeeds setting

The key word in the middle row is splits. TILOS literally divides your activity bar into two separate segments at the data date. The left segment is complete. The right segment is what remains. This is visually clean and very powerful — but it creates a problem for resources.

The Root Cause: Resources Are Assigned to the Original Activity, Not the Split

When TILOS splits an activity, your resource assignments remain on the original, pre-split definition. TILOS does not automatically know how much of a resource was consumed by the left segment versus what should remain for the right segment. Should it split proportionally by time? By distance? By a custom curve you set? It cannot guess — so it does nothing until you tell it.

⚠ The exact issue from the training room

Activities marked for progress update ✓ and the Split Progress method selected ✓ — but after running the update, the resource histogram is completely unchanged. This is expected TILOS behaviour. Resources require a separate configuration step to follow progress, and Split Progress requires that step more explicitly than any other method.

The Two-Part Fix

There are two things you need to set. Both are required. Skipping either one and the resources stay frozen.

Part 1 — Enable “Automatic Update” on the Resource Assignment

In the activity’s resource dialog, each resource assignment has a flag labelled Automatic (or Auto Update depending on your TILOS version). This tells TILOS: “when this activity’s progress changes, recalculate my quantity to match.”

  • 1Open the activity propertiesDouble-click the activity in the Time-Location view to open its property dialog.
  • 2Navigate to the Resources tabFind the tab labelled Resources or Resource Allocation.
  • 3Tick “Automatic” for each resourceFor every resource row assigned to this activity, tick the Automatic checkbox. Without this, the resource quantity is treated as a fixed, manually managed figure — TILOS will never touch it.
  • 4Confirm the quantity type is set to “Total” or “Rate”Resources set as a fixed total with no automatic flag behave as locked values. A rate-based resource (units/day or units/km) calculates from the activity duration/distance and responds naturally to progress once Automatic is enabled.
actual resources on TILOS

Part 2 — Set the Progress Update Method in the Resource Dialog

Even with Automatic ticked, TILOS needs to know how to redistribute the quantity across the split. This setting lives inside the resource assignment itself, under a field typically labelled Update Method or Calculation Base.

  • 5Set the calculation base to match your progress typeIf you are progressing bydistance(chainage), set it to Distance. If bytime, set it to Duration. A mismatch here is the second most common cause of resources not updating: TILOS calculates correctly but against the wrong axis.
  • 6Run Update Progress againGo to Project → Update Progress, confirm your data date, select Split Progress and run. This time, the resource quantities on the completed segment should recalculate.
  • 7Check the resource histogramOpen the resource histogram view. You should now see two distinct resource segments: actual quantities consumed on the left of the data date, and planned remaining quantities on the right.

💡 Pro tip — set Automatic on the activity template, not per-update

If you are building a new project from scratch, set the Automatic flag on every resource assignment as you create the activities — before any progress update ever runs. This way you never need to remember it during a live update session. For existing projects, you can also set it in bulk through the resource table view by filtering all assignments and editing the Automatic column directly.

Why Split Progress Behaves Differently From Other Methods

With a simple Percentage Complete update, TILOS is only changing a number — it is not restructuring the activity. The resource assignment still covers the whole activity bar, and the Automatic recalculation is straightforward: multiply the total quantity by the progress fraction.

With Split Progress, TILOS creates a genuinely different data structure. The original activity becomes two objects. The resource assignment now has to bridge across that structural split. This is why the Automatic flag is non-negotiable: TILOS needs an explicit instruction to carry the resource logic across the split boundary. Without the flag, it respects the existing assignment as a user-defined, locked value and leaves it alone.

This is actually sensible behaviour — imagine a scenario where a cost has been agreed as a lump sum for a phase, and you do not want the software redistributing it just because progress was recorded. TILOS gives you that control. The trade-off is that you have to explicitly opt in to automatic redistribution.

Checklist Before Every Progress Update Session

✔ Pre-update resource checklist

1. Automatic flag — is it ticked on every resource assignment for activities being progressed?

2. Calculation base — does it match the progress unit (distance or duration)?

3. Resource type — rate-based resources (units/km or units/day) respond more cleanly to Split Progress than fixed-total quantities.

4. Data date — is it correctly set before running the update? The split point is determined by the data date, so a wrong date means a wrong split location.

5. Baseline saved — always save your baseline before the first progress update. Once split, the original plan structure is gone from the live schedule.

What the Resource Histogram Should Show After a Correct Update

After a correctly configured Split Progress update, your resource histogram will have two visually distinct zones:

Left of the data date — actual resource consumption, calculated from the completed portion of the split. These figures represent what has genuinely been used.

Right of the data date — planned remaining resource demand, recalculated from the remaining portion. If the split has created any delay (the activity is running slower than planned), this zone will shift right and you will see the resource demand extend beyond the original planned finish.

If the histogram looks identical before and after the update — same shape, same totals — the Automatic flag is almost certainly missing. That is the first thing to check.

Summary — the three things TILOS needs to update resources on a split

  • The activity must be marked for progress update (the checkbox in the update dialog)
  • Each resource assignment must have theAutomaticflag enabled (in the resource tab of the activity properties)
  • Thecalculation baseon the resource assignment must match the progress unit you are using (distance or duration)
activity types in tilos

Triangle activities in TILOS: a step-by-step guide for beginners

Should I use a triangle activity in TILOS?

In TILOS, a triangle is a display type you apply to a normal line activity. It doesn’t change how the activity is scheduled. It shades a triangular area attached to the activity line, showing the part of the time-distance chart the work occupies, so nobody plans other activities there.

This guide walks you through it in five steps, then shows a worked example you can copy.

Step 1: Understand the line activity

On a time-distance chart, a line activity runs at an angle: it moves along the chainage as time passes. Think of a crew paving from km 0 to km 5 over four weeks.

A plain line only says “the crew is here at this moment.” It doesn’t show that the ground behind or ahead of the crew is also tied up.

Step 2: See what the triangle adds

Picture the sloped line as the long side of a right-angled triangle. TILOS shades that triangle on one side of the line.

The shaded area means “this stretch of road, during this period, belongs to this activity.”

Why use a triangle instead of a normal line?

A normal line tells you one thing: where the crew is on each day. It says nothing about the ground before the crew gets there or after it leaves. On real sites, that is often the part that matters most.

Take a simple case. A crew pours concrete at 100 m a day, and each section then needs 3 days to cure. Someone plans road markings to follow 2 days behind the pour, at the same speed.

With lines only, the plan looks fine. The two lines run side by side and never touch, so a reviewer sees nothing wrong. But the markings are always 2 days behind the pour while the concrete needs 3, so the crew would be painting on wet concrete along the whole road.

With Triangle upper and a 3-day time lag, the curing appears as a shaded band behind the pour. The road markings line now runs straight through it, and the problem is obvious at a glance.

So you use a triangle when:

  • The work leaves something behind that stops others using the area for a while: curing, drying, settlement, testing or a protected zone.
  • The work needs space prepared ahead, such as traffic management, a cleared site or survey set-out.
  • Other crews follow on the same stretch, and you need to see how close they can safely get.
  • You want one activity to tell the whole story, instead of adding a separate “curing” line after every pour.

If the work leaves nothing behind and needs nothing ahead, a normal line is enough.

One thing to remember: the triangle shows the constraint but doesn’t enforce it. If the gap must drive the dates, also link the two activities with the right lag. The triangle then makes that logic visible to everyone reading the chart.

Step 3: Choose triangle lower or upper

There are two versions, and they shade opposite sides of the line. Ask one question: is the area blocked before the crew arrives, or after it has left?

TypeWhat it blocksUse it for
Triangle lowerThe zone before the crew arrives at each pointSet-up, installing a traffic-management zone, ground kept clear ahead of the work
Triangle upperThe zone after the crew has passed each pointConcrete curing, settlement time, earthworks where cut is reused as fill nearby

An easy way to remember it: lower = before, upper = after.

Step 4: Adjust the size with lags

A plain triangle is rarely the right size, so expect to adjust it in the activity’s Display tab. The Triangle lower and Triangle upper options include:

  • Distance lag: extends the blocked area behind the activity line, in distance units.
  • Distance lead: extends it ahead of the line.
  • Time lag: extends it in time, at the start for a lower triangle or at the end for an upper one.
  • Lag date: sets the date the fill begins from.

Step 5: Set it up in TILOS

  1. Draw a normal line activity, for example “Earthworks km 2–6.”
  2. Select it and open the Display tab in the Object Properties pane.
  3. Change the Activity Type to Triangle lower or Triangle upper.
  4. Add distance or time lags until the shaded area matches the real occupation on site.
  5. Right-click the activity and choose Save as template, so you can reuse the same look for similar activities.

Worked example: concrete curing

A crew pours a concrete slab from 0 m to 500 m at 100 m per day, so the pour takes 5 days. Each section then needs 3 days of curing, and nobody can work on it in that time.

  1. Draw the line. Insert a line activity “Concrete pour” from 0 m to 500 m over 5 days.
  2. Pick the side. Curing happens after the pour, so choose Triangle upper.
  3. Change the display type. In the Display tab, set the Activity Type to Triangle upper. The area after the crew is now shaded.
  4. Add the curing time. Set Time lag = 3 days. Each section now shows as blocked for 3 days after its pour.
  5. Read the result. The section at 0 m is blocked from day 0 to day 3. The section at 500 m is blocked from day 5 to day 8.
  6. Check the next activity. Draw “Road markings” so its line stays outside the shaded area. If it cuts through, you’re painting on wet concrete, so move it later.

If the crew instead needed traffic cones set out 2 days before reaching each section, you’d use Triangle lower with a 2-day time lag at the start.

Why a triangle? Gantt chart vs TILOS

A Gantt chart shows the pour and the curing as two bars, one after the other. It says the whole 500 m slab is poured on days 0–5 and cures on days 5–8, so road markings can’t start until day 8.

But the slab isn’t poured in one go. The crew pours 100 m a day, so each section starts curing on a different day. A section is free once its last metre has cured.

SectionPouredCuring (blocked)Free from
0–100 mDay 0–1Day 1–4Day 4
100–200 mDay 1–2Day 2–5Day 5
200–300 mDay 2–3Day 3–6Day 6
300–400 mDay 3–4Day 4–7Day 7
400–500 mDay 4–5Day 5–8Day 8
tilos vs gantt

The dashed rectangle is what the Gantt chart blocks; the coloured staircase is what’s really occupied.

Step by step: from blocks to a triangle

  1. Plot each section on the time-distance chart, with distance across and time going down. Each section gets a small pouring block with a taller curing block under it.
  2. Each section starts one day later than the one before, so the blocks step down to the right.
  3. Look at all the blocks together. They form a staircase that follows the slope of the pour line.
  4. Make the sections smaller (50 m, 10 m, 1 m) and the steps shrink too. In the end the staircase becomes a smooth sloped band along the line.
  5. That smooth band is what TILOS draws with Triangle upper and a 3-day time lag. The triangle is simply the smooth version of the staircase.
  6. Compare it with the dashed Gantt rectangle. Its bottom-left corner is free ground the Gantt chart still treats as blocked, so road markings can start at 0 m on day 4 instead of day 8.

An everyday analogy

Think of mopping a long corridor. You start at one end and work your way along. The floor behind you is wet, but the first metres dry while you’re still mopping the far end.

A Gantt chart puts one “wet floor” sign on the whole corridor until the very last metre is dry. TILOS shows the wet strip moving along behind you, so people can walk on the dry part straight away.

Other activity types in TILOS

The triangle is one of several display types. Each one draws a different shape around the activity line to show which part of the time-distance chart is busy. You choose them all in the same place: Display tab, then Activity Type.

activity types in tilos

The blue line is the activity; the shaded area is what it blocks for other work.

TypeWhat it showsSimple example
Simple lineThe default. Where the crew is at each moment; nothing else is blockedA kerb-laying crew moving steadily along the road
RectangleA whole stretch is busy for the whole durationBuilding a bridge between km 3.2 and km 3.4 over 6 weeks
Triangle lowerArea reserved before the crew arrives at each pointSetting up traffic management ahead of resurfacing
Triangle upperArea blocked after the crew has passed each pointConcrete curing behind the pour
Parallelogram (time)The line widened in time: each point is busy for a set time before and after the crew passesA rolling lane closure put up just before the works and removed just after
Parallelogram (distance)The line widened in distance: the crew takes up a length of route ahead of and behind its positionA paving train or track renewal machine several hundred metres long
Parallelogram (working time / calendar time)A blocked period at the start or end of the line, counted in working days or calendar daysCalendar time for curing, which carries on at weekends; working time for a lag that only runs on shift days
StairsThe line drawn as steps of a set lengthWork done in fixed sections, such as 100 m of pipe laid and backfilled at a time
MilestoneA symbol at a single point in timeRoad opening, possession start, handover

Back to the corridor analogy: the simple line is the cleaner walking along. A rectangle is a room closed for cleaning. A triangle is the wet floor that follows the cleaner. A parallelogram is the cleaning trolley, which takes up a fixed length (distance) or stays at each spot for a fixed time (time). Stairs are cleaning one section at a time, and a milestone is the moment the corridor reopens.

The exact list can vary by TILOS version, so check the Activity Type drop-down in your copy.

Typical beginner mistakes

  • Choosing upper when lower was needed. Ask yourself whether the area is blocked before the crew arrives or after it has left.
  • Thinking the triangle changes the duration. Only the activity line drives the schedule. The triangle is a visual reservation of space.
  • Leaving the lags at zero. This usually makes the blocked area too small to be useful.

Source

Trimble TILOS Help – Define an Activity’s Display

Trimble TILOS Help – Assign Display Types