How to Keep an Arbitrage Journal and Track Useful KPIs

How to Keep an Arbitrage Journal and Track Useful KPIs

arbitrage journal KPIs is a focused control used to decide whether visible market data is genuinely comparable for the same asset, time window, and intended size. Unlike a general arbitrage introduction, this guide concentrates on the relationship among Fill Rate, Realised Slippage, and Cycle Time.

The practical question is not whether arbitrage journal KPIs can be displayed, but whether it remains consistent after Fill Rate, Realised Slippage, Cycle Time, Transfer Success Rate, and Expected-vs-Realised Variance are aligned. The worked case in this article starts with only successful transactions logged and ends with journal-corrected; the change is produced by validation, not by a prediction of future return.

What is arbitrage journal KPIs?

This concept is a repeatable governance method for recording assumptions, realised outcomes, and deviations.

The purpose of this article is not to encourage a transaction. It explains which evidence is required for arbitrage journal KPIs and when a displayed result should be treated as unreliable. In particular, Transfer Success Rate and Expected-vs-Realised Variance can expose constraints that are not visible in a headline percentage.

Key indicators to monitor

Fill Rate

Fill Rate is input number 1 in an arbitrage journal KPIs review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Realised Slippage

Realised Slippage is input number 2 in an arbitrage journal KPIs review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Cycle Time

Cycle Time is input number 3 in an arbitrage journal KPIs review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Transfer Success Rate

Transfer Success Rate is input number 4 in an arbitrage journal KPIs review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Expected-vs-Realised Variance

Expected-vs-Realised Variance is input number 5 in an arbitrage journal KPIs review. If it is not measured at the same timestamp and intended size, the comparison can become misleading.

Record the raw value, source, update time, and validation state, then compare it with the venue’s official interface or an independent second source.

Technical deep dive: measurement boundaries and audit trail

A robust arbitrage journal KPIs model should expose its assumptions instead of hiding them inside one score. The following deep dive separates measurement, source quality, size sensitivity, operational limits, and auditability. Each block is deliberately tied to a different input so the model can be reviewed and challenged.

Audit trail for Fill Rate

A reviewer should be able to reconstruct Fill Rate from stored inputs. Save the source, timestamp, planned size, formula version, rounding rule, account tier, and final classification. Compare the archived value with Realised Slippage after the event. This turns the model from an opaque signal into a process that can be tested and improved.

Measurement boundary for Realised Slippage

Realised Slippage should first be defined with a clear numerator, denominator, unit, venue, and timestamp. A value without those boundaries cannot be compared reliably with Cycle Time. Record whether the observation is a quote, a completed trade, an order-book aggregate, a venue rule, or an externally calculated field. This prevents a familiar label from hiding a different definition.

Source integrity behind Cycle Time

The usefulness of Cycle Time depends on where it came from and how it was transformed. Compare source time with receive time, preserve the raw response where possible, and document every normalisation step. If Transfer Success Rate comes from another endpoint or update frequency, the model should flag that asymmetry rather than silently combining both values.

Size sensitivity of Transfer Success Rate

Transfer Success Rate must be recomputed at more than one intended size. A value that remains stable at 500 USDT may change materially at 5,000 or 50,000 USDT because depth, minimums, rounding, or fixed costs enter the calculation. Plotting Transfer Success Rate against Expected-vs-Realised Variance across several sizes exposes the point at which the route stops behaving like the headline row.

Operational threshold for Expected-vs-Realised Variance

An operational rule should state when Expected-vs-Realised Variance is acceptable, when it requires manual review, and when it is a hard failure. The threshold should not be chosen only from historical success. It should also reflect data uncertainty, venue rules, and the effect of Fill Rate under an adverse case. Hard failures should override an attractive percentage.

Interpreting the formula without false precision

The working formula for this topic is Variance = realised outcome - expected outcome at decision time. It is a model, not a law of the market. Inputs may have different update intervals and some costs are known only after execution. Report a sensible range or confidence band when the data does not support many decimal places. A precise-looking result built on uncertain inputs is still uncertain.

Decision boundaries and failure modes

• A control for Survivorship Bias should identify who or what confirms recovery. A green status, a single successful request, or one completed transaction may not prove that normal operation has returned.
• Review Missing Failed Attempts after the event as well as before it. The difference between the predicted impact and the realised impact is useful calibration data for future arbitrage journal KPIs assessments.
• Inconsistent Definitions is not merely a theoretical warning. Define a detection signal, a review action, and a hard-stop condition for it. Link the condition to Cycle Time so the reason for rejecting or downgrading a route is visible.
• When Manual Entry Error appears, compare Transfer Success Rate with Fill Rate before accepting the screen result. If both inputs deteriorate together, a historical average is unlikely to be a sufficient safeguard.
• Treat Optimising the Wrong KPI as a scenario variable rather than a footnote. Recalculate the model with a conservative assumption and record how much of the buffer is consumed.

A compact decision record

For the hypothetical case—60 reviewed routes, initially only successful transactions logged, then a biased success rate until failed attempts are added, and finally classified as journal-corrected—store four separate statements: what was observed, what was calculated, what was independently verified, and why the final classification was chosen. Keeping those statements separate prevents later analysis from confusing model output with venue-confirmed facts.

Worked example: turning a screen signal into a decision

Consider a hypothetical route of 60 reviewed routes. The first screen shows only successful transactions logged. When Fill Rate and Realised Slippage are checked together, the picture changes to a biased success rate until failed attempts are added. After Cycle Time, Transfer Success Rate, and Expected-vs-Realised Variance are added, the route is classified as journal-corrected.

Variance = realised outcome - expected outcome at decision time

The example shows why a headline value cannot make the decision by itself. An arbitrage journal KPIs review quantifies the gap between a visible signal and operationally comparable conditions; account and venue rules can produce different outcomes for different users.

A step-by-step analysis process

Use the following workflow as a reproducible research sequence. A step can stop the review; later steps should not be used to rescue a route that has already failed a hard technical condition.

1. Define the route and intended size

Define the asset identity, venue pair, intended size, and unit of account. State exactly what arbitrage journal KPIs is expected to answer and what it does not answer.

2. Check data time and source

Collect Fill Rate and Realised Slippage from named sources. Preserve source timestamps and check whether both observations describe the same market moment.

3. Read the two most important indicators together

Recalculate Cycle Time from raw inputs rather than copying a screen value. Apply the venue’s precision, quantity, and status rules before comparing results.

4. Add fees and execution effects

Change the intended size and observe Transfer Success Rate. If the classification changes sharply, report the break point instead of one universal percentage.

5. Run a stress test

Treat Expected-vs-Realised Variance as an operational input. Define an acceptable state, a review state, and a hard-fail state before looking at the most attractive row.

6. Perform the final check on official exchange screens

Run the formula with the base case, a modest adverse case, and a combined stress case. Do not assume that price, depth, timing, and cost deteriorate independently.

7. Record the result and update assumptions

Store the decision-time inputs and compare them with the later realised or confirmed state. Use the difference to recalibrate thresholds, not to rewrite the original record.

Main risks and weak assumptions

The risk map below is specific to arbitrage journal KPIs. Each item can alter the meaning of the data even when the headline price difference remains unchanged.

Survivorship Bias

Survivorship Bias can create false confidence in an arbitrage journal KPIs review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Survivorship Bias to a measurable test involving Fill Rate or Realised Slippage; define who confirms the result and what condition blocks further review.

Missing Failed Attempts

Missing Failed Attempts can create false confidence in an arbitrage journal KPIs review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Missing Failed Attempts to a measurable test involving Realised Slippage or Cycle Time; define who confirms the result and what condition blocks further review.

Inconsistent Definitions

Inconsistent Definitions can create false confidence in an arbitrage journal KPIs review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Inconsistent Definitions to a measurable test involving Cycle Time or Transfer Success Rate; define who confirms the result and what condition blocks further review.

Manual Entry Error

Manual Entry Error can create false confidence in an arbitrage journal KPIs review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Manual Entry Error to a measurable test involving Transfer Success Rate or Expected-vs-Realised Variance; define who confirms the result and what condition blocks further review.

Optimising the Wrong KPI

Optimising the Wrong KPI can create false confidence in an arbitrage journal KPIs review. If it is not measured, the data comparison may break, an order may be rejected, or realised results may diverge materially from the initial estimate.

Control: connect Optimising the Wrong KPI to a measurable test involving Expected-vs-Realised Variance or Fill Rate; define who confirms the result and what condition blocks further review.

How Exarbi supports this analysis

Showing data status, risk level, transfer readiness, and fee impact alongside price differences helps separate an arbitrage journal KPIs review from a raw list of percentages.

Exarbi is an independent market-data and decision-support platform. It does not recommend a cryptoasset, execute orders, hold customer funds, or request exchange API keys. A displayed row is a research starting point, not a personal recommendation or an assurance of execution.

Pre-trade checklist

• Was Fill Rate validated at the same timestamp?
• Was Realised Slippage recalculated for the intended size?
• Does Cycle Time match the venue’s actual rule?
• Was an adverse case applied to Transfer Success Rate?
• Were Expected-vs-Realised Variance and the final assumptions recorded?

Frequently asked questions

Why is arbitrage journal KPIs not enough on its own?

Because price, liquidity, fees, transfer conditions, and account restrictions can change together. It is an important filter, not a substitute for final venue verification.

When should arbitrage journal KPIs be checked again?

During initial screening, immediately before any action, and whenever the underlying conditions change.

Which data should be recorded?

Record the raw value, source, timestamp, intended size, formula, account rule, and resulting classification.

Conclusion: make decisions from the full picture, not one metric

arbitrage journal KPIs supports more disciplined interpretation of visible data; it does not guarantee profitability or executability.

Review how Exarbi presents price differences, data condition, transfer-readiness signals, and risk indicators. Do not treat the interface as an instruction to enter a transaction.

Risk warning: Cryptoassets are high risk. You could lose all the money you invest. This material is educational and does not constitute investment, tax, or legal advice. Verify venue terms, fees, networks, account restrictions, and the lawful position in your jurisdiction.

======================================================================