ThemeForest Chopz - WordPress Theme

How to Set Up ThemeForest Chopz for a Public Safety or Municipal Department Website

ThemeForest Chopz is not a standalone WordPress theme. It is an Elementor Template Kit designed to help you launch a website quickly for a police department, sheriff's office, fire department, security unit, or another public-facing organization. This guide focuses on real implementation rather than the product listing: how to prepare the site, import the kit, build the homepage, configure the header, forms, news, and service sections, and verify that visitors can actually find the information they need without confusion.

The most common mistake with kits like this is treating the ZIP archive like a regular WordPress theme. A Template Kit is imported through a dedicated tool, stored in the Elementor library, and then inserted into pages. That means the workflow is different from installing a theme through Appearance - first you verify the environment, then import the global styles, then bring in the individual page templates, and only after that build the navigation.

Below is a complete working setup flow: what to check before installation, how to import the elements, where not to miss Global Theme Style, how to connect the header through Jeg Kit, how to adapt the blocks for real department services, how to configure MetForm, which warning signs point to import problems, and when Chopz is better replaced with a heavier full theme.

What Chopz Actually Gives You and Where It Works Best

Chopz solves the problem of getting a polished visual starting point fast. The kit includes ready-made pages for the homepage, organization info, services, staff, news, single post, FAQ, contacts, error page, header, footer, global style, and a MetForm form. That matters for municipal or service-oriented websites because this type of site rarely stops at a single landing page. Visitors need multiple pathways: news, contact details, emergency numbers, a list of services, answers to common questions, and clear next steps.

According to the official product page, Chopz is built for WordPress and Elementor, uses free plugins, does not require Elementor Pro for basic use, and includes 13+ ready-made templates. Elementor, Jeg Elementor Kit, and MetForm are specifically listed as required plugins. In practice, that makes the kit closer to a ready-made system of sections and pages than to a standalone theme with its own demo importer.

Visually, Chopz is built around contrast: a dark top section, blue service accents, a large hero area, news cards, a popular-post sidebar, a services grid, and emergency contact blocks. It is better not to break that logic during customization. If you replace everything with random photography and disconnected colors, the site loses the cohesion that makes a Template Kit worth using in the first place.

Where the kit is strongest

The most useful part of Chopz is the way multiple pages share one visual system. On the homepage, you can build a path like "news - service - emergency contact - department information"; on the Services page, explain actual service areas; on Officers, present department leadership or responsible staff; and in FAQ, answer recurring questions from residents. For a small department, that is much faster than designing every page from scratch.

The second advantage is Elementor itself. A content manager can replace text, service cards, addresses, and images in a visual editor instead of editing theme template files. But that same flexibility creates a risk: if every editor starts changing spacing, fonts, and colors by hand, the site becomes visually inconsistent within a few weeks. That is why this guide gives special attention to global styles and reusable blocks.

Who Chopz may not be a good fit for

The kit does not replace a specialized portal with user accounts, integration with internal agency databases, incident maps, advanced request forms, or secure document workflows. If the project requires citizen login, intake of official submissions with legal status, integrations with internal systems, or strict compliance with a government design standard, Chopz should be treated as an outer informational layer only.

You also need to account for the dependency on Elementor and extra plugins. For a site with very strict performance requirements, a minimal extension footprint, and long-term maintainability goals, a custom theme or a lightweight WordPress block theme may be the better path. Chopz works best when speed of launch, visual consistency, and no-code page editing matter most.

What to Check Before Installing It on WordPress

Preparation saves more time than troubleshooting later. A Template Kit usually breaks not because it is a "bad kit," but because someone tries to import it like a theme, skips the global styles, installs it on a bloated site with conflicting builders, or works on hosting with inadequate limits.

For Chopz, it is best to start on a staging copy or a fresh site. That is especially important for organizations whose public website is already receiving inquiries. Importing templates should not accidentally replace the live homepage, disrupt the menu, or break the contact form.

Minimum technical environment

Elementor's official recommendations require a current WordPress version, a modern PHP version, and enough memory. This guide will not lock the main text to specific numbers because requirements change, but before installation you should always check Elementor - System Info or Tools - Site Health. If you already see warnings there about memory, PHP, file permissions, or server limits, fix those first.

For an Elementor site, three things matter in particular: the ability to write CSS files to wp-content/uploads/elementor/css, a properly working REST API, and no aggressive security restrictions that block the editor iframe. If the editor only loads intermittently, it is too early to import Chopz onto that site.

The correct archive type

Chopz should stay in its original ZIP archive. You do not install it through Appearance - Themes, and you do not manually unpack it into the theme folder. Envato kits are imported through the Template Kit workflow, and the imported elements then appear in the Elementor library. If WordPress says it cannot find style.css during installation, that is almost always a sign that the kit is being installed the wrong way.

Pre-launch check: if the product and file name say Elementor Template Kit, use the template kit import flow, not the standard WordPress theme installer.

A clean build or an existing site

On a fresh site, it is much easier to preserve Chopz's design as intended: install a compatible theme, import the global styles, create the pages, and assign the homepage. On an existing site, you need to move more carefully: old theme styles, cache, other builders, and existing menus can all affect the result. In that case, start by importing a secondary page such as FAQ or Services and test how it looks on a separate draft page.

If the site already uses another page builder, do not mix approaches without a clear reason. Two builders on the same page often create a maintenance problem: different spacing systems, CSS, widgets, and caching logic start working against each other. Chopz works best when the kit's pages are edited in Elementor only.

Installing Chopz Without Confusing It with a Theme

The official installation path for Envato Elementor Template Kits comes down to importing the ZIP file through a dedicated Template Kit tool. The exact plugin name in the interface matters less than the workflow itself: upload the archive, install the kit requirements, import the global style, and then import the individual templates.

Basic import order

A reliable Chopz setup looks like this:

1. Make sure the site is running a compatible lightweight theme such as Hello Elementor or another theme that does not interfere with Elementor content.
2. Install and activate Elementor. If WordPress launches a setup wizard, you can close the extra marketing screens and return to the admin panel.
3. Install the Template Kit import tool recommended by Envato for this type of archive.
4. Go to Tools - Template Kit or the equivalent import section and upload the Chopz ZIP archive without unpacking it.
5. Click Install Requirements if the importer shows an orange notice about required extensions.
6. Import Global Theme Style first so the colors, fonts, and base settings are in place before the pages.
7. Import the templates one at a time. Do not fire off the whole kit with several parallel clicks.

Do not rush. If the server is weak, importing several heavy templates back to back can trigger an error or hang. It is better to wait for each item to finish, open it in the Elementor library, and only then move on to the next one.

Why Global Theme Style needs to come first

The global style is not a decorative extra. It defines the foundation: colors, typography, and the basic rhythm of the sections. If you import the pages before it, or skip it entirely, some pages may look "almost right" but still use the wrong fonts, spacing, and colors. That can be hard to catch later because visually it often looks like a caching problem or a theme conflict.

For Chopz, the blue accent and dark top contrast are especially important. Those elements repeat in the header, buttons, news labels, service cards, and emergency call blocks. So after importing the global styles, open the homepage preview and verify the basics: buttons are blue, the header area is dark, headings are large enough, and the news cards have not fallen apart.

How to create pages from the imported templates

After import, the templates usually live under Templates - Saved Templates. To turn one into a real page, create a new entry under Pages, click Edit with Elementor, open the library through the folder or Envato icon, choose the template you need, and insert it. For the homepage, use the Elementor Full Width layout so the theme's default page title does not add an extra top block.

Then assign the page as the homepage through Settings - Reading. That is safer than editing some old existing page because you are explicitly controlling which page becomes the public entry point.

Header, Menu, and Service Navigation Through Jeg Kit

Chopz includes a separate Header template, and the official product text describes setting up the header through Jeg Elementor Kit. This is one of the most important parts of the kit: for a public safety website, the header should immediately route people to services, news, contact details, and the emergency number. If you leave the header as a regular Elementor page block without display conditions, visitors may see a nice homepage but lose navigation on the internal pages.

Header setup logic

In the admin panel, go to the Jeg Kit section that controls the header. Create a new header, assign a display condition for the entire site, open it in Elementor, and insert the imported Header template from the Chopz kit. After saving, check not only the homepage but also the News, Services, and Contact pages.

The meaning of the All Site condition is simple: the header should be global. If no condition is assigned, the header may appear only in the editor or on a single page, while the rest of the site falls back to the theme header or ends up with no navigation at all.

How to adapt the menu to a real site structure

The Chopz demo header uses standard items such as Home, About Us, Services, Pages, News, and Contact. For a real site, do not carry those over mechanically. Start by structuring the menu around visitor tasks:

• Home - a concise entry point with key updates.
• Services - driver's licenses, permits, requests, records, or other real services.
• News - announcements, traffic alerts, reports, public warnings.
• About the Department - leadership, service area, department contacts.
• FAQ - recurring questions, office hours, submission rules.
• Contact - address, phone, form, map, non-emergency contact channel.

If the department has an emergency number, it should be visible, but it should not replace the standard informational pathways. For an international or localized version of the site, replace the demo phone numbers and labels with real ones only after they are approved by the responsible staff member.

Navigation check after saving

Open the site in an incognito window. Click through from the homepage to every main page. If a menu item leads to a draft, an empty page, or a demo anchor, fix that before launch. For a public service organization, a dead link looks worse than a temporarily hidden menu item.

Quick takeaway: first create the real WordPress menu, then connect the header in Jeg Kit, and then verify it across all page types. Do not edit the header separately on every page.

Homepage: How to Turn Demo Blocks into a Useful Visitor Path

The Chopz homepage looks rich: hero section, news, popular content, services, emergency contacts, responsibility blocks, team information. That is a strong starting point, but the demo content should not stay on the live site. The main risk with a Template Kit is "looks polished, but tells people nothing": visually everything is there, but visitors still do not know where to click for their specific task.

For a public-facing organization, the homepage should answer three questions: where to go in an emergency, where to find a service, and how to check current updates. That is why it is better to configure the homepage around visitor routes rather than simply following the order of blocks inside the editor.

Hero section and first screen

In the demo, the top section uses a strong photo and a large slogan. When replacing the text, do not turn it into a marketing tagline. It is better to make a clear promise about what the site does: "Department Information, Services, and Requests," "Public Alerts and Contact Information," or "Services for Residents and Businesses." Use a specific action in the button: go to contacts, view services, report an issue, or learn how to submit a request.

Images need to be selected carefully. The official Chopz product page explicitly warns that demo images require separate licensing or replacement. For launch, use your department's own photography, officially approved images, or neutral visuals with no licensing issues. Do not leave demo photos in place if you do not have the right to use them.

News block and popular content

In the Chopz demo, the news cards use labels like Crime, Police, Recruitment, Training, and similar categories. On a real site, those labels should be replaced with a local editorial structure. A solid set of categories might include "Announcements," "Traffic Alerts," "Prevention," "Careers," "Events," and "Safety." It is usually better to avoid alarmist or sensational wording if the site is meant to feel official and steady.

Make sure the cards lead to actual WordPress posts rather than placeholder pages. If the site does not yet publish regular news, it is better to temporarily keep 2-3 meaningful informational posts than to launch with six meaningless demo cards. A public trust website should not present fictional incidents as real news.

Services grid

The demo block "Explore Police Services & Information" works well as a service showcase. It should be turned into a compact action map. Every card should lead to a page that includes a description, requirements, office hours, contact details, and a clear next step. If the service is not handled through the website, say plainly where people should go instead.

Do not overload the cards with detail. A title, one line of context, and a link are enough. Put the full conditions on a separate page so the homepage stays navigational instead of turning into an oversized reference document.

Configuring Services, News, FAQ, and Staff Pages

Chopz includes several page types, and each one solves a different problem. If you only replace the demo text superficially, you end up with a pretty site that lacks depth. If you distribute the content correctly, the kit becomes a compact knowledge base: services answer actions, news handles timeliness, FAQ covers recurring questions, and staff pages support trust and accountability.

Services: cards that lead to action

On the services page, do not explain everything in a single paragraph. It is better to use a repeatable structure for each service:

• Who needs the service and in what situation.
• What information or documents to prepare.
• Whether the issue can be handled online or requires an in-person visit.
• Which department is responsible.
• How the visitor will know the request has been received.

This approach preserves the Chopz design while making the page practical. The service cards stop being decorative and become real navigation for real scenarios.

News and Single Post: how not to undermine trust

Chopz's news templates work well for announcements, prevention content, reports, and alerts. But on an official website, editorial discipline matters: date, source, author or responsible department, a clear headline, and no unverified wording. If a post relates to public safety, include a clear next step: where to call, where to check status, or what residents should do.

Elementor makes it easy to style every post beautifully, but you should not manually reinvent the structure of every item. It is better to standardize a few content formats: announcement, alert, event, and report. That way the editor does not have to redesign each post from scratch.

Officers: a careful trust block

In the demo, the staff page is presented like a leadership team block. For real-world use, it is important not to publish unnecessary personal data. Show only what your organization's policy allows: name, role, area of responsibility, and official department contact. If personal photos cannot be used, replace them with official portraits, the department emblem, or role cards without photos.

FAQ: the questions that reduce front-desk workload

In Chopz, FAQ is most useful not for generic answers like "what the department is," but for real recurring questions: office hours, the difference between emergency and non-emergency requests, how to prepare for a visit, where document-related questions should go, and what to do if the form fails. A good FAQ reduces incoming calls and helps people understand their next step.

MetForm in Chopz: A Contact Form Without a False Sense of Readiness

The kit includes a MetForm Contact template. That is convenient because the form already matches the visual style. But a form on a public organization's website is a sensitive element. It should not only look good, but also send email correctly, protect against spam, tell users what happens after submission, and avoid collecting unnecessary data.

Importing the form from the kit

The official Chopz instructions describe a separate procedure: import the MetForm blocks, open the page containing the form widget, enable the Elementor navigator, select the MetForm widget, click Edit Form, create or choose a form, insert the imported template through My Templates, and save it. That is not always intuitive because the form does not live on the page like a normal image block. It exists as a separate object inside MetForm.

After inserting the form, verify that the widget on the page is actually connected to the correct form. If only the outer block was imported but the form itself was never selected, the public page may show either empty space or a form missing its required fields.

Which fields to keep

For a contact form, a minimal set usually works best: name, contact information, request subject, message, and consent to data processing rules if required in your jurisdiction. Do not collect passport details, medical information, incident details, or other sensitive data through a standard public form unless you already have a secure approved process for handling that information.

The text next to the form should explain what it is for. For example: "This form is intended for non-emergency website questions and general service inquiries. For urgent situations, use the official emergency number." That lowers the risk of misdirected submissions.

Email, spam, and delivery testing

MetForm can send notifications, but email delivery depends on more than the plugin itself. On most sites, you need to configure an SMTP plugin or mail delivery service, otherwise messages may land in spam or never arrive. For the Chopz form, check the following:

• The sender address is on the site's domain or approved by the mail service.
• The recipient is a shared department mailbox, not the personal email of a random staff member.
• The email subject makes the type of request immediately clear.
• After submission, the user sees a clear confirmation.
• Spam protection is enabled before the form is made public.

Submit a test request from an external email address, then check the inbox, spam folder, and the confirmation text shown on the site. If the email never arrives, start by investigating mail delivery, not the form design.

Global Styles, Photos, and Safe Visual Customization

A Template Kit is valuable because it gives you a unified visual language. But this is also where chaos often starts: one heading gets changed manually, another stays in the demo style, a third button gets a new color, a fourth gets shrunk, and the site gradually loses its internal system. With Chopz, it is better to work from global settings and repeatable rules.

Colors and typography

The original Chopz visuals show a dark service-oriented background, a strong blue accent, white space in the news sections, and clean sans-serif typography. If the organization needs a different official color, change it through Elementor global colors or the kit's global style, not manually in every widget. That keeps buttons, category labels, service icons, and links consistent.

For typography, choose one pair: headings and body text. Do not add five fonts just for "variety." A public safety website should be easy to read quickly, especially on mobile and in stressful situations.

Photos and rights for demo images

The official Chopz listing states that the demo images come from Envato Elements or other sources and require separate licensing or replacement. That is not just a formality. For launch, use images you actually have the rights to publish: your own photography, official organization images, licensed stock assets, or neutral illustrations.

If you replace the images with real department photos, maintain a consistent look: similar color grading, sufficient sharpness, no accidental personal data visible in the frame, and proper cropping. Do not place a dark nighttime shot, a studio portrait, and a blurry phone photo side by side without adjustment. That kind of mix looks unprofessional.

A small CSS adjustment for consistent service cards

If the service cards end up with different heights after you replace the text, you can add a small reversible CSS adjustment through Appearance - Customize - Additional CSS or another safe CSS area provided by your theme. This does not rely on internal Chopz APIs. It uses a standard Elementor alignment approach. Before applying it, assign a shared CSS class to the relevant cards in Elementor, for example chopz-service-card.

.chopz-service-card {
  min-height: 180px;
}

.chopz-service-card .elementor-widget-container {
  height: 100%;
}

.chopz-service-card a {
  word-break: normal;
}

After saving, clear the cache and check the services page in both desktop and mobile preview. If the cards become too tall or the text starts looking stretched, remove the class or the CSS itself. Do not edit the kit files or modify plugin code.

Practical Scenario: Build a Department Homepage in One Pass

Consider a concrete example. You need to launch a homepage for a fictional city public safety department. The goal is for a visitor to understand within a minute where the news is, where the services are, where to call in an emergency, and how to send a non-emergency question.

Goal and preparation

Before you begin, Global Theme Style, Home, Header, Footer, News, Services, Contact, and MetForm Contact should already be imported. In WordPress, draft pages should already exist for the homepage, services, news, contacts, and FAQ. The menu can stay simple at first, without multi-level dropdown structures.

Setup steps

1. Create a page called "Home," open it in Elementor, and insert the Home template from the Chopz kit.
2. In the page settings, choose Elementor Full Width and hide the default page title if the theme displays it.
3. In the hero section, replace the slogan with a practical message and point the button to the contacts or services page.
4. In the news block, keep only the cards that will lead to real posts. Temporarily hide the rest or replace them with useful informational content.
5. In the services grid, create 6 cards for real visitor paths: requests, permits, records, traffic updates, public appointments, and non-emergency contacts.
6. In the emergency contacts block, replace the demo numbers with official information or remove the block until the information is confirmed.
7. Save the page and assign it as the static homepage through Settings - Reading.
8. Connect the global header through Jeg Kit and make sure the menu points to the pages you created.

Checking the result

Open the site as a normal visitor. Within the first 10 seconds, three things should be clear: who the site represents, where to click for services, and where to find contact information. Then test the paths: the hero button, service cards, news, menu, and form. If any route still leads to demo content, the page is not ready to publish.

Scenario note: if the site is already public, do not assign the new homepage until the full review is complete. First share the draft URL with the responsible staff, confirm the phone numbers and text, and only then publish.

Checking the Site After Setup and Launch

After importing and editing the kit, it is important to verify not just the appearance but the working paths. A polished Elementor layout can still hide serious problems: the form does not send email, the global header is not applied to inner pages, the images are not legally usable, the cache is showing an old version, or the mobile layout compresses the service cards badly.

Functional review

Walk through the site like a visitor who knows nothing about the organization's structure. Check the homepage, services page, contact page, FAQ, one news item, and one staff or department card. On each page, ask a simple question: is there a next step? If the page only looks informative but does not lead anywhere, add a link, a button, or a short instruction.

Technical review

After saving changes, clear both the site cache and your browser cache. If the design looks correct in the editor but wrong on the public page, use Elementor's tools to clear files and data, then check the page again in a private window. If the problem persists, temporarily disable the caching plugin on a staging copy and verify that it is not serving stale CSS files.

Also review the mobile version in Elementor's responsive mode. For Chopz, the most important areas are the menu, hero section, news cards, services grid, and form. If buttons are too small, long headlines break the card layout, or the contact block runs off the screen, fix the specific section rather than blindly changing global spacing.

Editorial review

Remove demo text, fictional addresses, temporary phone numbers, and sample names. Verify that all photos are legally cleared for publication. For the news cards, use real content or temporarily hide the block. Do not leave headlines that look like actual incidents if they came from the demo content.

How to Organize the Editorial Process After Launch

After publication, Chopz becomes more than a design. It becomes a working content system. A public safety or municipal department site usually has several responsible people: one handles news, another owns services, a third approves contact information, and a fourth monitors the form. Without an agreed update process, even a good Template Kit quickly loses discipline: some pages get updated, others keep outdated phone numbers, and others start collecting random styles.

The most practical approach is to split the site into stable areas and assign a simple operating rule to each one. For news, that rule might require a short headline, a category, a WordPress publication date, and a verified next-step link. For services, it might require the responsible department, a list of conditions, an up-to-date contact, and the date of the last internal review in an editorial document. For FAQ, it might require the source of the question and an answer already approved inside the organization. These internal notes do not have to be visible to visitors, but they make the site much easier to maintain.

What should not be handed to a random editor

A standard content editor can update text, images, links, and cards. But global colors, fonts, header, footer, form, and CSS are better restricted to a smaller group of users. The reason is simple: one careless edit can change the header on a single page only, disable the form, remove the header display condition, or replace a global color with a local one. In Elementor, that can happen by accident, especially when someone is editing visually and does not see the system-level connection between templates.

For safer support, create a short internal cheat sheet: which pages can be edited, which elements should not be touched, how to duplicate a service card, where to update the menu, and who to contact about the form. In practice, that kind of note is often more useful than long technical documentation because it captures your actual Chopz workflow.

How to update services without breaking the design

If a new service appears, do not build it from scratch in a separate style. Duplicate an existing Chopz card or section, replace the text and link, and then check the card heights in the row. If the new service is longer than the others, it is usually better to shorten the title and move the details to a dedicated page. The homepage should remain navigational: it helps people choose a path rather than explaining the full process.

For internal pages, use a consistent order: intro paragraph, who the service is for, what to prepare, how to submit the request, and how to check status or get a response. If every service follows the same logic, visitors can find their way faster and editors can maintain the site more easily.

When to rethink the structure instead of just adding more blocks

Over time, the site will accumulate new news items, new requests, and new pages. Do not keep pushing everything into the menu. Once the top navigation becomes crowded, visitors spend more time deciding where to click. Every few months, it helps to review analytics and user questions: which pages get opened most, which services generate form submissions, and which menu items nobody uses. Based on that, you can merge low-traffic sections, move important services to the homepage, or add FAQ content to a specific service page.

Chopz is convenient because its sections can be rearranged and reused, but that flexibility does not mean the homepage should expand forever. Sometimes the better move is to create a dedicated directional page and keep only one short card for it on the homepage. That keeps the site fast and the user path clear.

Limits and Tradeoffs for Performance, Security, and Maintenance

Chopz can give you a cohesive visual result quickly, but the site is still a WordPress project built on Elementor. That means speed, security, and long-term support depend not only on the template kit, but also on the hosting, plugin count, image quality, caching strategy, and editorial discipline.

Performance

A Template Kit can include a lot of sections, photos, icons, and widgets. On the Chopz homepage, keep only the blocks that genuinely help the visitor. If the organization does not publish news, do not keep a large news section just for visual effect. If you do not need a staff section, remove it or replace it with a short department overview. The fewer decorative sections you keep, the easier it is to maintain speed.

Optimize images before uploading them. Hero photos and news cards should be high enough quality to look professional, but they should not weigh as much as the original camera files. Use caching, modern image formats, and lazy loading, but always verify that the optimization does not break Elementor styling.

Security

Do not turn the contact form into a channel for sensitive information. For emergency reports, official statements, and personal data, use approved processes instead. Keep WordPress, Elementor, and the required plugins updated, but test changes on a site copy first. Be especially careful with plugins that add Elementor widgets: they expand what the site can do, but they also increase the support surface.

Content maintenance

Assign an owner to every page group. News should have a clear owner, services should belong to the responsible department, and FAQ should have an editor who collects recurring questions from the front desk or the form. Otherwise, the site quickly turns into a polished archive of outdated blocks.

When ThemeForest Chopz Is a Good Choice

Chopz is worth using if you need a fast, visually consistent Elementor-based site for a public safety agency, municipal department, fire department, security service, or a similar public-facing organization. The kit is especially useful when you need to assemble a homepage, services, news, FAQ, contacts, and a form in one consistent style, and the team is prepared to maintain the content through Elementor.

Before publishing, verify four things: the archive was imported as a Template Kit, the global styles are applied, the header and menu work on every page, and the MetForm form actually delivers messages. Then replace the demo photos, phone numbers, addresses, news items, and service cards with verified real data. Once those steps are complete, you can download the latest version of ThemeForest Chopz and test the kit on a staging copy of the site.

If the project requires complex agency integrations, strict government design compliance, a user account area, or minimal dependence on third-party builders, Chopz is better used only as a visual reference point. For a standard informational website with services, news, and contact details, it provides a strong starting point, but the final quality still depends on careful import, editorial discipline, and honest pre-launch testing.