Project action log template

Before you start

Use after progress meetings, schedule reviews or governance decisions. Keep one action per row and link it to the originating record.

• Meeting or review record with action identifiers
• Agreed deliverables, owners and due dates
• Reporting date for the current review
• Completion records for items proposed for closure

How to use it

Make the commitment testable

Write the expected deliverable, one accountable owner and an agreed due date. Avoid broad actions such as 'monitor progress' without a defined output.

Review exceptions

Set the reporting date before using the overdue column. Record a reason when dates change and use the source reference to preserve the original decision.

Close with evidence

Record the actual closure date and completion reference. A Closed status without that evidence should be resolved in the review.

Fields included

• ID
• Action / deliverable
• Owner
• Raised
• Due
• Priority
• Status
• Closed date
• Days overdue
• Record / closure evidence

A clarification that can be closed

Illustrative example: A-014 asks the scheduler to issue a revised testing sequence with activity IDs and a completion comparison. The log records the due date and meeting reference. The reviewer closes the action only after the revised submission is received and checked.

Before issue

• Each action has a specific deliverable.
• Owner and due date are agreed.
• The reporting date is current for the review.
• Closed items identify the completion evidence.

Practice references

• Kairos project-controls practice

Original Kairos working templates informed by common project-controls practice. Adapt them to your contract, project procedure and approval authority. They are not official standards-body forms or a certification of compliance.

Keep learning

• Monthly schedule update
• Look-ahead schedule