See what’s new at MCFP just improved.

This is intended

• Summary with jump to the affected step
• Error overview matching visible required fields and conditions

We measure completion by this

• An error leads directly to the correct visible field.
• Server check and protection against duplicate submissions remain effective.

Builds on these projects

This is intended

• Check view for prerequisites and latest technical results
• Deliberate test dispatch and cleaned support report

We measure completion by this

• A successful mail call is not output as confirmed delivery.
• The support report contains no answers, keys, or private form links.

This is intended

• Notes on missing field references and unreachable mandatory fields
• Test paths with sample data and mobile-previewable display

We measure completion by this

• A warning points to the affected field and the rule.
• Checks do not alter real customer processes.

This is intended

• Clear selection with dependencies, preview, and summary
• Copyable link plus optional QR code without included response data

We measure completion by this

• Deselected mandatory fields do not block a valid partial process.
• The original and system template remain unchanged.

Builds on these projects

This is intended

• Preview next reminder, pause, and clear sending history
• Maximum number, intervals and template selection with existing package rights

We measure completion by this

• Completed or deleted processes receive no further reminders.
• Repeated cron execution does not trigger duplicate sending.

Builds on these projects

This is intended

• Follow-up with selected fields, note, and processing status
• Change history and separate handling of already signed data

We measure completion by this

• Customers see only the approved additional claim.
• A change does not silently overwrite a previously completed version.

Builds on these projects

This is intended

• Views, search, filters, responsible persons and follow-up
• Clear separation of form status and internal processing status

We measure completion by this

• Only authorized persons can view and modify assigned data.
• New team statuses do not change the previous sending status.

Builds on these projects

This is intended

• Own drafts and traceable published versions
• Restore as new version with preview of differences

We measure completion by this

• An ongoing process retains its appropriate form version.
• Resetting does not delete any answers or version history.

Builds on these projects

This is intended

• Roles for create, edit, read, and administration
• Local event log without response content and secret links

We measure completion by this

• Permissions are checked server-side for every action.
• Logging and retention are limited and traceable.

This is intended

• Preview affected data and files plus secure confirmation
• Optional retention rules with preview before activation

We measure completion by this

• No automatic deletion without activated rule.
• Jointly referenced files and active processes remain protected.

Builds on these projects

This is intended

• Add, remove, and limit field groups
• Conditions, validation and PDF per group instance

We measure completion by this

• Each instance retains stable field assignments when continuing.
• Export and PDF show all instances without mixed values.

Builds on these projects

This is intended

• Secure print editor with preview and decimal formats
• Server-side recalculation and defined handling of empty values

We measure completion by this

• Manipulated browser results are not accepted without verification.
• Calculation rules, rounding, and PDF results match.

Builds on these projects

This is intended

• Configure sections, page breaks and attachment overview
• Preview with sample data and stable field mappings

We measure completion by this

• Long texts, images, and repeatable groups are not cut off.
• Existing PDF output remains available as compatible standard template.

Builds on these projects

This is intended

• Events, field mapping, signing, test data and shipping log
• Limited repetitions and protection against double processing

We measure completion by this

• Only explicitly configured targets and fields are transmitted.
• Private network addresses, secret logs, and uncontrolled retry loops are excluded.

Builds on these projects

This is intended

• Documented events and importable sample workflows
• Field mapping and understandable error cases

We measure completion by this

• Examples initially use fictitious test data.
• Duplicate events do not lead to duplicate processes in the reference workflow.

Builds on these projects

This is intended

• Select first connector based on demand and interface capability
• Assignment, duplicate check and manual error correction

We measure completion by this

• No blanket sync of the entire customer base.
• Connection errors do not affect form completion.

Builds on these projects

This is intended

• Optional aggregated step, error, and completion counts
• Filter by form version and limited retention

We measure completion by this

• No field values, signatures, or complete links in analysis events.
• Disabled analytics generate no additional events.

Builds on these projects

This is intended

• Focus management, error assignment, labels, and upload alternatives
• Test matrix for standard fields and individual sub-processes

We measure completion by this

• A form can be operated without a mouse until completion.
• Automatic checks and manual screen reader tests document the scope.

Builds on these projects

This is intended

• Prioritize real estate, services, and organizational practice inquiries
• Professional acceptance, professional days and package assignment per template

We measure completion by this

• Only the actually published library is announced.
• Templates include version status, professional assignment, and tested completion.

Builds on these projects

This is intended

• Form-related help texts and preview of suggested changes
• Clearly explain features and data processing before use

We measure completion by this

• Suggestions change answers only after explicit acceptance.
• The form continues to work fully without AI.

Builds on these projects

This is intended

• Change comparison, schema-capable suggestions, and rollback
• Check report on fields, conditions, and comprehensibility

We measure completion by this

• Existing templates are not replaced without confirmation.
• Invalid field references are caught before publication.

Builds on these projects

This is intended

• Signed references instead of personal data in freely shareable URLs
• Field releases, origin, and editable suggestions

We measure completion by this

• Customers of other cases do not gain access via manipulated parameters.
• Prefill does not replace mandatory field validation.

Builds on these projects

This is intended

• Pilot with clearly limited document type and separate test data
• Origin, uncertainty, data processing and correction per suggestion

We measure completion by this

• Before a product pilot, suitable providers and traceable data flows are defined.
• No recognized value will become binding form content without confirmation.

Builds on these projects

This is intended

• Field mapping in released PDF templates
• Limits for complex layouts, fonts, and signature display

We measure completion by this

• A pilot demonstrates lossless mapping for defined document types.
• No guarantee of universal PDF conversion.

Builds on these projects

This is intended

• Role-based invitations and separate approvals
• Order, reminders, and final version

We measure completion by this

• Each person sees only the assigned sections.
• Already confirmed versions are replaced traceably when changed.

Builds on these projects

This is intended

• Client Separation, Authentication, and Controlled Reuse
• Task overview with clear approvals

We measure completion by this

• A separate authorization and operational concept exists before the pilot.
• Data is not automatically transferred between customers or cases.

Builds on these projects

This is intended

• Isolated managed WordPress instance as first pilot candidate
• Compare portal operation regarding maintenance, export, and client separation

We measure completion by this

• Before implementation, operation, support scope, and data export are defined.
• The existing self-hosted plugin remains fully supported.

Builds on these projects

This is intended

• Defined states, roles, and return with justification
• Traceable approval of a specific version

We measure completion by this

• Only authorized roles can approve.
• A later change makes the necessary re-examination visible.

Builds on these projects

This is intended

• Local storage, device protection, upload limits and conflict resolution
• Explicitly activated pilot for defined fields

We measure completion by this

• No silent saving of sensitive data on shared devices.
• An offline draft is never shown as submitted server-side.

Builds on these projects

This is intended

• Validate needs and initial external target integration
• Clear separation between form completion and external result

We measure completion by this

• A failed external process does not lose form data.
• No payment or appointment confirmation without verified provider status.

Builds on these projects

This is intended

• Delegated accesses, license overview and update statuses
• Client-specific Reports and Handover to Website Owner

We measure completion by this

• Agency rights do not allow blanket access to response content.
• License and client separation are demonstrated before the pilot.

Builds on these projects

This is intended

• Existing templates gain conditional requirements and clear column layouts.

We measure completion by this

• Hidden answers remain in the draft and are filtered appropriately on completion and in the PDF.

Builds on these projects

This is intended

• Twelve topic areas with search and topic filter
• Basic 36, Pro 72, and Business 108 templates

We measure completion by this

• Templates, landing page, menu, and demo available together.
• Existing copies and responses are retained.

Builds on these projects

This is intended

• Prominent entry on the demo homepage and direct form pages
• Mobile-optimized display and retention of the open test run

We measure completion by this

• Product website and packages are directly accessible.
• The entry remains visible while scrolling.

This is intended

• 32 independent templates with package and profession assignment
• Own landing page and reset-proof filtered demo

We measure completion by this

• Basic 10, Pro 22 and Business 32 suitable workflows provided.
• Existing customer copies and editorial changes remain preserved.

Builds on these projects

This is intended

• 36 independent templates for sales, rental, and organization
• Industry landing page with package filter and public demo

We measure completion by this

• Basic 10, Pro 22 and Business 36 templates are specifically available by profession.
• Existing personal copies remain preserved during official synchronization.

This is intended

• 70 Independent Additions After Matching the Existing Catalog
• 38 thematic health add-on forms in the regular real estate agent workflow

We measure completion by this

• Professional days and package limits remain specifically filterable.
• New templates are officially added; existing custom copies remain preserved.