Patterns
How components combine into the pages and flows of Ascern.
Pattern · Files and CVs
A record's files, the viewer that opens them, and the path from a candidate's CV to a client's inbox. Flo formats and drafts; the consultant checks every CV and sends every email.
Pattern · Flo
Flo works beside the page, in the same ink, greys and one green as the rest of Ascern. It shows what it is doing, proposes changes for the member to approve, and every change it makes can be undone.
Pattern · Inbox and notes
How a consultant reads mail, replies, files what happened and adds the people they meet. Flo drafts and suggests; nothing is sent or added until the consultant says so.
Pattern · Meetings
The composites on Meetings and a meeting's page: where the calendar sits, how one meeting opens, and what happens before and after the call. Each is built from shared components; the colour of a meeting is its type.
Pattern · Onboarding and access
How people get in and get going: sign-in, two-step verification, invitations, the Get started checklist, connected accounts, the lookup meter and the sandbox clock.
Page templates
Every Ascern screen is built from six templates and three named exceptions. Each row names the template, what Ascern ships today and the rule it moves to.
Pattern · Record
The parts of a record page between the title and the details rail: what's owed next, the overview, the records it relates to, and a placement's own sections.
Pattern · Reports
The Dashboard: three fixed views over one load, read-only, for a chosen period and scope. A number changes where its record is edited, and every number that can list its records links to them.
Pattern · Rules
Rules run on their own, as the member who made them. The list, one Rule, its run log, Inbox sorting rules and the templates to start from. Anything that needs a decision waits for a person.
Template mockups
Today