The process
How it works
You do not prepare anything. You send what already exists, and you read what comes back. Two of the four steps are yours and neither takes more than half an hour.
The four steps
Hand over what you already have
Project reports, fee proposals, correspondence, meeting minutes, site instructions, spreadsheets, drawings, photographs, certificates, registers, debriefs, transcripts, voice notes and past submissions. Whatever exists, in whatever state it is in. Do not tidy it up, do not summarise it and do not write anything new. You do not need to send the criteria, the questions or the closing date, because we already hold those. Ten minutes.
Received 14 August · nothing tidied, nothing rewritten
Everything you sent, and what came out of it
Illustrative. What comes back confirming everything that was read, before any writing starts.
It reads everything and works out the case
Your material is broken into individual facts, each tied back to the document it came from. Against the published criteria, the engine works out which angle the evidence will actually carry, then writes every answer from claims that cite those facts. Anything it cannot support is stopped before you see it.
Criterion 3 · Safety outcomes
Every factual statement, and where it came from
Illustrative. A claim that fails is never quietly dropped. It becomes the specific thing worth going to find out.
You get the submission and the questions
A complete draft against every question, inside every word limit. Alongside it, a ranked list of what is worth going to get, each item naming who to ask, exactly what to ask them and what it would change. Plus the claims one more fact would unlock, and exactly which fact each one needs.
Ranked by what each answer is worth
Six questions for your team
How many hours would have been worked below the high water mark under the conventional in-situ method?
Would let us state how much exposure the design removed, rather than that it was removed
Was the November underspend returned to the client or reallocated within the programme?
Turns a cost result into a value-to-client result
Who proposed the bank-side lift, and at what point in the design programme?
Makes the innovation attributable to your firm rather than to the method
and 3 further questions, on criteria 2, 3 and 4
Today
Question 01 of 6
How many hours would have been worked below the high water mark under the conventional in-situ method?
Sent · 9:41 am
5 questions still open
Illustrative. Send answers back in any form, including a voice note.
Answers go in, the case is rebuilt
Send back whatever your team says, in any form, including a voice note. The case is rebuilt around the new evidence and you get a changelog of exactly what changed and what is still outstanding.
Revision 2 · after your team answered
What changed, and what is still open
Illustrative. You see exactly what moved and why, so nothing changes in your entry without your knowledge.
What lands in your inbox
One document, not a folder of fragments. Everything you have to lodge comes first, in the order the form asks for it, and everything behind the entry sits after it. It arrives as Word and PDF, so you can change any word of it before it goes anywhere.
Prepared for your firm · September 2026
Bridge replacement
Engineers Australia Excellence Awards · Project Excellence, over $10m
Contents
Everything you lodge
Everything behind it
Attachments, named in lodgement order
Numbered in the order the questions run, so they upload in sequence and each file is already named for the answer it supports.
Illustrative. Every answer arrives inside its own word limit, so lodging is a paste rather than a rewrite.
And the version that carries your name
Most entry forms are plain text fields, which is where a strong project goes to look like every other one. Where the programme allows a supporting document, you also get the whole entry laid out on your own letterhead, with a cover letter drafted for a director to sign and every image sitting beside the claim it proves.
Project Excellence, over $10m
Bridge
replacement
over live water
Deck erection without in-water work
14 August 2026
To the judging panel,
We are pleased to submit this entry for the bridge replacement over live water, under Project Excellence, over $10m.
The project set out to replace a road bridge without putting anyone into the water beneath it. That question was settled at the design table twelve weeks before the first segment arrived on site, and the pages that follow record the decision, what it cost to take at that point and what it measurably removed.
We have built this entry from the project’s own record rather than from recollection. Every figure, date and outcome in it traces to a document generated during delivery, and where the record would not carry a claim we have narrowed the claim rather than stretched the evidence.
We would like to thank the client and the delivery team, whose willingness to test the method before it was proven is the reason there is anything here worth reading.
We appreciate the panel’s time in considering it.
Kind regards,
Criterion 1 · Value to the client
Describe the value delivered to the client and how it was measured.
Value on this project is measured in an occupation handed back, not in a budget met.
The brief was a replacement crossing inside an eighteen month road occupation, and the occupation was the expensive part. Every week of it carried a traffic management cost to the client and a disruption cost to the network, and the programme had been built on the assumption that the deck would be cast in place above the water.
Erection from the bank removed the in-water works package in its entirety, and with it the marine plant, the exclusion zone and the weather dependency that had governed the critical path. The crossing opened five weeks inside the window, and the occupation was surrendered on the day rather than held to the date in the contract.
The saving was returned rather than absorbed. The November underspend was released back to the client’s own programme instead of being reallocated within the works, and is recorded as a credit on the final account, which is the difference between a project that came in under and a client who is better off.
Figure 1 Deck segments lifted from the eastern bank, October
Illustrative. Your letterhead, your logo, your words and your signature at the end of it. Prepared where the programme allows a supporting document, and skipped where it does not.
All ten jobs, and who does each one
The four steps above are your view of it. This is the whole job underneath, including the parts nobody counts until the fortnight before closing.
| The job | Who does it |
|---|---|
| Choosing which of your projects to enter | Probative, by comparing them against the criteria |
| Checking eligibility and category fit | Probative |
| Reading the questions, the criteria and how much each criterion is worth | Probative, already held for every programme on the list |
| Deciding which argument your evidence can actually support | Probative |
| Finding that evidence across years of project files | Probative |
| Working out what is missing and whether it is worth getting | Probative |
| Getting those answers out of your project team | You, from a ranked list of questions. About half an hour |
| Writing every answer around one argument, inside every word limit | Probative |
| Checking that nothing claims more than the evidence supports | Probative |
| Approving it and lodging | You. About an hour |
Eight of the ten are done before you read a word of it. The two that are yours are the two nobody else can do, because one needs your people and the other needs your signature.
It knows which questions are worth asking
Some of what your material says is backed by a document. Some of it is somebody’s recollection. A judge can only give credit for what an entry is able to point to, so the two are worth very different amounts, and sorting one from the other is how it works out which questions are worth putting to your team.
It behaves the same on a small job and a large one
Across the ten stored test entries, a single entry carries between 45 and 75 claims. Every one of them is cited, whatever the size of the entry, because citation is how a claim comes into existence rather than a check applied at the end.
Entries are described by size rather than by name, because what a client enters stays theirs.
The working, line by line
Open any line to see the count behind it, where it came from and what it does not cover. This is the level of detail most people do not want and a few people want very much.
You send material. You read what comes back
No forms. No questionnaire. No structured intake. No software to learn.
Most tools in this category ask you to type your achievements into a form and then organise what you typed. That leaves the judgement about what is worth saying with you, and that judgement is the part that takes the weeks. Probative reads the raw material and forms that judgement from what the evidence will carry.
The judgement about what is worth saying is the work. That is the part you are buying.
Start with two answers.
Send an award you are actually entering and whatever project material you already have. You get two complete answers, the case we would make, the questions we would send your team and the claims that one more fact would unlock.
Credited in full if you go ahead. If you read it and walk away, you owe nothing further.