Quality-check freelance drafts before an editor reads them
Every weekday morning, overnight writer submissions get checked for AI writing and copied text, so only the questionable ones reach your editor flagged.
Every weekday at 7am, quality-check the drafts my freelance writers submitted overnight, before an editor reads them or I approve an invoice.
Start with Google Drive "List Files" to find the documents added to my "Submitted drafts" folder since the last run. Use Drive query syntax scoped to that folder ID with a created time filter set to the previous run. On Monday, look back across the whole weekend so anything submitted from Friday evening onward is still picked up. For each file, record the file ID, the file name, the created time, and the writer, taken from the file owner or last modifying user, falling back to the document name if the account does not identify the person.
For each document found, use Google Docs "Get Document" to retrieve the latest version, and flatten the returned content structure into plain text before checking it.
Run that text through both Pangram "Detect AI-Generated Text" and Pangram "Check Text for Plagiarism". AI detection is asynchronous, so submit the text and poll the task until it reaches a terminal state before reading the result. Pace requests so several drafts in one run stay inside Pangram's rate limit. From the detection result, capture the overall AI likelihood and the segment level windows, so I know which specific passages were flagged rather than just a single score. From the plagiarism result, capture every matched source URL with its similarity score. Note that the two Pangram checks run against different base URLs, which is expected.
Treat a draft as needing review when the AI likelihood is at or above 80 percent, or when the plagiarism check returns a genuine match against an online source. Make the AI threshold easy for me to change in one place. Ignore trivial overlaps such as common phrases, correctly attributed quotes, standard disclaimers and boilerplate, so a properly cited statistic does not flag the whole piece.
Move anything that crosses either bar into the "Needs editor review" folder using Google Drive "Move File". Everything else stays exactly where it is, so clean drafts flow through untouched and my existing process is not interrupted.
Never delete, rewrite or edit a writer's document. The only change permitted is moving a flagged file between folders. Do not alter document contents, file names, or sharing settings under any circumstances.
Finish with one Slack summary posted to my editorial channel using "Send a Message". List every draft checked, with its title as a link to the document, the writer, the AI verdict with its score, the plagiarism verdict, the matched source URLs with similarity scores where plagiarism was found, and short quoted excerpts of the specific passages Pangram flagged. Say for each draft whether it was moved or left in place. Group the flagged drafts first so the editor sees them without scrolling. The goal is that an editor can open a document already knowing where to look.
Word the summary as things to check with the writer, never as accusations. These scores are one signal in an editorial judgement, not proof of anything, and a human editor makes the final call. Prefer phrasing like "worth asking about how this section was drafted" over stating that a writer used AI or copied text. If no drafts were submitted since the last run, post a short note confirming the check ran and found nothing waiting.
Example output
What does this prompt do?
- Each weekday morning, picks up every draft your writers added to your submissions folder overnight
- Checks each one for AI-written text and for passages copied from sources published online
- Moves only the drafts worth a second look into a review folder, and leaves clean work exactly where it is
- Posts one Slack summary listing each draft, its writer, what was flagged, and the specific passages to look at
What do I need to use this?
- A Google account with the Drive folder where your writers submit drafts, plus a second folder for pieces that need review
- A Pangram account on a paid plan, which covers both the AI detection and the plagiarism checking
- A Slack workspace and the channel where your editors work
- Drafts submitted as Google Docs rather than attachments
How can I customize it?
- Change when it runs, such as a later start time or seven days a week instead of weekdays
- Raise or lower the AI likelihood level that sends a draft to the review folder
- Point the summary at a different Slack channel, or send it straight to one editor
- Choose whether flagged drafts actually move folders or just get named in the summary
FAQs
Does this delete or rewrite my writers' documents?
What happens to drafts that come back clean?
Does a high AI score prove a writer used AI?
Will this work if my writers send Word files or PDFs?
What happens on a Monday, or when nobody submits anything?
Related templates
Every month we scan a fresh slice of your published posts for machine-written content and build a prioritized cleanup list your team can actually work through.
Every weekday morning, check new Greenhouse applications for AI-generated writing and send recruiters one Slack digest of who to read closely.
Every morning, new open-text survey answers get checked for AI writing and logged to a spreadsheet, with a Slack alert when too many look suspect.
When your flight moves, your calendar times get corrected automatically and you get a Slack note naming the meetings you're about to miss.
Every 15 minutes, forwarded phishing reports get traced back to the server that really sent them, with a verdict in Slack and the worst senders reported.
Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.
Stop reading every draft cold.
Give your editors a morning check that says which submissions need a closer look, and exactly which passages to start with.