Every project template has an assumptions section. The RAID log has a tab for it. The BRD has a heading for it. And on almost every project I have seen, that section is a list of fifteen sentences that nobody reads after week two.

The problem is not that BAs forget to write assumptions down. It is that a flat list treats them all as equal. "Users will have a modern browser" sits next to "Finance will approve the new refund rules" with the same font, the same bullet, and the same amount of attention, which is none. One of those can sink the project. The other cannot. A list that does not tell you which is which is not an assumption log. It is a disclaimer.

This piece gives you an assumption log that ranks instead of lists, with a worked example you can copy into a spreadsheet today.

What an assumption log is actually for

An assumption is something the plan depends on that nobody has confirmed.…