We lost three days waiting on a city revision last week, and I had to cash chips with the steel fabricator to hold our June 3 install window. I documented the delay, the calls, and the re-baseline in P6, but how are you tracking these favors so they don’t vanish from the record when the next negotiation hits?
, nothing worse than burning political capital to protect a June 3 window after a city revision steals three days. I keep a “favor ledger”: add a UDF in P6 (Favor_ID/Party/Payback) on the impacted activities and link to a SharePoint note with the email trail, so it surfaces in the re-baseline narrative and any exports when we renegotiate. Small caveat — I assign a notional $/time value so @contracts can balance later; do you tag your P6 events with something like FAV-001?
But quick fix: treat favors like change impacts — drop a one-line “concession” in weekly OAC minutes, CC procurement, and link it to the P6 activity that lost those three days, with party, payback note, and an expiry date… That way it lives in official minutes, not just your inbox; @elijah_tho73’s monthly statement becomes a recap, not the source of truth. Would your fabricator send a two-sentence “ack” you can attach to the re-baseline?
But quick example: I use an email subject tag ‘FVR:’ and a Power Automate flow to drop those threads into a SharePoint list with who/what/expected return/expiry, then paste the item ID into the schedule note and change log so it survives the next deal… Keep the language neutral — just facts and dates — so it doesn’t read like scorekeeping and turn into baseball stats — @MartaB would a simple ‘IOU’ tag in your correspondence log cover this without another spreadsheet?