A bid/no-bid call in one workspace, not three inboxes.
Aged-care operators get a quarterly stream of high-stakes tenders — catering, allied health, facility refurb, ICT. Tendor brings clinical, finance and ops into one structured space so the team decides together, with the evidence already aligned.

The current shape of the call
- 01 · RFP LANDS
An allied-health panel notice arrives at the GM's inbox.
The GM forwards to clinical for fit, to finance for margin, to ops for capacity. Three separate threads start — each scoped to one angle of the same brief, each with its own attachments.
- 02 · INBOXES DIVERGE
Three threads drift apart for a week.
Clinical replies on Tuesday with a question about scope. Finance pulls last cycle's AN-ACC numbers on Wednesday. Ops only reads the brief on Thursday afternoon. Nobody has seen the same version of the document.
- 03 · DECISION DRIFTS
By the time bid/no-bid is called, half the runway is gone.
A meeting gets scheduled to align the three views. The decision lands seven days after the RFP dropped. The response now has less than the back half of the window — and the team that decided to pursue is already tired.
Three streams. One workspace.
Reads scope against resident risk, allied-health rosters and accreditation lines.
Reads it against funding mix, AN-ACC margins and the cost of running the response.
Reads it against rosters, catering, refurb capacity and the calendar that already exists.
Where Tendor changes it
A signal from the field
Composite scenario based on private-preview cohort patterns.
TYPICAL · ILLUSTRATIVE — composite from private-preview cohort patterns.
Walk an aged-care brief with us in 30 minutes.
Bring a real tender you're weighing — catering, allied health, refurb, ICT. We'll walk the workspace, the evidence library and the awards record against it, and show you what the bid/no-bid call looks like when clinical, finance and ops are in the same room.

