| Main page | Talk page | Submissions Feed, Category, Sorting | Showcase | Apply Participants, By subject | Reviewing instructions | Help desk FAQ | Backlog drives |
Articles for creation (AfC) is Wikipedia's process for reviewing new draft articles before they are published to mainspace. It must be used by new and unregistered editors who cannot create articles directly in mainspace, and should be used by editors with a conflict of interest in the subject. More experienced editors can also choose to use AfC when they would benefit from another editor reviewing the draft before publication. Editors usually submit new drafts for review via the Article wizard.
Many draft authors are brand new to Wikipedia, and creating and submitting an article may be their first contribution to the project. They are likely to be unfamiliar with our policies, guidelines, and terminology. AfC reviewers therefore have two jobs:
AfC is not a general quality review. Draft authors are not expected to write good articles - it is enough that their drafts are suitable for mainspace and do not have serious policy problems. If the remaining problems can reasonably be dealt with through ordinary editing or maintenance templates, the draft should usually be accepted.
To review AfC submissions you need to meet the reviewer criteria and apply by visiting Wikipedia talk:WikiProject Articles for creation/Participants.
Administrators and New Page Reviewers can review AfC submissions automatically.
The AfC Helper Script (AFCH) is used to accept, decline, reject, and comment on submissions. It also notifies the draft author and performs necessary cleanup when a draft is accepted.
Enable AFCH in your Gadget preferences by selecting AFC Helper Script: easily review Articles for creation submissions (drafts).
We recommend enabling AFCH's logging feature. This records your accepts, declines, rejects, and comments on your user subpage, making it much easier to look back at your previous reviews. To enable, open AFCH on any draft, select preferences, and tick Log acceptance, declines, and rejects. If your log subpage gets too large it can lag the script so we recommend periodically archiving to reduce its size.
We also recommend enabling Twinkle from your Gadget preferences. AfC reviewers regularly encounter drafts which need actions outside AFCH, particularly speedy deletion, copyright cleanup, user warnings, and other maintenance tasks. Twinkle makes many of these actions much easier.
All drafts are displayed in a dynamic list at the Articles for Creation tab of Special:NewPagesFeed. You can filter drafts by clicking Set filters and choose from the available filters what kinds of drafts you would like to review.
You can also find a list at Category:Pending AfC submissions. Submissions sorted by their predicted category can be found at Wikipedia:AfC sorting.
Or you can click the button, which will take you to a random draft waiting for review.
You do not need to know every Wikipedia policy before beginning AfC reviewing. Start with straightforward drafts, use these instructions while reviewing, and ask another reviewer for help when you are unsure.
Your job as a reviewer is not to decide whether the draft is complete, perfectly written, or well formatted. Instead, it is to decide whether there is a substantive reason the draft should not yet be published as an article. Articles that will probably survive a discussion at Articles for deletion should be accepted. Articles that will probably not survive should be declined.
| Yes, it will probably be kept. | Then Accept it. We encourage you to fix formatting problems and tag with maintenance templates as appropriate. |
| No, it will probably be deleted. | Then Decline or Reject it where appropriate. Explain the problem that prevents the draft from being accepted. |
| Maybe, but I'm not sure. | Then ask for help on the project talk page. |
AfC reviews result in a draft being accepted, declined, or rejected. The basic distinction is whether the draft is ready for mainspace, fixable, or fundamentally unsuitable. If you are genuinely unsure, leave it for another reviewer or ask for help rather than guessing.
| No substantive reason to keep it out of mainspace? |
Not ready yet, but the problem could reasonably be fixed? |
Fundamentally unsuitable with no reasonable prospect of fixing? |
| ↓ | ↓ | ↓ |
|
ACCEPT |
DECLINE |
REJECT |
The AfC submission comments provide standardised decline reasons for common problems. You can choose up to two reasons to decline a draft in the AfC Helper Script.
The template is a starting point and you can add a short comment explaining what specifically the author needs to address. Explain the issue clearly and link to the relevant policy or guideline where possible. The existence of a standard decline reason does not mean that every instance of that problem requires a decline. Use a decline reason only where the problem is substantial enough to prevent acceptance; minor problems should normally be fixed or tagged instead.
If a problem would ordinarily be dealt with in mainspace through normal editing or a maintenance template, it usually does not justify an AfC decline. Do not decline an otherwise acceptable draft because:
If the problem can be quickly fixed yourself, fix it! Otherwise, accept the draft and use an appropriate maintenance template where necessary.
When you begin reviewing a draft, you may use Mark as reviewing in the AfC Helper Script. This lets other reviewers know that somebody is already reviewing the submission and helps avoid edit conflicts and duplicate reviews.
Before reviewing the draft itself, briefly check its page history, page log, and any previous reviews. This can tell you what problems have already been identified, what the author has changed since the last review, and if there are any issues which need particular attention.
If the draft has previously been declined, do not assume that the previous review was correct or that the same decline reason still applies. Review the current version yourself. If the author has made substantial changes, take those changes into account rather than simply repeating the previous decline.
Some drafts can be quickly declined, rejected, or marked for speedy deletion without a full review because they have an obvious issue contrary to our policies and guidelines. These can include:
Immediate action
Quick declines
Rejection
Review notability early. This avoids authors spending time fixing formatting, prose, or citation issues only to be told later that the subject does not qualify for an article at all. Many problems in a draft can be fixed through editing, but no amount of editing can overcome a lack of notability!
When assessing notability under the general notability guideline, we generally look for multiple sources that meet the three criteria below. Multiple is not defined, but in practice finding three strong and distinct sources will usually make notability easier to establish. The quality and depth of the coverage matters more than the number of references in the draft, and sources derived from the same original material should not be counted separately.
Assess the coverage itself, not merely the publication in which it appears. A reputable newspaper can publish an interview which contributes little or nothing towards notability. Likewise, a source may be useful for verifying a fact without helping to establish notability; for example, a company's own website may verify its address but cannot provide the independent coverage needed to establish notability.
Articles generally require significant coverage
in multiple, reliable sources
that are independent of the subject.
We need sources that provide significant coverage. Usually this means discussion of the subject directly and in detail, with some sort of analysis, critique, or debate. Not: passing mentions, directory or database listings, or government records.
We usually need more than one distinct source discussing the subject. There is no fixed number, but the sources should be distinct and provide separate coverage, rather than just repeating the same information.
We need sources that are reliable. Usually this means that the publisher has a reputation for fact-checking, editorial oversight, and accuracy. For example: books from reputable publishing houses, mainstream newspapers, academic journals, magazines, and other established publications. Not: tabloids, discussion boards, fansites, social media, and most self-published blogs.
We need sources that are independent of the subject of the article. This means not connected or influenced by the subject. Not: books or articles written by the subject, material paid for or commissioned by the subject, press releases, churnalism, or interviews where virtually all of the information comes from the subject or their spokesperson.
Before applying the general notability guideline, check whether a subject-specific notability guideline applies. Some SNGs provide an alternative route to notability.
Once you are satisfied that the subject is notable, check that the draft's important claims are supported in reliable sources, in particular the claims which are being relied upon to establish notability.
Be particularly careful for biographies of living people: contentious material that is unsourced or poorly sourced should be removed immediately rather than left in the draft for the author to fix later.
You usually do not need to analyse every reference with equal intensity.
Keep the following in mind:
Once you are satisfied that the subject is notable and the draft is adequately sourced, check whether it is written from a neutral point of view and is suitable for Wikipedia. Do not decline simply because the prose is imperfect. Avoid putting a draft through another review cycle for problems which can reasonably be fixed yourself or dealt with using a maintenance template.
Keep the following in mind:
If you have not found a substantive reason to keep the draft out of mainspace you should accept it. The AfC Helper Script will move the draft to mainspace, notify the author, and create the article talk page.
Draft:AC/DC is treated as a subpage of Draft:AC. Move the draft temporarily to a title without the slash, accept it, and then move the resulting article to the correct title.
Choose a topic below to find answers to common questions about creating, submitting and reviewing Wikipedia drafts.
The AfC Help desk is the main place for draft authors to ask about declines, sourcing, notability, and what to do next. Reviewers are encouraged to help answer questions there.
Ask substantive on-wiki questions at the project talk page. There's also an active Discord server where you can chat to other reviewers: New Page Patrol Discord server.
These tools can make AfC reviewing quicker, but none replaces checking the draft, its sources, and the applicable policies yourself.
Learn about useful optional tools
Assessing sources
Checking links and references
Identifying notability guidelines
Prose and cleanup
Copyright
Page information
Accessing paywalled sources
If you have access to the Wikipedia Library, the following bookmarklet can be added to your browser bookmarks. Clicking it while viewing a paywalled source will attempt to reopen that source through the Wikipedia Library:
javascript:void(location.href="https://wikipedialibrary.idm.oclc.org/login?auth=production&url="+location.href)
This is particularly useful for scholarly and academic sources.
Investigating possible AI-generated content
The following tools may assist when investigating suspected LLM-generated content. AI detectors are not reliable enough to establish AI use by themselves; use them only alongside source checking, page history, your own judgement, and the guidance at WP:AISIGNS.