TIME IS RUNNING OUT FOR 2026 TAX WRITE-OFFS

Keeping Voice Writing in the Intended Window on a VOX Laptop

A voice-writing workspace is easier to use when the reporter can identify the active document, the intended insertion point, and the selected recognition route before speaking. A short rehearsal makes those connections visible. By following one unique phrase from the microphone to its saved CAT location, a reporter can practice moving between windows while keeping the text destination clear.

Martel VOX Elite laptop; screen display simplified for illustration.

This guide builds a nonconfidential two-window rehearsal on a Windows 11 VOX laptop. It uses two clearly named practice documents, unique spoken cues, an intended CAT practice job, and one planned harmless notification. The exercise records which window was active, where recognized text appeared, what the CAT job saved, and whether an apparently missing phrase was actually inserted somewhere else.

All window names, spoken phrases, times, notifications, jobs, observations, and results are invented and illustrative. They do not describe an actual reporter, customer, proceeding, or product result. Use the supported instructions for the exact Stenomask or microphone, recognition route, CAT application, Windows 11 setup, and training method involved.

Identify four text-location observations

When a phrase is not where you expected, record what you can observe at each stage. These four labels give an instructor or support specialist a clear starting point for explaining the supported route:

  1. No recognized text observed. The phrase was spoken, but no text has yet been found in the expected output or either practice window.
  2. Recognized text found in the unintended window. The words appear, but the active insertion point belonged to the wrong application or field.
  3. Recognition visible, CAT result absent. The selected recognition route shows the phrase, but the expected CAT location does not contain or save it.
  4. Text present at an unexpected place in the intended job. The correct application received the phrase, but the cursor, field, pane, or job location was not the one the reporter intended.

These labels describe observations, not causes. A text destination can be affected by the active window, an application-specific command, the supported connection between recognition and CAT, a dialog box, a selected field, or an operator action. The first safe task is to find the words and preserve the state.

The published transcription foot-pedal focus guide also checks active windows, but it asks which application receives a pedal transport command while a typist works in another document. This article is different: it traces spoken recognition through a VOX workflow and asks where the recognized phrase and saved CAT result went.

Keep the recognition routes separate

Record the actual release and recognition choice beside your window-routing diagram. EclipseVox works with Dragon or Speechmatics. According to the publisher’s version table, Eclipse 10 and 11 support the local Speechmatics arrangement, whereas Eclipse 12 has local and cloud options. Use the matching setup instructions for the route you plan to follow.

  • Dragon is a local recognition route with its own profile, microphone state, supported applications, and correction workflow.
  • Cloud Speechmatics sends recognition work through the supported online route and therefore has a network and cloud-session state to check.
  • Local Speechmatics Enhanced uses the EclipseVox publisher’s designated local arrangement: its Boost Box or a qualifying laptop supplied by the publisher.

For local Speechmatics Enhanced, confirm the publisher-designated hardware arrangement separately from the Windows 11 laptop and the Dragon license. Record the recognition route selected for the rehearsal and follow the publisher’s current instructions for that route. This gives each software option its own clearly identified setup and practice record.

Use one currently supported recognition route for each complete window-destination exercise. If you later practice with another route, create a separate result sheet and follow its setup instructions. Keep any transition between routes within the training plan approved for your software and work. This worksheet provides a record of the selected arrangement rather than a comparison of recognition products.

The Martel VOX laptop buyer’s guide explains why the Stenomask, recognition route, CAT environment, licenses, and setup help must be treated as one planned workflow. The window rehearsal begins only after that supported arrangement is identified.

Name the two practice windows so a mistake is obvious

Open two expendable, nonconfidential practice documents. Give each a large, unmistakable heading:

  • AMBER DESTINATION — INTENDED
  • BLUE DISTRACTOR — DO NOT DICTATE HERE

Use a supported document field or application for each window. The intended window should represent the location that is supposed to receive text during this harmless rehearsal. The distractor should be a disposable local practice document, not email, messaging, a search box, a live form, or a customer record.

Use different background colors only if the applications support them and the change does not alter the recognition method. Color is a secondary cue. The title, application name, document name, and insertion point remain the evidence.

Place this fixed line at the top of each document:

This is invented window-routing practice. No client or proceeding information belongs here.

Save both documents before recognition begins. If unexpected text appears, it will land in a harmless place that can be inspected and discarded according to the normal practice-file procedure.

Do not open a real transcript beside the rehearsal. A window-focus test deliberately creates an opportunity for input to reach the wrong place. Close or save production work first, then use only the two named practice documents and the intended practice CAT job.

Create spoken cues that identify the intended destination

The exercise uses short, unique phrases that are easy to search. The cues should not resemble real names, legal language, passwords, addresses, or matter details.

Use these invented examples:

  • Amber route seven begins.
  • Cedar bridge confirms the amber destination.
  • Blue route nine is a distractor check.
  • Harbor window ends the rehearsal.

The words amber, cedar, blue, and harbor create four search anchors. If the first phrase is missing from the CAT job, search the two practice windows and any supported recognition-result view for the complete cue. Do not search across confidential applications or an uncontrolled account.

Speak at the trained volume and mask position used for harmless practice. Do not exaggerate the delivery to make recognition appear better. The purpose is destination tracing, not an accuracy score. Preserve the initial output without silently correcting it before the location is recorded.

If recognition substitutes one word, record the visible form. For example, if Amber route seven begins becomes Amber root seven begins, search for both the intended cue and the observed form. A substitution does not erase the routing evidence; it simply changes the text that must be traced.

Draw the supported route before testing

Write one line that describes what should happen. Examples:

Stenomask → selected recognition route → intended supported CAT practice location → saved CAT practice job.

For a standalone Dragon practice window, the line may instead be:

Stenomask → Dragon profile and microphone state → active supported practice document → saved local practice copy.

For EclipseVox with cloud Speechmatics on a supported release, use a diagram such as this to organize observations for the configured route:

Stenomask → EclipseVox cloud Speechmatics session → visible recognition state → intended CAT practice location → saved CAT practice job.

For local Speechmatics Enhanced, record the publisher-approved hardware condition:

Stenomask → EclipseVox local Speechmatics Enhanced on the publisher’s Boost Box or qualifying publisher laptop → intended CAT practice location → saved CAT practice job.

These diagrams organize practice observations. Adapt the chosen diagram to the setup approved for the installed release, including any separate recognition device. During the test, mark every stage confirmed, not observed, not applicable, or unresolved.

Record five states, not one green indicator

A microphone indicator can confirm activity without proving the destination of text. A CAT cursor can blink without proving recognition is ready. Record five distinct states:

State Question Evidence to keep
1. Voice input Did the intended Stenomask or microphone show the expected supported input state? Visible selected device and application input state
2. Recognition Did the selected route show ready/listening status and any initial output? Route name, profile or session label, exact visible status
3. Window focus Which application, document, field, or pane owned the insertion point before speech? Title, highlighted window, cursor location, harmless screenshot if allowed
4. Text destination Where did the recognizable cue actually appear? Exact cue as displayed and its document/location
5. Saved CAT result Did the intended practice job retain the phrase after the supported save and reopen check? Job name, line or field, saved result

Do not mark a row confirmed because another row passed. A moving input meter does not confirm recognized words. Recognized words in a result pane do not confirm the CAT save. A saved CAT phrase does not prove which window was active when the reporter began speaking unless the focus state was recorded.

Establish the ordinary baseline

Begin with every unrelated application closed. Open the selected recognition route, the intended CAT practice job or supported destination, and the two named practice documents. Make the AMBER DESTINATION — INTENDED window active according to the supported workflow.

Before speaking, confirm:

  • the correct practice job or document name;
  • the intended user, profile, or session;
  • the selected Stenomask or microphone;
  • the visible recognition state;
  • the insertion point after the heading in the intended location;
  • the distractor document is saved and inactive;
  • no modal dialog is waiting behind another window.

Speak Amber route seven begins. Stop. Do not continue with a paragraph until the first cue is located. Record its exact form and location. Then speak Cedar bridge confirms the amber destination and locate it.

Save through the application’s supported process. Close and reopen only the harmless working copy if the workflow calls for a saved-result check. Confirm that both phrases are present where expected. This baseline must pass before a notification is introduced.

If a baseline item still needs confirmation, pause the staged test before adding the notification. Preserve the five-state table and ask the responsible setup or support contact which stage to check next. Complete the ordinary arrangement first so the notification exercise answers one clearly defined question.

Prove that the distractor is detectable

The distractor window is not intended to receive voice-writing text. It exists to make accidental routing visible. Click inside BLUE DISTRACTOR — DO NOT DICTATE HERE only during the deliberate distractor check, after the baseline is saved.

Place the insertion point after its heading and speak Blue route nine is a distractor check. Record where the phrase appears. This result demonstrates what an unintended destination looks like under the tested supported arrangement. It does not prove that every application accepts recognition in the same way.

Immediately stop recognition or use the supported microphone-off action before moving between windows. Save the distractor only long enough to preserve the evidence. Then remove the inserted test phrase or close without saving according to the practice plan.

Return to the intended CAT practice location. Confirm the title, job, field, cursor, and recognition state again. Speak Harbor window ends the rehearsal. The cue must appear in the intended location for the return step to pass.

This deliberate wrong-window run creates a reference. Later, if a phrase seems missing, the reporter knows what to search for and what an unintended insertion looks like without experimenting inside a real case.

Add one harmless Windows 11 notification

A notification can draw attention away from the working window. It does not automatically prove that focus changed. The rehearsal should observe what happens rather than assume that every banner steals the insertion point.

Use a planned local notification that contains no client information, such as an authorized timer or a harmless test reminder. Do not use email, court messaging, team chat, calendar details, security alerts, or a real customer communication as the test source. Turn off preview content if the screen may be seen by others.

Prepare the intended location with the cursor after the heading. Record the five states. Trigger the harmless notification and do not click it. When it appears, record:

  • whether the intended application title still appears active;
  • whether the insertion point remains visible;
  • whether a dialog or panel opened;
  • whether recognition state changed;
  • whether the CAT job, practice document, or another window moved in front;
  • whether the notification disappeared without an operator action.

Then speak Amber route seven begins once. Locate the result before doing anything else. If the cue appears correctly, record notification observed; destination unchanged in this run. Do not turn one passing run into a promise about every future notification or application.

If the cue appears elsewhere, record the exact destination and the action that preceded it. If no cue is found, mark the result unresolved and follow the search sequence below. Do not repeat the phrase several times, because duplicates can obscure which utterance produced which text.

Search for an apparently missing phrase in a safe order

When the cue is absent from the expected CAT line or field, stop speaking. Repeated dictation can send more text to the same unintended place. Preserve the visible state and search in this order:

  1. Current CAT location. Check the active line, field, pane, and nearby text. Look above and below the expected cursor position.
  2. Other location in the same practice job. Check a selected note, command, search, caption, or dialog field only if that field is part of the supported application and contains no protected material.
  3. Recognition-result view. If the selected Dragon, Speechmatics, or EclipseVox workflow provides a documented recognition-output view, inspect it for the observed phrase while keeping the same recognition route.
  4. Amber intended practice document. Search the complete unique cue and its observed substitution.
  5. Blue distractor practice document. Search the complete unique cue and its observed substitution.
  6. Windows foreground history from your notes. Review the application title or harmless screenshot captured at the event. Do not install an unapproved tracking utility.
  7. Saved CAT practice job. Use the supported save and reopen check after the current state has been recorded.

Mark each location found, not found, not checked, or not applicable. “Not found” means the defined search was completed. It does not prove that the text never existed.

If the text appears in a password field, message, email, web form, or other inappropriate destination, stop and follow the organization’s information-handling and incident procedure. Do not copy the phrase into additional places merely to document it.

Distinguish focus from CAT routing

Window focus describes which application or control receives ordinary input at a moment. CAT routing describes the supported path by which recognition reaches the reporting job. Each needs its own check and a clear note about the state observed during the rehearsal.

Consider three illustrative outcomes:

Outcome A: text in the alternate practice application

The Windows title and cursor belong to the blue distractor. The phrase Amber route seven begins appears there. The recognized phrase followed that active destination. Record the application, stop recognition, preserve the harmless text, and return to the intended location using the supported workflow.

Outcome B: text in another field of the intended application

The CAT application is active, but a search field or note pane owns the cursor. The phrase appears in that field rather than the transcript location. The application name alone was not enough; the field and insertion point mattered.

Outcome C: recognition visible, CAT text absent

The selected recognition route shows the phrase, but neither practice document nor the expected CAT location contains it. Do not call this a wrong-window result yet. The supported connection between recognition output and the CAT destination remains unresolved.

These outcomes require different questions. A screenshot of a title bar may settle Outcome A but not Outcome C. A CAT save-and-reopen check may settle whether text was retained but not which window owned the cursor before speech.

Use a four-pass routing grid

Run the grid in a harmless practice session. Reset to the same starting state before every pass.

Pass Planned condition Spoken cue Required observation
A. Intended baseline Amber intended destination active Amber route seven begins Cue location, focus, CAT save
B. Deliberate distractor Blue distractor active by plan Blue route nine is a distractor check Cue location and safe cleanup
C. Return to intended Amber or supported CAT destination restored Harbor window ends the rehearsal Cursor, cue location, CAT save
D. Harmless notification Intended destination prepared; notification appears without a click Cedar bridge confirms the amber destination Focus before/after, cue location, recognition and CAT state

For every pass, record the same five states. Keep the recognition route, user or profile, Stenomask, practice job, Windows sign-in, application releases, and spoken delivery unchanged. The planned window condition is the only deliberate variable.

If a pass produces an unexpected result, do not repair it silently and continue. Mark the point of divergence. Reset only after the evidence is preserved and the supported recovery method is known.

Confirm the destination before moving text

Finding text in the blue distractor does not automatically authorize copying it into the CAT job. In a harmless rehearsal, you can preserve the result and then recreate the intended phrase according to the supported practice method. In real work, corrections must follow the reporter’s professional and application procedures.

Do not drag text between windows while recognition remains active. Do not paste a phrase into a field without confirming the job, location, speaker, punctuation, and source. Do not delete unexpected text until the appropriate record or incident requirement is satisfied.

Use this recovery note:

Spoken cue: Amber route seven begins. Intended location: Cedar Practice job, line 12. Found location: Blue Distractor practice document after the harmless notification. Recognition route: recorded separately. Action: recognition stopped; harmless state preserved; no production text involved; supported reset requested.

The note identifies what was intended, what was found, and what was not done. It does not claim why the destination changed.

After resetting, confirm the intended title, field, cursor, and route. Speak a new cue rather than repeating the old one. For example, use Harbor window ends the rehearsal. A new cue prevents the recovery run from being confused with text left from the first run.

Prepare a focused support packet

If the routing result cannot be explained from the practice record, prepare a small support packet. Include:

  • customer-facing Martel product name;
  • Windows 11 edition and version if requested;
  • recognition route: Dragon, cloud Speechmatics, or publisher-approved local Speechmatics Enhanced;
  • EclipseVox or CAT application name and release;
  • Stenomask or microphone customer-facing name and connection path;
  • intended practice job, field, and cursor location;
  • exact harmless cue spoken;
  • exact visible recognition result;
  • exact window or field where the cue was found;
  • whether the notification was clicked;
  • five-state table for the passing baseline and unexpected pass;
  • redacted harmless screenshot if the approved support method permits it.

Do not send real case files, dictionaries, profiles, account credentials, license keys, or broad system logs unless the authorized support person requests them through an approved method. A support packet should reproduce the harmless routing question without exposing work.

Ask one precise question:

In the harmless window-routing practice run, Dragon showed the cue while the CAT practice location remained empty, and neither named document contained the text. Which supported connection or application state should be checked next for this exact workflow?

Replace Dragon with the selected route when another route was actually used. Do not name several engines to make the report sound complete.

Prepare the rehearsal with a Martel VOX laptop

Use the current Martel VOX Elite Voice-Writing Laptop Package listing to discuss the recognition route and CAT workflow you plan to use. Keep the accepted order with the setup notes, including the software and preparation selected, current warranty, support arrangements and first practice appointment. The two-window exercise can then become a useful part of learning the delivered setup.

Browse the Voice Writers VOX Dragon Laptops category for current packages. Tell Martel which recognition route you use, which CAT application is part of the workflow and which Stenomask or microphone you already own. Together, identify the licenses, profiles, CAT files, input setup and practice checks to prepare for your appointment.

Bring the names of the two practice documents and an invented spoken cue to the setup session. Ask the person helping you to follow that cue through the configured recognition route into the intended CAT location. Save the completed practice record with the setup notes so you can repeat the same routine when your working arrangement changes.

One-page routing acceptance record

Complete this record before relying on the workflow:

Field Entry
Martel package or order identifier
Test date
Windows 11 version if required
Stenomask or microphone
Recognition route
Publisher hardware condition if local Speechmatics Enhanced
CAT application and practice job
Amber intended destination
Blue distractor destination
Baseline cue and result
Deliberate distractor cue and result
Return cue and result
Harmless notification source
Notification clicked?
Focus before and after notification
Recognition result location
CAT saved-result check
Confirmed, needs follow-up, or unresolved
Unresolved question and owner

Confirmed means each cue reached its planned harmless destination, the reporter could identify the active field before speaking, the notification run was observed without assumption, and the intended CAT result survived the supported save check. Needs follow-up means a specific checklist item needs another supported check. Unresolved means the available observations do not yet identify the route or destination state.

Keep an unresolved checklist item open until its required observation is confirmed. Finding the text answers where. Support may still need the recorded window, field, and route states to explain the sequence and help you complete the intended practice arrangement.

Complete illustrative result

In this invented example, Reporter Morgan uses Dragon as the single selected recognition route. The intended CAT practice job is named Cedar Practice. The disposable documents are AMBER DESTINATION — INTENDED and BLUE DISTRACTOR — DO NOT DICTATE HERE.

Pass A succeeds. The CAT practice location is active, the phrase Amber route seven begins appears at the planned line, and the supported save-and-reopen check retains it. Pass B also behaves as planned: after the reporter deliberately activates the blue document, Blue route nine is a distractor check appears there. Recognition is stopped, and the harmless result is recorded.

For Pass C, Reporter Morgan restores the CAT job, confirms the field and cursor, and speaks Harbor window ends the rehearsal. The phrase reaches the intended location and is retained.

During Pass D, a harmless local timer notification appears. Reporter Morgan does not click it. The CAT title still appears active, but the cursor is not visible because a small application dialog opened in front. The reporter stops before speaking, closes the harmless dialog through the supported action, confirms the CAT cursor, and restarts the pass with a new cue. The second notification observation leaves the intended field active, and Cedar bridge confirms the amber destination reaches the CAT practice location.

The result is passed with a documented pre-speech cursor check. It does not prove that all notifications are harmless or that every future application behaves the same way. It shows that the reporter observed an ambiguous state, did not dictate into it, restored the supported destination, and preserved the exact practice result.

This illustrative result covers the selected Dragon practice only. Prepare a separate practice record for cloud Speechmatics or local Speechmatics Enhanced, using the publisher’s instructions for the installed release. For local Speechmatics Enhanced, include the specified Boost Box or qualifying publisher laptop in that setup record.

Final checklist

  • Save and close production work before the rehearsal.
  • Use two disposable documents with unmistakable titles.
  • Use invented spoken cues that can be searched safely.
  • Record the selected recognition route; do not combine engine names.
  • Preserve the publisher hardware condition for local Speechmatics Enhanced.
  • Confirm the intended job, field, cursor, profile or session, and microphone before speech.
  • Record input, recognition, focus, text destination, and CAT save as separate states.
  • Pass the ordinary baseline before introducing a notification.
  • Create one deliberate distractor result so an unintended destination is recognizable.
  • Use a harmless local notification with no client information.
  • Observe whether focus changed; do not assume the notification changed it.
  • Stop speaking when a cue is missing.
  • Search the intended CAT location, supported recognition view, and two practice documents in order.
  • Preserve unexpected text before resetting.
  • Use a new cue for the recovery run.
  • Ask support one route-specific, evidence-backed question.
  • Confirm current product, licensing, setup, warranty, and support terms in writing.

Questions and answers

1. Where should I look when a phrase is not at the intended insertion point?

Check the intended field, the nearby CAT text, the two named practice documents, and the supported recognition-result view in the order described above. Stop speaking while you locate the phrase, and record the exact destination before choosing the next supported action.

2. Why do I need two clearly named practice windows?

They make an unintended destination obvious without exposing real work. The amber title marks the intended location, while the blue title marks the disposable distractor. A unique spoken cue can then be traced safely between them.

3. May the distractor be my email or messaging application?

No. Use a disposable local practice document. Email, chat, search boxes, forms, and customer systems can send, expose, or retain unexpected text. Close production and communication applications before the rehearsal.

4. Should I run the exercise inside a live CAT job?

No. Use a nonconfidential practice job and invented phrases. A routing test intentionally changes active windows and fields. A live proceeding is not the place to discover where an unexpected cue will be inserted.

5. Is Dragon the same as Speechmatics in EclipseVox?

Dragon and Speechmatics are separate recognition options in EclipseVox. Follow the instructions for the chosen option and installed release. Cloud Speechmatics uses the supported online arrangement; local Speechmatics Enhanced uses the publisher’s designated local hardware. Give each practice session a clearly named route and its own result sheet.

6. What is required for local Speechmatics Enhanced?

Put the hardware purchase on the local practice plan: EclipseVox’s publisher requires either its Boost Box or a qualifying laptop bought from that publisher for Speechmatics Enhanced to run locally. Add the supported connections and the setup instructions for the device you selected.

7. Can I switch recognition engines when words go missing?

Do not switch engines during a production assignment merely to chase text. Preserve the current state, follow the supported contingency, and test another route separately in a harmless practice job under current publisher guidance.

8. Does a moving microphone meter prove the phrase was recognized?

No. It may show an input state, but recognition and destination are separate. Record the selected device, recognition result, active window or field, actual text location, and CAT saved result as five different observations.

9. Does a blinking CAT cursor prove speech will go there?

No. A cursor can be visible while recognition is not ready or while another dialog or field owns input. Confirm the application, practice job, field, insertion point, and selected recognition state before speaking the cue.

10. What if the cue appears in the right application but the wrong field?

Record the exact field, stop recognition, and preserve the harmless result. This is different from text entering another application. Restore the supported CAT location and use a new cue for the recovery check.

11. Why should each phrase be unique?

Unique cues connect one utterance to one pass. Repeating the same phrase can create duplicates in several windows and make the sequence ambiguous. Amber, blue, cedar, and harbor cues give each step a separate search anchor.

12. What if recognition substitutes one word in the cue?

Record the visible substitution and search both the intended wording and the observed form. A substitution affects recognition accuracy, but the displayed phrase can still reveal which window or field received the output.

13. Does every Windows 11 notification change window focus?

No. The exercise observes whether focus or the insertion point changed in the tested run. Do not assume that a banner steals focus, and do not treat one passing notification as a guarantee about every application or future notification.

14. What notification should I use for practice?

Use an authorized harmless local timer or test reminder with no client information. Do not use real email, court messages, team chat, calendar details, or security alerts. Record whether you clicked it; the planned pass should not require a click.

15. What should I do first when a phrase is absent?

Stop speaking. Preserve the visible state, then check the expected CAT line or field, nearby locations in the same practice job, the supported recognition-result view, and the two named practice documents in the recorded order.

16. Should I dictate the phrase again immediately?

No. Repetition can send more text to the same unintended place and confuse which utterance produced which result. Locate or classify the first cue, reset through the supported method, and use a new cue for recovery.

17. Can I copy unexpected text from the blue document into the CAT job?

Do not move it blindly. In harmless practice, preserve the routing result and recreate the intended phrase according to the supported procedure. In real work, follow professional correction, source, and application requirements before changing a record.

18. How is this different from a foot-pedal focus test?

A foot-pedal test asks which application receives playback or transport commands while typing continues elsewhere. This VOX rehearsal traces spoken recognition, the active destination, the recognition-result state, and the saved CAT outcome.

19. What if recognition shows the phrase but CAT does not?

Mark recognition visible, CAT result absent. Do not call it a wrong-window event until the named practice windows and intended CAT locations are checked. Ask support which supported connection or application state should be examined next.

20. Should I save screenshots?

Only harmless, redacted screenshots through the approved method. A useful image shows the application title, practice document or field, cursor, and exact cue without exposing client material, credentials, license keys, account details, or unrelated notifications.

21. What must pass before I introduce the notification?

The ordinary baseline must show the intended route, active destination, recognized cue, and saved CAT result. If any of those items needs confirmation, preserve the practice record and ask for the next supported check before adding the notification variable.

22. What should I ask Martel before relying on the laptop?

Ask which recognition route, CAT workflow, licenses, Stenomask setup, file transfer, and practice checks are included for the current package. Confirm the written order, current product terms, warranty, and support responsibilities.

23. When should I repeat the window-destination rehearsal?

Repeat it after a supported change to the recognition route, CAT release, practice-window arrangement or notification routine. Use a fresh invented cue and record the date and changed item. Keep the earlier result as a reference for the setup used at that time.

24. What should I save in the final acceptance record?

Save the route name, publisher hardware condition when applicable, practice job, two window titles, cues, five-state results, notification source, whether it was clicked, CAT save check, pass status, and any assigned unresolved question.

Martel Electronics