40 CARROTOpen the final submitted roster
Use the exact roster accepted for the event, not an earlier draft or the list you intended to submit.
How do you check your Warhammer 40K army before a tournament?
Compare one final roster to three views of the same army: the imported list, the complete tabletop deployment, and the physical trays you will carry.
TL;DR
Check the exact submitted roster, import it, review names, counts, points, weapons, and attachments, then deploy every unit on the tabletop or in Reserves. Match that complete view to the physical trays one unit at a time, keep case locations consistent, take an external reference photo, print verified event references, and repeat the short physical pass before leaving and between rounds.
Which ten steps catch missing models and list drift?
Import the file or supported text
Use a .json, .ros, or .rosz file, or the Full Access text-import path for a supported list.
Review the imported details
Check unit names, model counts, points, weapon names, and attachments against the submitted roster.
Deploy the complete roster
Place every unit on the tabletop or in the appropriate off-table Reserves area.
Compare the tabletop with the physical tray
Match every on-screen unit to the models and transport sections you intend to carry.
Verify one unit at a time
Check the squad count, loadout markers, attached models, and transport assignment before moving to the next unit.
Keep transport contents consistent
Return each checked unit to the same labelled tray or case section so the final pass matches the first.
Take an external reference photo
Photograph the completed army or tray outside 40 Carrot so you have a quick visual packing reference.
Generate and print event references
Print custom Data Cards and phase reminders for the exact submitted roster, then verify them against official sources.
Repeat the check
Run the short physical pass before leaving home and again between rounds when models move between trays.
What does the army import tell you?
The army-import guide explains the two paths. File import for .json, .ros, and .rosz files is free. The supported army-list text-import path requires Full Access. Text import reads unit names, model counts, points, and weapon names; it does not invent complete profiles.
Source of each field
- Built in
- Unit names, base sizes, and current official points from the bundled lookup data.
- From the list
- Names, model counts, points, weapon names, attachments, and any detailed fields actually present in a supported imported file.
- From you
- Detailed stat lines, weapon profiles, abilities, saves, notes, and corrections you entered or saved in an exact-name library profile.
- Still manual
- Legality, event-specific restrictions, model condition, physical packing, and whether the tray really contains what the list says.
How should you run the physical tray check?
Start at the top of the submitted roster and touch the matching models before moving to the next unit. Count every model, confirm obvious loadout markers, find attached Characters, and return the unit to a consistent labelled section. An external photo of the completed tray gives you a fast visual reference without pretending the app can see the case.
Deploy the complete roster on the Virtual Tabletop first, including off-table Reserves. That view helps expose a unit left in a draft, a model count that changed, or a squad that never reached the physical tray.
Which references should match the final army?
Generate printable custom Data Cards only for the submitted roster. Add short phase reminders, then verify every player-supplied stat, save, weapon, ability, and squad detail against current official material. Remove draft cards so an old profile cannot enter the event bag.
- Warhammer 40,000 downloads for current official documents.
- Munitorum Field Manual for current official points.
- Your final submitted roster and current organiser pack for the event-specific check.
What can 40 Carrot verify, and what stays manual?
Capability boundary
- It can show
- The roster you imported, the data each file supplied, saved or manual profile details, complete tabletop placement, off-table Reserves, and printable custom references.
- It cannot see
- Which models are in a case, which tray is in a car, whether a miniature is damaged, or whether the physical loadout matches a note.
- It is not
- An army-legality checker. It does not validate event composition, enhancements, wargear limits, organiser rulings, or current rules.
Frequently asked questions
Can 40 Carrot see which models are packed in my case?
No. It can show the roster you imported and the units you placed on the tabletop or in Reserves, but it cannot inspect a case, tray, bag, or physical model. The final comparison is a manual physical check.
Does 40 Carrot check whether a tournament army is legal?
No. 40 Carrot is not an army-legality checker and does not validate event composition rules, enhancements, wargear limits, or organiser exceptions. Check the submitted roster with current official sources and the event organiser.
Which army details does 40 Carrot supply automatically?
The built-in lookup supplies unit names, base sizes, and current official points. Detailed stat lines, weapon profiles, and abilities appear only when the imported file includes them, you enter them, or an exact-name saved profile fills them.