Let's look at the working.

Bring a question about a schedule review, a delay method, or a finding you want to understand. We can walk through the generated example together and discuss where Schedule Forensics would — and would not — help.

Email Charley to arrange a walkthrough ↗

Or email charley.s.forey@gmail.com directly with a couple of times that suit you and what you would like to discuss.

What to expect

Allow thirty to forty-five minutes. There is no signup, purchase commitment, or requirement to send a file.

• Follow a real report. See the commands, the findings, the assumptions, and the clauses that need more evidence or a person's judgment.
• Discuss your review process. Which specifications govern your work? Which clauses get enforced? Which missing inputs cause the most back-and-forth?
• Ask the difficult questions. The limitations and measured evidence are available before the call. If this is not useful for your purpose, that is a worthwhile conclusion.

This is an independent research project. There is currently no software download, trial, price, or order form. Availability and liability explains the current position.

No project file needed

The worked example uses generated data and is enough for a walkthrough. Do not send confidential project material in an initial email.

For a project in dispute, or where a dispute is anticipated, route any proposed file sharing through your counsel of record. A completed project can still have a live claim.

If file sharing is appropriate and agreed separately, supply a derivative sanitised by you. The current local engine makes no network calls; this website does not accept or process schedule uploads. There is no SOC 2, ISO 27001, FedRAMP certification, penetration test, or cyber liability insurance to offer for your security review.

What happens to your message

It arrives in an inbox and is used to reply to your enquiry. It is not added to a mailing list or used for advertising. See privacy for the website and contact details.

Source: web/pages/talk.md. Source commit date: 2026-09-09.