One list, both sides
The policy your team writes is the policy the applicant works through. Neither side is reading a copy of the other side’s notes.
Decide what you require once.
Write down the documents and details you need from the people you onboard. Pagebread turns that list into what each applicant sees, one link and one checklist, and checks every submission back against it.
Onboarding flow
Business borrower onboarding
- Registered business nameShort textReceived
- Certificate of incorporationDocumentReceived
- Director identity documentDocumentReceived
- Bank statement, last 3 monthsDocumentReceived
- Proof of registered addressDocumentOutstanding
Checked against the policy: 1 of 5 requirements still outstanding.
Checked on arrival
Every submission arrives checked for presence against the policy it came from, so you start the review already knowing where to look.
The work is deciding, then chasing.
Collecting documents is rarely the hard part. Agreeing on what to collect is, and so is knowing, on any given morning, which of forty people has sent which of six things.
Deciding what to ask for
The list lives in somebody’s head, and two colleagues onboarding the same kind of customer remember it differently. Nobody finds out until the exception does.
Getting it back
Documents arrive by email, over chat, as photographs of a screen, one at a time, from people who cannot see what is still outstanding on their own application.
Knowing where everyone stands
Answering “what is left on this one” means opening a spreadsheet, an inbox and a folder of scans, and trusting that all three agree with each other.
Define it once. It applies to every applicant.
Write the policy
List the details and the documents you require. Mark what is mandatory, and say how each item should be supplied.
The list stops being remembered and starts being defined.
Publish the flow
The policy becomes a flow with its own link. Invite named applicants to it, or publish it openly and let people start from the link.
One address to send, instead of an email you rewrite each time.
Applicants submit
They answer the questions and upload what they have, from a phone if that is what they are holding, and return later to see where they stand.
They can see what is outstanding without asking you.
Review against the policy
Each submission arrives checked for presence against the policy it came from, with a checklist of what was supplied and what is still missing.
You start the review already knowing where to look.
One list. Two views of it.
The policy your team writes is the same policy the applicant works through. Neither side is reading a copy of the other side’s notes.
Your team sees
Everything outstanding, in one place
- Every submission across every flow, with the status it is in right now.
- What each applicant has supplied and what is outstanding, against the policy that applies to them.
- Documents in one place, opened through short-lived links rather than left sitting in an inbox.
- Colleagues you invite into the organization, working from the same policies rather than their own.
The applicant sees
What is needed, and what is still missing
- One link, and no account to create before they can start.
- The same list your team is working from, in plain language, with instructions on each item.
- Somewhere to upload from a phone, an item at a time, over as many sittings as it takes.
- A page they can come back to that shows where their application stands and what is still needed.
Wherever onboarding depends on documents.
The evidence differs. The problem does not: a defined list of what is required, a set of people who have to supply it, and a need to know where each of them has got to.
- Lending and credit onboarding
- Business and merchant onboarding
- Vendor and supplier onboarding
- Employee onboarding
- Tenant screening
How the documents are handled.
Verified on every request
An organization’s credential is checked with the authentication provider on every single request, on the server. Sign out, and the next request is already refused.
Two separate credentials
The credential an applicant holds and the credential your team holds are different mechanisms, verified in different places. Neither can stand in for the other.
Documents are not public addresses
An uploaded document has no URL anyone can hold on to. It is opened through a signed link that stops working after five minutes.
Uploads are evidence for your review. Where you are required to see an original, you still see the original: Pagebread gets you to that meeting with the checking already done, rather than replacing it.
This section is here rather than at the top on purpose. In this category these are the floor, not the argument, and a page that opens with them is telling you it has nothing better to say.
Get started
Start with one policy.
Write down what you require for a single kind of applicant, publish the flow, and send it to the next person you onboard. That is the whole of the first use.