Locking thresholds before the print and publishing the one you couldn't grade is the part I rarely see. A parallel check we ran on options-implied moves: last week's five reports (NFLX, NEE, IBM, LRCX, TSLA) each had a stored at-the-money straddle range, and four of the five finished inside it, with LRCX at -11.8% the miss. The caveat we keep stating is that for some records we can't prove the capture came before the release, so we label 'recorded before' and 'reconstructed after' separately instead of counting both. Did you decide in advance how to handle a guidance change on the morning of the report, like your Meta revenue line, or was that a one-off call? (Disclosure: I work on an options-data app; no link here.)
Fair question. The Meta adjustment exposed a gap in our process, which we’ve since addressed. We now verify the latest company guidance when we publish our thresholds. Once published, those numbers stand, even if guidance subsequently changes. Any correction before earnings must be disclosed, as we did with Meta.
Our exposure is looking foolish. Yours could be considerably more expensive.
Thanks for reading and for the thoughtful comment.
Thanks, that's a clear answer. Locking the number at publication and disclosing any pre-earnings correction is the cleanest rule I've seen. One follow-up: do you stamp the guidance source and the check time next to each threshold in the post, so a reader can tell which version of guidance it was built on?
Partly. We check for new filings and earnings-call transcripts every six hours, so thresholds are built on guidance that was current when the scorecard locks. Each scorecard is locked before the event, and where the company gave guidance we show the guided range and the company's own wording next to our thresholds, then grade against the filed results. Labeling every threshold with the exact source and check time, and noting guidance changes at grading, are on our list, but so are other requests. Thanks for the comment and the trigger to check out SIGNUMHQ. Very cool.
Locking thresholds before the print and publishing the one you couldn't grade is the part I rarely see. A parallel check we ran on options-implied moves: last week's five reports (NFLX, NEE, IBM, LRCX, TSLA) each had a stored at-the-money straddle range, and four of the five finished inside it, with LRCX at -11.8% the miss. The caveat we keep stating is that for some records we can't prove the capture came before the release, so we label 'recorded before' and 'reconstructed after' separately instead of counting both. Did you decide in advance how to handle a guidance change on the morning of the report, like your Meta revenue line, or was that a one-off call? (Disclosure: I work on an options-data app; no link here.)
Fair question. The Meta adjustment exposed a gap in our process, which we’ve since addressed. We now verify the latest company guidance when we publish our thresholds. Once published, those numbers stand, even if guidance subsequently changes. Any correction before earnings must be disclosed, as we did with Meta.
Our exposure is looking foolish. Yours could be considerably more expensive.
Thanks for reading and for the thoughtful comment.
Thanks, that's a clear answer. Locking the number at publication and disclosing any pre-earnings correction is the cleanest rule I've seen. One follow-up: do you stamp the guidance source and the check time next to each threshold in the post, so a reader can tell which version of guidance it was built on?
Partly. We check for new filings and earnings-call transcripts every six hours, so thresholds are built on guidance that was current when the scorecard locks. Each scorecard is locked before the event, and where the company gave guidance we show the guided range and the company's own wording next to our thresholds, then grade against the filed results. Labeling every threshold with the exact source and check time, and noting guidance changes at grading, are on our list, but so are other requests. Thanks for the comment and the trigger to check out SIGNUMHQ. Very cool.