About the humanise.ai Forum community
The humanise.ai Forum is a question and answer community for people who write with AI tools at university and at work. Someone whose lecturer has asked for an AI declaration and who is not sure what to put in it. Someone whose draft reads like every other chatbot draft. Someone who has been told that a detector flagged their essay and who needs to know what happens next. You ask a specific question, and you get a specific answer that names the policy, the tool and the step.
It sits alongside humaniseai.ai, which carries the free AI humaniser, the guides and the articles on AI writing and detection. The main site explains the general case. The forum is where your own situation gets looked at.
Who runs it
The forum is run by the humanise.ai editorial team and owned by humanise.ai. It is not an independent project and it is not run by volunteers: the people who answer are the same editors who write and check the articles on the main site. The team is based in the UK and the site carries the Made in the UK mark. We say this plainly so that nobody has to guess who stands behind the answers.
Who answers
Two editors answer and moderate.
- Harriet Pell, forum editor. Harriet works from Manchester and covers voice, tone and editing. She answers questions on turning an AI draft into writing that sounds like you, on British spelling and register, and on workplace writing.
- Bronwyn Ashby, detection and policy editor. Bronwyn works from Melbourne and covers AI detectors, academic integrity processes and policies. She answers questions on flags, appeals and disclosure, for readers in the UK, Australia and New Zealand.
Members can answer too, and good member answers are welcome. Editors check answers in the areas above, and say so when a rule differs between institutions or when we cannot verify something.
What we cover
The forum has twelve sections. Eleven are for questions and one is for conversation.
- AI at university and college. What your module allows and how to declare AI help.
- Detector flags and appeals. How scores are read and how to show your drafting history.
- Voice, tone and style. Keeping one voice across drafts.
- AI at work and in the office. Emails, reports and applications without breaking policy.
- Prompting and first drafts. Briefs, outlines and checking every claim.
- Editing and humanising drafts. Structural edits, line edits and humaniser tools.
- Referencing and sources. Checking that suggested references exist.
- English as an additional language. Writing in a second language and detector bias.
- Policies and disclosure. Reading institutional and employer policies.
- Humanisers and detectors compared. What tools do and what independent tests found.
- Dissertations and long reports. Planning and supervisors' rules.
- Common room and introductions. An open section for conversation.
How answers handle sources
An answer that depends on a rule should point to the rule. When we cite a university policy, a vendor's documentation or a published study, we link to the original page and say when we last read it. We label a vendor's own claim as the vendor's claim. We do not cite anonymous screenshots or other forum posts as evidence for a figure. If we could not open a source, or it does not say what a summary claims, we leave the claim out. The full approach is on the main site in the editorial standards.
What we will not do
We will not help anyone evade a detector, and we do not promise that any tool will beat one. We will not write assessed work for anyone, and we do not accept requests that amount to contract cheating. Detectors are probabilistic and can be wrong, so we help people understand a score and respond to it honestly. The rules are set out in the community guidelines.
Sign in and privacy
Members sign in with an emailed link. There are no passwords to set or lose. The privacy policy explains what we collect and why.
Corrections and contact
If an answer is wrong, out of date or unclear, tell us and we will check it against the source and correct it, with a note when the meaning changes. The ways to reach us, including the corrections process, are on the contact page. To try the free humaniser itself, go to humaniseai.ai.
Who answers here
Harriet Pell
Forum editor, voice and editing
Harriet edits the humanise.ai forum from Manchester. She writes the answers on voice, tone and editing AI drafts, checks university and employer guidance at the source, and says plainly when a rule differs between institutions.
Bronwyn Ashby
Detection and policy editor
Bronwyn covers AI detectors, academic integrity processes and workplace AI policy from Melbourne. She reads vendor documentation and published university policies, and writes the answers on flags, appeals and disclosure in Australia and the UK.