Quarterly Coaching Performance Audit Templates
Nour
Founder, Coachful

Quarterly coaching performance audit templates help a client examine what a progress claim actually rests on. A completed goal, a recorded attempt, a colleague’s observation and a business result answer different questions. A useful record keeps their sources, limits and decision implications visible.
This guide provides four evidence modules, a filled responsibility matrix and a complete fictional review. Its focus is checking performance evidence and authority. Our quarterly review guide covers the broader conversation; the quarterly ROI guide addresses monetary claims.
Define what this performance audit can establish
Some organizations call a quarterly coaching review an audit. Specify the mandate before adopting the label. A developmental conversation does not automatically provide independent assurance, an employment appraisal, a validated psychological assessment or certification of an operational process.
The coach can help the client inspect a claim: “Which record supports that? What would contradict it? Who can confirm the relevant status?” The organization retains responsibility for its own decisions. If a formal audit or employment judgment is required, agree an appropriately qualified process rather than quietly giving the coaching worksheet a new purpose.
The CDC’s 2024 evaluation framework distinguishes implementation, outcome and impact questions. Observing an outcome does not establish that an intervention caused it. Its evidence-gathering step also connects the question to sources and expectations. These distinctions inform this original coaching adaptation; the templates are not a CDC-approved assessment.
Make the decision explicit. “Did everything improve?” invites a vague verdict. “Which decision-clarification practice should Priya retain, and which project dependency needs the director’s action?” identifies something the evidence may actually help answer.
Write the review agreement above the templates
Use six fields: period, evidence cutoff, review question, intended audience, decision authority and service boundary. A cutoff is the latest time evidence enters this version of the packet. It does not move every later event into the quarter being examined.
In the fictional case, Priya manages customer service during an escalation-process project. Asha is her coach. Eli, the service director, has the organization’s delegated authority for this project’s scope and staffing. They are named roles in this example, not positions every organization delegates in the same way.
On 15 October 2026, Priya, Asha and Eli agree the review purpose and reporting boundary. The period is 1 August–31 October, with evidence received by 3 November at 17:00 Europe/London. Priya and Asha will meet on 4 November, 14:00–15:00. That is one sixty-minute coaching review, with no additional follow-up coaching included. Asha may send Eli only a specific summary Priya separately approves.
The private worksheet and colleague responses are for Priya and Asha. Eli receives no automatic access because he sponsors the work. The ICF Code of Ethics calls for clear agreements about roles and information exchange. Establish the actual arrangement before asking people to disclose material.
Keep the agreement readable. Ask the client to explain what the review is for and who receives which record. If their understanding differs, repair the arrangement before collecting more data. An extra form will not resolve a disagreement about audience or purpose.
Template 1: goals, milestones and authorized status
Copy these fields: agreed item; completion criterion; owner; evidence and date; status at cutoff; dependency; next authorized decision. Use an agreed criterion rather than selecting a more favorable definition after seeing the result.
| Priya’s item | Evidence and current status | What it does not establish |
|---|---|---|
| Decision-owner map | Eli accepted the map on 10 September. Complete against the agreed mapping task. | Every later request used the correct role. |
| Initial escalation draft | Eli accepted it for consultation on 20 October. Complete against that drafting milestone. | Permission to implement the process. |
| Pilot | Eli deferred it on 28 October because staffing was unresolved. Not completed. | A failure by Priya to run an authorized pilot. |
| Final process review | Not started; depends on an actual pilot. | Evidence about the eventual process’s effectiveness. |
Two of four listed items are complete. Calling this fifty percent may be arithmetically correct, but it compresses very different states. A deferred pilot requires an organizational decision; a dependent review cannot be completed by increasing Priya’s motivation.
Check the underlying verbs. Drafted, accepted for consultation, approved for implementation and used successfully are separate claims. If the work was accepted for a limited purpose, preserve that qualification in the status field and any sponsor summary.
A change in scope should also remain traceable. If an owner later removes a goal, record who agreed the change and when. Do not silently delete difficult items from the denominator or call an authorized cancellation a completed deliverable.
Inspect the source at the level the claim needs. A file named “final” shows a filename, not Eli’s acceptance. A dated message accepting a draft for consultation supports that limited status. If the underlying business record cannot appropriately enter the coaching system, identify the permitted source reference and owner rather than copy the entire file. Mark a status unconfirmed when the available evidence does not establish it.
Template 2: practice, opportunity and quality
Copy these fields: chosen behavior; eligible situations; recorded attempts; known non-attempts; unknown status; example of quality; interpretation; next practice. Keep the unit attached to every number.
Priya selected twelve meetings that all occurred during the quarter. Her intended practice was to clarify who would advise, approve or act. Her notes record eight attempts, two meetings where she did not attempt it and two with no entry about the practice.
- Eight attempts among ten meetings with known status: 8 ÷ 10 = 80%.
- Eight recorded attempts among all twelve selected meetings: 8 ÷ 12, approximately 66.7%.
- Two unknown entries remain unknown. Neither percentage establishes the quality of the requests.
The first rate answers a question about known records; the second preserves all selected meetings. Neither should be labeled “effective decision clarification.” The evidence is Priya’s account of attempts, not an independent observer’s rating of correct behavior.
Quality requires examples. One note describes a discussion where naming the approver helped. Another records a longer discussion after Priya asked for everyone’s sign-off when she wanted advice. Both can count as attempts while raising different questions about execution.
Ask whether an attempt had a clear purpose and whether a relevant recipient understood it. Do not retrospectively redefine an attempt as only a successful one. If a future practice needs a quality criterion, agree it prospectively and record the new definition separately.
Template 3: relevant observations from other people
Copy these fields: purpose; invited observers and basis for inclusion; invitation and response dates; actual response count; observations; contrary or uncertain evidence; intended recipients; limits.
On 2 November, Priya invites Marin, Tomas, Leah and Yusef, each of whom attended relevant meetings. The invitation says responses are voluntary, go to Priya and Asha, inform developmental reflection and will not be treated as an anonymous employment score. It asks for replies by 3 November at 17:00.
Use these three original questions:
- What, if anything, did you observe about how advice, approval or action was requested in a meeting you attended?
- When was your role clear or unclear? Describe an example without unnecessary personal information.
- What change would help a future discussion, and what context should Priya understand about that suggestion?
Marin, Tomas and Leah reply by the cutoff. Marin and Tomas describe clearer ownership. Leah says a 9 October request for “everyone’s sign-off” left her unsure whether she could stop the proposal or was being asked for advice. Yusef’s response is absent; Priya does not infer that he agreed, disagreed or declined.
The result is three accounts from four invited people, not a representative organization-wide finding. There is no comparable baseline survey. Two favorable observations do not cancel Leah’s example, and three responses should not be converted into a standardized leadership score.
CCL’s guidance on implementing 360 feedback emphasizes purpose, roles, confidentiality and follow-through. These three custom prompts are a smaller developmental inquiry, not a validated multi-rater instrument. If formal 360 assessment is needed, use the appropriate authorized process and interpretation.

The demo form builder illustrates structured prompts. Its sample content is not Priya’s evidence or a validated performance instrument. A form’s ability to collect answers does not determine their intended use.
Template 4: operational context and unsupported claims
Copy these fields: relevant business fact; source and date; relationship to the goal; other influences; financial claim, if any; remaining uncertainty; responsible business owner.
Priya attaches Eli’s 28 October staffing decision to the project status, rather than placing personnel details in the coaching worksheet. The permitted summary is that another team’s vacancy prevents the pilot proceeding as planned. The next staffing decision belongs to Eli.
Finance has attributed no cost saving to this work. The quarter contains no completed pilot or final process review. The worksheet therefore contains no financial-return estimate and no assertion that coaching improved the service process.
Context should explain the evidence without erasing the client’s choices. The vacancy affected the pilot. It did not require Priya to use “sign-off” when she meant advice. Explore each at the appropriate level instead of making every missed milestone either a personal failure or entirely somebody else’s responsibility.
In a contrasting case, a client may complete all milestones while operational performance deteriorates for reasons needing investigation. Conversely, useful learning may occur before a project can run. Keep deliverable status, behavior and operational outcome in separate fields rather than award one overall success color.
Check each claim in three passes
- Check the unit. Is the statement about meetings, attempts, people, milestones or outcomes? “Eight attempts” cannot become eight successful decisions simply because both descriptions use eight. Confirm that the denominator includes the situations the question actually concerns.
- Check the status and source. Is this a self-report, an accepted artifact or a relevant observer’s account? Preserve who could observe what. Priya can describe her intention; Leah can describe her understood role. Neither account alone establishes the other person’s understanding.
- Check the inference. What conclusion is being added? A correct role map does not prove every request was clear. A clearer request does not prove a pilot improved service. Put the supported conclusion in the record and leave the additional question open.
These checks help locate the repair. Sometimes the number is wrong; sometimes the number is correct but its label overclaims. Sometimes people disagree about meaning despite an accurate record. Correct the actual problem instead of replacing every uncomfortable finding with another survey.
Confirm decision rights with a filled RACI adaptation
The New Zealand NCSC governance guide describes RASCI in a cybersecurity context, including a Supporting role and one accountable role per task or function. This original four-role RACI adaptation omits Supporting. It is a conversation aid, not an instrument that grants authority.
| Work or decision | Responsible for doing it | Accountable for approval | Consulted | Informed |
|---|---|---|---|---|
| Prepare the consultation draft | Priya | Eli | Relevant team representatives and specialists | Affected teams |
| Resolve pilot staffing and scope | Eli prepares the decision | Eli within his actual delegated authority | Relevant department managers | Priya and proposed participants |
| Revise the draft after an actual pilot | Priya | Eli | Pilot participants and relevant specialists | Teams receiving the approved process |
Eli confirmed these roles when accepting the owner map. Asha remains outside the organization’s project approval roles. Where a named person has not accepted a responsibility, label it proposed. A completed coaching task cannot supply their acceptance.
Check the action as well as the name. “Eli owns the project” is less usable than “Eli decides whether staffing permits this pilot.” If the actual authority is elsewhere, change the matrix through the organization’s process before making a promise.
Run a sixty-minute review around the discrepancy
| Time | Work | Output |
|---|---|---|
| 14:00–14:10 | Confirm purpose, audience and context. | Review boundary remains agreed. |
| 14:10–14:25 | Inspect the four evidence modules. | Statuses, denominators and limits stay attached. |
| 14:25–14:45 | Explore the important discrepancy. | One actual request and its alternative wording. |
| 14:45–15:00 | Choose action and check communication. | Corrected private record and a separate proposed sponsor brief. |
On 4 November, Priya chooses the discrepancy between frequent recorded attempts and Leah’s unclear role. This fictional conversation develops the evidence rather than asking Priya to dismiss the unfavorable response:
Asha: “What did you ask Leah to do?”
Priya: “I said I needed everyone’s sign-off. I only wanted their advice before Eli decided.”
Asha: “What could she reasonably have understood from sign-off?”
Priya: “That she had approval authority. The owner map was correct, but my request was not.”
Asha: “What would preserve her input and make the actual decision role clear?”
Priya: “I want your advice on the draft. Eli makes the approval decision. Please identify concerns we should take to him.”
Priya chooses to use that distinction at a 5 November consultation meeting. Asha asks what would count as useful feedback. Priya will ask a participant to describe their understood role and listen for a discrepancy, rather than assume fluent wording proves understanding.
At 14:55, Priya checks Asha’s provisional note, “Eighty percent effective decision clarification.” She points out that eighty percent concerns attempts among known records. They correct the record to: “Eight recorded attempts among ten known statuses, across twelve selected meetings. Quality is mixed; the 9 October request confused advice with approval.” Priya reads and confirms that version before 15:00.
The agenda totals sixty live minutes. It does not count all preparation, colleague participation, organizational administration or later workplace activity. Nothing in this example establishes an efficient whole-project labor budget.
Complete the approved brief and the later check
On 4 November after the coaching review, Priya asks Eli to review the staffing decision on 10 November. He accepts that date. Asha’s proposed sponsor brief can now name an accepted decision review rather than promise Eli’s work without asking him.
Priya approves this exact limited copy by email on 5 November at 09:00:
“The quarterly review records two initial project milestones complete. The pilot is deferred for a staffing decision; the final process review depends on a pilot. Priya’s continuing development focus is distinguishing requests for advice from requests for approval. Eli has accepted a staffing decision review on 10 November. This summary does not establish pilot approval, service improvement or financial return.”
Asha sends it to Eli at 09:30. He acknowledges receipt at 10:00. The private worksheet, individual feedback and Priya’s reflection are not attached. Approval of this copy is not blanket permission for future reports.
At the 5 November consultation meeting, Leah initially paraphrases the request as “We are approving it today.” Priya corrects her: advice is requested, Eli remains the approver. Leah then describes her role as providing concerns for Eli’s decision. That is an actual correction and one person’s checked understanding, not proof that everyone understood.
On 10 November, Eli cannot secure the required staffing. He defers the pilot again and accepts a further decision review on 17 November. Priya records that as a review date, not a launch date. The project’s dependency remains unresolved despite the completed coaching conversation.
Priya uses “sign-off” again in a 12 November meeting, notices the slip and corrects the request before closing. She does not collect a further participant readback. On 13 November she completes her own dated reflection: “I can distinguish the roles when I check. I still use the old wording under pressure. The staffing decision is open.” This is client self-review, not an added Asha appointment.
Those later events do not alter the quarter’s twelve-meeting denominator. They belong in a follow-through record. Keep the limited corrected request, the recurrence and the still-unobserved pilot visible together. An informed client may continue, change, pause or finish coaching; unresolved business work does not itself authorize an extension.
Prepare the evidence packet in Coachful
Coachful is our #1 recommendation for organizing these coaching templates and selected actions. We build Coachful. Use it to preserve a usable review workflow; an accessible worksheet does not certify the client’s performance or replace the business’s approved records.
- Create the four original modules. Include a period, source, status, limitation and next decision. Request only evidence appropriate to the purpose; a permitted summary may be sufficient without uploading sensitive operational files.
- Assign preparation to the client. Open Clients, the client record, then Worksheets & resources and Assign. A copied private form link is not an access grant, and a staff preview is not a client response.
- Track a chosen next action. A goal-linked task may record preparation for the next role-clarification request. Its completion does not prove that Eli accepted a deadline, a colleague understood or the pilot was approved.
- Choose reflection visibility deliberately. Unshared journal and takeaway pages remain private. Where enabled, the client’s per-page Share with coach control intentionally exposes that page. Keep personal reflection unshared when that is the client’s choice.
- Check recap settings before relying on a draft. Recaps send automatically by default. Configure approval before sending, including any session-type override, when an evidence claim needs checking. Review actual wording and recipients; a client recap is separate from an authorized sponsor brief.

The demo My Coaching overview illustrates preparation and actions. It is not Priya’s record or an automatically calculated performance score. Compare the relevant Coachful features with the agreed review workflow.
Troubleshoot the evidence before adding another metric
The client disputes a comment. Preserve the observation as that person’s account. Ask about the actual interaction and alternative explanations. Do not force agreement, silently delete the response or diagnose the observer’s motives.
The status changes after the cutoff. Date the new information and identify whether it corrects an error in the original record or describes a later event. Keep a traceable version rather than quietly repaint the quarter.
A sponsor asks for a composite score. Explain what the evidence can support. A simple average of milestone completion, self-reported attempts and three comments has no established interpretation here. Agree a relevant measure prospectively if one is genuinely needed.
A formal complaint or clinical concern emerges. Use the appropriate qualified route and agreement. A developmental review should not become an undisclosed investigation or treatment process because the worksheet has an extra text box.
Frequently asked questions
What should quarterly coaching performance audit templates include?
Include the period, question, sources, status, interpretation, limitations and actual decision owner. Separate goals, practice, observer accounts and operational context. The four modules here are original developmental aids, not a validated assessment.
Can HR receive the completed worksheet?
Do not infer access from funding or job title. Follow the actual agreement and applicable obligations. In the fictional case, only an exact client-approved brief is sent to the director; the worksheet and individual feedback stay outside that report.
Does a high practice rate establish effective performance?
No. An attempt rate needs its denominator and evidence source. It does not establish correctness, recipient understanding or operational results. Examine actual examples and preserve unknown records.
Must a quarterly review produce financial ROI?
No. Financial attribution needs a relevant question and defensible evidence. Priya’s pilot has not run, so the review records no cost saving or return rather than filling the gap with hypothetical revenue.
What if the project is still deferred?
Record who controls the dependency and which decision they actually accepted. The coaching can still examine the client’s choices. Keep a future decision review separate from permission to launch, and do not assume a deferred project requires more coaching.







