Emergency preparedness starts with the essentials you use every day.
Build a manageable reserve, choose meals your household can prepare and keep safe drinking water at the centre of the plan. This free guide brings the earlier food-and-pantry topics into one practical starting point.
Build gradually around your household. The supplies pictured are examples, not an advertised complete kit.
01 / Food you will actually use
A pantry, not a panic purchase.
Start with a written household list and what is already in your cupboard. Canned beans, lentils, vegetables, fish or chicken can complement familiar shelf-stable foods. Compare labels and account for allergies, dietary needs and foods your household enjoys.
Keep a manual can opener and include ready-to-eat choices for times when cooking or clean-up is difficult. Dry rice, pasta and beans need water, fuel and preparation, so they should not be your only outage food.
Keep dry goods sealed, dry and protected from pests. Follow package storage instructions, mark dates and use older stock first. Review quantities when household needs change.
02 / Safe water comes first
Plan storage and treatment separately.
Start with a household reserve.
Manitoba recommends at least 14 days of home supplies and 4 litres of water per person per day for drinking, cooking and washing. Build toward that gradually. Consider pets and other individual needs, container weight and safe storage.
Follow the local advisory.
Listen to local authorities about whether tap water is safe. Keep commercially bottled water as an option and follow current official instructions for the actual contamination or advisory.
A demonstration is not treatment.
A bottle, cloth, gravel, sand and carbon can illustrate particle filtration. That demonstration does not make water safe to drink or reliably remove pathogens or chemicals. Do not rely on appearance or taste to judge safety.
These are flexible meal ideas, not a complete nutritional prescription or a promise that every ingredient is safe without refrigeration. Choose portions and substitutions for your household. Check preparation, storage and allergy information on each product.
Day one
Oats with canned peaches; tuna and bean salad; lentil-and-vegetable stew with rice.
Include a ready-to-eat alternative when water or cooking is limited. Prepare only what you can safely use or store.
Day two
Shelf-stable breakfast food and fruit; chickpea-and-vegetable wraps; salmon with tomato rice.
Keep safe water, a manual can opener and clean utensils available. Choose packaging sizes that suit the household.
Day three
A suitable ready-to-eat breakfast; bean-and-vegetable chili; coconut chickpea curry.
Cook only with equipment suited to the location. Never use an outdoor stove or barbecue indoors or in a garage.
04 / Keep the plan useful
Review, rotate and practise.
Think ahead about heat, cooking, safe water and a warm place to go.
Keep the food list beside your household contact and go-bag plans. Review stored supplies every six months and after important changes. Record what needs replacing instead of buying everything at once.
During an outage, keep refrigerator and freezer doors closed as much as possible and follow official food-safety guidance. Never taste food to decide whether it is safe.
For a broader plan, explore the free emergency guide, optional printable planning tools and locally sourced kit enquiries. Availability and any paid order details are confirmed separately.
Reviewed 3 November 2026. This page is general educational information, not a live alert service. Follow local emergency instructions and call 911 or your local emergency number for immediate danger.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature