Tender pack · live today
Know what you're pricing before you commit.
Who it helps: the estimator or MD who has to decide, fast, whether a tender is worth pricing and what to ask first.
| Step | What MERT does | What it needs | Your review point |
|---|---|---|---|
| 1. Sort the pack | Reads and sorts the whole pack and accounts for every document. | The tender folder or files. | Check the document list is complete. |
| 2. Find the key facts | Return date, client, site and your trade's sections of the specification. Another trade's submission is set aside. | The documents themselves. | Confirm or correct each fact. |
| 3. Flag conflicts and gaps | Flags "Documents disagree" and missing information such as no return date, client or site address. | The documents themselves. | Decide what matters for this tender. |
| 4. Draft the questions | Drafts the client questions in one email, in a table. | The flagged gaps. | You edit and send. MERT never sends. |
| 5. Track the answers | Matches each reply to its question. Phone answers stay "not yet confirmed in writing". | The client's replies. | You decide when an answer is good enough. |
| 6. Freeze the record | Freezes the tender document register at submission. | Your submission date. | Confirm the register. |
What it does not do yet: compare scope on the drawings against the specification, or measure quantities. Those are on the roadmap. MERT also shows how many documents it has read and flags gaps rather than hiding them.
How we measure it
We measure time to a first read of a pack, gaps found that the estimator then confirmed, and questions raised before the return date. We won't quote accuracy or savings figures until we can evidence them.