Top Lords Alliance Operations Guide

Use shared notes, manual shield incidents, sampled presence and assigned tasks for everyday officer work.

The Operations sidebar group holds the records your officers maintain together. Record what you know and keep task visibility appropriate to its audience.

1. Keep shared notes

Open Notes and add the information officers need for follow-up. Use search to find an existing note before creating another. Keep the wording factual and update it when the situation changes.

Shared officer notes are private alliance work records. Publishing an alliance page does not turn them into public content.

2. Record shield incidents manually

Open Shields and record the affected Lord, date and details of a known incident. Review the Lord's officer-visible history when following it up.

Shield incidents are manual records. A missing reading or low sampled presence is not evidence of a shield incident, and the app does not detect failures automatically.

3. Read sampled presence

Open Presence for dated counts from roster captures and manual counts. Check the captured cohort and timestamp. Presence summaries use UTC periods.

A sample describes that moment. It does not establish continuous playtime, an exact login duration or a Lord's full daily attendance. Follow data freshness and coverage for interpretation.

4. Create and assign a task

Open the task page under Operations and select Create task.
Write the title and details, choose assignees and set a due date if needed.
Choose visibility: All members or Assignees and managers.
Set daily or weekly recurrence and officer verification only when the duty needs them.
Save and check the list or board view.

Linked members see relevant tasks in My Lord. Private task details stay within their permitted audience. Assignment notices appear in the app; push task reminders are optional.

5. Follow completion through review

Assignees use Start and Mark done. A task requiring verification waits for an officer, who chooses Verify completion or Return to progress. A recurring task creates its next occurrence after final completion.

Use Activity log to inspect recorded changes. For reminders on due tasks, follow install and reminders. The alliance management page links the related tools.