Tenders
Tenders is the inbound side of procurement. It lists every package a builder has invited your organisation to price, across every project and every client, in one place, so a bid you were emailed about in March is still findable in June.
It sits at organisation level rather than on a project, because you are usually not on the project yet. Winning the work is what puts you there.
The register
Each row is one package you have been invited to: the package number and title, the client organisation, the project, the value of anything you have submitted, and the closing date.
The closing date is quoted in the project's own time zone, not yours. That is deliberate and it matters if you bid interstate. A tender closing at 4pm in Perth closes at 4pm in Perth, and the register shows you that instant rather than quietly converting it into your afternoon.
Your invitation carries a status: invited when it arrives, accepted once you have taken it on, declined if you have said no, and submitted once a bid is lodged.
Tenders shows the tenders of the organisation you are currently working in. If you hold accounts in more than one company, switch to the right one first. See Organisations and projects.
Opening a package
A package has four tabs.
Overview is the package details, the dates, and who at the client organisation is running it.
Tender Package is everything they have issued: the schedule of values, the scope, the drawings and specifications, and any files uploaded to the package. Download individually or take the lot in one go.
Submission is where you price and lodge.
Communication is the question and answer thread with the client about this package. Use it rather than email, because an answer given here is on the package record and the person covering for you next week can read it.
Addenda
Addenda issued after the package went out are numbered and dated, and they are the thing to check before you lodge. An addendum usually changes something you have already priced, so read the addendum before you read your own draft.
Accepting, and then pricing
You have to accept the invitation before Teralo will take a submission from you. Declining is a real answer and worth giving: a client chasing a bid that was never coming is a phone call neither of you needs.
Once accepted, there are two ways to price.
Pricing as a lump sum
This is the default, and it is what most bids are. Enter your total and upload your own quote document. Teralo is not trying to make you rebuild your quote in somebody else's format.
Pricing against their schedule
Line by line against the schedule of values they issued, which is what a client asks for when they intend to compare bids properly. Each line takes one of four answers: include or exclude, a quantity and a rate, a single amount, or a note where the honest answer is a qualification rather than a number.
A submission is a draft until you lodge it. Lodging a second one creates a new version rather than overwriting the first, so a revised bid keeps its history and the client can see what changed.
Re-pricing when the schedule changes
Two things happen automatically, and both are on your side.
If the client publishes a revision that materially changes a line you already priced, they can ask for that line to be re-priced, and it is flagged for you rather than left to be noticed.
Separately, Teralo records what each of your lines was priced against at the moment you lodged it. If the schedule later says 120 metres where you priced 100, the difference is visible on the comparison rather than buried. Neither of these changes your price. They stop your old price being read as though it answered a new question.
Closing dates, and being late
What the closing date means is set by the client, per package.
Most leave late bids allowed, because most builders would rather have your price than the principle. A bid lodged after the deadline goes in normally and is stamped with how late it was, which is the client's business to weigh up.
Where the client has made the deadline hard, the only way past it is for them to grant your organisation a specific late allowance, recorded against your name. There is no way to talk your way past the form.
The sealed tender box
Some packages are run with a sealed tender box. That is a restriction on the client, not on you: your price, your documents and your line items are withheld from them until the deadline passes and somebody deliberately opens the box.
The client can still see that you have responded, so a sealed box does not stop them chasing a firm that has gone quiet. It stops anyone reading prices early.
After the deadline
Teralo does not tell you the outcome automatically. There is no won or lost email on a package, by design: the decision is the client's to communicate and the timing is theirs to choose.
What you will see is the package stop accepting anything from you once it has been awarded, closed or executed. The Communication thread stays available, and it is the right place to ask.
If you win, the client will usually invite your organisation onto the project, and the commercial side moves to Contracts, Progress claims and Variations.
If you do not have a Teralo account yet
A client can invite a company that has never used Teralo. That invitation goes out as an email with a link, and the link opens a portal where you can read the package, ask questions and lodge a bid without an account at all. The link is good for thirty days.
Creating an account later joins the two up: the bid you lodged through the link becomes your organisation's, and it appears in this register alongside everything else.
Where all this lives
Tenders has no settings of its own. Everything about a package, the schedule, the dates, the close policy and the addenda, belongs to the client organisation that issued it, and is configured on their side in Procurement.
Who can do what
One permission governs the whole module, and it is held at organisation level: managing tenders. Whoever holds it can see every tender your organisation has been invited to, accept and decline invitations, price and lodge, and answer questions.
That is a single switch rather than a view-and-edit pair, so think of it as "this person bids for us". It is granted inside your own organisation, by whoever administers it, and not by any client. See How permissions work.