When "spread" does not identify the spread
When a broker writes "offer at +85 basis" in chat, a parser must decide whether 85 basis points refers to a G-spread, an I-spread, a Z-spread, an OAS, or a different basis altogether. A human trader may infer the intended reference from the bond, the desk convention, and the surrounding conversation. A structured record cannot safely rely on that inference unless the relevant context is captured.
Dealer communication is full of shorthand because the participants usually share a working context. "+85," "15 over," "basis unchanged," and "five through" can be sufficient for a trader who knows the issuer, maturity, benchmark, and side of the market. They are incomplete as standalone data fields.
That distinction matters when fixed-income desks consolidate quotes from Bloomberg Messenger, ICE Chat, Symphony, or Refinitiv Eikon Messenger. The task is not only to extract a number. It is to preserve what the number measures, what it is measured against, and how the dealer expressed the quote.
Spread has several precise meanings
In fixed-income markets, "spread" is not one universal metric.
- G-spread: the spread of a bond's yield over a government benchmark yield, typically selected by maturity or interpolation convention.
- I-spread: the spread over a swap rate at a corresponding maturity.
- Z-spread: the constant spread added to the benchmark zero curve to match the bond's present value, generally assuming the relevant cash flows and discounting framework.
- OAS: the option-adjusted spread, which accounts for the value of embedded optionality, such as a call feature, when comparing the bond with a benchmark curve.
These measures are not interchangeable. A bond can show a different G-spread and I-spread because the government curve and swap curve are different. Z-spread and OAS can also diverge materially for callable bonds, where the option changes the interpretation of the spread. The quoted number may be identical in form, such as "+85," while its economic meaning is different.
"Basis" is less controlled language. In dealer chat, it can mean the spread between two instruments, the difference between two yield curves, or a relative-value relationship that is obvious to the people in the conversation. It can also refer to a named market concept. The credit default swap, or CDS, basis is the difference between a CDS spread and a bond spread. ASW, or asset swap spread, describes the spread over swaps for a bond purchased at par. Those uses should not be collapsed into a generic field called spread.
An illustrative chat exchange
Illustrative broker chat: "ACME 2029 offer at +85 basis, 2mm."
That message contains an issuer label, a maturity reference, a side, a numerical level, and a size. It does not state whether "basis" means 85 basis points over the government benchmark, 85 over swaps, an ASW level, or a relative spread against another bond. If the bond is callable, OAS could be relevant, but the message does not say so. If the conversation concerns a bond and its CDS, "basis" may refer to the CDS basis instead.
The next messages may resolve the ambiguity:
Illustrative continuation: "Swap ref, not gov. 99.40 clean. Same offer versus 5y point."
Now the likely reference is the swap curve, and the comparison may involve an interpolated five-year point. But even here, an accurate structured record should distinguish what was explicitly stated from what was inferred. "Swap ref" supports an I-spread interpretation. "Same offer versus 5y point" may describe a relative-value comparison, not a replacement for the original spread field.
A parser that stores only spread = 85 has lost the central qualification. A better record might preserve:
- the quoted value and units, 85 basis points;
- the original term, "basis";
- the reference, swaps, if explicitly supplied later;
- the instrument, side, size, and maturity;
- the quote status, including whether it is firm, indicative, axes-related, or otherwise qualified;
- the message sequence linking the clarification to the initial quote.
The point is not to manufacture certainty. It is to retain enough evidence for a trader, reviewer, or downstream model to see where certainty ends.
What a structured quote needs to preserve
For spread and basis language, the minimum useful schema is usually wider than a price and a spread number. A desk may need separate fields for metric type, reference curve or instrument, value, unit, direction, and confidence or evidence status.
Metric type should distinguish G-spread, I-spread, Z-spread, OAS, ASW, CDS basis, and an unresolved or generic basis term. Reference data should identify the government benchmark, swap tenor or curve, zero curve, CDS contract, or comparison bond where available. Direction also matters. "Bid at +85" and "offer at +85" are not equivalent records, and "wider by 3" describes a movement rather than an absolute level.
The parser should also preserve qualifiers that affect interpretation:
- Instrument identity: issuer, coupon, maturity, currency, seniority, and, where relevant, call schedule.
- Benchmark selection: the named government bond, swap point, curve, or interpolation convention.
- Price context: clean or dirty price, yield, spread, or a relative-value expression.
- Trade status: inquiry, indication, axes, offer, bid, done, or a correction.
- Conversation context: the parent message, follow-up clarification, and any later amendment.
This is where chat structuring differs from ordinary text extraction. The number is often the easiest token to find. The difficult work is connecting it to the right instrument and preserving the dealer's reference convention without silently normalizing away ambiguity.
Relative value makes "basis" especially context-dependent
Basis language often appears when a trader is comparing instruments rather than quoting one bond against a standard curve. A dealer might write "two points through the 2030" or "basis is 12 wider versus the new issue." Those messages describe a relationship. They may not provide an absolute yield spread for either security.
The CDS basis is a useful example. If a bond trades at a 140 basis point spread and the corresponding CDS trades at 125, the CDS basis may be described as 15 basis points, depending on the desk's sign convention. Without storing both legs and the sign convention, a record containing only "basis 15" is difficult to interpret. The same issue arises when a desk compares an existing issue with a new issue, or one maturity point with another.
ASW introduces a different kind of precision. "ASW at 72" is not simply an unspecified spread. It signals an asset swap calculation, generally for a bond purchased at par, with the spread expressed over swaps. The calculation may depend on price, coupon, cash-flow treatment, and conventions. A parser should identify the ASW label when present instead of treating it as an ordinary I-spread.
The practical boundary is this: spread parsing can be useful even when the message is incomplete, but the output should retain unresolved status rather than present an inferred metric as fact. The question is not whether a numerical level can be extracted. It is whether the intended spread type and comparison basis remain visible in the record.
Where parsing remains uncertain
Not every exchange can be resolved cleanly. Dealers may use local abbreviations, omit the benchmark because it is understood, or switch from an outright quote to a relative-value discussion without announcing the change. A message such as "+85 still" may refer to the last agreed convention, while "basis back" may describe a move rather than a current level.
There are also cases where the surrounding context conflicts. One participant may use "spread" for an I-spread while another refers to OAS for the same callable bond. A broker may repeat a level from a prior conversation after the instrument has changed. A parser that forces every message into a single normalized metric can create false precision.
For that reason, our work at TwoWay focuses on structuring the conversation as well as extracting the quote. In an early-access pilot, the useful output is not a polished number detached from its source. It is a linked record that shows the quote, the relevant instrument, the stated reference, the conversation sequence, and any unresolved ambiguity. That gives a fixed-income desk a better basis for review and for comparing signals across channels.
For practitioners, the operational rule is straightforward: preserve the dealer's original wording alongside the normalized field. "+85 basis," "+85 I-spread," "ASW 72," and "CDS basis 15" should not become the same record. The reference, metric label, sign convention, and clarifying messages are part of the quote itself, not metadata to discard after the number has been extracted.