Meetings

Flowtly Editorial Team1 min

Meetings in Flowtly is a one-on-one request system between an employee and their manager. A meeting record tracks a single employee, a date range, an optional time, and notes, and moves through a status (requested, planned, finished, canceled) as it is scheduled and completed. Access to the module is gated by the Meeting Manager role.

By keeping meeting records within the platform, your organization builds a searchable history of one-on-one discussions between managers and employees. This is particularly valuable for recurring check-ins where tracking notes and status over time is essential for maintaining momentum and accountability.

Example use cases

  • Performance Reviews: Request and track one-on-one meetings between managers and their direct reports for periodic performance discussions.
  • Recurring Check-ins: Keep a status-tracked history of regular one-on-one sessions with a direct report.

App routes

Meetings have no standalone listing page or top-level navigation entry; each meeting is accessed individually at /meeting/:id.

Connection map

Refers toPart of
Documented hereDocumented elsewhere
audit-log records person. person works under agreement. work-schedule assigned to person. benefit-assignment held by person. employee-profile describes person. employee-document filed against person. responsibility assigned to person. performance-target set for person. meeting held with person. holiday-request submitted by person. leave-entitlement held by person. project staffed by person. project-rate rates person. booking books person.recordsworks underassigned toheld bydescribesfiled againstassigned toset forheld withsubmitted byheld bystaffed byratesbooksAAudit trail — The record of who did what and when. It is how a user action is investigated after the fact, and what compliance is demonstrated from.Audit trailPPerson — An employee. The central record the rest of the workforce data hangs off — profile, documents, leave, benefits, rates.PersonAAgreement — The document formalizing the terms between the organisation and one employee or contractor. It is the foundation of the employees module: whether someone has an active agreement decides whether they appear in the other modules at all.AgreementWWork schedule — The working days, hours and breaks assigned to an employee, from the week the assignment starts. It is what the Work Time calendar draws.Work scheduleEEmployee benefit — One benefit granted to one person for a date range. A person can hold several at once.Employee benefitEEmployee profile — The detailed record for one person: contact details, job role, department, employment history.Employee profileEEmployee document — A file attached to a person — a contract, a review, anything filed against them.Employee documentRResponsibility — An area of ownership assigned to a person.ResponsibilityPPerformance target — An objective set for a person and measured against.Performance targetMMeeting — A recorded one-to-one or review between people.MeetingHHoliday request — An employee's request for time off, submitted for approval. Approving it is what turns it into leave the rest of the system counts.Holiday requestEEntitlement — How much leave a person has for the leave year. A request draws it down; the balance is what remains.EntitlementPProject — The core organizational unit for a business initiative, client engagement or internal work. Everything tracked — time, cost, invoicing, profitability — hangs off one.ProjectMMember rate — A team member's billing or cost rate on a project. Rates are per member, so the same person can cost differently on two projects.Member rateBBooking — One person committed to one role for a stretch of weeks, at a percentage of their time. A booking is a plan, not a record of work done.Booking