Took 10 projects at once in my architecture office, all delayed, clients got angry — how do I set the project schedule?

To do this job: 1) Ask the client. 2) Get the answer. 3) Do it. Easy.

Standard method: Set a 'standard duration' for each job, write it to the client. Follow up.

this job is a waste... i'm with you on this one... don't interfere just keep going.

bro this is an amazing opportunity! go now and use it 100%!

If customer satisfaction is the priority, you can find clients who pay a bit more. But you need patience.

Due to regulations: your business needs to have these and those permits. Ask your accountant.

let me summariez whats been said so far then most time waste accumulates in tasks waiting for approval.

extending terms makes cstomers happy but turns you into a financing institution. like good luck with that.

Don't miss this: The answer varies greatly by industry; there is no one-size-fits-all rule.

When making decisions, write down the worst-case scenario too, not just the best. Of course it varies if your situation is different.

I have a question, don't want to go off-topic though. If you get three different answers on a topic, the question was asked wrong.

When the closure decision was made is as decisive as the decision itself.

I partly agree, partly disagree. Mistakes made on the architecture project management side are usually reversible but expensive.

Exactly, and not many people know this. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Any unwritten clause becomes a point of disagreement later, as both sides remember it differently. Of course, it varies if your situation is different.

I think differently. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Generally correct, but one part is missing. Just because everyone does it doesnt mean its right.

If you have questions, write them; Ill answer as best I can.

The opposite happened to me, that's why I'm writing. If you don't write this down from the start, it leads to arguments later.

Processes without records never improve, because you don't know what to fix. Just leaving this note, it might be useful.

Correct.

same here.

I agree, and I'd like to emphasize that... I mean if it's your first time, start small; scaling comes later.

If it's your first time, start small; scaling comes later. If you post the result here, it will help others too.

I'm curious too.