Castle Position Review Workflow

Review turns submitted applications into a reliable candidate pool. Acceptance makes a player eligible for scheduling. It does not assign or publish a Castle Position.

Find the application

Select the correct kingdom cycle, then use the Applications workspace to:

• search by player identity;
• filter by status;
• show or hide rejected records;
• compare total, accepted, pending, and rejected counts;
• open an application's submitted details and resource proof.

On a narrow screen, filters stack and the table scrolls within its container. Keep the selected kingdom and cycle visible before changing a status.

Review procedure

1. Verify the governor, in-game ID, kingdom, and alliance context.
2. Review requested stages, UTC choices, occupied-slot notes, resources, custom answers, and contact preference.
3. Open proof only when the cycle requests it and confirm that it supports the declared values.
4. Resolve missing or conflicting roster identity. Approval can link an existing player, correct a confirmed name, create an eligible missing player, or use a temporary participant when no roster record should be created.
5. Mark the supported outcome: accept, reject, or needs review.
6. Send accepted candidates to scheduling. Keep unresolved or rejected applications out of automated placement.

True Gold is a count, not a duration. Other configured resources can be shown as effective days. Do not read a True Gold value as 0d merely because both types appear in the same application.

Correct a submitted record

Authorized leadership can adjust a submitted application after verifying the source. Enter a note that explains the correction. The status view then shows:

• an adjusted badge and adjustment count;
• who changed the record and when;
• the review note;
• each field's old and new value;
• the original applicant submission for comparison.

Use this for a verified correction, not to hide a disagreement or rewrite an applicant's history. Applicants can see leadership modifications on their status view.

Resolve duplicates and rejected applications

When two submissions represent the same application scope, use the duplicate-resolution action to keep the existing record or use the latest submission. Do not schedule both as separate candidates.

A rejected application can be reopened to Needs review, corrected or rechecked, and then accepted when appropriate. Reopening is an explicit status change and does not assign a slot.

Interpret review states

• Submitted: waiting for review;
• Needs review or Standby: identity, eligibility, or another conflict needs attention;
• Accepted: eligible for the planner;
• Rejected: excluded until deliberately reopened;
• Scheduled: currently placed in a draft or published schedule, so publication state still matters.

Candidate ranking and suggestions consider recorded inputs only. They cannot see offline agreements or verify an unsupported resource claim. The manager remains responsible for the final review decision.

Next: Planning, Scheduling, and Publishing. For a participant who should not become a roster player, see Temporary Participants and Reviewed Players.