Symptom
After an import, the report lists lines with a note beside each. The script opened and reads correctly, but some lines are formatted as action when they should be something else.
Causes and what to do
"Could not tell whether this is a character or a transition." An all-caps line with no dialogue after it and no colon. Put the cursor on it and press CtrlAlt3 or CtrlAlt6; if it is a shout in action, leave it.
"Scene heading without a standard prefix." A heading that does not start with INT., EXT., or one of the recognized variants. Press CtrlAlt1 on the line, or add the prefix.
"Parenthetical outside dialogue." A (beat) on its own line with no character cue above it — usually a Final Draft file with an empty cue. Give it the cue, or fold the direction into the action.
"Unsupported element." Final Draft elements Plot has no equivalent for — a page-break marker inside a scene, a general or title element mid-script — arrive as action carrying their text. Keep, edit, or delete.
"Text was in the title page." Final Draft stores the title page separately; its fields become the project's title page in the export dialog, and anything that did not fit a field is reported here.
If a whole script arrived as action
The file was probably plain text with no Fountain cues — every line action, every name lowercase. Fountain needs scene headings in caps with a prefix and character names in caps on their own line. Fix the source file, or import and press Tab through the elements in Plot.
When to contact support
If a file that Final Draft opens will not import at all, or the report lists hundreds of lines for a script that is formatted normally. Attach the file; see Contact support.