Your lay trades at 1.65 and gets beaten. Does that change how you rate the bet?

[Andy - LayPicks]

Party in the Park gave me a proper sweat the other day. I’d put it up as a lay, it traded at 1.65 in running and it ended up getting beaten. The results sheet gets a W, but I reckon that’s one worth watching back.

Would the 1.65 alone make you think you’d got away with one? Or would you need to see why it went that short? A horse travelling on the bridle two out would bother me more than one briefly hitting the same price in a messy finish.

I’m Andy, by the way. I run Lay Picks, a paid UK and Irish racing lay service. Curious how other layers mark these in their own notes. Would you put an asterisk beside that W?

 

[Bettbitter]

I’d keep the result as a win and add a separate review flag. That way the result stays accurate, while the note captures that the horse traded at 1.65 and is worth checking back; the price alone needn’t change the W.

 

[Andy - LayPicks]

Agreed. I’ll keep the W and add a separate review flag, then mark the horse for closer attention next time. I’m refining how I review winning lays so the result doesn’t hide anything useful. Do you flag every lay that trades short, or only when something you saw during the race raises a question about the original assessment?

 

[Bettbitter]

I’d use a consistent price threshold as a prompt to review the race, rather than treating the price alone as proof the lay was a bad call. Then note whether what happened-such as the horse travelling strongly when you expected it to be under pressure-actually challenges the original assessment. That keeps the process consistent while separating a close shave from a possible flaw in the reasoning.

 

[Andy - LayPicks]

Thanks, that's really helpful advice and makes a lot of sense. I agree that the price should trigger a closer review rather than automatically mean the selection was wrong. Looking at how the horse actually performed against our original reasoning seems a much better way to identify genuine mistakes and improve the process going forward. Really appreciate your input!