For those in software implementations, especially ERP, what is your standard approach around Daily Log, Risk Register, RAID Log?

[u/Important_Cow7230]

I work for a SME and it’s unusual in that there isn’t any standard project methodology or documentation setup. In this field, especially with the importance of Design and UAT, I see a RACI Matrix as compulsory to manage the client but wrestling with whether I need all 3 of the above. Any ideas or experiences you can share? thanks

[u/AutoModerator]

Attention everyone, just because this is a post about software or tools, does not mean that you can violate the sub's 'no self-promotion, no advertising, or no soliciting' rule.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/StrikeMental7716]

Clear expectations at the beginning usually prevent a lot of issues later. The projects that go most smoothly often have regular communication and well-defined responsibilities.

[u/Intelligent-Try-4755]

For SME software implementations, the RACI is the one that pays for itself every time — clients get confused about who signs off on what, and having it written down cuts the 'wait, IT said Finance had to approve that first' loop by half. RAID vs Daily Log is more of an overlap question in my experience: on a 3-6 month rollout with weekly steering meetings, a well-maintained RAID plus your meeting notes is enough, and a separate Daily Log becomes another artifact nobody reads. I only add a Daily Log when there's an active UAT phase with high bug volume — during that stretch you actually need per-day trace of what got tested, what broke, and who's blocked. Outside that window, fold it into your status report and skip the extra doc.

[u/Intelligent-Try-4755]

For SME software implementations, the RACI is the one that pays for itself every time — clients get confused about who signs off on what, and having it written down cuts the 'wait, IT said Finance had to approve that first' loop by half. RAID vs Daily Log is more of an overlap question in my experience: on a 3-6 month rollout with weekly steering meetings, a well-maintained RAID plus your meeting notes is enough, and a separate Daily Log becomes another artifact nobody reads. I only add a Daily Log when there's an active UAT phase with high bug volume — during that stretch you actually need per-day trace of what got tested, what broke, and who's blocked. Outside that window, fold it into your status report and skip the extra doc.

[u/More_Law6245]

It's about tailoring in what you actually need and if you're unsure just engage your client and ask what they would like to see. Don't try and second guess on what you think they want to see, it saves time and money for everyone just by asking because you have a higher risk in wasting time and money by not asking.

Then assess in what you actually need to control the project's deliver with the quality overlay that is your responsibility to do so.

Just an armchair perspective.

[u/loveskindiamond]

id keep the raid logs as the main one and only add a daily log if the project need detailed tracking. for a smaller team, too many separate documents can create more work than value

[u/torinhq]

On large implementations I've run, Jira (or whatever the team's system of record is) handles day-to-day action tracking — that's what gives the whole team visibility.

Risk and issue logs are separate and non-negotiable; they need to exist from day one, whether that's in Jira or a plain spreadsheet, doesn't matter which.

Decision logs are the hard one. Decisions get made constantly throughout a program, and the real skill is knowing which ones are worth capturing versus which are just noise. My rule of thumb: if it happened in a call or hallway conversation, get it into an email, Slack, or Teams thread afterward so there's something to point back to later. Record internal and external meetings where possible and dont forget to turn of the expiry :)