Straight into the service manual page
WrenchQuarry
More

SDS request clocks: 15 days to notify, 25 working days

WrenchQuarry Editorial Team · Published · 10 min read · How these guides are written

California's rule sets two separate clocks for SDS requests

The first gives 15 days to notify the requestor, or to send the sheet, once the sheet has been received. The second gives 25 working days. If no response has come in by then, the escalation moves to the director.

The two clocks lead to different actions, so a desk that tracks only one of them can miss the other. This post covers the California text and the steps at the desk that takes the request, tracks the dates, and sends the reply.

The rule quoted here is California's, and it does not carry over to other places. Other states, federal agencies and other countries write their own definitions, and the same word can mean something different in each. Outside California, confirm which rule applies with the agency that enforces it or a qualified safety adviser.

The 15-day notice starts when the sheet arrives

Under California's rule, the 15-day clock in subsection (C) runs from the day the sheet arrives from the manufacturer, producer or seller. Within those 15 days, the requestor is to be notified that the sheet is available, or a copy of the sheet is to be provided. The quoted text puts both options in one sentence, so the reply can be either a notice or the sheet itself. The source section has the wording.

Notice the starting point. The clock is tied to the day the sheet arrives, not the day the request came in. A request can sit for days while the source sends its sheet, and the 15 days begin only when the sheet is in hand.

If the sheet has not arrived, there is no date to count from. The log should show the sheet as outstanding rather than start a count the rule does not support. The day the sheet comes in is the one date this clock depends on, so it is the first thing the log needs.

The 25-working-day clock ends with a copy to the director

Under California's rule, a copy of the written inquiry goes to the director if no response has come in within 25 working days. That is the whole escalation step: a copy of the written inquiry, sent to the director, when no response has arrived. The same section sets out the step in its own item (D).

The quoted text does not say when the 25 working days begin, and it does not define working days. This post cannot supply a start date for your desk. Choose one, apply it the same way to every request, and show it on the log so anyone can see how the count was run.

The rule also says "a response" without describing what that response must contain. So the log should show what was sent and when. The log should also record any response received and its date, since a record of what was sent does not show whether a response came in.

The two clocks side by side

The table sets the two clocks next to the separate duty that sits beside them.

ItemPeriodWhat the rule requires
Notice or copy to the requestor15 days from arrival of the sheetNotify the requestor that the sheet is available, or provide a copy
Escalation to the director25 working days without a responseSend the director a copy of the written inquiry
Preparer's copy to the directorNo period statedThe preparer provides the director with a copy of the SDS

The third row is a separate duty. The rule gives it no time limit, so it should not be folded into the other two when you plan the work.

When a sheet marks a sub-heading as empty

Under California's rule, if no relevant information is found for a sub-heading within a section of the sheet, the manufacturer, importer, or employer preparing the sheet marks that sub-heading to show that no information was found. The rule text is in Section 5194 of the California Code of Regulations.

The mark says only that no information was found for that sub-heading. Pass on exactly that, and do not add a meaning the mark does not carry. A reader who turns a blank mark into a conclusion is making a claim the source never made, and a crew may plan around that claim.

A sub-heading that is missing altogether is a different case. The rule addresses a marked sub-heading, not an absent one. If one is missing, log the gap and ask the source where the sheet came from. The rule does not say what to do in that situation, so the question to the source is the practical next step.

The preparer sends the director a copy of the SDS

Under California's rule, the preparer of a safety data sheet provides the director with a copy of that sheet. The Section 5194 page has the wording. This duty is separate from the requestor notice and the escalation step, and it sits with the preparer, not the desk.

If your business prepares its own sheets, the duty is yours to carry out. If it does not, the practical job at the desk is to know who prepares the sheet for each product, so questions and paperwork reach the right party from the start.

Labels on containers follow a separate rule

Sheets and container labels are different documents, and the desk often handles both. The CCOHS guidance on workplace labels, a Canadian resource, addresses label responsibility: "In most cases, suppliers are responsible for labelling the hazardous products they provide to customers." It adds that "Suppliers of hazardous products are required to apply a label that meets the requirements of the Hazardous Products Regulations." Those are Canadian requirements, so they do not govern a California desk, but they show where the labelling duty generally sits.

The same page says that "There are two situations when a workplace label is not necessary." Read that as a reason to look at the situation before assuming a label is either missing or required.

Match the product name before anything goes out

Compare the product name on the request with the name on the sheet before sending a reply. Requests often use a trade name, a short name, or a name copied from a container, and a sheet for a similar product can look close enough to send by mistake. Check the manufacturer name too.

If the names do not match, do not send the sheet. Note the mismatch on the log and send a short question back to the requestor with the name you found. That is quicker than a correction after the reply has gone out.

Reply in writing when the request came in writing

A written request deserves a written reply, so the answer matches what was asked. A phone call can confirm that a sheet is on its way, but the reply and its date still belong on the log.

If a reply is ever questioned, the message text or the attached file name is the fastest way to show what was said.

Send the notice or copy early

Send the notice or copy as soon as the sheet is in hand, not on the last day of the count. Waiting until the final day leaves no room for a missed email, a wrong address, or a sheet that needs a second look before it goes out.

Sending early costs little. A reply that goes out well inside the 15-day limit leaves the desk with nothing to explain later.

Keep a log line for each request

Use one line for each request, with four date fields: the day the request arrived, the day the sheet arrived from the source, the day the reply went out, and the 25-working-day start date. The rule sets no format for it, so the layout below is a desk habit.

Log fieldWhat it settles
Request receivedOpens the file; does not start the 15-day count
Sheet receivedStarts the 15-day count
Reply sentShows whether a response was sent
25-working-day start dateThe date chosen for the escalation count, written beside the line
OwnerWho to ask about the request

Keep the log in one place that more than one person can read, so a coworker can pick up a request without asking where it stands.

Working days and calendar days need separate counts

The two clocks use different units: the notice is counted in days and the escalation in working days. The rule defines neither term beyond those words, so the desk should not assume the two counts line up.

When a count crosses a weekend or a holiday, the line should show which days were counted, so anyone can follow the math.

One owner for each request

Assign one name to each request on the day it arrives, so the counts have a single keeper. A request with two owners can end up with none, because each person assumes the other has sent the reply. Put the owner's name beside the product name on the log, so anyone who opens the line knows whom to ask.

This is a desk habit rather than a rule in the Section 5194 text, and it changes none of the deadlines above.

Escalate a silent source on the dates you have

When a source has not sent a sheet, the dates show where things stand. Without the sheet in hand there is no date to count from, so the 15-day clock cannot start.

Each attempt to get the sheet, such as a call or an email, belongs on the log with its date. If no response has come within 25 working days, the escalation step applies, and the dated inquiry on the log shows exactly what was asked and when.

A weekly review shows which counts are running out

Once a week, list every request with no reply on the log and check each date against today. A request with only a few days left gets a call to the source the same day, not at the end of the week.

A short weekly review also gives the dispatcher a chance to move a stuck request to someone else before its date passes. Put the review date on the log so the next person can see when the list was last checked.

A backup should be able to read the log

If the owner is out, a request with no visible status can stall while the dates keep running. A backup who knows where to look can answer a status question without waiting for the owner to return.

Test the log once with someone who did not create it. If they can tell from the line alone whether the sheet has arrived and whether a reply has gone out, the log is doing its job.

Tell a requestor only what the log shows

Give a requestor the status the log supports and nothing more. Saying a sheet has been requested is different from saying it has been sent, and a requestor who hears the wrong one may plan around a document they do not yet have.

When the sheet has arrived but has not gone out, say so and give the date you expect to send it. When it has been sent, give the date it went. Avoid describing the contents of a sheet you have not read, because a guess about what a sheet says can become a problem for the crew that relies on it.

Store each sheet where the crew lead can find it

Keep one current copy of each sheet where the crew lead can open it without calling the office. A shared folder with files named by product name works, and so does a binder on the truck, as long as the two copies do not drift apart.

When a sheet is replaced, file the new one under the same product name and move the old one to a separate folder. That keeps last year's version from being opened by accident while the current one sits in the usual place.

Keep crews working while a reply is pending

Crews should not wait on a reply to learn what they are working with. While a sheet is outstanding, the dispatcher can give the crew the product name, the container, and any information already on hand, and say plainly that the sheet has been requested.

The CCOHS page gives one case: "For example, when the person who poured the product into another container will be the only person who will use it, and the product will be used during one shift, a full workplace label may not be required." A crew should not assume a container is unlabelled or fully labelled, so telling them what the container holds is the safer default.

Not legal or tax advice.

Related guides: Apply 8 safety checks before dispatching for hot work · Battery charging safety: 7 checks before you start · Bid withdrawal: 2 North Carolina deadlines.

Sources

More field guides