VocairoStart learning

Shouldn't have + V3: regret and criticism of a past action

Shouldn't have + past participle lets you look back on an action that actually happened and describe it as a mistake, an unwise decision, or a source of regret. Learn to establish the action from context, build modal + have + V3, choose the correct participle, and distinguish retrospective judgement from present prohibition, negative deduction, and an unfulfilled obligation.

Published

Looking back: the action happened, but the judgement is negative

In the target meaning of shouldn't have + V3, the speaker evaluates a past action that was carried out. The negation concerns its desirability, not whether it happened: the action occurred, but the speaker now considers it a mistake.

The meaning is that doing the action was unwise or inadvisable. Keep the two components distinct: a known past fact and a present negative assessment of that fact.

How to build it

the action happened + negative assessment → subject + shouldn’t have + V3

subject / S
—
The grammatical subject: who or what the clause is about; the verb agrees with it. In The book was written, the book is the subject, although someone else does the action.
V3 / past participle
—
The third verb form: worked, gone, seen. Used after have/has or in the passive, for example; it is not always the same as V2.

I shouldn't have stayed up so late; I'm exhausted now.

I shouldn't have stayed up so late; I'm exhausted now.

The speaker really stayed up late and now regrets it because of the evident consequence.

We shouldn't have booked the room before checking its size.

We shouldn't have booked the room before checking its size.

The booking has already happened; the team judges the order of its actions to have been a poor choice.

Form: shouldn't or should not + have + V3

After the subject, put shouldn't or the full form should not, followed by unchanged have and the past participle of the main verb. The subject does not change have: I, she, the team, and they all use shouldn't have.

Regular past participles usually end in -ed: stayed, opened, shared. Learn irregular forms separately: say–said–said, take–took–taken, write–wrote–written, choose–chose–chosen.

How to build it

subject + shouldn’t/should not + have + past participle (V3)

subject / S
—
The grammatical subject: who or what the clause is about; the verb agrees with it. In The book was written, the book is the subject, although someone else does the action.
V3 / past participle
—
The third verb form: worked, gone, seen. Used after have/has or in the passive, for example; it is not always the same as V2.

She shouldn't have shared the password.

She shouldn't have shared the password.

Unchanged have follows shouldn't, and shared is the past participle.

They should not have taken that road.

They should not have taken that road.

Full should not have is grammatically equivalent to the contraction, and take has the past participle taken.

He shouldn't have written that comment.

He shouldn't have written that comment.

Have requires the past participle written, not the Past Simple form wrote.

Regretting your own action and criticising others

With I or we, the construction often expresses personal regret, acknowledgement of a mistake, or part of an apology. With you, he, she, or they, it may criticise someone else's action, so tone and the relationship between people matter.

The sentence itself gives an assessment, but a reason makes that assessment easier to understand. A consequence, a broken rule, or a known better alternative helps the listener see why the action was a poor choice.

How to build it

I/we shouldn’t have … — often personal regret; you/he/she/they shouldn’t have … — possible criticism

I shouldn't have interrupted you. I'm sorry.

I shouldn't have interrupted you. I'm sorry.

The speaker acknowledges their own completed action and explicitly apologises.

He shouldn't have promised a Friday delivery when the work was not ready.

He shouldn't have promised a Friday delivery when the work was not ready.

The promise was made, and the state of the work explains the criticism.

Context must establish what happened

Do not invent the event in a learning task. Before retrospective criticism, the context should show that someone really sent, said, bought, or otherwise did something, through an admission, an observable consequence, a record, or a direct account.

If it is unknown whether the action happened, a different communicative step is needed: a question, a cautious possibility, or an inference from evidence. Shouldn't have does not replace checking the fact.

How to build it

known fact → assessment of a past action

Nadia says, ‘I sent the private file to the whole group.’ She shouldn't have sent it to everyone.

Nadia says, ‘I sent the private file to the whole group.’ She shouldn't have sent it to everyone.

The admission directly establishes that the file was sent, so the next response evaluates a known action.

We don't know whether Nadia sent the file.

We don't know whether Nadia sent the file.

The fact is not established here. Without further information, categorical retrospective criticism would be premature.

Do not confuse four different messages

Shouldn't + V1 gives advice or a prohibition concerning the present, future, or general behaviour: You shouldn't share passwords. Shouldn't have + V3 looks back on a known completed action: You shouldn't have shared that password.

In retrospective advice, should have + V3 names a desirable alternative past action. However, should/shouldn’t have can also express an expectation: The parcel shouldn’t have arrived yet means that its arrival is not expected by now. This does not establish that it arrived. Can’t have + V3, by contrast, expresses a strong negative deduction.

How to build it

shouldn’t do — advice; shouldn’t have done in this lesson — criticism of the past; can’t have done — negative deduction

You shouldn't share your password with anyone.

You shouldn't share your password with anyone.

This is general advice about behaviour, not an assessment of an established past action.

You shouldn't have shared your password with that caller.

You shouldn't have shared your password with that caller.

Context establishes that the password was disclosed; the action is now criticised.

You should have checked the caller's name first.

You should have checked the caller's name first.

Checking was desirable but was not done. This contrasts with shouldn't have shared, where the criticised action happened.

Mina can't have shared that password; she has never known it.

Mina can't have shared that password; she has never known it.

Her lack of knowledge of the password provides grounds for ruling out disclosure. This is a deduction, not an assessment of a known action.

Tone: making criticism responsible

Direct You shouldn't have… can sound harsh. When responsibility is shared, We shouldn't have… is more accurate. In a sensitive conversation, you can add I think or perhaps, or name the consequence without attacking the person.

Softening does not change the grammatical form or erase the assessment. It helps focus on the decision and its consequence without belittling the other person.

How to build it

I think + we/you shouldn’t have + V3 + explanation of the reason

V3 / past participle
—
The third verb form: worked, gone, seen. Used after have/has or in the passive, for example; it is not always the same as V2.

I think we shouldn't have released the update before the final test.

I think we shouldn't have released the update before the final test.

I think and shared we soften the tone, while the known action and its assessment remain clear.

Perhaps you shouldn't have mentioned that detail in public.

Perhaps you shouldn't have mentioned that detail in public.

Perhaps makes the criticism less categorical; the conversation has already established that the detail was mentioned.

Application in speech and a separate polite expression

To use the rule independently, first identify the completed action, then its consequence or the principle it violated, and only then formulate the assessment. This works in an apology, a shared review of a decision, friendly advice after an event, or a short dialogue.

Also learn the fixed You shouldn't have! as a polite response to a gift. In that situation, it is usually warm gratitude rather than literal criticism. Without context, this expression should not be treated as evidence of understanding the main meaning.

How to build it

fact → consequence → regret or criticism; response to a gift: You shouldn’t have!

I sent the message while I was angry. I shouldn't have written it so quickly.

I sent the message while I was angry. I shouldn't have written it so quickly.

The first sentence establishes the fact; the second assesses it as a mistake.

A new notebook for me? You shouldn't have!

A new notebook for me? You shouldn't have!

This is conventional polite gratitude for a gift, not a genuine reproach.

Common mistakes

Incorrect:I shouldn't stay up so late last night.

Correct:I shouldn't have stayed up so late last night.

Regret about the completed action last night requires have and the past participle stayed.

Incorrect:She shouldn't has shared the password.

Correct:She shouldn't have shared the password.

After modal shouldn't, use unchanged have, not has.

Incorrect:We shouldn't have chose that route.

Correct:We shouldn't have chosen that route.

Have requires the past participle chosen; chose is the Past Simple form.

Incorrect:He didn't should have posted the photo.

Correct:He shouldn't have posted the photo.

Modal should forms its negative without auxiliary did.

Incorrect:They shouldn't have write to the client.

Correct:They shouldn't have written to the client.

After have, use the past participle written rather than base-form write.

Sources
Practise with Vocairo