DEV Community: Duaer Team

How to Capture Tribal Knowledge Before You Need It: A Register, a Backup Person, and a 20-Minute Interview

Duaer Team — Thu, 15 Oct 2026 03:23:11 +0000

This article is AI-generated.

Every team has things that only one or two people know. How to restart the label printer when it jams. Which customer needs certificates in a particular format. Why a step in the month-end process is done in that odd order. None of it is written down because it never seemed worth writing down, until the person who knows is on holiday, off sick, or gone.

The usual advice is "document everything," which is why it rarely happens. This guide takes a narrower approach: find out what only one person knows, decide which of it matters, and capture it in short, repeatable sessions.

Step 1: Ask the right question to find it

Tribal knowledge is hard to list because people don't notice they have it. Instead of asking "what do you know?", ask questions that surface it:

"What do people come to you for that they can't get anywhere else?"
"If you were away for two weeks, what would go wrong first?"
"What do you do that isn't in any procedure?"
"Which questions do new starters ask you most often?"

Ask these of each team member in a 15-minute conversation. Write each answer as a short topic, for example "Restarting label printer after jam" or "Certificate format for customer X."

Step 2: Build a knowledge register

Put the topics into one sheet, one topic per row.

Column	Content	How it's filled
A	Topic	Manual
B	Who knows	Manual
C	Backup person	Manual, can be blank
D	Written down?	Y or N
E	Last checked	Date the write-up was last confirmed
F	Status	Formula

Illustrative data (placeholders):

Topic	Who knows	Backup	Written?	Last checked
t1	Ana	Raj	Y	2026-08-01
t2	Ben		N
t3	Cy	Dee	N
t4	Ana	Ben	Y	2025-12-01

Status (F2)

=IF(D2="Y",IF(TODAY()-E2>180,"STALE","COVERED"),IF(C2="","SINGLE POINT","AT RISK"))

SINGLE POINT: not written down and nobody else knows it. Highest priority.
AT RISK: not written down, but at least a second person knows it.
STALE: written down, but nobody has confirmed it in six months. Processes drift; old notes can be worse than none.
COVERED: written and recently checked.

With 2026-10-15 as today, t1 is COVERED, t2 is SINGLE POINT, t3 is AT RISK, and t4 is STALE because its last check was more than 180 days ago. Change 180 to suit how fast your processes change.

Count the most urgent rows with:

=COUNTIF(F:F,"SINGLE POINT")

Step 3: Prioritise

You won't capture everything, and you don't need to. Add a column for impact, a simple 1–3, and ask: if nobody could do this tomorrow, how bad would it be? Start with SINGLE POINT rows that score 3. A team that captures its top ten topics has done more than one that writes a hundred-page manual nobody reads.

Step 4: Run a 20-minute capture interview

Experts are usually busy, and asking them to "write it up" tends to stall. Instead, have someone else interview them and do the writing. A structure that works:

When does this come up? (2 minutes) What triggers the task or question.
Walk me through the last time. (8 minutes) Concrete steps, in order. Ask "then what?" repeatedly.
What goes wrong? (5 minutes) Common mistakes, warning signs, and what to do about them.
Who else is involved? (3 minutes) People, systems, and files you need.
What would you tell someone doing it for the first time? (2 minutes) This often surfaces the most useful line in the whole note.

The interviewer writes it up the same day, keeping it short: a title, when it applies, numbered steps, and a "watch out for" section. The expert reviews it, then the register is updated: D becomes Y and E gets today's date.

Step 5: Turn a backup into a real backup

Writing something down is half the job. For SINGLE POINT and AT RISK topics, name a backup person and have them do the task once, using the write-up, while the expert watches. Anything they get stuck on goes back into the note. Then put the backup's name in column C.

Step 6: Keep it alive

Quarterly: filter for STALE and ask the person who knows to confirm or update each note.
When someone changes role or gives notice: filter the register by their name. Every row where they are the only person who knows becomes this month's priority.
When a new starter asks a question twice: check whether it should be a topic in the register.

Common questions

Where should the write-ups live? Wherever your team already looks for documents. A note in a place nobody visits is still tribal knowledge.

What about knowledge that's hard to write down, like judgment calls? Capture the examples. "Last time we saw X we did Y because Z" is far more useful than an abstract rule.

Start with the register and one interview this week. The first SINGLE POINT you close is the one you won't be scrambling for later.

Knowledge transfer when contractors rotate out: track what only they know before their end date

Duaer Team — Thu, 15 Oct 2026 01:08:01 +0000

This article is AI-generated.

A commenter on Hacker News put it plainly: "Even with the best documentation people will build up knowledge that no one has, and their departure is costly."

With employees, there's usually a notice period and some kind of handover routine. Contractors are different. Their end date is in a contract that sits with procurement or finance, the team lead finds out two weeks before, and the handover becomes a rushed call on the last afternoon. Then the contractor's knowledge of why the pipeline is built that way, which customer needs the special export, or what to do when the overnight job fails leaves with them.

This guide shows a simple tracker for teams that rely on rotating contractors: one row per contractor, their end date, a named successor, and a count of knowledge items listed, written up and confirmed. Two formulas tell you who's at risk of leaving with gaps.

Why contractor handovers go wrong

End dates are invisible to the team. The date is known, just not by the people who need to plan the handover.
No successor is named. "The team" will pick it up, which means nobody.
Documentation is measured by volume, not coverage. A 40-page wiki can still miss the three things that actually break.
Nobody checks the successor can do it. Writing something down isn't the same as someone else being able to use it.

Step 1: Pull end dates into one place

Ask whoever holds contractor agreements for a list of current contractors and end dates, including any extension decisions pending. Put them in a sheet the team lead can see. If an extension is likely but not signed, keep the current end date; plan for the date you actually have.

Step 2: Build the tracker

Column	What goes in it
A Contractor	Name or placeholder
B Area	What they own: "Data pipeline", "Network", "Billing scripts"
C End date	From the contract list
D Successor	One named person
E Items listed	Number of knowledge items on their list (see Step 3)
F Items written up	How many have a written note
G Items confirmed	How many the successor has done or explained back
H Coverage	Formula
I Status	Formula

H2, coverage:

=IF(E2=0,"",G2/E2)

Format as a percentage. Note it uses confirmed items, not written ones.

I2, status:

=IF(D2="","NO SUCCESSOR",IF(E2=0,"NO LIST",IF(G2>=E2,"DONE",IF(C2<TODAY(),"LEFT WITH GAPS",IF(C2-TODAY()<=14,"AT RISK","IN PROGRESS")))))

The order is deliberate: without a successor nothing else matters; without a list you can't measure anything; once every item is confirmed you're done regardless of dates; otherwise the end date decides how urgent it is. The 14-day window is a starting point; use whatever fits how long your handovers take.

Illustrative example (assume today is 15 October 2026):

Contractor	Area	End date	Successor	Listed / written / confirmed	Coverage	Status
Contractor A	Data pipeline	2026-10-22	Employee B	12 / 9 / 5	42%	AT RISK
Contractor C	Network	2026-10-10	Employee D	8 / 8 / 6	75%	LEFT WITH GAPS
Contractor E	Billing scripts	2026-12-01	(blank)	0 / 0 / 0		NO SUCCESSOR
Contractor F	Reporting	2026-10-09	Employee G	6 / 6 / 6	100%	DONE
Contractor H	Integrations	2026-11-20	Employee B	5 / 1 / 0	0%	IN PROGRESS

Contractor C is the useful lesson: everything was written up, but two items were never confirmed by the successor, and the contractor has already gone.

Step 3: Build the knowledge list with the contractor

The list is the core of this. Sit down with the contractor early (four to six weeks before the end date if you can) and go through:

Things that break and how they fix them. Ask: "What have you fixed more than once?"
Things only they do. Scheduled jobs, manual steps, monthly fixes.
Why decisions were made. The odd configuration that looks wrong but isn't.
Who they talk to. People in other teams or at vendors, and about what.
Where things live. Repos, folders, dashboards: the file name and location for each.

Each becomes one item. Keep items small enough that someone can confirm them in one sitting.

Step 4: Confirm, don't just collect

An item counts as confirmed when the successor has either done the task with the contractor watching, or explained it back without notes. Then the written note gets updated with anything that came up.

Book short sessions, one or two items each, spread across the remaining weeks. Update columns F and G after each one.

Step 5: Review weekly

Once a week, sort by status. NO SUCCESSOR and AT RISK go to whoever can assign people or extend the contract. LEFT WITH GAPS means writing down what the successor still needs and, where agreements allow, arranging a short follow-up call with the former contractor. Whether follow-up after the end date is possible depends on the contract; ask whoever manages contractor agreements.

Common questions

What if the contractor is extended?
Update the end date and keep going. Coverage never hurts.

What if there are dozens of contractors?
Start with the ones whose end date is within 60 days, and the ones who own something nobody else understands.

Isn't this the contractor's job?
Writing notes, yes. Making sure someone can use them belongs to the team that stays.

Wrapping up

Contractor knowledge loss is predictable because end dates are known in advance. One tracker with end dates, named successors and confirmed coverage turns a last-day scramble into a few weeks of short sessions, and it shows early which handovers are at risk.

How to follow up on action items: when to nudge, when to escalate, and how to close the loop

Duaer Team — Wed, 14 Oct 2026 01:11:11 +0000

This article is AI-generated.

The tracker is usually not the problem. Most teams have somewhere the action items live. What goes wrong is the bit between meetings: nobody is sure when it's polite to nudge, so nobody does; overdue items get raised once and then forgotten; and items that were quietly finished never get marked done, so the list stops being believable.

This article is about the follow-up routine, not the tracker layout. It covers a simple rule for when to nudge, when to escalate, and how to close items properly, plus one formula that tells you which of the three to do for each row today. The day counts are illustrative; pick the ones that suit your team. Names are placeholders.

The minimum columns

You only need six columns for the routine to work:

Column	Field
A	Action (written as something you can check)
B	Owner (one person)
C	Due date
D	Status: Open / In progress / Done / Dropped
E	Done on
F	Last nudged

The column people skip is Last nudged. Without it, you can't tell whether you're about to nudge someone for the first time or the fourth.

The rule

Here's an example rule (adjust the numbers):

One working day before due: a heads-up to the owner. Short, no pressure.
Overdue: a nudge, then wait 3 days before nudging again.
7 days overdue: escalate. Raise it with the person who set the priority, or put it on the next meeting's agenda by name.
Done without a date: ask the owner to add the date. An item isn't closed until it says when.
No owner or no due date: fix that first. You can't follow up on an item that belongs to nobody.

One formula for "what do I do today?"

G2:

=IF(D2="Dropped","",IF(D2="Done",IF(E2="","DONE - ADD DATE",""),IF(B2="","NO OWNER",IF(C2="","NO DUE DATE",IF(TODAY()-C2>=7,"ESCALATE",IF(C2<TODAY(),IF(OR(F2="",TODAY()-F2>=3),"NUDGE","WAIT"),IF(C2-TODAY()<=1,"HEADS-UP","")))))))

We ran it in LibreOffice with today set to 2026-10-14, covering the awkward cases:

Action	Owner	Due	Status	Done on	Last nudged	Next step
Send revised layout	Owner A	2026-10-15	Open			HEADS-UP
Book supplier visit	Owner B	2026-10-10	In progress			NUDGE
Update training slides	Owner B	2026-10-10	In progress		2026-10-13	WAIT
Confirm spare parts list	Owner C	2026-10-01	Open		2026-10-13	ESCALATE
Share site photos	Owner A	2026-10-09	Done			DONE - ADD DATE
Circulate notes	Owner A	2026-10-09	Done	2026-10-09		(blank)
Review layout options	Owner C	(blank)	Open			NO DUE DATE
Draft visitor rules	(blank)	2026-10-20	Open			NO OWNER
Old request	Owner C	2026-10-01	Dropped			(blank)

(Illustrative data.)

"In progress" doesn't stop an item counting as overdue. Owners saying they're on it is useful information, but the due date still passed.

How to word the nudge

Name the item and the date, not "just checking in".
Ask one question: what's blocking it, and what's the new date?
Make it easy to say "done": "If it's finished, reply with the date and I'll close it."
Write the new date into the tracker and keep the original due date in its own column, so slips stay visible.
Update Last nudged the same day.

Closing the loop

At the next meeting, go through only three groups: ESCALATE, NUDGE, and DONE - ADD DATE. Read out what was closed since last time in one line. Items that were dropped get a sentence on who decided and why, then stay in the sheet as history.

Common gaps

Nudging by memory. Without Last nudged, some people get chased daily and others never.
Escalation that's a surprise. Agree the escalation rule in advance so it isn't personal.
Moving the due date silently. Keep the original date visible.
"Done" with nothing to show. A done date (and where the output is) makes it checkable.
No owner on new items. Assign one before the meeting ends.

Following up well isn't about being pushy. It's about a rule everyone knows in advance, a record of when you last asked, and a clear moment when an item is closed. With those three, the list stays believable.

Repeated training sessions for employees: how to stop running the same session every month

Duaer Team — Wed, 14 Oct 2026 01:05:51 +0000

This article is AI-generated.

Someone in an HR community recently wrote: "we have experienced a need for intensive and repeated training sessions for our employees". If you run training in operations, quality or a warehouse, you probably know why. You deliver the session, people sign the sheet, and three weeks later the same questions come back. So you schedule another session.

Repeated training isn't always a sign that people weren't listening. Usually it means three things are missing: a record of who was trained on which version, a place where answers live after the session ends, and a way to spot who actually needs a refresher instead of retraining everyone.

This guide shows a lightweight setup in any spreadsheet: a training matrix with two formulas that tell you exactly who needs what, and a question log that turns repeated questions into written answers.

Why the same sessions keep happening

Look at your last few repeated sessions and you'll usually find one of these:

The procedure changed, but only some people heard. Half the team was trained on version 2, the procedure is now on version 3, and nobody tracks the difference.
Answers stayed in the room. Questions asked during a session got good answers, but nobody wrote them down. The next person with the same question has to ask again, or wait for the next session.
Refreshers are all-or-nothing. Without a record of who was trained when, the only safe option is to retrain everyone.

Step 1: Build a training matrix

One row per person per procedure. Columns:

Column	What goes in it
A Employee	Use names or IDs your company is comfortable keeping in a sheet
B Procedure	e.g. "Forklift pre-use check"
C Version trained	The version they were trained on
D Current version	The version in use now
E Date trained	A date; blank if never trained
F Refresher (months)	Your company's interval for this procedure
G Refresher due	Formula
H Status	Formula

G2, refresher due:

=IF(E2="","",EDATE(E2,F2))

Format as a date.

H2, status:

=IF(E2="","NOT TRAINED",IF(C2<>D2,"NEW VERSION",IF(G2<TODAY(),"REFRESHER DUE",IF(G2-TODAY()<=30,"DUE IN 30 DAYS","OK"))))

Fill both down. The order matters: someone who was never trained comes first; someone trained on an old version comes next, even if their refresher date is far away, because what they learned no longer matches the procedure.

How often a refresher is required depends on the procedure and your company's rules. If it's a safety or regulated task, ask your HR, safety or legal contact what interval applies; the sheet just tracks whatever you decide.

Illustrative example (assume today is 14 October 2026):

Employee	Procedure	Trained / current	Date trained	Refresher due	Status
Employee A	Forklift pre-use check	v3 / v3	2025-11-01	2026-11-01	DUE IN 30 DAYS
Employee B	Forklift pre-use check	v2 / v3	2026-05-01	2027-05-01	NEW VERSION
Employee C	Forklift pre-use check	v3 / v3	2025-09-01	2026-09-01	REFRESHER DUE
Employee D	Goods-in inspection	– / v5	(blank)		NOT TRAINED
Employee A	Goods-in inspection	v5 / v5	2026-08-01	2027-08-01	OK

To see how many people need a session on one procedure, put the procedure name in a cell (say J1) and use:

=COUNTIFS(B2:B500,J1,H2:H500,"<>OK")

In the example, three people need something on the forklift check, but for different reasons. Employee B only needs the v2-to-v3 changes, not the full session. That alone can turn a full repeat session into a fifteen-minute briefing.

Step 2: Keep a question log

During and after every session, write down every question, in the words people used. One column for the question, one for the procedure, one for the answer, one for where the answer is written down (file name and location).

To spot repeats, add a count next to each question (questions in A10:A200):

=COUNTIF(A$10:A$200,A10)

And a flag that shows once per repeated question:

=IF(AND(B10>=3,COUNTIF(A$10:A10,A10)=1),"WRITE IT DOWN","")

Any question asked three times gets written into the procedure or a short FAQ next to it. Exact wording varies, so tidy similar questions into one phrasing when you log them; otherwise the count won't catch them.

Step 3: Put answers where people work

A written answer only stops repeat training if people can find it at the moment they need it:

Keep the FAQ next to the procedure, in the same folder, with the same name plus "FAQ".
Point to it at the workstation. A short note or QR code on the station: "Questions? See [procedure] FAQ."
Answer with the link. When someone asks a question that's already answered, reply with the location of the answer, not just the answer.

Step 4: Run sessions from the matrix

Before scheduling any training, filter the matrix:

NOT TRAINED: full session.
NEW VERSION: a short briefing on what changed, using the procedure's change notes.
REFRESHER DUE / DUE IN 30 DAYS: a refresher, grouped by procedure.
OK: nothing.

After each session, update columns C and E, and add any new questions to the log.

Common questions

Isn't this a lot of admin?
The matrix takes an afternoon to set up for one team. After that it's one row update per person per session, less time than one unnecessary repeat session.

What about people who were trained but still get it wrong?
That's a sign the procedure or the answer isn't clear. Check the question log for that procedure first.

Should training records be kept in a spreadsheet?
If your company has formal record-keeping requirements for training, check with HR or quality where the official record must live. The matrix can still be your working view.

Wrapping up

Repeated training sessions usually come from missing records, not forgetful people. A training matrix tells you who needs what, a question log tells you what to write down, and putting answers next to the procedure means fewer people need to ask in the first place.

How to chase suppliers for missing documents without chasing from memory

Duaer Team — Tue, 13 Oct 2026 13:13:23 +0000

This article is AI-generated.

Anyone who handles supplier paperwork knows the routine: a certificate of conformity that never arrived with the delivery, a safety data sheet that's two revisions old, an insurance certificate that expired last month. You email, you wait, you forget, you email again. One commenter on Reddit summed it up: "Chasing is a poor use of company resources ( your time)".

The problem usually isn't that suppliers refuse. It's that nobody on your side has a list of what's missing, when it was asked for, and when to ask again. This guide shows a simple routine that works in any spreadsheet: one register of missing documents, three formulas that tell you who to chase today and who to escalate, a fixed chase sequence, and a short message template. It's written for purchasing, quality and operations teams in manufacturing, distribution and logistics.

Step 1: Decide what you need, once

Before chasing anything, agree internally what a complete supplier file looks like. For most teams it's a short list per supplier type, for example:

certificates of conformity or analysis for each delivery or batch;
safety data sheets for chemicals, at the current revision;
quality or management system certificates, with expiry dates;
insurance certificates;
any customer-specific declarations you have to pass on.

Write this list down. Half of the chasing in most companies comes from asking for different things at different times, so suppliers never know when they're done.

Step 2: One register, one row per missing document

Don't track missing paperwork in your inbox. Track it in a register with one row for each document you're waiting for:

Supplier	Document	Requested	Due	Last chased	Chases	Status	Days overdue	Next chase	Flag	Owner
Supplier 1 (illustrative)	CoC, PO 4471	2026-09-20	2026-10-01	2026-10-06	1	Waiting	12	2026-10-13	CHASE TODAY	Buyer A
Supplier 2 (illustrative)	SDS rev. current	2026-10-01	2026-10-15		0	Waiting		2026-10-08	CHASE TODAY	Quality B
Supplier 3 (illustrative)	ISO certificate	2026-09-01	2026-09-15	2026-10-08	3	Waiting	28	2026-10-15	ESCALATE	Buyer A
Supplier 4 (illustrative)	CoA, batch 0912	2026-09-01	2026-09-15	2026-09-20	1	Received				Quality B

A few rules make this work:

One owner per row, a named person, not "Purchasing".
A due date for every request. "As soon as possible" can't be tracked. If the supplier hasn't committed to a date, set a reasonable one yourself, often 10 working days.
Status has three values only: Waiting, Received, Not needed. Anything else drifts.
Received means checked. Mark a row Received only after someone has confirmed it's the right document, the right revision and still valid.

Step 3: Three formulas

Assume Requested is in column C, Due in D, Last chased in E, Chases in F and Status in G.

Days overdue (column H):

=IF(OR(G2<>"Waiting",D2=""),"",IF(TODAY()>D2,TODAY()-D2,""))

Blank unless the row is Waiting with a due date set; otherwise the number of days past due.

Next chase (column I), a week after the last chase, or a week after the request if you've never chased:

=IF(G2<>"Waiting","",IF(E2="",C2+7,E2+7))

Format the column as a date.

Flag (column J):

=IF(G2<>"Waiting","",IF(AND(F2>=3,D2<>"",TODAY()>D2),"ESCALATE",IF(AND(I2<>"",I2<=TODAY()),"CHASE TODAY","")))

After three chases on an overdue document, it stops being a chasing job and becomes an escalation. Otherwise, any row whose next chase date has arrived shows CHASE TODAY.

I tested these in LibreOffice Calc with a fixed date of 2026-10-13 in place of TODAY(), using the four rows above plus one with no due date. The results matched the table: 12 and 28 days overdue, CHASE TODAY for suppliers 1 and 2, ESCALATE for supplier 3, blanks for the received row, and no flag for a request sent on 2026-10-10 (next chase 2026-10-17). In some locales you'll need semicolons instead of commas between arguments.

Step 4: A fixed chase sequence

Request: send one message listing every missing document for that supplier, not one email per document. Give a due date.
First chase, a week later: reply on the same thread so the history stays together. Restate what's still missing.
Second chase: copy the supplier's account manager or quality contact, if you have one.
Third chase: same thread, and say clearly what happens next, for example that the goods will stay in quarantine or that orders will be held, if that's your policy.
Escalate: when the flag says ESCALATE, the owner hands it to their manager or the person who owns the supplier relationship. They decide whether to hold orders, accept a deviation, or call the supplier.

After every chase, update Last chased and add one to Chases. That's what moves the next chase date forward and keeps the flags honest.

Step 5: A message that's easy to answer

Suppliers respond faster when they can see exactly what you need and can reply with attachments in one go. An example:

Missing documents (illustrative): Hello, we're still missing the following for our orders with you: (1) certificate of conformity for PO 4471, delivered 2026-09-25; (2) current safety data sheet for product X. The due date was 2026-10-01. Could you reply to this email with both attached by 2026-10-16? Thank you.

Keep it short, number the items, give a date, and always reply in the same thread.

Step 6: A weekly ten-minute review

Every Monday, the register owner filters on the Flag column and sends each owner their CHASE TODAY rows.
ESCALATE rows go to the weekly purchasing or quality meeting.
Rows marked Received are checked by a second person once a month, so "received" doesn't quietly mean "someone said they sent it".
When a buyer leaves or changes role, their open rows get a new owner as part of the handover.

Checklist

[ ] A written list of required documents per supplier type.
[ ] Every missing document has its own row, owner and due date.
[ ] Status is limited to Waiting, Received, Not needed.
[ ] Days overdue, Next chase and Flag formulas are set.
[ ] Last chased and Chases are updated after every chase.
[ ] Chases stay in one email thread per supplier.
[ ] ESCALATE rows have a named decision-maker.

Common mistakes

Chasing from memory. Some suppliers get three emails a week, others none. Fix: chase only what the register flags.
One email per document. Suppliers lose track. Fix: one numbered list per supplier.
No due date. Nothing is ever overdue. Fix: always give a date.
Marking Received too early. The wrong revision gets filed. Fix: check before you mark it.
Chasing forever. Ten polite reminders don't change anything. Fix: escalate after three.

Contract notice period reminders: how to catch the window before an auto-renewal

Duaer Team — Tue, 13 Oct 2026 11:04:01 +0000

This article is AI-generated.

Many service, software, equipment and maintenance contracts renew automatically unless you give notice. The trap isn't the renewal date itself. It's the notice period in front of it. If a contract ends on 31 January and requires 90 days' written notice, the real deadline is early November, and by the time anyone notices the end date, the decision has already been made for you.

This guide shows a simple routine that works in any spreadsheet: a register that records the notice deadline rather than just the end date, one formula that tells you which contracts need a decision now, a fixed sequence for deciding and sending notice, and a habit of writing down proof that notice went out. It's written for operations, procurement and finance teams who look after a few dozen to a few hundred contracts.

Step 1: Read three things from each contract

For every contract that can renew automatically, find:

The end date of the current term. Not the signing date.
The notice period. Usually in days or months, and sometimes "before the end of the term" or "before the anniversary date".
How notice must be given. In writing, by email to a specific address, by letter to a registered office, through a customer portal. This matters as much as the date.

Write the clause reference next to each one so anyone can check it later. If the wording is unclear, mark the row "check with legal" rather than guessing. This guide is about tracking dates, not interpreting contracts.

Step 2: Build a register around the notice deadline

One row per contract. Illustrative (all names are placeholders):

Ref	Supplier	What it covers	Term end	Notice (days)	Notice deadline	Days left	Flag	Owner	How notice is given	Contract file (name and location)
CT-01	Supplier A	Equipment maintenance	2027-01-31	90	2026-11-02	20	ACT NOW	Ops lead X	Letter to registered office	Contracts / Suppliers / CT-01_signed.pdf
CT-02	Supplier B	Software subscription	2027-02-28	90	2026-11-30	48	DECIDE	IT lead Y	Email to named address	Contracts / IT / CT-02_signed.pdf
CT-03	Supplier C	Cleaning services	2026-11-30	60	2026-10-01	-12	MISSED	Facilities Z	Written notice	Contracts / Facilities / CT-03_signed.pdf

The key columns:

Notice deadline is the date you sort and filter by. It's the term end minus the notice period.
Owner is one named person who decides whether to renew, not a department.
How notice is given saves a scramble on the last day, when someone discovers the letter needs a signature and a courier.

Step 3: Two formulas

With term end in column D and notice days in column E:

Notice deadline (column F):

=D2-E2

Days left until the deadline (column G):

=F2-TODAY()

Flag (column H):

=IF(G2<0,"MISSED",IF(G2<=30,"ACT NOW",IF(G2<=60,"DECIDE","")))

I checked these in LibreOffice Calc with 13 October 2026 standing in for TODAY(). The three illustrative rows above came out as shown: CT-01 gave a deadline of 2 November with 20 days left (ACT NOW), CT-02 gave 30 November with 48 days left (DECIDE), and CT-03's deadline had passed 12 days earlier (MISSED). Format column F as a date. In some locales, use semicolons between arguments.

If the notice period is in months, use =EDATE(D2,-E2) instead of =D2-E2 and enter months in column E. Calendar months and days don't line up, so match what the contract says.

Step 4: Decide early, act on a fixed sequence

The flags map to a routine:

DECIDE (31–60 days before the deadline): the owner answers one question: renew as is, renegotiate, or end it? If renegotiating, this is the time to talk to the supplier, while you still have the option to leave.
ACT NOW (0–30 days): if ending or renegotiating, prepare and send the notice in the required form. Don't wait for the last week. Letters get lost, the named email address may have changed, and a signatory may be away.
MISSED: record it, check the contract for the next opportunity to give notice, and set the new deadline in the register. Then look at why it was missed, which is usually an owner who left or a contract that was never in the register.

A short message from whoever runs the weekly check keeps things moving. Illustrative:

Notice reminder (illustrative): CT-01 Equipment maintenance, Supplier A. Term ends 31 Jan 2027, 90 days' notice, so the deadline is 2 Nov 2026 (20 days left). Notice must be a letter to their registered office. Please confirm by Friday: renew, renegotiate or end?

Step 5: Keep proof that notice was sent

Add two columns: Notice sent on and Proof (file name and location). Proof might be a scanned letter with a courier receipt, or an email saved as a file with its headers. When someone asks a year later whether you really cancelled, you can point to the file rather than to someone's memory.

Once notice is sent, clear the flag by adding a status column ("Notice sent", "Renewed", "Ended") at the end of the register (column N, if the two proof columns are L and M) and wrapping the flag formula so it only shows for open rows:

=IF(N2<>"","",IF(G2<0,"MISSED",IF(G2<=30,"ACT NOW",IF(G2<=60,"DECIDE",""))))

Step 6: One weekly check, one owner for the register

Weekly: someone sorts by notice deadline, filters on the flag column, and messages each owner with a flagged row. Ten minutes.
When contracts are signed: the new contract doesn't count as filed until its row exists. This is how you stop contracts from never entering the register.
When people leave: their rows get a new owner as part of the handover.

Checklist

[ ] Every auto-renewing contract has a row.
[ ] Term end, notice period and notice method are taken from the contract, with the clause reference.
[ ] Notice deadline is calculated, and the register is sorted by it.
[ ] Flags show DECIDE, ACT NOW and MISSED.
[ ] Each row has one named owner.
[ ] Notice sent date and proof are recorded.
[ ] Someone checks weekly, and new contracts are added on signing.

Common mistakes

Tracking only the end date. The decision window has closed before the end date looks urgent. Fix: sort by notice deadline.
Assuming email is enough. Some contracts require a letter or a specific address. Fix: record the notice method in the register.
A department as owner. Nobody acts. Fix: one named person.
No proof kept. Disputes become your word against theirs. Fix: file the proof and note its location.
Months treated as days. "Three months" isn't always 90 days. Fix: use EDATE when the contract says months.

Onboarding buddy program: what the buddy does, how much time it takes, and what they don't answer

Duaer Team — Mon, 12 Oct 2026 01:23:53 +0000

This article is AI-generated.

An onboarding buddy is the colleague a new starter can ask the small questions: where things are, how people actually do things here, who to talk to. When it works, new people settle faster and managers get fewer interruptions. When it doesn't, the buddy is either a name on a welcome email who never gets asked anything, or the person who ends up answering every question for three months.

This article covers how to set up a buddy program that holds up: what the role is, how much time to set aside, and a clear split between what the buddy answers and what should already be written down. It isn't about planning the first 30 days of training or about handling repeated questions in general. Examples are illustrative, with placeholder names.

Define the role in one paragraph

Write down what the buddy is for before you pick anyone. A version you can adapt:

The buddy helps the new starter find their way around in the first few weeks: introductions, everyday how-we-do-it questions, and pointing to the right document or person. The buddy is not the new starter's manager or trainer, and doesn't assess their work. (illustrative)

That last sentence matters. If the role isn't separated from training and management, the buddy ends up doing all three.

Choosing a buddy

Not the manager. New people ask different questions when the person can't judge them.
Been here long enough to know where things are, but close enough to the new starter's work to be useful.
Willing. Ask, don't assign. A reluctant buddy is worse than none.
Has the time. Agree it with their manager, so it isn't squeezed into lunch breaks.

Set the time explicitly

A buddy program fails quietly when nobody budgets the time. Agree on a rough shape up front, for example (illustrative):

Period	Buddy time
Week 1	A short check-in each day
Weeks 2–4	Two check-ins a week
Weeks 5–8	One check-in a week, then end

Put an end date on it. It gives both people permission to stop, and it's a natural point to ask what worked.

What the buddy answers, and what they don't

This split is the core of the program. Write it as a short table and give it to both people on day one.

Question type	Who answers	Example (illustrative)
Where is something / who do I ask	Buddy, then point to the document	"Where are the expense forms?"
How do people usually do this here	Buddy	"Do people book meeting rooms or just use them?"
Rules, policies, procedures	The written document; buddy shows where it is	"What's the approval step for purchases?"
How to do my actual job	Manager or trainer	"How do I prepare the weekly report?"
Anything about workload, priorities or personal matters	Manager

The buddy's most useful habit is "let me show you where that's written", not "here's the answer". Each time they point to a document, the new starter learns where to look next time. Each time they answer from memory, the knowledge stays in their head.

A buddy checklist

Give the buddy a one-page list (illustrative):

[ ] Day 1: introduce the new starter to the people they'll work with most
[ ] Day 1: show where the team's shared documents and procedures live
[ ] Week 1: lunch or coffee, no agenda
[ ] Week 2: ask what they've had trouble finding
[ ] Week 4: ask which questions they've asked more than once
[ ] End: pass the list of repeated questions to the manager

Turn repeated questions into documents

The last item on that checklist is where a buddy program pays off beyond one person. If a new starter asked the same thing twice, or the buddy answered it from memory, the answer probably isn't written down anywhere obvious. The manager decides whether to add it to the onboarding documents. The next new starter then finds it without asking.

Common pitfalls

Buddy becomes trainer. Keep the split table visible.
No end date. The relationship drifts and neither person knows if it's still on.
Buddy is the only source. If every answer comes from one person, nothing gets written down.
No feedback. Ask both people at the end what they'd change.

Wrap-up

A buddy program works when the role is narrow, the time is agreed, and the buddy points to documents rather than replacing them. Set those three things up and the program helps the next new starter too, not just this one.

How to track follow-up tasks so nothing quietly stalls

Duaer Team — Sun, 11 Oct 2026 01:18:31 +0000

Follow-up work is the stuff that happens after the "real" task: chasing a reply, checking that a fix actually shipped, confirming that a request someone promised to handle got handled. It's rarely hard. It just slips. One person in an automation forum listed the usual casualties: "a client wrote and nobody replied, a deal sat untouched for weeks, a payment was started and never finished."

None of those are failures of skill. They are failures of tracking. This article walks through a simple, tool-agnostic way to track follow-up tasks for yourself or a small team: what columns to keep, what each status means, how to run a weekly overdue review, and a formula you can drop into a spreadsheet to flag what's late. It isn't about meeting action items specifically; it covers any loose end that needs someone to come back to it.

Why follow-ups get lost

Follow-ups have three properties that make them easy to drop:

They're triggered by something else. You send an email and the follow-up is "check for a reply on Thursday". The original task feels finished, so the follow-up never gets written down.
They depend on other people. You can't complete them alone, so they sit in a vague "waiting" state with no date.
They're small. Nobody wants a project plan for "ping the supplier again", so they live in memory, chat history or a sticky note.

A tracker fixes all three if it does one thing well: every follow-up gets a line, an owner and a date the moment it's created.

Step 1: Pick one place

The specific tool matters much less than having exactly one. A spreadsheet, a task app, a plain text file—any of these works if it's the only place follow-ups live. The common failure is a split: some in email flags, some in a notebook, some in a chat "saved messages" list. Then the weekly review has to search four places and nobody does it.

If you're tracking for a team, use a shared spreadsheet or shared list everyone can see. Visibility is half the value: people follow up faster when the item has their name on it in public.

Step 2: Use a small set of columns

Here is a layout that works for most people. Keep it this small at first; add columns only when you notice you keep needing the information.

Column	What to write	Why it matters
ID	A short number (F-001, F-002…)	Lets you refer to an item in chat without retyping it
What	The follow-up as an action: "Get signed quote back from Supplier X"	A verb forces clarity about what "done" is
Owner	One name	Two owners means no owner
Waiting on	Who or what you're waiting for, if anyone	Separates "my move" from "their move"
Created	Date the item was added	Shows how long things really take
Next check	The date you'll look at it again	The single most important column
Status	One of the defined statuses below	Lets you filter
Done when	One sentence describing completion	Stops items closing too early
Notes	Latest update, with date	History without a separate log

Illustrative rows:

ID	What	Owner	Waiting on	Created	Next check	Status	Done when
F-014	Get signed quote back	Person A	Supplier X	2026-10-02	2026-10-08	Waiting	Signed PDF saved in contracts folder
F-015	Confirm login fix works for user	Person B	—	2026-10-09	2026-10-12	Open	User confirms they can log in
F-016	Reply to client question about invoice	Person A	—	2026-10-10	2026-10-20	Open	Reply sent and client acknowledged

Note the column called Next check rather than "Due". Many follow-ups don't have a real deadline, but every one of them needs a date when somebody looks again. If you leave this blank, the item is already lost.

Step 3: Define your statuses and stick to them

Statuses only help if everyone means the same thing. Four is usually enough:

Open — the owner needs to act next.
Waiting — someone else needs to act; the owner checks again on the next-check date.
Blocked — it can't move until something specific changes; the note says what.
Done — the "Done when" sentence is true. Not "mostly", not "I sent it".

Two rules make statuses trustworthy:

Every status change gets a dated note. "2026-10-08 chased by email, they said Friday" is enough.
Waiting always has a next-check date. "Waiting" without a date is how deals sit untouched for weeks.

Avoid adding statuses like "In progress" or "Almost done". They feel informative but don't tell anyone what to do next.

Step 4: Capture follow-ups at the moment they're created

The tracker is only as good as what goes into it. Build the habit of adding a line at the exact moment a follow-up is born:

You send an email that needs a reply → add a line with next check in two or three working days.
Someone promises to do something for you → add a line with them in "Waiting on".
You hand something to a colleague → add a line, owner is them, and tell them.
A ticket or request is "fixed" → add a line to confirm with the requester.

If adding a line takes more than thirty seconds, the tracker is too complicated. Trim columns until it doesn't.

Step 5: Flag overdue items automatically

A spreadsheet can do the nagging for you. Add a Flag column with a formula that looks at the status and the next-check date. Assuming Next check is in column F and Status in column G, put this in row 2 and fill down:

=IF(G2="Done","",IF(F2<TODAY(),"Overdue",IF(F2-TODAY()<=2,"Due soon","")))

What it does:

Done items show nothing.
If the next-check date has passed, it shows Overdue.
If it's within two days, it shows Due soon.
Otherwise it stays blank.

I tested the logic in LibreOffice Calc with a fixed reference date of 2026-10-11 in place of TODAY(): a Waiting item dated 2026-10-08 showed Overdue, an Open item dated 2026-10-12 showed Due soon, an Open item dated 2026-10-20 stayed blank, and a Done item dated 2026-10-01 stayed blank. Depending on your locale, LibreOffice may expect semicolons instead of commas between arguments.

Add conditional formatting so "Overdue" turns red and "Due soon" turns amber, then sort or filter by the Flag column. That view is your daily list.

Step 6: Run a weekly overdue review

Daily glances catch the urgent items. A weekly review keeps the tracker honest. Set a fixed fifteen-minute slot, same day each week, and go through it in this order:

Overdue first. For each one: act now, set a new next-check date with a note explaining why, or close it.
Waiting items. Has the other person gone quiet twice? Change the approach: call instead of emailing, or ask whoever can unblock it.
Blocked items. Is the blocker still real? If it's been blocked for more than two weeks, raise it with someone who can decide.
Items with no next-check date. There shouldn't be any. Add one.
Done items. Move them to a "Closed" sheet so the active list stays short. Don't delete them; the history is useful.

For a team, do this review together for the overdue items only, and keep it brisk. The goal is decisions, not status reports.

Step 7: Decide when to escalate

Some follow-ups will never close by politeness alone. A simple rule removes the awkwardness of deciding each time:

Second missed next-check on a Waiting item → change channel (phone, a direct message, or in person).
Third missed next-check → tell the person who asked for the work, or someone who can make the call.
Blocked for two weekly reviews → escalate with a one-line summary: what's needed, from whom, since when.

Write the rule at the top of the tracker so it's not personal when you apply it.

A checklist for a healthy tracker

[ ] Every item has exactly one owner.
[ ] Every non-Done item has a next-check date.
[ ] Every Waiting item says who it's waiting on.
[ ] Every item has a "Done when" sentence.
[ ] The Flag column shows no overdue items older than a week.
[ ] Done items have been moved out this week.

Common mistakes

Tracking tasks instead of follow-ups. The tracker becomes a full to-do list and the follow-ups drown. Fix: only add items that depend on coming back later or on someone else.
Shared ownership. "Person A / Person B" means each assumes the other did it. Fix: one name; mention the second person in Notes.
Closing on effort, not outcome. "Emailed them" isn't done. Fix: the "Done when" column.
Skipping the weekly review when busy. That's exactly when things slip. Fix: keep it to fifteen minutes and review overdue items only if time is short.
Endless date pushing. Moving next check forward without a note hides a stuck item. Fix: every date change needs a dated note, and the escalation rule applies after two misses.

Wrapping up

Tracking follow-up tasks comes down to a handful of habits: one place, one owner, a next-check date on everything, clear statuses, a formula that flags what's late, and a short weekly review. None of it needs a special tool. Start with the columns above, add your current loose ends today, and run your first review at the end of the week.

This article was drafted with AI assistance.

Meeting action items tracker: one table, one owner per row, overdue first next time

Duaer Team — Sat, 10 Oct 2026 23:35:19 +0000

This article is AI-generated.

Meeting notes often end with a few lines like "maintenance to look at it", "follow up with the carrier", "someone to update the checklist". A week later nobody can say which of those happened. The notes weren't wrong. They just didn't say who, by when, or what finished looks like.

This article gives you a tracker layout to replace the to-do section of your meeting notes: the columns, a worked before and after, and how to open the next meeting by walking through overdue items first. How to nudge and escalate between meetings, and how to track personal tasks outside of meetings, are separate topics. Names and items below are illustrative.

The columns

Column	What goes in it	What not to write
A ID	A running number that is never reused, e.g. WH-118
B Raised	Which meeting it came from
C Action	One action, starting with a verb	"Packaging issue"
D Owner	One person's name	"Procurement", "Person A and Person B"
E Due date	A real date	"ASAP", "next week"
F Done when	The visible result that closes it	"follow up", "look into"
G Status	Open, In progress, Blocked, Done
H Last update	Date of the latest note
I Notes	One line: what's blocking it, or the new date
J Days overdue	Formula
K Sort order	Formula

One owner per row. Two names means each person assumes the other is doing it. If several people are involved, name one owner and list the others as "with" in the notes.

"Done when" is the column people skip. "Follow up with the customer" can stay open for a month. "Send the complaint analysis to Person A" is either sent or it isn't.

Two formulas

Days overdue, J2:

=IF(OR(G2="Done",E2=""),"",IF(E2<TODAY(),TODAY()-E2,""))

Sort order, K2, so overdue rows float to the top and rows with no due date don't hide at the bottom:

=IF(G2="Done",4,IF(E2="",1,IF(E2<TODAY(),2,3)))

1 is "missing a due date", 2 is "overdue", 3 is "on time", 4 is "done". Sort the sheet by column K, then by due date. Rows with no owner or no due date are the ones to fix before you even look at overdue items, because they will never become overdue on their own.

With illustrative data, assuming today is 2026-10-09:

ID	Raised	Owner	Due	Status	Days overdue	Order
WH-101	2026-09-25	Person A	2026-10-02	Open	7	2
WH-102	2026-09-25	Person B	2026-10-16	In progress		3
WH-103	2026-09-25	Person C	2026-10-05	Done		4
WH-110	2026-10-02	Person B	2026-10-07	Blocked	2	2
WH-111	2026-10-02	Person D	(blank)	Open		1

(illustrative data; formulas tested on this sheet in LibreOffice; the syntax is the same in Excel, but I haven't run each one in Excel itself)

WH-111 sorts above the overdue rows on purpose: until it has a due date, it can't be tracked at all.

Before and after

Before (illustrative), from a weekly warehouse meeting:

Action items: Dock door 4 keeps jamming, maintenance to look at it. Late carrier pickups again this week, follow up. Returns checklist is out of date, someone to update. Label printer on packing line 2, ASAP. Person A and Person B to sort out the cycle count backlog.

After (illustrative):

ID	Action	Owner	Due	Done when
WH-118	Book a repair for dock door 4	Person C	2026-10-12	Repair date confirmed in the maintenance log
WH-119	Send the carrier a list of this week's late pickups	Person A	2026-10-10	List sent, reply requested by 2026-10-14
WH-120	Update the returns checklist to the current process	Person D	2026-10-16	New version saved in "warehouse/checklists", old one moved to "retired"
WH-121	Get the packing line 2 label printer fixed or swapped	Person B	2026-10-10	Line 2 printing labels again
WH-122	Clear the cycle count backlog for aisles 1–6	Person A (with: Person B)	2026-10-20	Counts entered for aisles 1–6

(illustrative)

Every "before" line was a real concern. What was missing: "maintenance" and "someone" aren't people, "ASAP" isn't a date, "follow up" has no end, and two names on one line meant nobody owned it. The "after" version fixes those four things and nothing else.

Anything with no action and no owner, such as "everyone please keep aisles clear", stays in the notes as a reminder and stays out of the tracker.

How to run the tracker at the next meeting

Before the meeting, the person who writes the minutes sorts the tracker by column K and filters out Done.
Open the meeting with the tracker, in this order: rows with no owner or no due date, then overdue, then due before the next meeting.
Overdue rows get a new date in the notes, not in the due date column. Keep the original due date so the days-overdue column stays honest.
A row is only Done when its "done when" is met. "Mostly done" stays In progress with a note.
New actions from this meeting get added before you leave the room, or within the same day. A tracker updated three days later has already lost the details.

Keep this part short. If reviewing the tracker takes the whole meeting, the tracker has too many open rows, which is itself useful information.

A few rules that keep it usable

One tracker for the meeting series, not a fresh list inside each set of minutes. Minutes link to the tracker by ID: "see WH-120".
IDs never get reused. When an action is split, the original stays and the new part gets a new ID.
Blocked needs a name. A Blocked row should say in the notes who it's waiting on, otherwise it sits there indefinitely.
File name and location, not "see attachment". If an action produces a document, the notes say where it is, for example warehouse/checklists/returns-checklist_v4 (illustrative).

How to combine multiple Excel files with different columns into one fixed report, and check the totals

Duaer Team — Thu, 08 Oct 2026 01:16:56 +0000

If you work in operations, admin, a PMO or a budget office, you probably know the routine: every month or quarter, several projects, departments or regions each send you their own file or sheet, and you roll them up into one report with a fixed layout that goes to leadership or finance.

Disclosure: I'm on the Duaer team, and this article was drafted with AI help.

The merge itself is rarely the hard part. The hard parts are that no two sheets look alike, and that once the report is done, nobody can quite explain why the total is the number it is. This article walks through a method you can reuse every period: a column mapping table, a fixed set of cleaning rules, an exceptions table that separates "included after a fix" from "excluded", a reconciliation page that ties every number back to its source, and an acceptance checklist you can copy.

The images below come from an illustrative demo workbook we built: four regional source sheets, a merged detail sheet, an exceptions sheet, a summary report and a checks page. Every number in it is randomly generated, and row 1 of every sheet says so. None of it comes from a real business or a real transaction.

Why "everyone fills in their own sheet" goes wrong

When the sheets come from different people, a predictable set of problems shows up period after period:

Different column names and order. One region calls it "Order ID", another "Order #", a third "Order No". Dates are in column A in one sheet and column B in the next.
Mixed date formats. One sheet has real dates. Another has text such as 2026/7/3. A third has text such as 3 Jul 2026.
Amounts stored as text with commas. The cell shows 4,420.00, but it is a string. SUM quietly skips it, the total comes out low, and nothing warns you.
Subtotal rows mixed into the data. Someone adds a "month total" row at the end of each month. Treat it as an order and that month is counted twice.
Blank rows and exact duplicates. Left over from copy and paste.
One order ID on two rows with different quantities. The dangerous one, because there is no way to tell from the sheet which row is right.

None of these is hard to fix once. The problem is fixing them every period, slightly differently each time. The goal is to turn each fix into a written rule, keep the rules in the workbook, and leave a trail anyone can follow.

Before you start

Pin down the report layout. The best spec is last period's report, the one that was accepted. Which columns, which breakdown (for example month by region), where the totals sit. Once the layout is fixed, each period only the data changes.
Keep an untouched copy of every source sheet. Never clean in place. Every check later on goes back to the original, and an edited original cannot be reconciled.
Count the raw data rows per sheet. Everything below the header, including blank and subtotal rows. That count is where your reconciliation starts.
Decide what you don't want anyone deciding for you. If an order appears twice with different quantities, do you want the person doing the merge to pick one, or to list both for you to confirm? I'd strongly suggest the second.

Step 1: Build a column mapping table

The mapping table answers one question: for every column in every source sheet, which unified field does it feed, and what was done to it? It is the instruction sheet for the job. Next period you follow it again; if someone else takes over, they follow it too.

Here is the mapping sheet from the illustrative demo:

A header you can copy (illustrative values, swap in your own column names):

Unified field	Sheet A column	Sheet B column	Sheet C column	Handling
Order ID	Order ID	Order #	Order No	Kept as is; used for duplicate checks
Date	Date	Date (text, 2026/7/3)	Order time (text, 3 Jul 2026)	Converted to real dates, shown as YYYY-MM-DD
Region	(none)	(none)	(none)	Filled in from the sheet name
Amount	Amount	Amount (text with commas)	Deal amount	Commas removed, converted to numbers; blanks go to Exceptions
(not used)			Notes	Not in the report; kept in the source

Three rules for a good mapping table:

Every column of every sheet appears. Columns you don't need are listed as "not used", so the next person knows they were dropped on purpose.
The Handling column states a rule, not an outcome. "Commas removed, converted to numbers" works next period too. "Fixed" doesn't.
Fields the report needs but the sources lack say where they come from. Region from the sheet name, month from the date.

Step 2: Clean by category, with a fixed rule for each

With columns aligned, work through the problem types in this order. For each one, decide what happens to the row and where the evidence goes.

Text amounts. Strip the thousands separators and convert. A helper column in Excel or Sheets does it:

=VALUE(SUBSTITUTE(E3,",",""))

Mixed dates. Normalise text into something unambiguous before converting. DATEVALUE on a string like 3 Jul 2026 depends on your locale settings and failed in one of our test environments, so for that pattern a lookup on the month abbreviation is safer:

=DATE(VALUE(RIGHT(B3,4)),
      MATCH(MID(B3,FIND(" ",B3)+1,3),{"Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec"},0),
      VALUE(LEFT(B3,FIND(" ",B3)-1)))

For 2026/7/3, =DATEVALUE(SUBSTITUTE(B3,"/","-")) worked in our tests. Whatever you use, spot-check a few rows afterwards and confirm every date falls inside the reporting period.

Subtotal rows. They are not orders, so they stay out of the detail. Don't just throw them away, though. A subtotal is a number the sheet owner calculated themselves, which is exactly what you want to reconcile against later. Log each one in the exceptions table as "excluded, used as a cross-check".

Blank rows. Excluded, but logged with sheet and row number, so the gap between raw rows and merged rows can be explained line by line.

Exact duplicates. Only treat a row as a duplicate when the order ID and every other column match. Keep the first occurrence and log the rest. Building a key from the whole row is more reliable than checking the order ID alone:

=COUNTIF(K3:K2000,K3)

Here column K joins order ID, date, product, quantity and amount with a | separator; anything above 1 is a duplicate.

Same order ID, different quantity. Do not guess. "Keep the larger one" or "keep the later one" sounds reasonable, but either way you have made a business decision for someone else. Exclude both rows, list them as waiting for the owner's call, and add the confirmed row back once you hear.

Blank amounts. Two cases. If quantity and unit price are both present, you can fill in quantity × unit price and include the row, but it must be listed in the exceptions table so everyone knows the number was calculated. If quantity is missing too, leave it out and wait; don't estimate.

Step 3: An exceptions table that separates "included after fix" from "excluded"

Every row that was skipped, recalculated or put on hold goes into one exceptions table. This is the one from the illustrative demo:

Header to copy:

Source sheet	Source row	Order ID	Issue	Handling	Included	Amount involved

The "Included" column takes only Yes or No:

Yes means the row was corrected and is in the merged detail. The exceptions table is simply telling you it was touched.
No means the row is not in the merged result at all: blanks, subtotals, duplicates, and anything waiting for confirmation.

In this illustrative demo file, the four source sheets hold 6,324 raw data rows in total and the merged detail holds 6,303. The exceptions table has 25 rows: 21 excluded and 4 included after the amount was recalculated as quantity × unit price. The 21 excluded rows are 8 exact duplicates, 3 blank rows, 3 monthly subtotal rows, 3 rows with neither amount nor quantity, and 4 rows belonging to two order IDs that each appear twice with different quantities. Those four are all left out until the owner confirms. 6,303 plus 21 is 6,324, so every raw row is accounted for.

Step 4: A reconciliation page that explains the total

This is the page worth the most effort. It doesn't ask whether the report looks right; it asks whether a handful of equations hold. The checks page from the illustrative demo:

Three groups of checks cover most of the risk.

Per sheet, rows and amounts. One line per source sheet: raw data rows, merged rows, excluded rows from the exceptions table. Then the source amount calculated under the same rules, and the merged amount.

=IF(B3=C3+D3,"Match","Mismatch")
=IF(ROUND(F3-G3,2)=0,"Match","Mismatch")

"Calculated under the same rules" is doing real work there. Text amounts are summed after stripping commas. A sheet with subtotal rows is summed without them. A sheet with recalculated amounts adds those back. A sheet with excluded duplicates subtracts them. If the check uses different rules from the cleaning, it proves nothing.

Existing subtotals against merged totals. If a source sheet came with its own monthly subtotals, compare each one with the merged total for the same region and month. When the owner's own arithmetic agrees with your merge, you know no rows went missing or got doubled in between.

Report total against merged detail total. Build the summary report entirely from formulas that point at the merged detail (SUMIFS by month and region, for example), so the two totals should be equal by construction. When they aren't, it is usually a month or region label written slightly differently and silently left out.

In the illustrative demo, that adds up to 12 checks: 4 row checks, 4 amount checks, 3 monthly subtotal checks for the North sheet and 1 grand-total check. All 12 show "Match".

Acceptance checklist (answer yes or no to each)

[ ] The column mapping covers every column of every source sheet; unused columns are marked "not used"
[ ] The report's columns, breakdown and total positions match the agreed fixed layout
[ ] Every date in the merged detail is a real date and falls inside the period
[ ] Every amount, quantity and unit price in the merged detail is a number, not text
[ ] Every merged row carries its source sheet and source row, and a few picked at random trace back correctly
[ ] Per sheet: raw data rows = merged rows + excluded rows in the exceptions table
[ ] Per sheet: source amount under the cleaning rules = merged amount
[ ] Each existing subtotal in a source sheet (if any) = the matching merged total
[ ] Report grand total = merged detail amount total
[ ] Every exceptions row states the issue, the handling and Yes/No for included
[ ] Every recalculated row is listed in the exceptions table with how it was calculated
[ ] Rows sharing an order ID with different content were not resolved by guessing and are listed for the owner

Hand the report over only when every line is yes.

Common pitfalls

Text amounts skipped without warning. SUM ignores text and doesn't complain. Add "every amount is a number" to the checklist, and calculate the per-sheet source amount from comma-stripped values.

Subtotal rows counted as orders. They look like data rows with a blank order ID. Pull them out before merging, log them as exceptions, and add "existing subtotal = merged total" to the checklist.

Deduplicating on order ID alone. A repeated ID can be a pasted copy or two genuinely different records. Remove only exact duplicates automatically; list the rest.

Dates landing in the wrong month. Day and month get swapped, and 3 July becomes 7 March. Check that every date is inside the period, and compare row counts per month with last period.

Hand-typed numbers in the report. Typed in under deadline pressure, they break the moment next period's data arrives. Keep every report cell a formula, and say so in the checklist.

Logging what was dropped but not what was recalculated. Recalculated rows feel finished because they're in the result. Log both kinds, with the Included column filled in every time.

Handing it off

If you pass this job to a colleague or to an AI, give them three things up front: the original source sheets, last period's accepted report, and your preference for rows that need confirmation. Ask for the mapping table, the exceptions table and the reconciliation page back, then go down the checklist.