The current reputation requirement for editing posts or approving suggested edits are
- 500 reputation during private beta
- 1000 reputation during public beta
Those are very steep hurdles during the very early stages of beta for a new site. On the new Biology site we had something like 2-3 users being able to approve edits for a day, but now that it went into public beta there is not a single user left that can edit or approve edits. Now we're entirely dependent on the SE community team to approve all edits.
I don't think this is a good solution, the community team has a lot of reponsibilities, I just don't think we should shovel all those edits onto them. They certainly know the SE system inside-out, but they usually have no specific domain knowledge, which makes it hard to judge the validity of the more subtle aspects of editing a post.
The goal should be to always have a certain number of users able to edit and approve edits. Those users should be active on the site (measured by reputation), and lacking any other useful metrics, activity on other SE sites should also count in their favor. Ideally, you'd like an expert in the field that is familiar with the SE system to approve the edits on a brand new site.
What I propose is to lower the reputation requirements for editing as long as not enough users have achieved the reputation necessary to edit during that particular stage of the beta. It might make sense to take the activities of the user on other SE sites into account, a user familiar with other SE sites is more likely to have experience with approving edits.
The goal should be to have new SE sites pretty much self-sufficient with regards to editing posts during the early beta period.