Lucky Systems
EN ES
Book a mapping call
Home Solutions Builds Industries Insurance & risk Home services Custom Software About Book a mapping call
EN ES
Book a mapping call

Builds Document portal

Interactive demonstration · Insurance, mortgage & legal teams

Four documents, one customer. Watch the chase disappear.

One file, four documents. The missing one is found and requested automatically — then a named person approves.

Run the demonstration Book a mapping call

The six scenes — amber marks the gap, and the person who decides

  1. Checklist
  2. Request
  3. Uploads
  4. Missing
  5. Notify
  6. Review

Worked example: an insurance policy file. The same six scenes run a mortgage refinance or a legal matter.

How the document portal closes a file A four-item checklist feeds a secure portal. Three items arrive and are filed. The one missing item loops back out of the portal as a specific request and returns. The completed package leaves as one record, and a named reviewer decides whether to approve or return it. REQUIRED · 4 ITEMS Photo ID Current policy Vehicle photos Prior declarations SECURE PORTAL COMPLETE PACKAGE NAMED REVIEWER AUTOMATIC CHASE ONE ITEM, NAMED EXACTLY
One gap chased · one package out · one named reviewer

Guided demonstration · six scenes

Six scenes.
One complete package.

Play it, or jump to any scene. Each scene shows what arrived, what the system did, what the record says, and who owns it.

Live demo Insurance · policy file
Customer
Ana Reyes
File
New auto policy
Required
4 documents
Reviewer
Underwriting desk

1 / 6scene

Scene 01 / 06

Checklist created

Secure document portal Ana Reyes · New auto policy 0 of 4 received
  • Photo IDRequired
  • Current policyRequired
  • Vehicle photosRequired
  • Prior declarationsRequired

System

Checklist: photo ID, current policy, vehicle photos, prior declarations

  1. What arrived

    A new policy file

  2. What the system did

    Built the required list

  3. Record now says

    0 of 4 received

  4. Owner

    SYSystem

Scene 02 / 06

Secure request sent

Secure document portal Ana Reyes · New auto policy 0 of 4 received
  • Photo IDRequested
  • Current policyRequested
  • Vehicle photosRequested
  • Prior declarationsRequested

Assistant

Please upload 4 documents using this secure link. The list shows exactly what we need.

  1. What arrived

    The checklist, ready to send

  2. What the system did

    Sent one secure upload link

  3. Record now says

    4 items requested

  4. Owner

    ASAssistant

Scene 03 / 06

Documents uploaded

Secure document portal Ana Reyes · New auto policy 3 of 4 received
  • Photo IDReceived
  • Current policyReceived
  • Vehicle photosReceived
  • Prior declarationsWaiting

System

Received 3 of 4 · auto-named · filed to the customer record

  1. What arrived

    Three uploads from Ana

  2. What the system did

    Named and filed each one

  3. Record now says

    3 of 4 received

  4. Owner

    SYSystem

Scene 04 / 06

Missing item identified

Secure document portal Ana Reyes · New auto policy 1 item missing
  • Photo IDReceived
  • Current policyReceived
  • Vehicle photosReceived
  • Prior declarationsMissing

System

Missing: prior declarations page

  1. What arrived

    Nothing more from Ana

  2. What the system did

    Checked the list, found the gap

  3. Record now says

    Missing: prior declarations

  4. Owner

    SYSystem

Scene 05 / 06

The exact item is re-requested

Secure document portal Ana Reyes · New auto policy 1 item re-requested
  • Photo IDReceived
  • Current policyReceived
  • Vehicle photosReceived
  • Prior declarationsRe-requested

Assistant

One item left: the prior declarations page. A phone photo works fine.

  1. What arrived

    The named gap

  2. What the system did

    Asked for that one item

  3. Record now says

    1 item re-requested

  4. Owner

    ASAssistant

Scene 06 / 06

Complete package routed to a person

Secure document portal Ana Reyes · New auto policy 4 of 4 · in review
  • Photo IDReceived
  • Current policyReceived
  • Vehicle photosReceived
  • Prior declarationsReceived

System

All 4 items received · audit trail attached

Underwriting desk · human

Underwriting desk: package complete — starting review.

Collection complete — review open

Human actionApprove the package or return it with a reason

The collection workflow is finished. The file is not — approving or returning a policy package is a licensed judgement, so it stays with the named desk and the system waits.

  1. What arrived

    The last document

  2. What the system did

    Attached the full trail

  3. Record now says

    4 of 4 · in review

  4. Owner · human

    UDUnderwriting desk

Activity trail — writes itself as the run plays

Every scene writes one line.
TimeEventOwner
Day 1 · 09:00Required-document checklist createdSystem
Day 1 · 09:05Secure document request sentAssistant
Day 1 · 14:10Documents received and filedSystem
Day 1 · 14:11Missing item identified: prior declarations pageSystem
Day 1 · 14:12Specific request sent to customerAssistant
Day 2 · 10:02Complete package routed to reviewerUnderwriting desk

Synthetic data. The workflow is real; Ana Reyes, the uploads and the underwriting desk are made up so you can click through them. No client, no client result, no live integration.

Never automated

  • Approving or returning a package
  • Deciding an item is “close enough”
  • Contact outside approved templates

The same run, one frame

The checklist
completes itself.

Six scenes drawn as one working day. Three documents file themselves, the fourth goes missing and is chased without anyone being asked to remember — and the finished package stops, on purpose, at a named person.

A document checklist completing itself over one working day A timeline runs left to right from Day 1 at 09:05 to Day 2 at 10:02. Four required documents sit in a checklist on the left. Three of them — photo ID, current policy and vehicle photos — arrive during Day 1 and are named and filed automatically. The fourth, prior declarations, stops part way as a missing item; an amber loop returns to the checklist at 14:12 as one specific automatic request, and the document arrives the next morning. All four then converge on the governed build, which produces one complete package of four of four with the trail attached. The package stops at an amber human gate, where the underwriting desk approves or returns it. Nothing is approved automatically. REQUIRED · 4 ITEMS DAY 1 · 09:05 DAY 1 · 14:10 DAY 2 · 10:02 AND THEN IT WAITS Photo ID NAMED AND FILED Current policy NAMED AND FILED Vehicle photos NAMED AND FILED Prior declarations CHASED, THEN FILED MISSING DAY 1 · 14:12 · AUTOMATIC CHASE ONE ITEM, NAMED EXACTLY COMPLETE PACKAGE 4 OF 4 · TRAIL ATTACHED NO AUTOMATIC APPROVAL HUMAN GATE · UNDERWRITING DESK APPROVES IT, OR RETURNS IT WITH A REASON THE SYSTEM WAITS UNTIL THEY DO
Day 1, 09:05 to Day 2, 10:02 — the run above, drawn as one frame. Amber is the only colour here that means a person is required.

Before and after

The same document file,
two ways.

Nothing below is a measured result. It is a description of how the work is organised — which is the part you are actually buying.

Manual today

  • Staff chase documents by email and phone
  • Uploads arrive unnamed in an inbox
  • Missing items surface at review time

Connected system

  • One secure link lists exactly what to send
  • Uploads are named and filed automatically
  • Gaps are found and requested specifically

Scenario arithmetic

What does the document chase represent?

These three numbers are assumptions, not measurements. Change any of them on the mapping call and the arithmetic changes with it.

files × reminders × minutes ÷ 60
= administrative time represented

  • Customer files per month80
  • Manual reminders per file3
  • Minutes per reminder6 min

Monthly administrative time represented

24 h

240 reminders · 80 customer files

Scenario estimate based only on the assumptions selected in this demonstration. It is not a forecast, guarantee, or measured client result. Disclosures

Security and privacy posture

What the portal is
allowed to touch.

A document workflow only earns trust if the boundary is written down. Here is what crosses it, and what never does.

What crosses the system boundary Four kinds of information cross into the build and are logged: the checklist definition, the uploaded documents, who uploaded them and when, and the approval or return decision. Three kinds are stopped at the boundary and never enter: protected health information, passwords and credentials, and payment account details. SYSTEM BOUNDARY CHECKLIST DEFINITION UPLOADED DOCUMENTS WHO UPLOADED AND WHEN APPROVAL OR RETURN COLLECTED AND LOGGED PROTECTED HEALTH INFORMATION PASSWORDS AND CREDENTIALS PAYMENT ACCOUNT DETAILS NEVER ENTERS DEMOS OR BUILDS
The boundary is drawn during discovery and written into the build, not assumed afterwards.

Collected

Only what the checklist defines.

The documents your team listed, what each arrived as, when, and who asked for it. Nothing else.

Access

The narrowest that still works.

The customer sees only their own checklist. The assistant can request, name and file — it cannot approve. The reviewer decides.

Excluded

Protected health information, categorically.

Protected health information is excluded from demos, prompts, and development systems categorically. A workflow that must handle it does not begin until the right contracts, controls and reviews are in place — that is a scoping conversation, not a switch we flip.

This page stores nothing

There is no file input, no upload endpoint and no storage behind this demonstration. Nothing you do here is transmitted or retained.

Retention and deletion are yours

How long each document class is kept, who can delete it, and what the trail keeps afterwards are your policy decisions. We map them with you before anything is built.

Judgement stays human

Approving, returning, and anything uncertain, sensitive or regulated stops and routes to a named person with the full context attached.

No transmission or storage method is perfectly secure, so keep passwords, protected health information and financial account details off this site. Privacy Disclosures

Same engine, different checklist

Three files.
One set of rules.

The six scenes above do not change. Only the checklist, the reviewer, and the item that goes missing change — which is why this pattern moves between industries without being rebuilt.

Insurance

Running above

New policy file

Customer
Ana Reyes
Reviewer
Underwriting desk
  • Photo ID
  • Current policy
  • Vehicle photos
  • Prior declarations

Missing item found: prior declarations page

Mortgage

Refinance application

Customer
David Kim
Reviewer
Processing team
  • Photo ID
  • Two pay stubs
  • Bank statement
  • W-2

Missing item found: second pay stub

Legal

Contract dispute matter

Client
Grace Osei
Reviewer
Supervising attorney
  • Signed engagement letter
  • Contract
  • Correspondence
  • Invoices

Missing item found: signed engagement letter

Where a checklist item is a document set rather than a single page — two pay stubs, a set of vehicle photos — the rule and the chase are defined with you, item by item, before anything is built.

Explore another workflow

Five more systems you can run.

All six demonstrations

The demo is simple — the operating rules are specific

Map your document workflow.

A real build starts from your checklists, review rules, retention policy, and reviewer roles — mapped together on one call.

Bring us the problem. We’ll build a better way.

Book a mapping call Return to all builds

30 minutes. One workflow mapped. You keep the map either way.