Before AI turns a design brief into a schedule, check the contradictions
A brief that disagreed with itself, and practical checks for using AI to turn design briefs into schedules without hiding unresolved decisions.
What happens when your client’s brief disagrees with itself, and an AI tool turns it into a tidy schedule anyway?
If the workflow has no way to keep the conflict visible, a clean schedule can make an unresolved assumption look like an approved decision. I learned that one firsthand.
I was using AI to pull dates from a client’s sale brief into a structured calendar. One item had two different start dates in different parts of the document.
Extracting the dates turned out to be the easy part. Someone still had to decide how to handle the disagreement.
I reviewed the proposed entries before anything was written, and I approved loading them with each judgment call noted beside its entry, flagged for my own follow-up check.
Full disclosure: this was a marketing operations workflow, not a design-project schedule. But the lesson applies anywhere a team turns narrative instructions into structured information.
Where this applies in a design practice
For architecture and interior design teams, I’d look at extracting requirements from a client brief, preparing an initial FF&E schedule, or organizing dates from supplier correspondence.
Those are proposed uses of the lesson, not implementations I’m claiming to have delivered.
The key distinction is between extracting what a source says and deciding which information the project should rely on.
If one section of a brief names a date and another names a different one, copying either of them accurately doesn’t resolve the conflict.
What I’d require from the workflow
I’d want the review output to show:
- The proposed value.
- The source passage or document reference.
- Any conflicting value found elsewhere.
- The person responsible for resolving the question.
- The decision and its date, once the conflict is resolved.
These are review requirements. The tool or table structure can vary.
The point is to make uncertainty visible before the information starts driving other work. A PM should be able to see why an entry needs attention without rereading every source from the beginning.
Keep the review step meaningful
Human review gets a lot less useful when the system presents every extracted value with the same apparent confidence.
A better review separates the straightforward entries from the ones that need interpretation. That gives the reviewer a clearer job: confirm the routine information and resolve the flagged exceptions.
In the workflow that prompted this, the brief’s contradictions were my reason for keeping a reviewed step rather than setting up unattended processing.
A question to ask before you implement
When you’re evaluating AI brief extraction, ask to see what happens when the source disagrees with itself.
A demo using a perfectly consistent brief won’t answer that question.
What you want is a schedule whose entries trace back to their sources, with unresolved decisions still visible to the people responsible for them.