Kopersbegeleiding (Buyer Guidance)

The buyer guidance module manages the buyer journey of a nieuwbouw project: staged option closing dates per construction phase (sluitingsdata per bouwfase), a dossier per buyer with a journey checklist, automated deadline reminders, and a buyer-facing journey view in the portal.

The module is gated behind the buyerGuidance tenant scope.

Closing phases (sluitingsdata)

Every project gets an ordered list of option-closing phases. Each phase has:

• Name and order: e.g. Ruwbouw, Afbouw, Sanitair & tegelwerk
• Sluitingsdatum: the closing date; a phase without a date never blocks
• Affected options: option categories and/or individual option names that close on that date
• Block/house overrides: staggered closing dates for a specific block or bouwnummer (a house override wins over a block override)

Manage phases in the project editor → Sales → Configurations tab. Each phase shows a computed status: open, closing soon (default within 14 days), or closed.

Presets from the type

Phases usually follow the same structure for every project that uses a type. Define closing phase presets on the type (Type editor → Presets): name, order, and affected option categories, without dates. In the project, use Prefill from type to copy the preset structure in, then fill in the project-specific sluitingsdata. Prefilling never silently merges: it requires an empty schedule or an explicit replace.

Enforcement

Once a phase closes, the options it covers can no longer be changed:

• Buyers (configurator/portal) are hard-blocked: the save fails with a clear message listing the blocked options and the closing date. Re-submitting an unchanged configuration always works.
• Internal users can override with the OVERRIDE_CLOSED_PHASES permission; overrides are audited on the configuration.

Buyer dossiers

A dossier is created per house+buyer: automatically when a buyer is assigned to a house, or via Backfill dossiers for existing projects. Each dossier contains:

• Journey checklist: steps snapshotted from a journey template (tenant-wide default, or a project-specific template) with due dates, assignees, and buyer visibility flags
• Kopersbegeleider: the assigned buyer guide, notified on assignment
• Linked records: the buyer's configuration, estimates (linked automatically when generated from a configuration), and DMS documents
• Timeline: all communication and events related to the buyer (emails, estimate signed, steps completed, portal messages), merged from across the platform
• Messages: a thread between the buyer and the kopersbegeleiding team (see below)

Find dossiers per project under Projects → [project] → Buyer guidance.

Buyer messages

The dossier detail page has a Berichten met koper thread. It is the buyer-facing counterpart of the portal's dossier page:

• A staff reply is stored on the thread and emailed to the buyer, via the tenant's BUYER_DOSSIER_MESSAGE template when one is configured under Communications → Automation, otherwise a built-in fallback with a link to the portal. Variables: buyerName, houseNumber, senderName, messageContent, portalUrl.
• A buyer message (sent from the portal) appears on the thread and raises an in-app notification for the assigned kopersbegeleider (scope BUYER_DOSSIER_CLIENT_MESSAGE, deep-linking to the dossier).
• Attachments are supported in both directions.

Messages also show up as entries on the dossier timeline.

Kopersbegeleider task queue

The Kopersbegeleiding page (construction menu) shows the current user's open journey steps across all projects, sorted by due date, with due-soon/overdue filters. Steps without their own assignee fall to the dossier's kopersbegeleider. Overdue steps also trigger a daily in-app notification.

Automated buyer reminders

Two email automation triggers are available under Communications → Automation (they follow the standard template + reminder configuration):

• OPTION_CLOSING_REMINDER: scheduled reminders before a sluitingsdatum. Reminder moments are calendar days relative to the closing date (e.g. −14, −7, −1). Sent once per house, phase, and moment. Variables include buyerName, projectName, houseNumber, phaseName, closingDate, daysRemaining, and portalUrl.
• OPTION_PHASE_CLOSED: informs the buyer that a phase has closed and their options are final.

Buyer portal

Portal clients (magic-link login) with the buyerGuidance scope see a Mijn woning card on their dashboard and a journey page with:

• Their journey progress and the buyer-visible checklist steps
• All phase deadlines with status and countdown
• Links to their estimates and change orders
• A Dossier & berichten page per dossier: one chronological timeline of milestones (dossier start, completed buyer-visible steps) and the message thread with the kopersbegeleiding team, with a composer to ask questions and attach files. Internal dossier events and staff comments never appear there.

Permissions