Product
Flows
The product in use, step by step: signing in first, then the flows of the product itself. Each flow is a page of its own with a step player.
The flows
Sign-in first, then the flows of the product, in the order they are met.
Sign in with Microsoft
Dana signs in with her Valere Microsoft 365 account; the first sign-in shows the mailbox-capture policy; someone without an account is told whom to ask.
From a candidate site to a formal instruction
Priya accepts a candidate, Jamie works the Lead, the appraisal is approved within 5 working days, Site Review, Instruction Approval and the fee agreement signed: Hatch Farm is instructed and handed to Partnerships.
From instruction to an acceptable offer
Dana pitches Orchard Lane to the recommended buyers from her own mailbox, compares the offers like for like and chooses the Preferred RP.
From an acceptable offer to an acceptable build
Conor tenders Orchard Lane: the longlist with its red flags, the bids read against the benchmark, the preferred contractor, Acceptable Build.
From Heads of Terms to completion
Church Farm’s Heads of Terms signed through Adobe Sign, Legals tracked to its critical dates with weekly chasers, exchange and completion, the fees flagged until invoiced.
A Site parked, closed as Dead, and reopened
Jamie puts Mill Pond on hold from the weekly review and closes Old Dairy as Dead; Rhys finds Mill Croft, closed in September, and reopens it with a reason.
The Monday meeting
Rhys chairs the Morning Meeting on the shared screen; Jamie runs the Weekly Regional Review and locks the week; the partner pack goes on Friday.
The MD’s exceptions and decisions
Requests for a partner exception reach Rhys; on the Executive dashboard Rhys declines one with a reason and approves another, and each requester is told.
An email or a meeting becomes a record update
A solicitor’s email becomes a proposed date change Dana accepts; an enquiry becomes a Candidate lead; a Teams transcript becomes actions the chair approves.
The admin changes a rule
Tom changes a stall threshold, sees its impact before saving, and the change applies from then on, on record and restorable.
A leaver, an absence and the named cover
Dana names Priya as cover for a week away; actions and deal emails go to Priya. Tom hands over a leaver’s work, revokes the token and deactivates the user.
Cut-over from Excel
Tom loads the trackers, merges duplicates, runs the parallel run with its daily reconciliation, and cuts over; the trackers become read-only.