Build a 6-week look-ahead your site team will actually use
Your master programme is right. The trouble is nobody on site is going to open a five-thousand-activity P6 file to find out what they're pouring on Thursday. Here's the exact workflow to cut a clean, rolling six-week look-ahead straight from the master — the window filtered, the slip bars kept, a data-date curtain dropped, RAG'd by area — and re-generated in seconds every week.
The short-interval look-ahead is the one schedule the field genuinely reads. It's the six weeks in front of the crew: what starts, what finishes, what's tight, what's already slipping. Get it right and the Monday coordination meeting runs itself. Get it wrong — or, more often, don't produce it at all — and the site falls back on a whiteboard and whatever the last person shouted across the compound.
So why is it usually the ugliest, most out-of-date document on the job? Because most look-aheads are hand-built. Someone exports the master, deletes the rows that don't matter, wrestles the dates into a spreadsheet or a slide, colours a few cells by hand, and prints it. By Wednesday it's wrong, and by next Monday the whole ritual starts again. The look-ahead isn't a different plan — it's the master, cropped to six weeks and dressed for the field. Crop it, don't rebuild it.
Why the desktop look-ahead is a chore
Cropping six weeks out of the master is trivial in principle and miserable in practice with a desktop scheduler. You filter to a date band, then fight the layout: the bars are hairline-thin, the fonts are dense, there's no room for a legend, and the moment you tune it for print someone updates the master and your carefully-arranged page is stale. So it gets rebuilt in a spreadsheet or pasted into slides — which strips the logic, the slip and any link back to the source. The field ends up reading a hand-typed table that stopped being true days ago.
The category answer to "make it pretty" is usually a presentation add-in or a screenshot pasted into a deck. Both share the same fatal flaw: the picture is a copy, frozen the instant you made it. Next week you do it all again from scratch. A look-ahead's whole value is being current; a static rebuild is out of date before the ink dries.
The six-week look-ahead in six steps
Take a real shape — a plant turnaround with the outage split across a few areas: the boiler, the compressor train, the pipe rack and the electrical room. The master lives in P6, fully logic-linked. What the shift teams need on the wall is the next six weeks, area by area, with what's slipped shown plainly and the current date marked. Here's the version that takes seconds to re-cut each week instead of an evening to rebuild.
- Filter to the window. Import the master (P6
XER/XML, MS ProjectXML, or Excel) — it parses in your browser, nothing uploaded. Set a look-ahead window from the data date to six weeks out and filter the rows to activities that start, finish or run through it. Thousands of activities collapse to the few dozen the field can act on. - Keep the baseline and slip bars. Leave the baseline switched on so each activity shows a thin baseline bar under the current one, and turn on slip bars so the gap between planned and current is drawn in red. The crew doesn't just see what's happening — they see what's moved, and by how much, without reading a single date.
- Drop a data-date curtain. Add the data date and a curtain shading everything to its left, so "past" reads instantly as greyed-out and the live window pops. Fill progress to the curtain and add a status line so ahead/behind is obvious at a glance.
- Colour by RAG, per area. Group the window into section bands — one per area — and drive a RAG stoplight off status or float using conditional symbology: green on track, amber tight, red slipping. Now the whole page answers "where's the trouble?" before anyone reads a word.
- Export the one-pager or share the link. Add your header, footer and logo, then export a clean landscape PDF, PNG or PowerPoint for the site cabin wall — print matches screen exactly. Or send a read-only link that rebuilds the whole look-ahead in the recipient's browser, no install, nothing to open.
- Refresh next week. When the master is updated, hit Refresh and point it at the new file. Sketchedule re-syncs and shows you what changed — dates moved, activities added, activities dropped — before you accept it. The window rolls forward, the slip re-draws, and the field view is current again in seconds. No rebuild, no retyping.
What makes the field actually read it
A look-ahead the crew ignores is worse than none — it signals that planning and the field aren't looking at the same thing. Three details turn a cropped programme into a page people trust on the wall.
Slip bars, so movement is visible
A bare current bar tells you when work is happening. A baseline bar with a red slip bar tells you it's two days later than we said — and that's the conversation the coordination meeting needs. Keeping the slip in the field view means the crew argues about the right thing: recovering the days, not whether they exist.
A curtain, so "now" is unmistakable
Six columns of week bars blur together fast. Shade everything left of the data date and the eye snaps to the live window: past is grey, ahead is bright, and the current date is a hard line down the page. It's a small thing that does a lot of work on a busy wall in a noisy cabin.
RAG by area, so the trouble finds you
Grouping by area and colouring each band's stoplight means the superintendent reads the page in the order that matters: red areas first. On our turnaround that's the compressor train — one glance, before a single bar is studied, and the meeting starts where it should.
Keeping it in step, week after week
The reason short-interval look-aheads decay is friction: if refreshing one is a half-day job, it quietly doesn't happen, and the wall goes stale. Cut that to a Refresh and the discipline sticks. Each week you re-point the same view at the updated master, review the diff — what moved, what's new, what dropped out of the window as it rolled forward — accept it, and re-export or re-share. The look-ahead becomes a living artefact that always shows the real six weeks, because it's cropped from the real programme every single time.
| Ingredient | What it does for the field | In Sketchedule |
|---|---|---|
| Window filter | Only the next six weeks — no scrolling | Look-ahead window from data date + row filter |
| Baseline + slip bars | Shows what's moved and by how much | Baseline on; slip bars baseline → current |
| Data-date curtain | Makes "now" unmistakable | Data date + curtain shading the past |
| RAG by area | Trouble finds the reader first | Section bands + conditional stoplight symbology |
| Export / share | Wall print or a link anyone can open | PDF/PNG/PPT print-matches-screen; read-only link |
| Refresh | Current again in seconds, not an evening | Refresh from the updated master + diff preview |
Key takeaways
- A six-week look-ahead is a crop of the master, not a separate plan — filter the window, don't rebuild it.
- Keep the baseline and slip bars so the crew sees what's moved, and drop a data-date curtain so "now" is obvious.
- Group by area and RAG it so the trouble reads first — then export a one-page PDF or share a read-only link.
- Refresh from the updated P6/MSP each week — the field view re-generates in seconds instead of an evening.
- The master stays the source of truth; the look-ahead is a live, dressed view of it — clean, current, and never hand-typed.
Cut your own six-week look-ahead
Open Sketchedule in a browser — free, no install, nothing uploaded. Drop in your master and crop the window.
Primavera and P6 are trademarks of Oracle Corporation; Microsoft Project is a trademark of Microsoft Corporation. Sketchedule is an independent product and is not affiliated with, endorsed by or sponsored by Oracle or Microsoft. Figures are illustrative, drawn in Sketchedule; Fig 3 is a faithful redraw of the turnaround look-ahead example built in the app.