Preparing text

Can I use a text AI checker on code, tables or bullet points?

The short answer

AiChecker examines connected prose. Do not read a text score as evidence of who made a code block, a spreadsheet or a keyword list. Each of those needs a review that fits the material.

A report can need several kinds of review

Take a technical report containing an explanation, a function and a results table. The explanation is a writing sample. For the function, inspect the code. For the table, go back to the observations or calculations that produced the figures.

Keep a complete explanation

Pick a whole explanatory passage and note which blocks you left out. Do not stitch identifiers, numbers and loose bullets into a made-up paragraph just to fit the input.

A slide with only a few labels may give you too little prose to review. Speaker notes, or a conversation with the author about the argument, are more useful than extra text added to pad those labels.

Follow the work back to its source

Run the code, look through it, and trace the table inputs. Ask the author how the method works. RAID tests detection across writing domains and model settings; it does not establish that every format pasted into a text box is a valid writing sample.

Source: Dugan et al. (ACL 2024): the RAID evaluation benchmark

Put the guidance into practice

Choose the passage you want to review and keep its context alongside the result.

Check your textReview technical text and datasets