Persian can place passive, perfect, future, subjunctive, modal, negation, and clitic layers around one lexical event. A form such as بررسی شده باشد is ordinary formal Persian; ممکن است بررسی شده بوده باشد is structurally interpretable but expensive to process. Advanced editing requires two judgments at once: is the stack grammatically well formed, and does every layer earn its place?
The answer is not “avoid auxiliaries.” Auxiliary structure expresses real distinctions. The practical method is to parse from the lexical event outward, identify the agreement-bearing finite site within each auxiliary chain, establish scope, and then replace any recoverable layer with a time phrase, explicit subject, or separate clause. A matrix predicate such as ممکن است has its own finite verb outside the embedded chain, while the داشتن + می-verb progressive exceptionally has matched agreement on both verbs.
Build outward; read inward
| Surface stack | Layers from inside outward | Finite element | Register |
|---|---|---|---|
| بررسی شد | review + passive past | شد | neutral/formal |
| بررسی شده است | review + passive + perfect | است | neutral written |
| باید بررسی شده باشد | review + passive + anteriority + modal inference/requirement | باشد | formal-neutral |
| بررسی شده خواهد بود | review + passive + predicted future result | خواهد | marked formal |
| بررسی شده بوده باشد | review + passive + anterior-to-past + subjunctive | باشد | rare, highly formal |
Start with the lexical predicate, not the leftmost word. In باید تا حالا بررسی شده باشد, the inner event is بررسی کردن; شدن passivizes it; the perfect subjunctive presents it as anterior but nonasserted; باید adds an outer inference or requirement.
با توجه به تاریخ ثبت، درخواست باید تا حالا بررسی شده باشد.
bâ tavajjoh be târikh-e sabt, darkhâst bâyad tâ hâlâ barrasi shode bâshad.
Given the registration date, the application must have been reviewed by now. (formal-neutral; epistemic باید over perfect passive)
طبق برنامه، پرونده باید تا فردا بررسی شده باشد.
tebq-e barnâme, parvande bâyad tâ fardâ barrasi shode bâshad.
Under the schedule, the file must have been reviewed by tomorrow. (formal; deontic requirement for a future result)
The same shape supports different modal force. با توجه به تاریخ ثبت supplies evidence and favors inference; طبق برنامه supplies a rule and favors obligation. Morphology alone does not decide every outer scope.
Agreement belongs to the outer finite layer
Past participles are invariant. In a simple passive, finite شدن agrees: نامهها فرستاده شدند. In perfect subjunctive, final باشـ agrees: نامهها فرستاده شده باشند. In formal future, خواهـ carries agreement and the following short stem is invariant: نامهها فرستاده خواهند شد.
ممکن است پاسخها به نشانی قدیمی فرستاده شده باشند.
momken ast pâsokh-hâ be neshâni-ye qadimi ferestâde shode bâshand.
The replies may have been sent to the old address. (formal-neutral; plural agreement on باشند)
نسخههای اصلاحشده عصر امروز منتشر خواهند شد.
noskhe-hâ-ye eslâh-shode asr-e emruz montasher khâhand shod.
The revised versions will be published this afternoon. (formal future passive; agreement on خواهند)
Multiple visible verbs do not mean multiple independent subjects. Agreement on a participle or short stem is a warning that the writer has imported an English auxiliary chain rather than built the Persian construction.
Negation reveals scope
Where negation appears determines what is denied. Compare prohibition with a positive requirement for nonoccurrence:
این اطلاعات نباید پیش از اعلام رسمی منتشر شود.
in ettelâ'ât na-bâyad pish az e'lâm-e rasmi montasher shavad.
This information must not be published before the official announcement. (formal; prohibition)
طبق توافق، نام شاهد باید در گزارش منتشر نشود.
tebq-e tavâfoq, nâm-e shâhed bâyad dar gozâresh montasher na-shavad.
Under the agreement, the witness's name is required not to appear in the report. (formal; positive requirement scopes over a negated event)
In many practical contexts both keep information out of a document, but their logic differs. نباید P prohibits P; باید نه-P makes non-P the required outcome. The latter is marked and should be used only when contrast or legal precision makes that scope relevant.
Possibility creates another minimal contrast:
ممکن است پیوست دریافت نشده باشد.
momken ast peyvast daryâft na-shode bâshad.
The attachment may not have been received. (possibility over a negative event)
ممکن نیست پیوست بدون امضا دریافت شده باشد.
momken nist peyvast bedun-e emzâ daryâft shode bâshad.
It is impossible that the attachment was received without a signature. (negation over possibility)
Moving نـ is not stylistic cleanup. It changes the proposition. Stacked Irrealis and Modal Scope develops these logical contrasts.
Clitics need a licensed host
In a perfect stack, the lexical participle is not freely available as an object-clitic host. Neutral edited prose should prefer a full pronoun or noun phrase: آن را بررسی کرده بودیم. In suitable conversational contexts a clitic can appear on an earlier nonverbal element or the finite auxiliary, but stacking already raises processing cost, so compactness is not always clarity.
این پیوست را قبلا بررسی کرده بودیم، اما نسخهی نهایی نبود.
in peyvast râ qablan barrasi karde budim, ammâ noskhe-ye nehâyi na-bud.
We had reviewed this attachment before, but it was not the final version. (neutral; full object keeps the stack transparent)
فایل را باز کرده بودیمش، ولی صفحهی آخر نمایش داده نمیشد.
fâyl râ bâz karde budim-ash, vali safhe-ye âkhar namâyesh dâde nemi-shod.
We had opened the file, but the final page was not displaying. (careful conversation; doubled object clitic on finite auxiliary)
The second form is possible but marked. It illustrates host placement; it is not a recommendation for formal prose. The dedicated Object Clitics on Infinitives and Participles distinguishes object, possessor, and performer readings.
Grammatical does not guarantee usable
Persian can recursively participialize auxiliaries. امضا شده بوده باشد combines passive شده, anterior auxiliary participle بوده, and final subjunctive باشد. It is defensible when a present hypothesis concerns an event earlier than a separately established past reference point. Without that three-way timeline, the form is unnecessary.
بعید است نسخه پیش از جلسهی دیروز امضا شده بوده باشد.
ba'id ast noskhe pish az jalase-ye diruz emzâ shode bude bâshad.
It is unlikely that the copy had been signed before yesterday's meeting. (highly formal; past-perfect subjunctive passive)
If the only point is uncertainty about prior signing, ordinary perfect subjunctive is clearer:
بعید است نسخه پیش از جلسه امضا شده باشد.
ba'id ast noskhe pish az jalase emzâ shode bâshad.
It is unlikely that the copy was signed before the meeting. (clear formal-neutral)
Marked future perfects invite the same test. تا آن زمان منتشر نشده خواهد بود is grammatical formal projection, but تا آن زمان منتشر نمیشود usually communicates the deadline more naturally.
با برنامهی فعلی، گزارش پیش از پایان هفته منتشر نمیشود.
bâ barnâme-ye fe'li, gozâresh pish az pâyân-e hafte montasher nemi-shavad.
Under the current schedule, the report will not be published before the end of the week. (clear formal-neutral; futurate present replaces a heavy negative future perfect)
The shorter revision must preserve the intended viewpoint. If a technical forecast explicitly evaluates the resultant state at a future checkpoint, the future perfect may be justified. Editing is semantic accounting, not automatic deletion.
A five-pass editing method
- Event: circle the lexical noun or participle: بررسی، امضا، ارسال.
- Voice: decide whether شدن is passive, change of state, or part of a lexical compound.
- Time and mood: identify the final finite verb and its reference point.
- Scope: paraphrase each modal and negation as a full clause.
- Readability: if two interpretations remain live or the reader must backtrack, restore an agent, add a time phrase, or split the sentence.
ممکن است پرونده ناقص بوده باشد؛ بنابراین دبیرخانه آن را دوباره بررسی میکند.
momken ast parvande nâqes bude bâshad; banâbarin dabirkhâne ân râ dobâre barrasi mi-konad.
The file may have been incomplete; therefore, the secretariat will review it again. (clear formal; hypothesis and response split into two clauses)
This version exposes two propositions and names the second agent. Compressing everything into one passive-modal chain would save punctuation while making causal responsibility harder to recover.
Common Mistakes
1. Giving agreement to the participle
❌ پاسخها فرستادهاند شده باشند.
Incorrect — the participles are invariant; plural agreement belongs on final باشند.
✅ احتمال دارد پاسخها به پوشهی هرزنامه فرستاده شده باشند.
ehtemâl dârad pâsokh-hâ be pushe-ye harz-nâme ferestâde shode bâshand.
The replies may have been sent to the spam folder.
2. Negating the wrong layer
⚠️ ممکن نیست نامه رسیده باشد یعنی شاید نامه نرسیده باشد.
momken nist nâme reside bâshad ya'ni shâyad nâme na-reside bâshad.
The sentence is grammatical, but the asserted equivalence is false: impossibility of arrival is stronger than possibility of nonarrival.
✅ شاید نامه هنوز نرسیده باشد، اما رسیدنش ناممکن نیست.
shâyad nâme hanuz na-reside bâshad, ammâ residan-ash nâ-momken nist.
The letter may not have arrived yet, but its arrival is not impossible.
3. Using a full infinitive inside formal future
❌ پرونده بررسی خواهد شدن.
Incorrect — future خواستن selects the short infinitive شد, not شدن.
✅ پرونده پس از تکمیل مدارک بررسی خواهد شد.
parvande pas az takmil-e madârek barrasi khâhad shod.
The file will be reviewed after the documents are completed. (formal)
4. Attaching the object clitic to the lexical participle
❌ فایل را بررسی کردهاش بودیم.
Incorrect for “we had reviewed it” — کرده is not the object-clitic host in this perfect stack.
✅ آن فایل را پیش از ارسال بررسی کرده بودیم.
ân fâyl râ pish az ersâl barrasi karde budim.
We had reviewed that file before sending it.
5. Combining indicative and subjunctive endings
❌ شاید فرم امضا شده بوده است باشد.
Incorrect — a single chain cannot close first with indicative است and then again with subjunctive باشد.
✅ شاید فرم را پیش از ارسال امضا کرده باشند.
shâyad form râ pish az ersâl emzâ karde bâshand.
They may have signed the form before sending it. (clear neutral; ordinary perfect subjunctive)
Key Takeaways
- Parse from lexical event outward, but locate finite agreement from the right edge inward.
- Participles and short infinitives stay invariant; the outer finite auxiliary carries agreement.
- Negation placement determines scope, so never move نـ merely to improve rhythm.
- Clitics require a licensed host, but full objects are usually clearer inside long stacks.
- A rare stack is justified only when its passive, temporal, modal, and scope layers all contribute independently recoverable meaning.
Now practice Farsi
Reading grammar gets you part of the way. The exercises are where it sticks — free, no signup needed.
Start learning Farsi →Related Topics
- Perfect SubjunctiveB1 — Form and use the Persian perfect subjunctive—رفته باشم and its paradigm—to place an earlier event inside doubt, possibility, desire, or evaluation.
- Past Perfect SubjunctiveB2 — Parse and use the rare layered form رفته بوده باشم when a proposition is both anterior to a past reference point and subject to present modality.
- Future PerfectB2 — Interpret the marked construction رفته خواهد بود, form its auxiliary stack correctly, and choose more natural Persian deadline constructions in ordinary use.
- Object Clitics on Infinitives and ParticiplesB2 — Interpret enclitics on nominal infinitives, passive infinitives, perfect auxiliaries, and participial noun phrases without confusing object and possessor roles.
- Stacked Irrealis and Modal ScopeB2 — Interpret Persian clauses in which negation, possibility, obligation, perfect subjunctive, and conditionality take scope over one another.