You design the building. Vorker reads the tender.

Vorker reads the tender packages, extracts the requirements, plans the submission and assembles the pack, held for your approval. Built for practices of 1-5.

An architect leaning over a large drawing on a worktable in a small studio, rolls of drawings in the foreground

FAQ

Will it submit or send anything without me seeing it?

No. Every submission, fee proposal, update and email is prepared and then waits for you. You can read it, edit it, reject it, or approve it and schedule it to go out later. Nothing sensitive happens on its own.

Can it really read a 240-page tender package?

Yes, that is the point. It reads the whole package, pulls every requirement, criterion and deadline into one checklist, and flags anything ambiguous for you to raise in the question window. You check the checklist against the package once, instead of reading it three times.

Does it make the go/no-go decision for us?

No. It assesses the fit against your references and capacity and gives you an honest recommendation, but the decision and the press are yours. It will tell you when a mandatory requirement rules you out, which is the cheapest no you will ever get.

We are three architects and no office manager. Is this overkill?

That is the size it is built for. In a small practice the partners do the tender reading, the invoicing and the client updates at night. Vorker is the practice manager you cannot yet hire, and you stay the one who approves.

What happens to our drawings and project files?

They stay in your own storage. Vorker reads what it needs to assemble packs and answer questions, files documents per project, and never shares anything externally without an approval press from you.

Do I have to learn a new system?

No. You type or say it the way you would tell a practice manager, and Vorker works inside the tools you already have: your email, your calendar, your files, your accounting. The packs and proposals arrive as ordinary PDFs.