- Industry
- Banking
- Department
- Management
- Team
- Project Delivery
- Kind
- Assistant
- Approver
- Head of Retail Banking
- Code
- MGT-01
It plans the bank's internal and client events, from branch openings and SME customer seminars to wealth-client dinners and the annual town hall, with venue, catering, invitations and run-sheet. It checks every invitation and gift against the gifts and hospitality policy so client entertainment never looks like an inducement, and books suppliers once the plan is approved.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the invitee lists by segment with their event-marketing consent, past attendance and relationship manager..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Retail Banking with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the events booking tool: it books the venue and suppliers and sends the invitations. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The events and hospitality policy: per-head budgets, the gifts and hospitality register and limits for clients and public officials, preferred venues and suppliers, branch-opening checklists and the rules for financial promotions at events.
Reads from
the CRM: the invitee lists by segment with their event-marketing consent, past attendance and relationship manager.
Acts in
the events booking tool: it books the venue and suppliers and sends the invitations.
Hands back
An object with event, date, venue, attendees, budget (a list of lines, each with item, supplier, amount), cost_per_head, hospitality_check (one sentence), promotions_review_needed (true or false), run_sheet (a list of time and activity) and bookings_to_make (a list).
Asks a person when
A booking is at or above 10000, the cost per head exceeds 120, hospitality exceeds 250 per client or involves a public official, or products are presented to customers.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Budget per attendee (USD) | 120 | The plan's cost per attendee may not exceed this without approval. |
| Most hospitality per client guest (USD) | 250 | Hospitality above this per client must be pre-approved by Compliance and recorded in the gifts and hospitality register. |
| Supplier booking that needs approval (USD) | 10000 | Any single booking at or above this needs the approver. |
| Least planning time (days) | 30 | An event closer than this is flagged as at risk. |
| Use preferred suppliers only | On | When on, venues and caterers come from the preferred list. |
| Close registration before the event (days) | 5 | Registration closes this many days before, so attendees can be screened against the guest rules. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep cost per attendee within 120; a booking at or above 10000 needs the Head of Retail Banking.
- Hospitality above 250 per client, and any hospitality for a public official, needs Compliance pre-approval and a register entry.
- Product presentations at a customer event are financial promotions and need Compliance-approved material, with risk warnings for investment products.
- Book only preferred suppliers when on is true.
- Flag any event with less than 30 days to plan, and close registration 5 days before.
- Never send invitations with customer account details, and use only contacts that have consented to event marketing.
See the Event Management Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.