Audit Senior Survival Guide: First 90 Days

Why the first 90 days define your reputation

The audit senior role is the first position where your output is other people's work, not your own. As a staff member, you controlled your own sections. Now you control the file. ISA 220.31 makes this explicit: the engagement team member directing fieldwork must ensure that work performed provides sufficient appropriate audit evidence to support the conclusions reached. That person is you.

The practical shift hits harder than the technical one. You already know how to test revenue. What you don't yet know is how to make someone else test revenue to your standard while you're simultaneously dealing with a client who hasn't provided the bank confirmations you requested two weeks ago.

Build the right systems in these first 90 days, or spend the next year fighting fires.

Most seniors who struggle don't struggle because they lack technical knowledge. They struggle because nobody taught them the operational side: how to plan a week of fieldwork across four people, how to write review notes that get resolved on the first pass. Technical knowledge matters. But it's table stakes by the time you reach senior.

Weeks 1 to 2: own the planning file

Your manager expects a planning file that does two things: documents the audit strategy under ISA 300.7 and gives the partner enough information to approve the plan without asking follow-up questions. In practice, this means your planning memo needs to answer four questions. What changed since last year? Where are the risks? What's the materiality? What's the timeline?

Start with last year's file. Open every section. Read the risk assessment, the materiality calculation, the scoping decisions, and the prior year's management letter points. Write down anything that looks wrong, outdated, or incomplete. This list is your first deliverable: the updates the planning file needs before it can be rolled forward.

ISA 300.A14 requires you to consider whether changes in the client's business or environment since the previous audit affect the overall audit strategy. Don't treat last year's file as a starting point you merely update with new dates. Treat it as a document you're re-approving.

Talk to the prior year senior if they're still at the firm. Ask two questions: what nearly went wrong, and what would they do differently. You'll get more useful information from those two answers than from reading every working paper in the archive.

Then set the timeline. Work backward from the signing date. Allocate partner review time first (most partners need a minimum of five working days for a mid-size file), then manager review, then your own review time for staff work. Whatever remains is your actual fieldwork window. If the window is too short, raise it now. Not in week six when you're behind.

Weeks 2 to 4: brief your staff before fieldwork starts

The single biggest time sink for a new senior is re-reviewing staff work. A working paper that comes back needing significant rework costs you twice: the time to write detailed review notes and the time to re-review after the staff member addresses them. Multiply that by fifteen sections and you've lost a full week.

Invest time before fieldwork in briefing your staff properly. ISA 220.31 requires that the engagement team member directing fieldwork ensures team members understand what they're doing and why. Most seniors interpret this as "assign sections and answer questions." That's not enough.

For each staff member, prepare a one-page brief covering:

• The test objective (not "test revenue" but "confirm revenue is not overstated by testing whether revenue is recorded in the correct period around year-end")
• The source documents they need from the client
• The sample size and selection method
• What the completed working paper should look like

Four items, one page. Writing each brief takes you 20 minutes. Each one saves you two hours of rework when the working paper comes back.

Then hold a 30-minute team briefing. Walk through the timeline and the key risks from your planning memo. Explain which sections depend on each other so that staff don't sit idle waiting for a predecessor section to finish. ISA 315.13 requires the engagement team discussion on susceptibility to material misstatement. Your briefing satisfies that requirement and accomplishes something practical at the same time.

Weeks 4 to 8: run fieldwork without losing control

Fieldwork is where new seniors lose control. The volume of incoming work, outstanding client requests, and open items creates a feeling of perpetual triage.

You need a system. It needs to be simple enough that you'll actually maintain it during a 55-hour week.

Build a tracker. A shared spreadsheet works. One row per working paper section. Columns for: assigned to, status (not started, in progress, ready for review, review notes issued, cleared), date completed, and open items. Update it every morning. This tracker becomes your single source of truth and the document you send to your manager every Friday afternoon instead of a verbal status update.

Review staff work within 48 hours of receiving it. If you let working papers pile up and review them all in the final week, you'll find issues you can't fix because the client's finance team has moved on to their next deadline. The AFM's 2023 inspection report specifically flagged insufficient timeliness of review as a recurring quality finding in non-Big 4 firms.

When you write review notes, be specific. "Needs more work" is not a review note. "The sample selection in cell B14 uses a random number generator but ISA 530.A13 requires the selection method to give every sampling unit a chance of selection proportional to its size for MUS. Recalculate using the MUS sampling tool or document why random selection is appropriate for this population" is a review note. Your staff member should be able to resolve it without asking you a question. Every follow-up question means the note wasn't specific enough.

Handle client requests systematically. Send one consolidated PBC (prepared by client) list at the start of fieldwork, not a drip of individual emails. Set a deadline. Follow up once at the midpoint. Escalate to the manager if material items remain outstanding with one week of fieldwork left.

Managing upward: how to communicate with your manager

New seniors make two communication errors with roughly equal frequency. Some say nothing until a problem is unsalvageable. Others flag every minor issue, generating noise that makes the manager tune out.

The rule is simple. If something might affect the timeline, the budget, or the audit opinion, tell your manager the same day you discover it. Everything else goes in the Friday tracker update.

Format matters more than speed. Don't send a message saying "we have a problem with revenue." Send a message saying "the client's revenue recognition policy on long-term contracts doesn't match the percentage of completion method described in their accounting policy note. I've asked the controller for the contract-level calculations. If those don't support the current booking, this may require an adjustment of approximately €200K based on a preliminary recalculation. I plan to discuss this with the client on Wednesday and will update you after that meeting."

Your manager can act on the second version. The first one just creates anxiety without providing anything to work with.

ISA 220.18 requires the engagement partner to take responsibility for the direction, supervision, and performance of the engagement. In practice, your manager serves as the daily proxy for this responsibility. Make their job easy by giving them information they can act on, not information they need to decode.

Weeks 8 to 12: completion and what reviewers actually look at

Completion is where files pass or fail inspection. The AFM and other European regulators consistently flag the same issues: insufficient evaluation of uncorrected misstatements under ISA 450, inadequate going concern conclusions under ISA 570.A2, and missing or boilerplate subsequent events procedures under ISA 560.10.

Build a personal completion checklist. Don't rely solely on your firm's generic methodology checklist.

Every engagement partner has a shortlist of items they check first. Some always start with the going concern conclusion. Others go straight to the misstatement summary. Learn what your partner's shortlist contains on your first engagement and put those items at the top of your own checklist.

ISA 450.11 requires you to communicate all misstatements accumulated during the audit to the appropriate level of management and request that they be corrected. Start your misstatement summary on day one of fieldwork, not during completion. A summary assembled from memory and scattered notes during the final week is exactly the type of documentation the AFM flags.

Then there's the manager review, which determines whether your file moves to partner or bounces back. Managers review the same areas first on every engagement: planning memo, risk assessment, materiality, key audit areas, completion memo. If those areas are solid, everything else goes faster. A single issue in any one of them makes the manager question the rest of the file.

Worked example: first planning meeting at Vos Techniek B.V.

Vos Techniek B.V. is a Dutch industrial automation company based in Eindhoven. Revenue is €38M, profit before tax is €2.1M, and total assets are €27M. This is the firm's second year on the engagement. The prior year senior has moved to another firm. You're the new senior. Your manager has scheduled a planning meeting for Thursday.

1. Review the prior year file (Monday-Tuesday)

Open the prior year planning memo. Revenue was €34M last year, so the 12% growth is material. The prior year identified revenue recognition (percentage of completion on long-term contracts) and inventory valuation as the two key audit areas. A management letter point flagged a lack of segregation of duties in the purchasing cycle.

Documentation note: Prepare a prior year summary noting key changes. Record the revenue growth percentage, any changes to key audit areas, and the status of prior year management letter points. File in WP A.1.

2. Update the risk assessment (Tuesday-Wednesday)

ISA 315.26 requires you to identify and assess risks of material misstatement at both the financial statement level and the assertion level. Revenue grew 12% on long-term contracts, which increases the risk that percentage of completion estimates are aggressive. Check whether Vos Techniek signed any new contracts above €2M individually (your performance materiality will likely sit around €1.1M).

Documentation note: Update the risk register with the revenue growth data point and the new contract inquiry. Cross-reference to ISA 315.26. File in WP B.2.

3. Calculate materiality (Wednesday)

Using the ciferi materiality calculator: revenue benchmark at 1.5% gives overall materiality of €570K. Profit before tax at 5% gives €105K. Vos Techniek is a private client with no debt covenants, so revenue is the more stable benchmark. Set overall materiality at €570K, performance materiality at 75% (€427K), and the clearly trivial threshold at €28.5K.

Documentation note: Record the benchmark selection rationale, the percentage applied, and the qualitative factors considered per ISA 320.A3. File in WP B.1.

4. Prepare the planning memo (Wednesday-Thursday morning)

Draft the planning memo covering what changed since last year (revenue growth, prior year senior departed, management letter points), where the risks sit (percentage of completion, inventory valuation, purchasing cycle segregation), and the proposed timeline with key dates. Send to the manager for review before the Thursday meeting.

Documentation note: The planning memo satisfies ISA 300.7-8. Include the proposed audit strategy, the key dates, and the team allocation. File as WP A.0.

The partner sees a file where the new senior identified the revenue growth impact on risk, updated materiality with a documented rationale, and prepared a planning memo that anticipates questions rather than waiting for them.

Your first-week checklist

1. Open the prior year file and read the planning memo, risk assessment, materiality calculation, and management letter in full. Write down every item that needs updating before roll-forward.
2. Contact the prior year senior (if reachable) and ask what nearly went wrong and what they'd change. Record the answers.
3. Build your fieldwork timeline by working backward from the signing date. Allocate partner review, manager review, and your own review time first, then calculate the remaining fieldwork window.
4. Prepare one-page briefing documents for each staff member's assigned sections, covering the test objective, source documents, sample approach, and expected output format.
5. Set up a fieldwork tracker (shared spreadsheet, one row per working paper section) and share it with the team before fieldwork starts.
6. Send the consolidated PBC list to the client with a single deadline and a clear list of document names, not a paragraph describing what you need.

Common mistakes new seniors make

• Waiting until completion to assemble the misstatement summary. ISA 450.11 requires you to accumulate misstatements throughout the audit. Starting this document during completion means you're reconstructing from memory and scattered notes, which the AFM flagged as a documentation deficiency in their 2022 inspection cycle.
• Writing vague review notes that generate follow-up questions instead of answers. "Please reconsider" is not a review note. Specify what's wrong, cite the ISA paragraph, and describe what the corrected working paper should contain. The time you invest in a precise review note is always less than the time you'll spend answering questions about a vague one.
• Not escalating timeline risks early enough. A manager can solve a timeline problem in week two. By week eight, the only option is overtime. The PCAOB's 2023 inspection report noted that audit quality deficiencies were concentrated in engagements where time pressure was highest in the final two weeks.

Related Ciferi content

Related guides:

Put audit concepts into practice with these free tools:

Frequently asked questions