ListFind test conditions I am considering

        &lt;input type="checkbox" name="arConfig[3]" value="payout"  
            &lt;cfif ListFind(attributes.config[3], "payout") NEQ 0&gt;checked="checked"&lt;/cfif&gt;  /&gt; Payout&lt;br /&gt;
        &lt;input type="checkbox" name="arConfig[3]" value="points"  
            &lt;cfif ListFind(attributes.config[3], "points") NEQ 0&gt;checked="checked"&lt;/cfif&gt;  /&gt; Points&lt;br /&gt;
        &lt;input type="checkbox" name="arConfig[3]" value="quarter" 
            &lt;cfif ListFind(attributes.config[3], "quarter") NEQ 0&gt;checked="checked"&lt;/cfif&gt;  /&gt; Quarter&lt;br /&gt;


Vs

        &lt;input type="checkbox" name="arConfig[3]" value="payout"  
             &lt;cfif ListFind(attributes.config[3], "payout") GT 0&gt;checked="checked"&lt;/cfif&gt;  /&gt; Payout&lt;br /&gt;
        &lt;input type="checkbox" name="arConfig[3]" value="points"  
             &lt;cfif ListFind(attributes.config[3], "points") GT 0&gt;checked="checked"&lt;/cfif&gt;  /&gt; Points&lt;br /&gt;
        &lt;input type="checkbox" name="arConfig[3]" value="quarter" 
             &lt;cfif ListFind(attributes.config[3], "quarter") GT 0&gt;checked="checked"&lt;/cfif&gt;  /&gt; Quarter&lt;br /&gt;


Which is clearer the NEQ 0 or the GT 0 ?
You don't care what the numeric value here is, so don't test for it. You want a boolean, and I think the listFind() call is semantically boolean itself without the comparison.

So: "neither". Do this instead:

&lt;cfif ListFind(attributes.config[3], "payout")&gt;


Either/any option looks pretty cluttered as it is, so given yer repeating the same string except for the difference of the value, I'd put that lot in a loop over the values too, maybe?