This is now the primary Repository for MCForms for use with JS8Spotter. Anyone is, of course, free to publish these or any other forms, but our aim is to have the latest version of every MCForm in use available here on this page. Having the forms publicly available satisfies the FCC Part 97.117 rule prohibiting “codes and ciphers” in addition to making them available to everyone.
➤ These forms only work if both the sending and receiving station have the current version form installed on their copy of JS8Spotter, so it is important that new custom forms be distributed as quickly as possible.
To have your custom MCForm(s) published on this Repository site:
- Test your form before submitting it.
- Confirm that it meets the Guidelines for Publishing Forms.
- Use the Contact form to upload your file.
- Include a brief description of your form and your FCC call sign.
- Be sure to include a valid email address (for questions only – not published)
- The form number will be assigned by the Repository, the file will be edited to include the ID number, version date, and renamed if needed.
- Before publishing, it will be sent to the email provided to make sure you approve of any needed changes.
To create your own MCForms, see the MCForms page or download the latest JS8Spotter Manual. Need help? Use the Contact form – we’re glad to help.
MCForms Categories
| Form/File Name | Description |
|---|---|
| 000 – 099 | Preliminary. Used for forms being proposed or developed. Not in general use |
| 100 – 199 | Informational, Informal, Non-Emergency |
| 200 – 299 | Reserved for future allocation |
| 300 – 399 | Emergency & Emergency Exercise, Situation Reports |
| 400 – 499 | Reserved for future allocation |
| 500 – 599 | Surveys of general conditions, such as supply availability, weather, etc. |
| 600 – 699 | Reserved for future allocation |
| 700 – 799 | Group and Net forms used by specific groups, not intended for general use. These will be included in the forms packaged with the JS8Spotter program files and in the ZIP files available on this site unless the form designer requests otherwise. |
| 800 – 899 | Reserved for future allocation |
| 900 – 999 | Misc. forms that do not fit into any other category or overflow from other categories |
| Alpha Characters | Forms outside of the standard configuration, and/or not intended for general use. If you just need to have your MCForm published in order to satisfy FCC requirements, this is the category. It’s sort of a “no man’s land” of forms. These will NOT be included in the forms packaged with the JS8Spotter program files or in the ZIP files available on this site – distribution beyond its availability here – is entirely up to you. |
Form Changes
- Once a form has been published, there should not be any changes to that form that affect how it is prepared and displayed.
- Minor wording changes are ok if they just serve to clarify.
- For a new form, there is a “grace period” of up to one week where significant changes may be made, but after that point, any changes that affect preparation and display should have a revision letter attached, making it a separate form. For example, F!123 might be revised and renamed to F!123A.
- We recommend that both the original (F!123) and the update (F!123A) remain in the Forms directory until the new version is widely accepted and distributed.
- All changes to a form should be recorded in the form code, following a “#” (EXAMPLE: # Version 02/16/2026 – Changed Observation Time to UTC (was Local time))
➤ NOTE: Some forms that were already in use before the file naming convention was developed are “grandfathered in” and retain their original MCForm number, regardless of category.
➤ Most forms need Ver. 1.15 or higher of JS8Spotter to work correctly.
Keep your MCForms up to date
❒ Download all MCForms with supporting docs (.ZIP format) (as of 02/20/2026)
❒ Version Log (as of 02/20/2026)
❒ List of MCForms (PDF) (as of 02/20/2026)
These are brief descriptions and suggested uses for the MCForms available for use in JS8Spotter. Some of this, of course, is subjective opinion, but we hope you’ll find this helpful – especially as the number of available MCForms increases.
100 – 199 Informational, Informal, Non-Emergency
F!100
Amateur Operator Information F!100
10 Items covering your ham radio interests and activities.
This is a standard MCForm to include in your Expect System options to let others know about you. [JS8Spotter]
F!101
Amateur Station & Equipment Details F!101
9 items describing your radio, antenna, power, modes, and grid-down capabilities.
Used as an Expect System option to let others know details of your station. [JS8Spotter]
F!102
JS8Call Operation Details F!102
6 items about how you use JS8, experience and comfort level, and bands. [JS8Spotter]
F!103
Net Checkin F!103
4 items for a basic, standard net check-in. Use this for JS8 nets unless your net has a custom report. [JS8Spotter]
F!104
@SITREP Basic Check-in F!104
6 items for basic check-in and independent information sharing. Designed as a Top Level form that points to any relevant current reports. [KN4AM]
⚑ The @SITREP group tag is used to indicate independent, non-affiliated traffic, as well as use by groups. Including @SITREP in your Expect System Allowed Callsign/Groups (“*,@SITREP” plus any other groups you want, separated by a comma) allows others to “find” you by sending “@SITREP E? CMDS”. This is key to building an effective decentralized information sharing network.
⚑ Include the word “ALERT” in this report, if appropriate, to flag it to other stations so they don’t miss something important.
F!104 is designed for use with F104Mapper – https://sitrepnet.com/f104-mapper/
F!105
Information Exchange Planning F!105
5 text entry and 6 MC items to initiate information exchange during both normal times and in times of crisis. The focus here is on creating decentralized, independent connections. [KN4AM]
F!106
Impromptu Net Notice F!106
2 text entry and 8 MC items to announce details of an impromptu net, typically used to address a specific event. (Note that this could be just 2 stations passing traffic.) [KN4AM]
F!107
Request for Information (RFI) F!107
6 text entry and 3 MC items to request information and gather intelligence. This is used to analyze and compile reports and information bulletins that are sent out QST. It includes an expire date and a serial number to keep things organized and current. [KN4AM]
F!108
Station Schedule and Temporary Closing/Reopening Notification F!108
NCS tool used to report station operating schedule, frequencies, and pending QRT. (KN4AM)
300 – 399 Emergency & Emergency Exercise, Situation Reports
F!300
Situation Report F!300
12 items reporting on post-disaster conditions. This is designed for use with a group, rather than individual reporting. Supporting docs (TXT) available for this form. Be sure to read the supporting doc before using this form; it describes multi-part answers which can greatly increase the capabilities of MCForms. Use F!304 or F!301 if reporting as an individual station. [JS8Spotter]
F!301
Field Situation Report F!301
9 items. This covers all the basics in a quick, easy-to-use format. Same as F!304, but includes “Operator reporting for” item. Use F!304 if the “Operator reporting for” item is not needed. [JS8Spotter]
F!302
Hospital Bed Report F!302
8 items reporting available hospital beds by specialty (emergency, pediatrics, burn, etc.). Use this when working with hospitals during a disaster. Typically paired with F!303. [JS8Spotter]
F!303
Hospital Status Report F!303
10 items reporting on the infrastructure required to keep a hospital operational. Includes evacuation and casualty stats. Typically paired with F!302. [JS8Spotter]
F!304
Individual Situation Report F!304
8 items reporting on current infrastructure conditions at your location. This is the primary SitRep for individual reporting, and covers all the basics in a quick, easy-to-use format. Same as F!301, but without “Operator reporting for” item. [JS8Spotter]
➤ If in doubt when reporting on your local conditions, this is a good choice.
F!305
Early Warning Awareness/Alert Report F!305
4 items and 4 text entry fields. Early Warning Awareness/Alert for an anticipated event in which net activation, further communications, or preparedness actions may be called for, along with net and other followup information. Utilizes the Source and Information Reliability Matrix found in FM 2-22.3 Human Intelligence Collector Operations, Appendix B. [KN4AM]
F!306
Power Stability Report F!306
1 item reporting on electrical power stability at your location over the last 48 hours, plus 1 item on your station backup power capability. [KN4AM]
F!307
Wildfire Status Report F!307
2 text entries and 7 MC items to report the status of a wildfire. [KE7FST]
F!308
Open Source Information Report F!308
4 text entries and 4 MC items to report open source information for news bulletins. [KN4AM]
500 – 599 Surveys of general conditions, such as supply availability, weather, etc.
F!500
Local Supply Survey F!500
15 items used to gauge availability of supplies and level of consumer anxiety. Designed for use during a supply chain disruption, the lead-up to a disaster (hurricane) or crisis (possibility of war or other major disruption). [KN4AM]
(NOTE: F!501 and F!502 are now OBSOLETE, replaced by F!504. Obsolete forms are no longer included in the files distributed with JS8Spotter updates.)
F!504
Comprehensive Weather Report F!504
18 items for a comprehensive report on weather conditions, suitable for advanced weather forecasting. This is intended for weather forecasting by casual and serious WX hobbyists or a “crowd sourced” weather service. Focus is on basic instruments (thermometer, rain gauge, barometer, sling psychrometer) and visual observation to make it usable by the largest number of observers. Many will not be able to report on all items – report what you can, and leave the rest blank. Supporting docs on this website provide guidance for visual observation. [KN4AM]
F!505
Area Assessment F!505
32 items for a very detailed assessment of an area. [KN4AM]
F!505 is designed for use with JS8Reporter. Click here for “Best Practices for using F!505”, and learn more about JS8Reporter.
700 – 799 Group and Net forms used by specific groups, not intended for general use
F!700
4SQRP Net Checkin F!700
6 items used for low power JS8 nets. Learn more and join 4SQRP at https://www.4sqrp.com/
F!701
MAGNET Information & Observation Report F!701
6 items and 3 optional sub-forms to report observations and information. Revised 02/27/2025. [MAGNET] – for more information https://magnethf.com/
F!702
SEEN Operator Station & Equipment Details F!702
9 items to report station and equipment details. Used to assess capabilities in both grid-down and “normal” operating environments. [SEEN] – for more information https://www.senetwork.us/
F!702A
SEEN Net Check-in F!702A
3 items for net check-in. [SEEN] – for more information https://www.senetwork.us/
F!703
COOP 9 Line Medivac Reporting Form F!703
10 items for requesting medical evacuation in a war zone or similar situation [COOP].
Alpha-Character forms (Not distributed with JS8Spotter updates)
F!BDN
BDN Price Survey (Temporary test report) F!BDN
Updated 03/31/2026 – Report of basic item prices. Used to provide data to build a reporting/analysis/distribution system. (Replaces F!720) For more information: https://sitrepnet.com/dist-net/
