Banquet contracts and restaurant documents
A wedding, a christening or a company party needs a contract. EasyOS fills it in from the event record and sends it to the client to sign. In EasyOS the banquet contract is generated from the restaurant's template with the event details already filled in, and goes to the client as a link where they sign. The document sent stays unchanged and the signed copy is stored separately, as proof. Beyond banquets, you keep a register of supplier and rental contracts with a warning before they expire, and send documents for signing internally, or externally by link.
- The banquet contract — The restaurant's Word template, filled in from the event record: date, hall, guest count, menu. Generated automatically when the event is finalised, if you picked a template for that. The client opens it through a link and signs with a drawn signature. The restaurant's signature is set once in settings. A contract can be cancelled; you can see what was sent and what was signed.
- Other documents — A contract register: suppliers, rent, services, with IDNO, value and term. An alert when a contract expires, plus tracking of debts with due dates. Signing internally or externally by link, with a list of what awaits your signature. A document generator from templates and a digital archive. Write-off acts and purchase orders, kept next to the stock.
- How to start — Upload the banquet contract template you already use. Set the restaurant's signature. Send the first contract to a client from the event record. Add supplier contracts and the lease to the register.
- Does the client have to come in to sign?
- No. They get a link, open the contract and sign from a phone or computer.
- Can I use my own contract instead of a standard one?
- Yes. Upload your template and its fields are filled in from the event record.
- Will I know in time that the lease is ending?
- Yes, the contract register warns you before the expiry date.
Restaurant banquet contracts signed online | EasyOS