Industry·5 May 2026·6 min read

A tender programme exhibit that looks considered — without exposing your working plan

The submission wants a delivery programme. You want to show you've thought it through — clean phases, the right milestones, a mobilisation window — without handing the client (and their evaluators, and the incumbent) your detailed sequencing, your float, and every soft spot in your plan. Here's how to build a branded exhibit that reads as considered in minutes, and gives away nothing you didn't choose to.

Every bid team hits the same wall. The ITT asks for "an outline programme demonstrating your delivery approach." Great — except the working plan either doesn't exist yet (you're at concept stage, weeks before anyone opens a scheduling tool), or it does exist and it's a 2,000-line control schedule that would be commercial suicide to print. So you screenshot something, paste it into a slide, squint at it, and ship a grey blur nobody can read.

An outline programme is a communication, not a control schedule. Its job is to prove you understand the shape of the work, the sequence, and the dates that matter — at a level the evaluator can actually read. Say exactly enough to score, and not one activity more. Here's what a considered exhibit looks like, then how to build one.

Fig 1. Same delivery approach, two exhibits. The left one hands the evaluator a headache and hands your competitors your plan. The right one scores.

Build the outline directly — you don't need a P6 first

Here's the trap: teams assume a programme exhibit has to come out of a scheduling tool, so at concept stage — when there's no detailed plan yet — they either fake one in a slide or crash a P6 build they'll throw away. Neither is right. At bid stage you're describing the shape of delivery, and you can draw that shape directly.

Type the phases straight in as outline rows — Mobilise, Design, Procure, Construct, Commission, Handover — set start and finish by dragging or keying dates, and drop the milestones that matter. Or, if a working plan already exists, roll it up: import the MS Project XML or Primavera XER, collapse the WBS, and let the summary bars draw themselves. Either way the output is the same clean exhibit — you're just choosing your starting point.

Fig 2. Bid teams don't need a detailed schedule to produce an exhibit. Build the outline at concept stage, or roll up a plan you already have — both land on the same clean, branded page.

The five-minute exhibit

Say the client wants a one-page delivery programme with a bid-stage mobilisation window and the key hold points marked. Here's the version that takes five minutes and gives away nothing you didn't intend.

Build or roll up to a summary. At concept stage, type the delivery phases straight in as outline rows and set their dates. Working from an existing plan? Import the XER/XML and collapse the WBS so the detail folds into automatic summary bars — the granular sequencing never appears on the page. Everything parses in your browser; nothing is uploaded.
Phases and key milestones only. Turn each phase into a clean summary bar with a section-band label, then promote just the milestones that matter — award, mobilisation complete, planning consent, key handovers. A handful of bars and a few diamonds. Anything that would expose your method or your contingency, you simply leave off.
Draw the mobilisation curtain. Add a curtain over the mobilisation window — a shaded band that says "this is when we stand the project up" without dictating exact internal sequencing. It reads as deliberate and gives the evaluator the reassurance they're marking, at summary level.
Brand the header, footer and logo. Add your company logo, a header with the project and bid reference, and a footer with the revision and "commercial in confidence." Print matches screen, so what you see is exactly what lands in the submission — no reflow, no surprises.
Export to PowerPoint and PDF. Export a landscape PDF for the appendix and a PowerPoint slide for the presentation deck — both watermark-free on Pro, both carrying your brand. One exhibit, two formats, ready to drop into the submission pack.

Fig 3. The branded bid summary programme, built in Sketchedule: a logo header, a phase grid with Start / Finish / % columns, phase summary bars on a month axis, a shaded mobilisation curtain, award / consent / handover milestones, and a "commercial in confidence" footer. Six rows tell the whole delivery story — and nothing beneath them is on the page.

The whole point: the evaluator sees a considered delivery approach with the right dates and hold points — and your competitors, the incumbent, and the client's own team see only that. Your sequencing, your float, and your commercial contingency stay off the page by design.

Show the driving path — at summary level

A common evaluator question: "which phase governs the end date?" You can answer it without opening up the detail. Highlight the driving phase bar — the one on the longest path to handover — or add a single note calling it out. That signals you understand where the risk sits and that you've planned around it, which is exactly what the method statement is trying to demonstrate. You're showing judgement, not disclosing the network.

Fig 4. Highlight the driving phase and mark the slack on the parallel work. You demonstrate you know what governs the end date without exposing a single logic link.

Why not just use what you've got?

Bid teams already own two tools for this, and both fight you. A full desktop scheduler is built to run a project, not present one to a client: it exposes far too much, its native print output is dense and ugly, and every attempt to strip it back to a clean page is a fiddle. The other route — screenshot the schedule (or a slide-tool Gantt) and paste it in — looks exactly as amateur as it is: pixelated bars, mismatched fonts, a legend nobody can read. Neither says "we've thought this through."

The category gap is a presentation layer that starts from what you want the reader to see. You compose the exhibit — these phases, these milestones, this mobilisation window, our brand — and it prints crisply because it was drawn to be printed. It runs free in a browser, so a bid coordinator with nothing installed can build it, and the whole thing is done in minutes, not an evening in the plotter room. That's the difference between a programme that scores and one that just fills a required appendix.

Where the source of truth stays. When there is a detailed plan, it lives in Primavera P6 or MS Project — that's the engine, and it stays there. The exhibit is a curated view of it (or, at concept stage, a standalone outline). Keep the working plan private and the presentation public; never confuse the appendix the client sees with the schedule you actually run.

Key takeaways

An outline programme is a communication, not a control schedule — say exactly enough to score, no activity more.
You don't need a P6 first: build the phases directly at concept stage, or roll up an existing plan by collapsing the WBS.
Compose it from phase summary bars, key milestones and a mobilisation curtain — the detail stays off the page by design.
Show the driving path at summary level to prove judgement without exposing your logic.
Brand the header/footer/logo and export to PowerPoint and PDF — a considered exhibit in minutes, not an evening.

Build your tender exhibit

Open Sketchedule in a browser — free, no install, nothing uploaded. Draw the outline or roll up a plan, and export a branded page.

Start free →Browse examples

← BlogAll articles Next →Brand a board pack

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 a branded bid summary programme built in the app.