Biltevo is your programme and your site diary in one. Plan the work, log the day against the activity it belongs to, and the record writes itself.
How it works
Biltevo is both of them — the plan you agreed and the days as they actually went, in the same place, on the same dates, with nothing to reconcile at month end.
01 · Build
Put the jobs on a canvas and join them up in the order they happen. The dates, the critical path and the knock-on effects come out of the logic, not out of a spreadsheet.
02 · Plan
The same plan as bars on a timeline. Import one from Asta, P6 or MS Project and the links come across with it — you do not keep the old tool running beside this one.
03 · Deliver
Three taps on a phone, against the activity it belongs to. Not a diary sitting next to the programme — the same programme, so a blocked morning moves the finish date.
04 · Record
Every change carries its date, its cause and whose it is, and cannot be edited after the fact. Nothing is assembled at the end of the month, because it is already written.
05 · Check
Nine industry-standard checks in plain English: jobs with nothing driving them, negative float, tasks running longer than anyone can honestly report on.
Harbour Street — refurbishment · launch the demo
Working with other people
The work you have given to somebody else is one line on your plan and a fortnight of detail on theirs. That detail normally never arrives — it lives in their spreadsheet, and you find out what was in it when it goes wrong.
Send them the line and the dates you have left for it. What comes back sits inside your bar: their steps, their durations, their words, on your programme. If it does not fit the slot, the page says so in days.
Needs you
Partitions — floor 1 · from Harbour Street — refurbishment
It arrives as one card. Who sent it, what it is, and the dates it turns on. Nothing is accepted by looking at it — reviewing is where it joins the job.
Why Biltevo
Everywhere else the programme sits in one tool and the day sits in another, and somebody spends the end of every month deciding which one is right. Here there is nothing to decide.
Partitions held 3 daysAccess restriction · Thu 17 Sep, 08:42
You log against the activity, not against the date. There is nothing to match up later because nothing was ever apart — the programme and the diary are the same records, read two ways.
Time lost goes in as working days against the job that lost them. The chain re-runs there and then: float goes, the critical path moves if it moves, the finish date changes. You know what the day cost on the day, not next month.
You pay for the job, not the heads on it, so the PM, the QSs, the site manager and the subcontractors are all on. Per-seat pricing is what takes the subbies off a licence, and they are the ones who saw what happened.
What it takes off your desk: a programme updated monthly at best, a diary nobody opens until there is an argument, and the week somebody spends putting the story back together afterwards.
Also in here
1,284 activities97% matched
| Activity | Biltevo | The file | |
|---|---|---|---|
| Piling — grid A | 14 Sep | 14 Sep | — |
| Steel erection | 06 Oct | 06 Oct | — |
| Envelope — east | 21 Nov | 17 Nov | +4d |
| Roof covering | 02 Dec | 02 Dec | — |
38 disagree · 31 of them a calendar difference
Import an Asta, P6 or MS Project file and Biltevo re-runs it. Every date and every float compared against what your own tool stored, and the ones that disagree grouped by what caused it.
The board puts your live projects on a single timeline — what moved, what did not, and how far — without opening any of them.
Mon–Fri232 working days
Weekends · bank holidays · the Christmas shutdown
One working-time calendar: your week, your bank holidays, your shutdowns. Every duration on every programme is counted against it, so nobody argues about whether Christmas was in the ten days.
Trade · area · floor — free text, never a fixed list
Tag by trade, by area, by floor — your words, not a fixed list — and the programme regroups to match. The same tags colour the bars, so a floor reads at a glance.
Price
Fourteen days free, no card. Drop a programme in, see what is wrong with it, fix it and export it. If you stop there you keep everything you made and can still export it — you just cannot change it.
One planner, their own programmes. Canvas, Gantt, critical path, import and export.
Everyone on that job, every mode — the PM, the QSs, the site manager, and the subcontractors you invite.
Up to 10 live projects on one invoice — cheaper than per-project from seven jobs on. £2,150 to 25. More than that, or a group of companies, tell us about the estate and we will price it.
£199 for the job, whoever is on it. The PM, two QSs, the site manager and four subcontractors — eight people, still £199. A per-seat planning tool at the £30–40 a head they charge puts the same eight at £240 to £320 a month for one job, and an Asta seat alone is £1,113 a year. That is the arithmetic that takes the subcontractors off the licence, and they are the ones who know what happened.
Questions
Biltevo is project planning software that keeps the programme and the daily site record as one set of records rather than two. It runs a real critical path — a forward and backward pass with total float on every activity — and a day logged from site attaches to the activity it belongs to, so time lost recalculates the completion date straight away. It is used mainly on UK construction projects.
£39 a month for one project and £199 a month for ten live projects. Unlimited projects with SSO and your own retention policy is priced on request — the shape of an estate that size decides the number. Pricing is per project, not per seat, so the project manager, the quantity surveyors, the site manager and the subcontractors are all included at no extra cost. Billing is not connected yet, so early projects run free until it is.
Yes. Biltevo imports Asta Powerproject, Primavera P6 (XER) and Microsoft Project (XML) files, bringing across the activities, the durations and the links. It then re-runs the programme through its own engine and reports every date and every float that disagrees with what the source file stored, grouped by what caused the difference. Programmes export back out to XER, MSPDI, CSV and spreadsheet formats.
Yes. A full CPM forward and backward pass, total float on every activity, the critical path, and a completion date measured against the contract date. It also runs nine of the fourteen DCMA schedule assessment checks and reports them in plain English — activities with nothing driving them, negative float, and durations longer than anyone can honestly report against.
Field-scheduling tools such as Aphex run the week downstream of a master programme that stays in Primavera P6 or Asta Powerproject, and their site diary is a separate product priced separately. Biltevo holds the master programme itself, so a day logged from site moves the completion date rather than being reported against a lookahead, and the plan and the record are the same object with nothing to reconcile between them.
Yes, at no extra cost, because the price is for the project rather than for each person on it. A main contractor can send a subcontractor a package with the dates set aside for it; the subcontractor plans their own steps and those come back inside the main programme as part of it, not as a separate document to be read and re-typed.
Logging the day works in a phone browser — three taps, filed against the activity it belongs to. There is no native app to install. Building the plan and reading the forensic record are designed for a desktop screen.
Start
The demo opens on Harbour Street — refurbishment with the plan, the log and the record already in it. Drag a bar and watch the completion date move. Or put your own programme in and see what it says — the file stays on your computer. Nothing to install, nothing to sign.