FFXIV Loot Priority Guide: An Auditable EP/GP Workflow

Start with a policy document, not a calculator

The FFXIV Loot Priority Calculator performs one transparent operation: it divides effort points by positive gear points, filters out ineligible rows, and orders the remainder. It cannot make that quotient fair. Fairness comes from a policy members can read before loot appears.

At minimum, define what earns EP, what adds or removes GP, when values become effective, how absences and substitutes are handled, how recruits enter the system, and who may correct an error. State whether points are per character, per role, or per player. If officers retain discretion, define its scope and require a recorded reason.

Separate five facts in every decision

1. The award

The item or coffer must actually exist. Do not rank hypothetical future rewards.

2. Compatibility

Confirm the member's job and the item's current use or exchange rules.

3. Interest

An eligible member may pass. Capture that choice before assigning a rank.

4. Ledger state

Freeze EP and GP at a named cutoff so values cannot move during debate.

5. Governance outcome

The calculator gives a provisional order; the final recipient and any exception belong in the award log.

This separation prevents a common failure: treating a high quotient as proof that a member deserves or can use every item. Eligibility is a gate, not another multiplier.

A six-step raid-night procedure

1. Before the instance: publish a read-only point snapshot and list unresolved corrections.
2. When an award appears: name the exact item and record the confirmed quantity.
3. Collect eligibility: mark only members who can use the item and have not passed.
4. Run one ledger pass: verify names, EP, GP, and the resulting order aloud or in the loot channel.
5. Apply the documented tie-break or override: never invent a rule after seeing who benefits.
6. Close the transaction: record the recipient and point update before evaluating another award.

Empty award-log schema

Keep the log empty until a real event occurs. A useful CSV or sheet can start with these columns:

timestamp_utc,patch,tier,duty,item,award_count,eligible_members,pre_award_ep_gp,provisional_order,tie_break,final_recipient,point_change,override_reason,recorded_by

This is a schema, not sample evidence. Avoid prefilled rows that look like observed raids. Link a dated Lodestone note or in-game capture when eligibility or reward restrictions materially affect the decision.

Worked policy example

Suppose a group awards 100 EP for a completed session and increases GP by a written item value after receipt. Before the current award, Member A has 1,000 EP and 500 GP; Member B has 900 EP and 600 GP. Their quotients are 2 and 1.5. If both are eligible and one item exists, A ranks first. If A passes, eligibility changes and B becomes the first ranked row. If both have a quotient of 2, the pre-published tie-break decides the outcome.

The example proves only the arithmetic. It does not recommend those point values, claim that attendance equals performance, or represent Square Enix's loot rules. A group should test whether its chosen policy creates perverse incentives before using it.

Override discipline

Some statics reserve discretion for progression goals, role swaps, or an upcoming encounter. An override is not automatically unfair, but an undocumented override makes the ledger ceremonial. Require the officer to cite the policy clause, state the reason before assigning the item, and record who agreed. Review recurring overrides; if the same exception appears repeatedly, the written policy or point model likely needs revision.

Patch and source boundary

Square Enix's Patch 7.4 Notes describe current tier reward eligibility and restrictions. They do not prescribe EP/GP. Treat the official note as evidence for the game boundary and your group document as evidence for governance. Recheck both when the tier unlocks or your roster changes.

Monthly audit questions

• Can every member reproduce a recent quotient from the saved snapshot?
• Were any ineligible members ranked or any eligible members omitted?
• Did an officer change points after seeing the item?
• Were ties resolved by the published rule?
• Do overrides cluster around one role or person?
• Does the ledger match the actual inventory and award history?

If the answer to any question is unclear, pause the system and repair the records. A smaller trustworthy ledger is more valuable than a precise-looking history nobody can verify.