Reinsurance Broker Workflow Web Application
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted1 hour ago
Project Brief: Reinsurance Broker Workstation 1. Project Overview
I need a secure, cloud-hosted, responsive web application designed specifically for a reinsurance broker handling FAC, QS, and XOL business.
The application must work on desktop, tablet, and mobile devices. It must be independent of my employer's email system.
Strict exclusion: No Outlook integration, email account connection, mailbox access, automatic email reading, or email sending. All placement records, follow-up dates, and market responses will be entered manually.
The application should be simple to use daily, with a clear dashboard, searchable records, internal reminders, and structured document storage.
2. Core Modules A. Dashboard Open placements by business class and status. Today's tasks and overdue follow-ups. Pending reinsurer responses. Quotes approaching expiry. Upcoming agreement renewals. Signed-line progress and outstanding requirements. B. Reinsurer Database
Each reinsurer record should include:
Unique Reinsurer ID and legal name. Country, rating agency, rating, and verification date. Business classes and underwriting appetite. Capacity by class, currency, territory, and relevant agreement. Restrictions, exclusions, and notes. Contact names and manually entered contact details. Agreement/facility details, effective dates, and expiry dates. Last verified date and source of information. Related documents and historical notes. C. Placement Tracker
Create a unique Placement ID for every transaction.
Common fields:
Client or insured reference, subject to confidentiality rules. Business class: FAC, QS, or XOL. Risk description, territory, currency, limits, premium, and key dates. Submission date, inception date, and expiry date. Status: Draft, Preparing, Submitted, Quoting, Negotiating, Bound, Declined, or Closed. Responsible person, next action, and next action date. Links to related reinsurers, responses, and documents. D. Market Responses
Allow multiple reinsurer responses per placement.
Track:
Reinsurer approached and date approached. Response status and response date. Quoted terms, price/rate, currency, exclusions, and conditions. Offered line percentage and signed line percentage. Quote validity and expiry. Outstanding requirements and next follow-up. Manual notes and links to relevant records.
Include configurable validation checks for signed-line totals, missing data, expired quotes, and outstanding actions. FAC, QS, and XOL must have separate, appropriate fields and validation rules.
E. Internal Reminder System Create reminders directly within the application. Assign a due date, priority, and related placement or reinsurer. Show overdue, due-today, and upcoming tasks. Generate alerts inside the application when the user logs in. Support recurring reminders where appropriate. Avoid duplicate alerts for completed or closed items. Allow snoozing, rescheduling, and marking tasks complete.
Email, SMS, WhatsApp, and external push notifications are not required for the initial version.
F. Knowledge Base and Documents Searchable library for procedures, regulatory references, reinsurer profiles, technical notes, and templates. Document categories, tags, dates, and source links. Attach or link documents to placements and reinsurer records. Version/history tracking where supported. Search by keyword and filter by category. G. Reporting and Export Filterable tables and dashboard summaries. Export authorized records to Excel/CSV. Printable placement summaries. Ability to export all owned data in a documented, usable format. 3. Technical Requirements Responsive web application with optional PWA installation. Secure individual login and password recovery. Central cloud database with structured relationships. Server-side access control and validation. HTTPS, encrypted storage where supported, and secure session management. Automated backups and documented recovery procedure. Audit trail for important changes. Search, sorting, filters, and pagination. Clear error messages and data validation. A documented method to migrate data and transfer the system to another provider.
The developer must recommend the technology stack and cloud hosting provider, explain the recurring costs, and confirm the hosting region and data-processing arrangements before implementation.
4. Privacy and Ownership No access to my employer's email or Microsoft 365 account. No use of real company/client data during development without written authorization. Use dummy data for demonstrations and testing. All application source code, database schema, documentation, and project-specific deliverables must be transferred to me under agreed intellectual-property terms. Hosting, domain, database, and administrative accounts should be registered in my name or an approved business account, not exclusively controlled by the freelancer. No hidden administrator accounts, unauthorized telemetry, or undisclosed third-party services. Document how to revoke developer access after handover. Provide a data export and deletion procedure. 5. Delivery Milestones Requirements confirmation and clickable prototype. Database schema and working core modules. Placement workflows, reminders, and validation. Document library, reporting, and responsive interface. Security checks, user acceptance testing, and bug fixes. Deployment, documentation, backup verification, and handover training.
Each milestone must have a written acceptance checklist. Payment should be linked to accepted deliverables.
6. Please Include in Your Proposal Fixed-price quote broken down by milestone. Estimated delivery timeline. Proposed technology stack and hosting location. Monthly hosting, storage, backup, and maintenance costs. Security approach and access-control design. Examples of similar database/workflow applications. Support period after launch. Confirmation that no email integration is required. Confirmation of full source-code and data handover.
Please begin with a working prototype using dummy data before building the full system.
I need a secure, cloud-hosted, responsive web application designed specifically for a reinsurance broker handling FAC, QS, and XOL business.
The application must work on desktop, tablet, and mobile devices. It must be independent of my employer's email system.
Strict exclusion: No Outlook integration, email account connection, mailbox access, automatic email reading, or email sending. All placement records, follow-up dates, and market responses will be entered manually.
The application should be simple to use daily, with a clear dashboard, searchable records, internal reminders, and structured document storage.
2. Core Modules A. Dashboard Open placements by business class and status. Today's tasks and overdue follow-ups. Pending reinsurer responses. Quotes approaching expiry. Upcoming agreement renewals. Signed-line progress and outstanding requirements. B. Reinsurer Database
Each reinsurer record should include:
Unique Reinsurer ID and legal name. Country, rating agency, rating, and verification date. Business classes and underwriting appetite. Capacity by class, currency, territory, and relevant agreement. Restrictions, exclusions, and notes. Contact names and manually entered contact details. Agreement/facility details, effective dates, and expiry dates. Last verified date and source of information. Related documents and historical notes. C. Placement Tracker
Create a unique Placement ID for every transaction.
Common fields:
Client or insured reference, subject to confidentiality rules. Business class: FAC, QS, or XOL. Risk description, territory, currency, limits, premium, and key dates. Submission date, inception date, and expiry date. Status: Draft, Preparing, Submitted, Quoting, Negotiating, Bound, Declined, or Closed. Responsible person, next action, and next action date. Links to related reinsurers, responses, and documents. D. Market Responses
Allow multiple reinsurer responses per placement.
Track:
Reinsurer approached and date approached. Response status and response date. Quoted terms, price/rate, currency, exclusions, and conditions. Offered line percentage and signed line percentage. Quote validity and expiry. Outstanding requirements and next follow-up. Manual notes and links to relevant records.
Include configurable validation checks for signed-line totals, missing data, expired quotes, and outstanding actions. FAC, QS, and XOL must have separate, appropriate fields and validation rules.
E. Internal Reminder System Create reminders directly within the application. Assign a due date, priority, and related placement or reinsurer. Show overdue, due-today, and upcoming tasks. Generate alerts inside the application when the user logs in. Support recurring reminders where appropriate. Avoid duplicate alerts for completed or closed items. Allow snoozing, rescheduling, and marking tasks complete.
Email, SMS, WhatsApp, and external push notifications are not required for the initial version.
F. Knowledge Base and Documents Searchable library for procedures, regulatory references, reinsurer profiles, technical notes, and templates. Document categories, tags, dates, and source links. Attach or link documents to placements and reinsurer records. Version/history tracking where supported. Search by keyword and filter by category. G. Reporting and Export Filterable tables and dashboard summaries. Export authorized records to Excel/CSV. Printable placement summaries. Ability to export all owned data in a documented, usable format. 3. Technical Requirements Responsive web application with optional PWA installation. Secure individual login and password recovery. Central cloud database with structured relationships. Server-side access control and validation. HTTPS, encrypted storage where supported, and secure session management. Automated backups and documented recovery procedure. Audit trail for important changes. Search, sorting, filters, and pagination. Clear error messages and data validation. A documented method to migrate data and transfer the system to another provider.
The developer must recommend the technology stack and cloud hosting provider, explain the recurring costs, and confirm the hosting region and data-processing arrangements before implementation.
4. Privacy and Ownership No access to my employer's email or Microsoft 365 account. No use of real company/client data during development without written authorization. Use dummy data for demonstrations and testing. All application source code, database schema, documentation, and project-specific deliverables must be transferred to me under agreed intellectual-property terms. Hosting, domain, database, and administrative accounts should be registered in my name or an approved business account, not exclusively controlled by the freelancer. No hidden administrator accounts, unauthorized telemetry, or undisclosed third-party services. Document how to revoke developer access after handover. Provide a data export and deletion procedure. 5. Delivery Milestones Requirements confirmation and clickable prototype. Database schema and working core modules. Placement workflows, reminders, and validation. Document library, reporting, and responsive interface. Security checks, user acceptance testing, and bug fixes. Deployment, documentation, backup verification, and handover training.
Each milestone must have a written acceptance checklist. Payment should be linked to accepted deliverables.
6. Please Include in Your Proposal Fixed-price quote broken down by milestone. Estimated delivery timeline. Proposed technology stack and hosting location. Monthly hosting, storage, backup, and maintenance costs. Security approach and access-control design. Examples of similar database/workflow applications. Support period after launch. Confirmation that no email integration is required. Confirmation of full source-code and data handover.
Please begin with a working prototype using dummy data before building the full system.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.