01Listings or full pages per tenant?
A short listing per tenant (name, what they make or offer, how to reach them, a link to their own site) scales and survives turnover. Full pages per tenant multiply content the manager must chase every time someone leaves or rebrands.
In the quoteAgree the listing format and the number of listings at launch. Static listings are agreed content; a searchable directory or tenant-editable system is scoped separately.
02Who approves each?
Each listing needs an approved name, permitted logo or photo, accurate description and a current destination. Do not assume the venue manager can approve every tenant's claims or owns the rights to their images. Keep a small roster of who supplies and approves each entry, with a clear way to remove a departed business's information.
In the quoteAgree an approved launch roster, supplied assets and a named manager. Entries awaiting approval stay off at launch. Later roster changes and any self-editing system are separately agreed work.
03Join inquiries?
People wanting to rent space need different information from customers: what is available, the general terms you choose to publish, and how to ask. Mixing them sends join inquiries to tenants and customer questions to the manager.
In the quoteAgree a join route with fields you choose. One basic form is standard; tenant applications, document uploads or lease tools are separate.