Briefings
Nine people, nine different mornings, one system underneath.
A credit officer, a collector and an owner do not need the same screen and never did. They need the same book, read three different ways, by something that knows what each of them is accountable for this morning.
A FactorFox briefing answers six fixed questions against the scope a person actually carries, states what moved since the last one, and puts the evidence and the next action in the same place as the finding. It is written for the operator running the funding company, never for the business being funded.
Morning briefing
Owner · whole book · 07:00
Where is risk and why?
Concentration in one debtor moved from 43.2% to 95.5% of the book overnight.
Share of the book rose 52.3 points since the last observation. Paper past 60 days against this debtor rose 96.4 points in the same window.
Evidence
Sunline Packaging normally submits at a median of $14,125. Confidence is 45% because the baseline holds few invoices. Submitted outside business hours.
Evidence
Which decisions require me now?
Three approvals are waiting on you. One is blocked because you requested it.
What changed since the last brief?
Four material movements. Two concentration, one aging, one submission pattern.
Where is cash and what can move safely?
Net availability holds. Two releases are clear of every gate and can go today.
What is likely to happen next?
Two promises lapse this week. One debtor's days to pay is drifting past its own history.
Am I within covenant?
Within every threshold. Concentration reaches its limit in eleven days on current trajectory.
Why briefings and not dashboards
The information was always there. Finding it was the job.
Nothing on this list is a software failure in the narrow sense. Every one of these systems recorded the truth correctly. They just never told anybody.
The six questions
Fixed questions, because the questions were never the variable.
These are the six a funding company answers every day whether or not it owns software. What changes between people is the scope they are answered over, not which questions get asked.
| The question | What produces the answer |
|---|---|
| Where is risk and why? | Concentration migration, dilution movement, payment velocity against each debtor's own history, aging tipping between buckets, and invoice patterns that sit outside the client's own baseline. |
| Which decisions require me now? | Approvals, overrides and exceptions waiting on your authority, including the ones you are blocked from giving because you raised them yourself. |
| What changed since the last brief? | The delta against the last recorded observation. Where no prior observation exists, it offers to take a first one rather than inventing a yesterday. |
| Where is cash and what can move safely? | Net availability, releases clear of every gate, payment files ready by rail and by bank, and anything sitting inside the human only hold window. |
| What is likely to happen next? | Promises due and promises lapsing, days to pay drifting against a debtor's own record, availability compression with days to zero, and covenant trajectory. |
| Am I within covenant? | Facility limits, concentration, eligibility, advance rates, reserves and reporting obligations, measured against the covenants you record, with days to breach on the current path. |
Scope
Scope follows responsibility, and permission is not responsibility.
The tempting design is to brief people by job title. It is also wrong, and it fails on the first day a company has two credit officers with different books.
FactorFox briefs against responsibility. An account executive with forty clients is briefed on the forty, not the three hundred their role allows them to open. A collector is briefed on the debtors assigned to them, ordered by exposure and promise history rather than by age alone. A treasury officer is briefed on cash and the rails, not on onboarding files. The owner is briefed on the whole book, because the whole book is what an owner is accountable for.
Cadence follows scope as well. An owner gets a morning brief, exception alerts through the day and a closing view. A credit officer is briefed continuously, gated by materiality, because an event that does not change a decision is not worth interrupting anybody for. Operations lives in a queue that updates as the queue moves. Nine role shapes ship with the platform and every one of them is a starting point rather than a fixed template.
The escalation lane
Narrow scope has one obvious failure: something serious happens just outside it and nobody hears. So severity has a second route. A material event outside a person’s book travels the escalation lane to somebody whose scope covers it, and it arrives labelled, with the scope it came from named.
Escalated items are never blended into your own findings, because an item you are being told about and an item you are accountable for demand different responses. Owners and directors carry book wide escalation scope, so there is always a person with the authority to act.
Nine roles
What each person is handed, and how often.
These are the shipped role shapes. Read them as the scope and cadence a real operation ends up with, not as a permissions matrix.
| Role | Scope | Cadence | What the brief carries |
|---|---|---|---|
| Owner and principal | Whole book | Morning brief, exception alerts, end of day |
|
| President and executive | Whole book or division | Morning brief, midday movement, end of day |
|
| Credit officer | Assigned clients and debtors | Continuous, gated by materiality |
|
| Underwriter | Pipeline and assigned files | On event |
|
| Operations | Queues and exceptions | Throughout the day |
|
| Account executive | Assigned clients | Morning brief, client events |
|
| Collections | Assigned debtors | Morning worklist, promise events |
|
| Treasury | Cash and rails | Morning brief, release windows |
|
| Accounting | Ledger and close | Daily, and at close |
|
One day, four contacts
Morning brief, movement, exceptions, close.
The briefing is not a single email at seven. It is a rhythm, and the rhythm is what stops the day from being interrupted by everything at once.
- Morning
The brief that decides the shape of your day
Six questions answered over your scope, ordered by severity, with the count of items that require you specifically shown before you read a word. The owner sees whole book exposure and the approvals only they can give. Operations sees what is blocking today's funding, ordered by dollars. Both are looking at the same records.
- Through the day
Movement, gated by materiality
Not every change deserves an interruption. A signal reaches you when it crosses materiality for your scope, and it arrives with its severity, its reason and the action it wants. Everything below that line waits for the next brief instead of training you to ignore notifications.
- On event
Exceptions and approvals, wherever you are
An approval that needs you arrives in the web application, in Microsoft Teams and on your phone from the same endpoint. Acting on it crosses the ordinary application surface, so role checks, four eyes, counter review and facility guards run identically to a browser click, and the audit record names the origin.
- Close
What moved, and what is carried into tomorrow
The closing brief states the difference against the morning rather than repeating it. Promises lapsing overnight, releases that did not clear a gate and why, covenant position with days to breach on the current trajectory, and anything the escalation lane carried up during the day.
Anatomy of an answer
Four things, on every single item, without exception.
This is the contract. If an item cannot carry all four, it is not shown as a finding, because a finding you cannot open is a rumour with a number attached.
| Part | What it is | Why it is there |
|---|---|---|
| Severity | Critical, attention, clear or nothing, applied consistently across every surface. | So a scan of the page in ten seconds produces the same ordering that a careful read would. Severity is assigned by the platform, not chosen by whoever wrote the rule. |
| The reason | Plain language: what moved, from what to what, over which window, and against which baseline. | An alert without a reason gets dismissed, and once people start dismissing they stop reading. The reason is also what makes a dismissal defensible when somebody asks about it later. |
| Evidence references | Links into the actual FactorFox records. Invoices, aging observations, documents, payment behaviour, policy versions, contract clauses. | So the person deciding can open what produced the number instead of taking it on faith, and so the same references sit in the packet three years later. |
| Actions with permissions | The next steps, each labelled with the permission it requires, offered only to somebody holding it. | The finding and the fix belong in one place. Showing an action to somebody who cannot take it is how work gets forwarded four times before anything happens. |
Where a conclusion rests on a source that is not connected, the item says so and reports coverage separately from confidence. A thin baseline lowers confidence and the item says that too, in the same sentence as the finding.
Straight answers
What people ask about briefings
Why are the six questions fixed rather than configurable?
Because a configurable brief becomes a report, and a report becomes something nobody reads. The six questions are the ones a funding company answers every morning whether or not it has software: where is risk, what needs me, what changed, where is cash, what happens next, am I within covenant. Fixing them means the brief has a shape you learn once and can scan in forty seconds. What is configurable is scope, cadence, thresholds and the evidence sources behind each answer.
Who decides what each person is briefed on?
Responsibility does, not job title. Two credit officers with the same title and different books get different briefs. Someone who owns forty clients is briefed on those forty, even though they may be permitted to view three hundred. Permission to see something is not the same as being accountable for it, and briefing on everything a person may view is how a brief turns back into a dashboard.
What happens to something serious that falls outside my scope?
It reaches you through the escalation lane and it arrives labelled as escalated, with the scope it came from named. It is never blended into your own items as though it were yours. Owners and directors carry book wide escalation scope, so severity can always find a person with the authority to act, and the record shows who was reached and when.
How is the second briefing of the day different from the first?
It states the difference rather than restating the book. If nothing material moved, it says so in a line. The delta is computed against the last recorded observation, and where no prior observation exists the platform refuses to invent one. It offers to take a first observation instead, which is the honest version of a chart that would otherwise show a change nobody can prove.
Do briefings reach people who never open the platform?
That is the usual case for owners and treasury. The same endpoint serves the web application, Microsoft Teams and mobile, so a brief read on a phone is not a summary of the real brief. It is the brief. Actions taken from it cross the ordinary application surface, which is why four eyes, role checks and audit still apply to a tap made in a car park.
Related
Ask for the briefing your own role would receive.
Tell us the seat you sit in and the size of book you carry. We will run the brief for that scope against a demonstration portfolio, and you can open every reference on it.