About this tool
Record which AI tools helped with which parts of an assignment and export a clean usage log for submission.
The AI Usage Log for Assignments records, entry by entry, which AI tools helped with which parts of a submission — the section of the work, the tool, how the output was used, what was asked and when — and exports it as a clean Markdown or plain-text declaration. Its fields follow what university academic-integrity policies and UNESCO's 2023 guidance on generative AI in education ask students to declare when AI use is permitted. It is built for students and teaching staff who need a consistent, honest record attached to submissions.
Open AI Usage Log for Assignments on AltFTool — it loads instantly in your browser.
Provide your input — an image, text, or data.
Let the tool analyze or generate the result.
Review, refine, and reuse the output wherever you need it.
Captures the five things integrity policies ask for: which part, which tool, how it was used, what was asked, and when.
From brainstorming to verbatim quoted output, so the log reflects the real level of reliance.
Produces Markdown or plain text with a built-in declaration sentence, ready to paste into an appendix.
If your institution or unit permits AI use, almost all of them require a declaration of how it was used; if AI use is prohibited for the unit, a declaration does not make it acceptable. Check the assignment brief or unit guide first — policies differ per unit, not just per university — and ask the coordinator when unsure.
Per use: the part of the work the AI touched, the tool's name, how the output was used (brainstorming, editing, drafting, and so on), a short summary of the prompt, and the date. This is the field set common to university declaration templates and UNESCO's guidance on transparent generative-AI use in education.
It depends on the unit's policy. Many institutions exempt basic spelling and grammar checkers but require declaration once a tool rewrites sentences or generates text — Grammarly's generative rewrite features usually cross that line. Logging it costs one line and is never wrong; omitting it can be an integrity breach where the policy requires it.
Only if the unit policy allows it, and then it must be treated like any other source: quoted or clearly marked and cited, not silently pasted. This log has a dedicated 'output used verbatim (quoted and cited)' mode so that the heaviest form of reliance is declared explicitly.