You find out when it is too late to argue.

Three changes, and they are the ones that move the lines above.

• You get the finding, not the data

  A dashboard shows you a number and leaves the work to you. This arrives as one specific proposed action, ranked, with the rule it invoked and the records it cited attached to it.

• A named person decides

  A finding arrives as a drafted action and waits. Approving it is what sends it, and who approved it, when, and what they changed stays on the record — so the reason can be given later without assembling it again.

• Your records stay on your machines

  The files and the reasoning about them run on hardware you control. Nothing is sent to an outside model provider, which is usually the shortest route through a security review.

Read the FACE paper The long version: what it reads, what it produces, who approves it and where it runs.

Find the line that reads like your week. Each one opens on the scenarios that industry actually runs — cold chain, a customs filing, an equipment limit, a loss file, a clause — each worked from the record that starts it to the person who approves what is done about it.

• Logistics & Supply Chain

  An entry held at the port for a missing paper while the daily charge runs. A freight claim still inside its filing window that nobody had the morning to assemble.

  Operations directorChief financial officerTrade compliance

  Open

  How it is read today

  A container on a hold nobody has joined to the document it is waiting for, while free time runs out. A filing window that closes while the evidence sits in four systems.

  How Runink reads it

  Every entry is compared against the rule that governs it — held, under examination or detained, with days held above zero — so a hold arrives as a named entry with the charge counted from your own rate.

  Where it shows up in your operating numbers

  • Demurrage, detention and the claims that expire

    Where yours is

    The accessorial lines on the carrier invoice, against the free-time clock on the entry. Claims filed against claims available.

  1. Before it ships

     Demand and fulfilment

     A line starts moving weeks before the reorder point does, and the plan catches up after the stockout.

     Equipment limits

     The chiller, the conveyor and the lift write down what they are doing all day, and somebody reads it after the load is the evidence.

  2. In transit

     Cold chain

     A container drifts warm overnight and nobody opens the door until morning.

     Reactive logistics

     The plan that was right at six in the morning is wrong by ten, and nobody re-runs it.

     Customs filing

     The box is stopped at the border and the filing it was declared under is a separate story in a separate system.

  3. After it comes back

     Reverse logistics

     A return is worth the most on the day it comes back, and the grading call waits.

  4. When the money moves

     Claims and disputes

     A claim expires because assembling one takes a morning nobody had that week.

     Underwriting

     The wording, the loss report, the reserve history and the authority limit sit in four places.

  Customs hold · A container held at the port, from hold to cleared

  1. The hold shows up

     An entry comes back held, under examination or detained, and the count of days it has been held is above zero. That combination is the whole test — it is a fixed rule, not a judgement, and it runs against every entry rather than the ones somebody thought to check.

  2. The cost is counted from your own rate

     The days it has been held, multiplied by the per-day demurrage rate in your own agreement. That is the arithmetic in full. It is the figure that is already accruing while the entry sits in a queue nobody reads end to end.

  3. The missing paper is named

     The reason for the hold and the documents outstanding against it come off the entry record and are stated on the item, so the person who picks it up is not starting by finding out what is wrong.

  4. The accountable party is checked

     Separately, entries are read for an importer of record that is blank, or filled in with the consignee, or with a placeholder somebody typed once. Those carry duty and tax with nobody accountable for them, and they are raised as their own item with the amount at stake attached.

  5. Every pound is counted once

     Demurrage on a held entry and duty on an unattributed one are different money, and counting them as one number is the commonest way this sort of total gets inflated. They stay separate, deliberately, and there is a test that fails if they ever merge.

  6. A named person decides

     The item waits. Approving it is what sends anything, and who approved it, when, and what they changed is written down. If part of what was drafted could not be carried out, the result names that part rather than reporting success.

  Cold chain · A reefer that drifted warm, from the door to a filed claim

  1. The frame arrives

     A photograph taken on a handheld at the door, or a still pulled off a yard camera. Before anything reads it, it is checked to be an image: the header is decoded on its own, the format has to be one of two, and the size is capped both in bytes and in pixels. A PDF, a video container or raw bytes are refused at that step.

  2. A model reads it, on your hardware

     The frame is reduced to a size the model can take and read by a vision model running on machines you control. What comes back is a written observation tied to the exact frame it was read from, so the sentence and the evidence for it stay together.

  3. The paperwork is read beside it

     The consignment record, the handover, and the condition the documents say the load should be in. The observation is set against what was already written down rather than against a threshold somebody picked.

  4. What differs comes out named

     The pallet, the crate, the container door — named, in the words a person would use. A severity score cannot be argued with in front of a carrier. A named part of a named consignment can.

  5. The call reaches the person who owns it

     A cue can be broadcast to whatever is subscribed to the yard's event stream, and the record keeps it as what it is: requested. What happens next is somebody's decision, and the record says so rather than implying a movement was stopped.

  6. A named person decides

     The item waits, exactly as the held entry does. Approving it is what sends anything, and who approved it, when, and what they changed is written down.

  Customs filing · A manifest that came back rejected, from the filing to the paper it named

  1. The filing is read, not the clearance

     An entry can be stopped at the border on a manifest the authority accepted, and a filing can be rejected while the box is still moving. Held is a clearance state and rejected is a filing state. Each is read where it is written, and neither is ever read as the other.

  2. The code travels as it was written

     The exception code the rejection carried comes across word for word, with the manifest it belongs to, the port it was filed at and who filed it. Your broker gets the reference to quote back rather than somebody's paraphrase of it.

  3. Each missing paper is named on its own line

     Every document the filing named as outstanding comes out as its own item, carrying the record it was read from. What is waiting on whom is the first thing on the page rather than the thing somebody works out from it.

  4. Silence is written down as silence

     Where the records do not say what the filing came back as, that is raised as its own finding. Reading the clearance status as the filing status would assert a filing nobody declared, so it is never done — an entry can sit on a hold with its manifest accepted.

  5. The delay is counted once

     Demurrage running on that entry is already counted by the held-entry item above, so here it travels as what is at stake rather than as a second charge. One delay counted twice is the commonest way a total gets inflated, and there is a test that fails if the two ever merge.

  6. A named person decides

     What leaves is the document a broker or a port authority is shown, and it leaves when somebody approves it. Who approved it, when, and what they changed stays with it.

  Equipment limits · A machine drifting towards the limit its own feed states

  1. A limit nobody stated is not a limit

     The figure a reading is compared against is read out of the feed itself — an alarm temperature, a trip point, a replace-below level. Where the feed states only what the machine ran at when it was healthy, the drift is reported and nothing is projected against it, because a healthy baseline is not a point at which anything fails.

  2. The readings are compared in order

     The first reading in the window, the latest one, how many were comparable, and how far the latest sits from the stated limit. Each figure carries the reading it came from, so your engineer checks the arithmetic against the feed instead of taking it on trust.

  3. The line drawn through them is arithmetic, not a forecast

     Where the readings support it, a straight line through the first and the last says when it would reach the stated limit at that rate. That is a description of two readings, and every document of this kind says so on its face.

  4. No probability, no confidence, no remaining life

     None of the three is on the document, and that is structural rather than a matter of wording: there is no field for them to go in. A failure score fitted to a handful of readings reads as a measurement and is not one. A number a planner can recompute is worth more than a confident one they cannot.

  5. A named person schedules the work

     The item reaches maintenance with the machine, the channel, the stated limit and the readings behind it. Approving is what raises the job, and who approved it, when, and what they changed stays on the record.

  See the fit →

• Insurance

  A review threshold raised to clear a backlog, meant to be temporary, never put back and never decided either way. Reserve movements checked by sample because the stream is too long to read.

  Claims operationsCompliance and riskInternal audit

  Open

  How it is read today

  A review threshold raised to clear a backlog, with the policy document still carrying the old figure and nobody deciding either way.

  How Runink reads it

  The figure that sets a second review is read out of the policy wording itself and compared against what the workflow applied, so a file reviewed on the wrong threshold comes back named rather than sampled.

  Where it shows up in your operating numbers

  • Reserves and recoveries signed off on a sample

    Where yours is

    The share of files that took a second review, against the figure your policy wording states.

  1. when authority is delegated

     Delegated underwriting

     You still answer for what is decided under the agreement, and the reports the agent sends back have to be read against it.

  2. when a loss is notified

     Cargo loss survey

     What was lost, what it was carried under and what the cover declares it to be worth sit in the claim file, the shipment record and the policy, and somebody assembles the three by hand.

     Clause and deadline review

     A paragraph settles the question and a date decides whether it is still worth asking, and both take an afternoon to find.

  3. while the file is open

     Second review

     The workflow applies one figure while the policy document still carries another, and which of the two governs is settled the first time somebody is asked.

  4. at period end

     Reserving and recovery

     Treaty terms set what you can recover, and whether a loss was presented under the right ones is a reading of the treaty against the file.

  Policy drift · A second-review threshold, from raised in the workflow to decided on the record

  1. The policy wording is read

     The clause that sets the value at which a claim needs a second review is read out of the policy document. It comes back stated in plain English, with the document it was read from named beside it.

  2. The workflow's own rule is read

     Separately, the claims system is read for the threshold it actually applies to a file today. It is read where it sits: the connection to your claims data reads the records and leaves them as they are.

  3. The difference is named as drift

     Every rule lands in one of four states. Aligned: the policy says it and the systems do it. Drift: the systems do something adjacent. Shadow: logic is running that no policy describes. Missing: the policy describes a control nothing performs. A threshold raised in the workflow and left out of the document comes back as drift. Read that as a reconnaissance: the finding names the policy document and the implementation it was read out of, and carries a confidence, so a compliance officer is checking a specific claim against two named sources.

  4. The finding reaches one queue

     It carries the observation, the rule it invoked, the records it cited, a severity and one specific proposed action. This one turns on risk appetite — whether the raised threshold is the one you now want — so it waits, with the ambiguity named and the write-up already done.

  5. A named person decides

     Someone approves, edits or rejects the drafted action, and that decision is recorded as an event carrying who made it. Whether the wording is updated to the new figure or the workflow is put back to the old one, the observation, the rule, the records and the approval are kept as the work is done. When an auditor asks what this control did, answering is retrieval.

  Cargo underwriting · A loss file assembled for the underwriter who has to decide

  1. The file is built from the records, not from the account of them

     What the records say was short, what they say was damaged, which shipment it travelled on, and what the cover declares it to be worth. Every figure is cited at the moment it is read, so an underwriter opens one document instead of four systems.

  2. The deductible is stated and never subtracted

     Taking it off the loss produces a recoverable figure, and that arithmetic only means something once somebody has decided the policy responds. That decision belongs to the underwriter, so the figure is left where they can make it.

  3. The conditions the cover sets are audited on their own

     A temperature band, a packing standard, a security routing — each read against the records that either kept it or did not. The audit never reads the loss and the loss file never reads the audit. Putting the two in one paragraph composes a coverage defence, and composing one is an underwriter's act rather than software's.

  4. Could not look is not the same as no breach

     A condition the records say nothing about comes back as not evidenced, never as kept. A band written in one unit is not compared against a probe logging another, because converting invents precision the records never had. A claim declined on an assumed condition is paid for by the assured, who never learns why.

  5. A named person decides whether it responds

     Nothing here binds, settles or declines. The survey and the audit chain to the same shipment, arrive together, and wait for the person with authority over the file.

  Paralegal review · The clause that governs it, and the record it was held against

  1. The question is the ordinary one

     May they sub-contract this. Is the retention period we run the one we committed to. Somewhere in the agreement a paragraph settles it outright, and finding the paragraph is the whole cost.

  2. The passage comes back with the record beside it

     The clause is read out of the document and stated in plain English, with the document it came from named. The rule as it actually runs is read where it runs. The two arrive side by side, so the conversation starts at the difference rather than at the search.

  3. A date is computed by a named rule, and refuses to guess

     A notice period or a filing window is worked out from a date on the record by a rule that cites the authority it comes from, and it says which event it ran from — the day the goods arrived, or the day they should have. Where the record carries no usable date, no date is produced: the item says so and carries the warning instead.

  4. Checked and clean and could not check are different entries

     Most tools show both as a tick. Here the second is a state in its own right, with the reason it arrived written in a sentence — nothing came back, what came back could not be read, what came back was empty. It is the entry an audit is actually hunting for.

  5. It hands back a note, and the judgement stays yours

     What comes back is a next step in business language: draft this letter, raise this ticket, take this to the officer who owns the framework. The reading is the software's. Deciding what it means is the person's, and their name is on the record that says so.

  See the fit →

• Banking & Financial Services

  A break that grows inside the range you always clear, so no single month escalates and nobody reads the sequence. A supplier contract nobody has opened since signature.

  Compliance and riskInternal audit and control testingFinance

  Open

  How it is read today

  A movement that sits inside the range every month, so nothing escalates and nobody reads the sequence the months make.

  How Runink reads it

  Each break is read against the sequence its own months make rather than the range it sits inside, so a movement that clears every month stops disappearing into the aggregate.

  Where it shows up in your operating numbers

  • Breaks that clear inside the range you always clear

    Where yours is

    The age profile of open items, against how many months each one has been carried.

  1. when a payment destination changes

     Destination verification

     Whether the rule on a payment destination was enforced in the system or followed by a person has a habit of surfacing after the event rather than before it.

  2. after a contract is signed

     Supplier obligations

     The agreement carries obligations on service levels, sub-contracting, data handling and notification, and reading it back against the relationship you actually have is a comparison that gets made when something has already gone wrong.

  3. when the fee is charged

     Rate card check

     Tiers, thresholds and product terms make the fee a reconciliation between what the terms say and what was charged.

  Open items · A reconciliation break, from a run of clearings to a decision on the record

  1. The month clears as usual

     The movement sits inside the range that has been cleared before. It is cleared the way the month before it was cleared, and on its own it reads like that month.

  2. The sequence is read, not the month

     The comparison runs over the series rather than the latest figure. What stands out is the shape of a run of movements, each of which sits inside the range on its own.

  3. The item is raised with its series

     The item says the sequence is unusual against the history available, and cites the series it was read from. The months, the values and the range they sat inside travel with it, so whoever opens it starts with the evidence in front of them.

  4. A named person decides

     The item waits in one queue with the series it cites already attached. Approving it, editing it or rejecting it is that person's decision, and the cause is theirs to write: naming one takes somebody who knows what changed in the operation that month.

  5. The record answers the next request

     Who decided, when, what was cited and what was changed stay together, each entry hashed against the one before it, so a later change to the record shows. When the supervisor or the internal reviewer asks, the answer is read rather than reassembled.

  Supplier obligations · Service levels the agreement prices, read against what was delivered

  1. The obligations are read out of the agreement

     Service levels, sub-contracting, data handling, notification. Each comes back stated in plain English with the clause it was read from named, so what you signed up for is legible without opening the file.

  2. What the supplier delivered is read where it is recorded

     The performance records are read where they already sit, and set against the level the agreement states. The comparison runs item by item rather than over a sample, so a miss arrives as a named item instead of a share.

  3. A miss the contract already prices carries that price

     Where the agreement sets a credit for the breach, the figure is the agreement's own arithmetic over the misses that were confirmed. It is money already owed under a document both parties signed, not a claim invented on top of one.

  4. A named person decides what is asked for

     Whether the credit is claimed, waived or raised at the next review is a commercial decision, and it stays one. The item waits with the clause, the records and the arithmetic attached, and the approval keeps who decided and why.

  See the fit →

• Telecom

  A rating change that is right for the promotion and wrong for a legacy plan, too small to move an aggregate. A sweep that returns an error rate when operations needs the accounts by name.

  Revenue assuranceInterconnect and partner settlementFinance and procurement

  Open

  How it is read today

  A rating change right for the promotion and wrong for a legacy plan, too small to move an aggregate and too late to re-rate once it does.

  How Runink reads it

  Each account's rated output is read against that subscriber's own plan terms, record by record rather than as a monthly sweep over a sample.

  Where it shows up in your operating numbers

  • Rating errors that arrive as a rate, not as accounts

    Where yours is

    The error rate revenue assurance reports upward, and the sample size and month behind it.

  1. when usage is rated

     Revenue assurance

     Rating is where the plan terms meet the usage, and a change made for one product lands on every account the configuration touches.

  2. at period end

     Interconnect settlement

     Your traffic, the counterparty's record of the same traffic and the agreement that sets the rates are three sources, and the one difference that matters shows up at period end as an open item with an age on it.

  3. as sites are built

     Network rollout

     Approved spend, purchase orders, equipment received and sites carrying traffic sit side by side only when somebody assembles that view by hand, and a site that took delivery but was never turned up sits inside it unnoticed.

  Revenue assurance · A rating change wrong for one legacy plan, from the first wrongly rated call to an approved re-rate

  1. The rating is read against the plan

     Each account's rated output is read against that subscriber's own plan terms, and the comparison is per record rather than a monthly sweep over a sample. What comes back is the accounts by name, which is what a re-rate needs, rather than an error rate, which is what a report needs.

  2. The finding carries its evidence

     Before anything goes to a model, the finding is checked: complete enough to read, carrying evidence, with at least one piece of that evidence readable, about the account it names rather than something next to it, and dated recently enough to say something about now. Evidence that only writes the claim out a second time ends the matter there. Each check that fires states its own reason in a sentence a person reads.

  3. The rate is recomputed from counts

     A finding that claims a rate is settled by arithmetic on the raw counts, recomputed rather than accepted. A count divided by nothing comes back as unable to judge.

  4. A second credential forms the verdict

     The judging runs on a different credential from the submitting, and which credential a message carries is settled by the door it arrived at rather than by a field the sender fills in. A verdict of unable to judge is an answer in its own right: it arrives with its reason written next to it and goes to a person, exactly as a disagreement does.

  5. Revenue assurance approves the re-rate

     The item waits, with the account named, the plan terms it was read against, and the records it came from. Approving is what sends anything, and who approved it, when, and what they changed stays on the record. The remedy is a configuration correction and a re-rate, made while a re-rate still fixes it.

  Interconnect settlement · Two records of the same traffic that do not agree

  1. Both sides are read against the agreement

     Your record of the traffic, the counterparty's record of the same traffic, and the agreement that sets the rates. The reading happens while both sides still hold the detail rather than at the end of the cycle, when one of them no longer does.

  2. A disagreement is never averaged

     Two readings of the same traffic that differ come back as unable to judge, carrying both figures and where each was read. Splitting the difference produces a third figure neither party observed, and in a settlement argument that figure cannot be defended by either side.

  3. Unable to judge is an answer, with its reason attached

     No evidence, evidence that only writes the claim out a second time, evidence about a different account, evidence too old to say anything about now — each ends the matter there, states its own reason in a sentence a person reads, and goes to a person.

  4. A named person takes it to the counterparty

     The item carries the period, both records and the rate the agreement sets. Approving is what sends it, and what was cited and what was changed stay on the record for the next cycle to start from.

  See the fit →

• Marketing

  The audit tool knows the site is slow. The content tool does not, so it keeps writing for a page nobody stays on. Every campaign starts again from a blank page.

  The marketing leadIT and information securitySales

  Open

  How it is read today

  The audit tool knows the site is slow; the tool that writes does not, so it keeps writing for a page nobody stays on. This one is Runink PULSE, not FACE.

  How Runink reads it

  Your site and the channels you publish on are read first, so the next brief starts from where you actually stand instead of from a blank page.

  Where it shows up in your operating numbers

  • Work that starts again from a blank page

    Where yours is

    How long a brief takes to become something published, and how much of last quarter's work the next one reused.

  1. before anything is written

     Deciding what to say

     What to write next depends on what the site is already doing, and those two answers live in different tools.

  2. between brief and publication

     Getting it out

     Brief, draft, review, schedule — each step waits for the one before it, so whether you can answer a competitor's announcement at all is decided by your own turnaround.

  3. when a lead arrives

     Following up

     The customer system knows a lead went quiet in week three; the scheduler does not.

  Site audit · A page nobody stays on, from the audit that finds it to an approved draft

  1. The audit reads your site

     You bring your website and the channels you publish on. Reading them and telling you where you stand is the first thing Runink PULSE does. What it finds comes back ranked, and it is applied from the same screen.

  2. One diagnosis feeds every channel

     That same diagnosis feeds the channel analysis, the content plan, the schedule and every draft. What goes out carries one argument rather than four versions of it.

  3. The brief becomes a draft

     The brief goes in and a draft comes back. From there it sits in a queue where you can see it, instead of going quiet between one step and the next.

  4. Each piece carries one status

     Draft, waiting for review, approved, rejected, published, archived. Those are the statuses PULSE keeps, so what is waiting on you and what actually went out are both visible.

  5. A named person approves it

     Every draft — post, whitepaper, cold email, call script — lands in a review queue with an approve and a reject. Approving is a step a named person takes rather than a formality the system performs for them.

  Lead follow-up · A lead that went quiet in week three

  1. The customer record is what says it went quiet

     The lead, the stage it reached and the day it last moved are read from the customer-record system the team already works in, rather than from a second list somebody keeps beside it.

  2. The company is researched before anything is written

     Runink PULSE reads what is public about that company first, so what it drafts starts from what it found rather than from a template with a name dropped into it.

  3. The follow-up comes back written for that one company

     A cold email, a call script and a direct message per company, and the leads synchronise back to the customer-record system, so sales keeps working where it already works.

  4. A named person sends it

     Every draft lands in a review queue with an approve and a reject, and carries one visible status while it waits. Approving is a step somebody takes rather than a formality the system performs for them.

  See the fit →