Show the output.
Count the whole task.
A workflow earns its place when the next person can use the result and the total effort makes sense.
Reviewed 20 October 2026. The examples below are fictional teaching scenarios, not measured client results, design instructions or a fabrication release.
Example: a support schedule for the shop.
A trade team needs a schedule that lets the shop identify and count the agreed supports. Adding more model fields is only useful if they help that handoff.
| Sample output | What the receiver checks |
|---|---|
| Support ID: SUP-001 | Unique and traceable to the agreed model revision. |
| Type: EXAMPLE-A · quantity: 12 | Type and quantity match the agreed source, with no duplicate counting. |
| Revision: SAMPLE-R1 · status: review only | The shop understands this is not released for fabrication. |
This deliberately omits dimensions, loads and material selections. The responsible project team must define and approve those requirements where needed. BIMTA does not supply an engineered support detail.
Agree the acceptance check first.
- Name the output, intended receiver and permitted use.
- Define required fields, units, revision and missing-data rules.
- Compare the full sample against an agreed baseline. Log missing, duplicate and incorrect entries.
- Have the receiving role confirm that the output is usable for the stated purpose.
- Keep fabrication approval separate from a successful data export.
Example: does automation actually save time?
Suppose a repeatable task takes four minutes manually and two minutes with a tool. For 100 repetitions, include 120 minutes of setup and 30 minutes of additional checking and correction.
| Illustrative effort | Minutes |
|---|---|
| Existing method: 100 × 4 | 400 |
| Tool-assisted work: 100 × 2 | 200 |
| Setup + additional review/correction | 150 |
| Total alternative effort | 350 |
| Net saving against the baseline | 50 minutes / 12.5% |
The task itself is twice as fast in this scenario. The complete first run saves 12.5%, provided both methods deliver an accepted result. Later runs may differ because setup, maintenance and rework change.
Try your own cost assumptions →The first BIMTA pilot.
We are seeking five trade companies to try an existing checklist, budget or workflow on a bounded task. Participation is voluntary; there are no completed BIMTA pilot findings to report yet.
Use a permitted, nonconfidential sample. Record baseline effort, setup, execution, review, corrections and the receiver’s acceptance. Include failed attempts. Publish a summary only after the contributor approves its wording and disclosure.
The formatted Excel workbook includes instructions, 24 BIM-only cost codes, task budgets, actual costs and forecasts. Use one copy per project. It is a cost tracker; record comparable test conditions and acceptance evidence alongside it.
Keep the completed record in your own approved storage. This page does not upload or collect project information. Do not put client, employer or employee information in a forum post.
What we will publish.
A useful result identifies the task, sample size, software versions, acceptance checks, complete effort and limitations. No savings claim will be labelled a BIMTA finding until it has actually been measured and reviewed.
Start with the scope checklist →