# NotaryCentral Business Suite requirements

## Appointments & daily work

### Calendar event duration

Use the configured duration when placing appointments on the calendar.

- Calendar events reflect the selected appointment duration rather than a fixed one-hour block.

Evidence: Passing linked suites.

### Appointment location labels

Show online sessions and physical venues clearly in appointment details and search.

- RON appointments show an online location; in-person appointments show their saved venue.

Evidence: Passing linked suites.

### Editable appointment checklists

Let a notary view and update the checklist attached to an appointment.

- Checklist interactions preserve item state and call the appointment update action.

Evidence: Passing linked suites.

## Booking & customer intake

### Versioned booking policies

Validate policy settings and protect updates with ownership and version checks.

- Invalid rules, another owner’s policy, and stale edits are rejected.

Evidence: Passing linked suites.

### Required booking questions

Validate required answers, available choices, and numeric answers before saving an intake snapshot.

- Missing, unknown, and invalid answers fail; accepted wording and answers retain their order.

Evidence: Passing linked suites.

### Accepted policy snapshots

Keep the policy text, revision, acceptance time, and deadlines accepted by a customer.

- Later policy edits do not change an accepted snapshot; cancellation and no-show boundaries use the saved rules.

Evidence: Passing linked suites.

### Set up an embedded booking form

Configure embedding for a booking form using an enable switch, the parent website page URL, and an allowed origin.

- The booking/calendar settings form submits embedding enablement, a trimmed parent page URL, and a trimmed allowed origin together.
- Parent page URLs reject credentials, query strings, fragments, and non-HTTP protocols; allowed origins reject paths.
- The settings container calls the update action and navigates back only after success; a failed update keeps the form open.

Evidence: Passing linked suites.

## Clients & communications

### Searchable client directory

Search client records and return a consistent company/name order with counts.

- Search input is trimmed and listing results retain deterministic sorting and counts.

Evidence: Passing linked suites.

### Email template previews

Preview reusable appointment email templates before using them.

- The preview renders the selected template and its configured content.

Evidence: Passing linked suites.

### Participant reminders

Send participant reminders to signers, witnesses, and interpreters.

- The linked reminder suite verifies eligible participant roles and excludes unrelated recipients.

Evidence: Passing linked suites.

## Invoices, expenses & mileage

### Invoice adjustments

Apply service discounts, waiting charges, and courtesy adjustments using saved rates.

- Adjustments enforce ownership and invoice version checks and do not compound on repeated saves.

Evidence: Passing linked suites.

### Expense dates and periods

Assign new expense dates in the user’s time zone and include the requested end date in searches.

- Default dates use the configured zone; expense queries include the end-of-day boundary.

Evidence: Passing linked suites.

### Mileage expense estimates

Calculate mileage totals and estimated expenses from recorded trip dates and distances.

- Calculations apply the rate associated with each trip date and tolerate missing or invalid distance input.

Evidence: Passing linked suites.

## Shared workspaces & access

### Assignable Business Suite seats

Assign purchased seats without consuming the same assignment twice.

- Assignments cannot exceed purchased capacity; existing active assignments are reused and released seats are marked inactive.

Evidence: Passing linked suites.

### Paid workspace coverage

Grant shared appointment access only when the workspace has active Business Suite coverage.

- Inactive, canceled, or unavailable subscription data does not create paid workspace coverage.

Evidence: Passing linked suites.

### Workspace MFA policy

Let authorized workspace managers require verified second-factor authentication.

- The owner must satisfy MFA before enabling it; members without a verified second factor are blocked and policy changes are audited.

Evidence: Passing linked suites.

## Guided business setup

### Canonical setup steps

Map Business Suite setup steps to the settings and interactive milestones they configure.

- Every registered step has metadata and a route; approved setting keys map to the expected setup steps.

Evidence: Passing linked suites.

### Relevant setup sequence

Calculate the remaining setup sequence from current settings and durable progress.

- Completed or already satisfied steps are omitted from the remaining sequence and progress totals.

Evidence: Passing linked suites.

### Resume completed setup

Recognize setup decisions and settings that have already been completed.

- Saved workspace and booking choices and existing invoice configuration prevent redundant setup steps.

Evidence: Passing linked suites.
