The goal of the SitRepNet project is to build the framework for a highly decentralized means of information exchange. Sending the independently-gathered SitReps and other reports using JS8Spotter gets the information “out there”, but there is still a need for compiling that information into a more usable and accessible form, and that’s what the SitRep Summary Reports (SSR) are for.
There are several news and information reports already being distributed on a regular basis, but they all have one critical point in common: they all depend on information collected using the Internet in one form or another. In a grid-down situation, they may have nothing to report beyond what can be gathered through receiving short wave broadcasts, and maybe a handful of “mystery sources”. The SSRs are a way to compile reports on local conditions in different areas, and then send that compiled report out so that others with more limited radio capabilities can receive them – including receive-only stations.
Problems with the SSRs – They are based on voluntary submissions that are not vetted, they are likely to be sporadic, they are vulnerable to intentional misinformation, as well as other significant problems. The SSRs are a case of making the best of a bad situation.
Mitigating factors – “Quantity has a quality all its own.” The more SitRepNet and other reports are available, the less weight that false outliers will carry. And the biggest factor: What is the alternative when the internet and power grid are down?
“Isn’t this the same as any other net?”
• A conventional net is where a number of stations meet at a scheduled time, frequency, and mode, and then traffic is passed to the entire net.
• The SSR is a Distribution Net, produced by taking the various reports created and sent using JS8Spotter over the previous week, and then summarizing that in a report, which is then sent out on a set schedule.
“Who creates the SSR and transmits it?”
• You do. In keeping with the whole SitRepNet concept – anyone can and should.
• The goal is to have a number of people in different areas of the country creating and sending the reports. This is a DIY project.
“How do the SSRs get distributed?”
• There are a couple of ways, and as you would expect for a decentralized system, you choose the most appropriate for your situation. These are the most likely, in order of preference:
➊ FLDIGI Distribution Net (Recommended as the primary distribution method)
••• Use the SitRepNet Distribution Macros (modify as needed)
••• Use FLMSG and/or FLAMP with MFSK32 or Contestia4/250.
••• Use F!106 to let others know of your distribution schedule
➋ JS8Spotter Expect System Request (Used for only very brief SSRs)
••• Save a very brief report using SSR as the Expect statement
••• Add SSR to your CMDS Expect list
➌ JS8Spotter Expect System (Used for only very brief SSRs)
• “Send Now” command, sent to @SITREP
“When, Where, and How?”
• First check the HF Digital Net Database to make sure you aren’t interfering with an already established net.
• When – Pick a time when the band you are using is typically at a high point. Since 40 meters is sort of the default band for JS8Call, that’s a good place to start. An hour or two after sunset is a good starting point.
• Where – For JS8, 7.078 is logical choice, as well as 7.107. Pick a frequency where you know you will be heard, but not interfere with others.
• How – For very brief SSRs, JS8Spotter will work, but for longer reports, a faster mode is the better choice. Typically, that would be MFSK32 or Contestia 4/250, using FLDIGI and either FLMSG or FLAMP.
Now is the time to practice
Just as some groups currently pass weekly information bulletins, SSRs should also be routinely passed, and for the same reasons – practice and refining the system. Get started now so we can work out the bugs in the system and establish routines and schedules – BEFORE they are needed.
===== Still working on the following sections =====
“What would a SSR look like?”
Here’s an entirely fictitious sample that would be suited for a FLDIGI mode:
SitRep Summary Report Week ending AUG 25 2026 Sources (Report:Stations) - F!104:12, F!301:4, FL EL99 Power out since JUL13, No fuel deliveries since AUG08,
“How does this actually happen?”
• F!308 – Open Source Information Report will likely be a primary report that will be used to compile the Summary Reports, but use whatever is appropriate. The situation may call for the Wildfire Status report or the Power Stability report, or any other MCForm. These are sent as a matter of routine reporting. These are what the SSRs are based on.
• F!106 – Impromptu Net Notice.
