A RAB, the Indonesian construction cost estimate, helps contractors, builders and project teams explain the planned work, quantities, unit prices and total value to the client. A well-organised document speeds up scope discussions and reduces repeated calculations caused by unclear versions.
Creating estimates in 101 is free. You can prepare a RAB on your phone while on site or on a computer when the team needs a larger screen to organise the price list and check details.
A good result still depends on the input data. The application helps organise and calculate, while quantities, prices, units and scope must be checked by someone who understands the project.
Contents:
What does a free RAB mean in 101?
The free plan on 101 includes estimate management. Teams can start preparing a RAB without purchasing a paid plan. This is useful for testing the workflow, preparing an initial quotation or moving price lists from separate files into one place.
A RAB in the application is a calculation of the work to be offered or discussed. Each item contains the work name, unit, quantity, price and value. Grouping items by stage makes the document easier for the team and client to read.
The application does not replace technical review. If the project must comply with particular standards, guidelines or contract requirements, use official sources and competent professionals. For the Indonesian context, one government reference for estimating construction work costs is the Ministry of PUPR guideline (in Indonesian). Do not treat the project price list as a substitute for applicable obligations; this Indonesian reference does not establish requirements for other countries.
What data should you prepare?
Define the scope before creating the RAB. Write down the result to be delivered, work boundaries, site conditions and anything that cannot yet be calculated. An unclear scope produces a document that looks detailed but can still lead to disputes.
Prepare the following data:
- work stages and item list;
- consistent units for each item;
- quantities obtained from measurements or calculations;
- prices for work, materials, labour or equipment, following the company’s calculation model;
- the tax, indirect-cost and margin rules actually used for the project;
- notes on exclusions and assumptions;
- the document date and version identifier.
Prices should come from data the team can substantiate. Supplier conditions, location, specifications, working methods and timing can affect costs. Use the company’s own price list or checked project data, then update it when conditions change.
For uncertain work, avoid entering figures as though they were final. Mark assumptions, create provisional items if the company’s process permits them and explain what must be checked before a value is agreed.
How do you create a RAB?
The workflow below deliberately uses neutral terms so it remains relevant on phones and the web without relying on particular button names.
- Create a company workspace and prepare the project to be estimated.
- Enter or organise the work price list used by the company.
- Group items by stage, area or type of work.
- Add the unit, quantity, price and notes to each item.
- Check each group subtotal and the overall total.
- Review costs, margin and other terms actually applicable to the quotation.
- Save the checked version and prepare the document for discussion with the client.
Start with the broad structure, then add detail. For example, a renovation project may be divided into preparation, demolition, structural work, installations, wall enclosure, flooring, ceilings, painting, fixtures and cleaning. The appropriate structure differs by project type.
One item should represent work that can be measured and explained. Combining too many activities in one line makes it harder to change quantities, schedule work, report progress and discuss additional work.
Separate work and materials where appropriate
Separating work and materials can help the client understand what makes up the cost. It also allows the team to change procurement assumptions without changing the entire RAB structure. Use this separation only when it fits how the company offers and performs the work.
Use the price list consistently
A price list speeds up repeated RAB preparation. Use the same names, units and calculation rules to prevent items being duplicated under different spellings. When prices change, record the update date and check documents that still use the old version.
What mistakes should you avoid?
RAB errors often originate in the underlying data rather than addition itself. A short check before sending the document can prevent many revisions.
| Problem | Effect | Check |
|---|---|---|
| Inconsistent units | Incorrect item quantities and values | Make sure the unit matches the measurement method |
| Duplicate work items | An inflated quotation | Compare each item’s name, stage and scope |
| Unsupported quantities | A calculation that is difficult to explain | Keep measurement records or assumptions |
| Outdated prices | Execution costs differ from the quotation | Check the date and source of price data |
| Unstated exclusions | Client expectations expand | Add exclusions and work boundaries |
| No document version | The team discusses different files | Add a date and version number |
Also check the relationship between subtotals and the final value. Apply cost adjustments using consistent rules. If changes follow the client discussion, create a new version and record the reasons.
How should you prepare a RAB for the client?
The client document should be readable without a lengthy explanation. Use a logical work sequence, clear item names, understandable units and short notes for special conditions. Avoid internal abbreviations understood only by the estimator.
Where possible, have two people cross-check the document before sending it. One checks scope and quantities; the other checks prices, subtotals and the final total. For a small project, a second check can still be performed after a time interval so the author sees the document with fresh eyes.
Use a dated, versioned document. When revisions occur, explain which items were added, removed or changed. This keeps discussion focused on scope changes and reduces confusion caused by several similarly named files.
101 can prepare estimate documents from project data. Choose an available format that suits the company’s process, then check that the final document is easy to read before sharing it.
What happens after the RAB is approved?
An approved RAB provides the basis for preparing execution. Connect work groups to the schedule, procurement needs, team responsibilities and payment schedule. Once work begins, compare planned values with transactions and progress that actually occur.
Do not overwrite the original RAB when additional work appears. Keep the agreed baseline and record changes as a separate version or section according to the company’s process. Each change needs a clear scope, value, time impact and approval.
Start with one project and a simple price list. Once the structure proves easy to use, apply the same pattern to the next project. A free RAB application then becomes an entry point to a consistent estimating process, with more value than a calculator producing one total.
