Content & publishing

Find likely passive constructions without treating them as mistakes.

Review exact English grammar patterns, the sentences that contain them, and the ambiguous cases that still need human judgment. This is a transparent editing aid, not a writing-quality score.

  • Runs in your browser
  • Exact triggers shown
  • English heuristic
  • No signup required

Step 1 · Add an English sample

Paste the text to review.

Use complete prose rather than navigation labels or a keyword list. Findings clear whenever the text changes.

436 UTF-8 bytes1,048,576 maximum

Analysis runs in this browser. Plainview Tools does not fetch, upload, store, or send the text you enter.

Step 2 · Inspect the evidence

Likely passive patterns

Example result

Analysis complete. 3 likely passive sentences, 1 contextual review, across 8 sentences.

Likely sentences
3
Likely share
37.5%
Review in context
1
Total sentences
8
  1. Sentence 1Likely passive pattern

    The editorial calendar was approved by the team on Monday.

    • was approvedpast participle + nearby by-phrase
  2. Sentence 3Likely passive pattern

    Each source is checked before publication.

    • is checkedbe + past participle
  3. Sentence 5Likely passive pattern

    The final article will be reviewed by a second editor.

    • will be reviewedpast participle + nearby by-phrase
  4. Sentence 7Review in context

    The team was tired after a long launch week.

    • was tiredbe + past participle
Pattern occurrences3 likely · 1 contextual

Sentence boundaries: Intl.Segmenter. Latin-script coverage: 100.0%.

Passive voice is not automatically wrong.

It can emphasize the receiver, avoid blame, or work when the actor is unknown. Review each highlighted phrase in context; this tool does not assign a grammar, quality, accessibility, or search score.

What the detector looks for

A pattern review, not a grammar verdict.

Passive constructions commonly combine a form of be or get with a past participle. English also uses many of those participles as adjectives, so a deterministic detector has to preserve uncertainty instead of hiding it.

Be + past participle

was approved, has been reviewed, and will be published

Modal, perfect, and continuous auxiliary chains are included when the supported pattern is present.

Get + past participle

got delayed or gets updated

The informal get-passive is reported separately from an active use of get.

Review in context

was tired, is interested, and other state-like phrases

These may describe a state or use a participle as an adjective, so they are not counted as likely findings.

Version 1.0 boundary

This detector supports English prose. An 80% Latin-script coverage guardrail prevents obviously unsupported samples, but it is not language detection.

Likely findings require an English be or get auxiliary followed by a regular or curated irregular past-participle candidate, with a small allowance for negation and adverbs.

Some past participles also act as adjectives or describe a state. Those forms are separated into Review in context unless a stronger nearby signal is present.

The heuristic can miss reduced clauses, rare irregular verbs, dialect forms, unusual punctuation, and passive meaning expressed without the supported auxiliary patterns.

Sentence totals share Plainview Tools' browser-only text foundation. Highlight offsets use Intl.Segmenter when available and a conservative punctuation fallback otherwise.

Grammar and segmentation sources

Review the evidence behind the method.

Source check: August 24, 2026. Grammar references establish the supported passive forms and their legitimate uses. Unicode guidance informs sentence-boundary handling; Plainview Tools documents its narrower detection rules and blind spots above.