Event
One catering service, from the first enquiry through to the invoice it closes at.
Enobase Approvals · Productivity
Record the purpose, requester and supporting document before asking for a decision.
Record the purpose, requester and supporting document before asking for a decision.
Choose the fields that explain the work and the next decision.
Purpose, amount and linked work give the reviewer context.
Keep the document that explains the request with its record.
Give each request a person responsible for moving it forward.
Model the states your team uses, from preparation to a recorded outcome.
These illustrative configurations show how the unit of work changes with the operation.
The request links a supplier quote to an event, with the amount and delivery date the event manager must review.
The request concerns a role, site and planned start date. The decision owner needs headcount context rather than a supplier invoice.
Arrange requests by state, reviewer and date. Open the record to read the evidence before deciding.
Start from the records on each side, then agree which actions belong in the configured process.
Keep the approved request linked to the purchasing work it concerns.
Prepare the purchasing hand-offBring the expense and its supporting information into the review.
Keep expense contextStart with a defined process and its required records. Agree the configuration and connected actions before extending it to other teams.

30 minutes, your real events on screen. We'll show you exactly where Enobase saves your team time, no slides.
| Name | Type | Properties | Constraints |
|---|---|---|---|
| Event name | Text | Required | |
| Covers | Number | Required | |
| Venue | Relation | ||
| Service moment | Select | ||
| Subcontracted to | Relation | ||
| Client brief | Styled document | ||
| Margin | Percentage |
© 2026 Enobase, Inc. All rights reserved.